D&D Session Scheduling: Find a Date Your Group Can Keep
Use a D&D session scheduling poll to collect player availability, set a quorum and confirm your next game without a long chat thread.

In a made-up example, Friday's D&D group has five players, one Dungeon Master and three competing work rotas. A chat thread produces six date suggestions, but nobody confirms one. The session slips another week.
Good D&D session scheduling gives everyone the same choices, asks for a clear answer and sets a rule for how many people must attend. That is enough to replace most of the follow-up messages. It also gives a Dungeon Master a date they can put in the calendar and prepare around.
I use a date poll when the group cannot keep a regular night. The important part is not the poll itself. It is the decision around it: which dates count, how long people have to reply and what happens if one player cannot attend. Set those rules before you send the link.
CharGen's Table is a beta tool for scheduling the next session inside Campaign Studio. It gives the group one link, a short list of dates and three answers: Yes, If need be and No. The steps below also work with a shared calendar or another D&D session scheduler.
Why D&D session scheduling breaks down in chat
Chat is good for quick questions. It is poor at collecting availability from six people across a week. One player replies to the first suggestion. Another reads the thread later and misses the second. Someone writes “maybe next Friday”, but the group does not know whether that means a firm yes or a fallback.
The problem grows when dates receive replies at different times. A simple “who can do Thursday?” can produce separate threads, partial answers and a date that looks popular before everyone has replied. The DM then has to copy the replies into a note and ask the group to confirm again.
A poll gives each player the same choices and stores one answer per date. That makes the result easier to read. It also makes an unanswered poll visible. Silence is not the same as a No. The DM can send one reminder to the players who have not answered instead of restarting the whole discussion.
This is a common pain point in tabletop groups. A recent r/DnD discussion about session scheduling raised the familiar problem of late replies and the need to set a minimum attendance rule. A poll cannot make people answer. It can show who has replied and give the group a clear deadline.
Choose a regular night or poll each session
Ask the group whether it wants a fixed rhythm before you compare dates. A monthly game on the first Saturday needs a different process from a weekly game with changing shifts. A regular night is easier to remember. A date poll gives more choice when work, caring duties or travel make routines difficult.
For a stable group, agree on a default night and use a poll only when the usual time fails. For a group with rotating shifts, set the next date after every session. Do not make players repeat the same availability discussion if their calendars follow a pattern. Record useful preferences, such as “usually free on Tuesday after 19:00”.
The next-session poll is not a recurring event planner. It answers one question: which of these dates works for the next game? If you need to arrange a whole season, first ask players for their regular limits. Then schedule a short run of sessions and review it when the campaign reaches a natural pause.
You can also reduce the number of dates before the poll. Ask each player privately for days they cannot play, or choose dates that fall after pay day, school holidays or a work rota change. Keep the group poll for the dates that remain. That gives players a real choice without asking them to mark every day in a month.
Set the rules before you send a D&D scheduling poll
Decide what counts as attendance before you look at the results. Some groups want every player at the table for a major story session. Others can play with one seat empty. A clear quorum prevents the DM from changing the rule after seeing which date is most popular.
Quorum is the minimum number of campaign seats that can attend before a date meets your rule. For example, a group with five player seats might agree to play with four. In a date poll, Yes means the player can attend. If need be means they can probably attend if the group chooses that date. No means they cannot make it. Yes and If need be can count towards the minimum, but the DM should still read each answer before setting the night.
Decide what to do with a tie too. You could choose the earlier date, choose the night with more firm Yes answers or ask tied players to decide. Pick a rule the group accepts before the poll closes. This keeps a close result from turning into a second debate.
Set an answer deadline. A poll without a deadline can stay open long after the DM needs to book a room, arrange a lift or prepare the next session. A useful deadline gives players time to check their calendars and gives the DM time to act. Two or three days is often enough for a small group, but use a longer window if players work shifts.

Offer a short list of real dates
Offer dates that you can actually run. Do not add a night because it might collect a useful vote if you already know you are unavailable. Two strong options are more useful than six guesses. A short list also makes it easier for players to check each date carefully.
CharGen's Table lets the DM offer two to six dates on a month grid. In Campaign Studio, open the Table part and choose Offer dates for session N. If the link is off, choose Start, then Copy link. Set one start time for all dates, choose the quorum and set an answer-by time. Players open the campaign link, select their seat and mark Yes, If need be or No for each date. They do not need a CharGen account to answer.
There is one useful limit to know before you start: the poll uses the same start time for every date. You cannot compare Friday at 18:00 with Saturday at 20:00 in one poll. If the group is flexible about start times, agree on a shared time first. If time itself is in question, run a separate poll or ask the group to agree on a time before you offer dates.
I would keep the date range close enough for people to check their current calendars. For example, a group planning a November game could compare the 13th, 20th and 27th at the usual start time. A poll covering six months asks players to predict too far ahead. It can also favour the dates that feel easiest now, not the dates that remain practical later.
Avoid dates that carry a hidden cost for one player. A public holiday may suit some people and create family plans for others. A late Sunday start might look free on a calendar but leave a player with an early work shift. Add a note when a date has a special detail, such as a shorter session or a different venue.

Write an invite players can answer quickly
Tell players what the poll is for, when it closes and what each answer means. Keep the message short enough to read on a phone. Add the campaign name if the group plays more than one game. State the time zone when players live in different regions.
Here is a made-up example for a group of five players. The DM can run the game with four seats. The group has agreed to meet at 19:30 London time. These sample details show the shape of a clear invitation; they are not a record from a real campaign.
Next session: please mark every date you can make by Wednesday at 20:00. We can play with four of five players. Choose Yes if you can attend, If need be if you can attend as a fallback, and No if you cannot. All dates start at 19:30 London time. I will set the best date on Thursday.
The invite answers four questions before players reply: which session, the deadline, the minimum attendance and what each choice means. It also states when the DM will decide.
If the group uses an existing chat, post the poll link there and pin the message until the deadline. Avoid sending one invitation to each player if the poll already shows who has answered. One shared link makes the process easier to find and reduces duplicate messages.
For a private spreadsheet or calendar poll, use the same wording. Ask players to mark each option, not just their favourite date. A player may be available for three nights and should be able to say so. If the tool does not show unanswered players, add a reply deadline and send a short reminder before it passes.
Read the answers and choose a date
Do not set the first date that receives a few replies. Wait until the answer-by time, or until everyone has answered. Then compare each date against the quorum. CharGen's Table ranks dates by the number of seats that can attend. It breaks ties by firm Yes answers, fewer No answers and earlier start times. A date that reaches quorum is a workable option, not a command to the DM.
Look at the actual answers as well as the total. Four “Yes” answers may be stronger than three “Yes” answers and two “If need be” answers, even when both dates meet the same threshold. A fallback answer tells you the player can attend if needed. It may not mean they prefer the date.
Check the missing answers before deciding. Someone who has not replied may have missed the link. Send one reminder while the poll is open. Do not treat a missing answer as a No, and do not assume it is a Yes. If the player cannot answer by the deadline, decide whether the group can proceed without them.
When two dates tie, apply the rule you agreed on. If the table has not chosen one, ask a single focused question: “Both dates meet quorum. Do you prefer the 13th or 20th?” Avoid reopening the full month. A poll should narrow the choice, not create a new round of open-ended planning.
The Table asks the DM to confirm a date. If that date has fewer people than the quorum, it warns the DM and asks whether to set it anyway. That is a useful last check. A majority vote should not override the attendance rule by accident. If you choose to play below quorum, tell the group why and agree on any story changes before the session.
Confirm the session and close the loop
Once you choose a date, post the decision where the original poll lives. Include the date, start time, time zone, expected end time and any preparation the players need. If you use a venue, include the address or meeting link. A short confirmation prevents players from searching through a long thread for the final answer.
Add a calendar event after the date is set. Include the confirmed time, session title and location. Google Calendar supports inviting guests by email and tracking their replies. The group's calendar can then carry the reminder, while the poll remains the record of how the date was chosen. CharGen's Table can also give players a calendar ticket for Google, Apple, Outlook, an .ics file or a calendar feed.

The Google Calendar invitation guide explains how to add guests to an event. If players use different calendar apps, share a standard .ics file or a calendar link that they can open in their own app. Ask them to check the time zone before they accept.
Then close the poll. Do not leave the group wondering whether the date is final. If something changes, post the new decision in the same place and contact any player who has not seen the update. A short note is enough: “We are set for Friday 20 November at 19:30. I moved the calendar invite.”
The date sets the time you have to prepare. A week leaves room to revisit clues and maps. Two days may call for a shorter plan. I use a D&D session planning tool to make a prep list. I use campaign management tools to keep notes and records together.
What to do when no date works
If no date reaches quorum, do not keep the same poll open for another week without changing anything. Ask why the options failed. The group may need later dates, a different weekday or a temporary change in start time. Make one change and offer a fresh set of dates.
If the blocker is the hour, agree on a different time before starting another poll. CharGen's Table uses one start time across the date poll. It cannot compare several time slots. If players cannot agree on a time, compare times in a separate tool first. Then offer dates in Table at the agreed time.
If one player is unavailable for a long stretch, ask the group how the campaign should handle that absence. You might pause the main story, run a short side session or continue with that character off screen. The answer belongs to the group. A scheduling tool should show the available options, not decide what the story does with an absent player.
For a very small group, quorum can be strict. If two players and the DM are the whole table, a date with one player missing may not feel like the same game. For a larger group, one absent seat may be easy to handle. Set the rule according to the way your group plays, then keep it stable from poll to poll.
If the date works but the venue does not, treat that as a separate question. Confirm whether the group can play online or move the game to a different home. Do not make players repeat the availability poll when only the location has changed. Clear questions reduce the work each person must do.
Use a repeatable D&D session scheduling routine
The simplest routine is short. After the session, choose two to six dates that work for the DM. Set one start time, choose the minimum attendance rule and add a reply deadline. Share one poll link. Remind only the people who have not answered. Then set a date and send the calendar event.
You do not need a complicated rota for every campaign. A stable weekly group may only need a quick confirmation when the usual night changes. A group with rotating shifts may need a poll after every session. Use the amount of structure your players need, and remove steps that do not solve a real problem.
If you already keep campaign notes in CharGen, the Campaign Studio page shows how its workbench holds sessions, notes and the Table together. You can also use RPG Session Notes to capture what happened and decide what needs attention before the next date. The poll sets the night. The notes give the group a place to continue.
For most groups, one deadline and one clear quorum will do more than another round of chat. Pick dates you can run, explain the choices and confirm the result in the same place. The next session then has a date everyone can check.
Set dates in Campaign Studio