Gamer planner
A session with a date, a game, the people, and what you will play.
Gamer planner
Sample layout
| When | Game | Who | Scenario |
|---|---|---|---|
| Fri 8pm | Campaign | Four players | Chapter 3 |
| Sun 2pm | Co-op | Two players | Mission 5 |
Sample sessions. Times are examples.
What the planner decides
A gamer planner answers when the group plays and what is on the table. One row per session: date and time, game, players, and the scenario, mission, or chapter. A note for what happened last time belongs on the row after you play, so the next session does not start with a recap from memory.
Recurring groups can share one database and filter by campaign. A one-off night is still one row. If you are booking a larger room or a public event, the event planning fields (place, headcount, tasks) fit better than a session note.
Keep it out of the task list
A session is an appointment. Put it on the calendar, including the weekly planner if that is the calendar you look at. Do not also create a task called 'play on Friday'. The session row is the commitment.
Questions
- What should a session row include?
- Date and start time, game or campaign name, who is in, and the scenario you will run. Add a two-line recap after you finish.