You found a listing that looks right. The time slot fits. The pitch reads well. The GM sounds organized. You're about to send a reply, and you want to know whether this table will actually last past session three or whether you'll be back on r/lfg in a month.

This is the checklist. Seventeen questions, organized by what they actually filter for, written the way a player would ask them in a Discord DM after the GM messages back. None of these are stiff. None of them require you to disclose your character concept first. They're vetting questions for a vetting situation, and they work the same whether you're applying to a Tuesday-night ET table out of Austin, a Thursday BST table out of Manchester, or a Saturday CET table running out of Berlin.

The order matters. Schedule comes first because it eliminates the most candidates with the least information. System comes second because mismatched edition expectations kill more campaigns than playstyle conflicts. Content boundaries come third because the GM either uses safety tools or doesn't, and that single answer tells you more than any twenty-line "about the world" paragraph.

If you only have time for five questions, ask 1, 4, 6, 13, and 16. Those five carry most of the predictive weight.

Why You're Vetting the Table, Not Just Joining It

Most players approach LFG posts as if they're applying for a slot. The GM holds the seats, you audition, you hope to be picked. That framing is half right and half disastrous. The GM is choosing players, yes. You are also choosing a table. Treating the reply as a one-sided pitch is how players end up six weeks into a campaign with a homebrew rule set they hate, an attendance policy that doesn't exist, and a "weekly" schedule that produces three sessions a month.

A listing on r/lfg, r/UK_TTRPG, a Discord LFG channel, or a Quest Board listing on Guildhall is the GM's recruitment post. It's written to attract. Your reply is the start of a two-way conversation where you find out whether what attracted you was the actual table or the version of the table that lives in the GM's head before any players have shown up.

For the GM side of this dynamic, see How to Recruit D&D Players. Good GMs write listings that pre-answer most of what's below. The ones who don't are the ones you need to ask.

For where to look for listings in the first place, see How to Find a D&D Group Online. This piece picks up after you've found something that looks promising.

The 17 questions below map almost one-to-one onto the fields a Quest Board listing on Guildhall asks the GM to declare before the listing goes live. That's intentional. If the GM has already answered question 1, 4, 6, 9, 11, 13, 16, and 17 in the listing itself, you have fewer questions to ask and a clearer signal that this is a GM who has thought about what they're running. The rest of the time, you're doing the work the listing should have done.

Schedule Reality (3 Questions)

Most "weekly" online D&D campaigns are not weekly. Most "every other Wednesday at 7" tables miss every fourth Wednesday for the first three months until one player drops and a replacement search begins. The GM is rarely lying. They wrote the schedule they want. You need the schedule that exists.

1. "Honest take: how often does the table actually meet vs. how often it's scheduled?"

This is the single most useful question in the list. A GM with a real answer will tell you "we aim for weekly, we average three sessions a month, we usually miss one for someone's work travel." A GM with a vague answer will tell you "we play weekly" and nothing else. The vague answer is the answer. If the GM hasn't tracked the gap, the gap is large.

Ask it warmly. The point is not to interrogate. The point is to find out whether the GM has run enough tables to know that scheduled cadence and real cadence diverge, and whether they've built habits around the gap.

Guildhall captures this as The Timetable. A Quest Board listing declares both the target cadence and the realized cadence after the first six sessions, so a player doesn't have to ask: the listing already shows "weekly target, three of four last month."

2. "Cool, what's the cancellation norm if someone has to bail Tuesday afternoon?"

The day-of cancellation policy tells you almost everything about how the table holds together. There are two healthy answers and one unhealthy one. Healthy answer A: "We cancel the session, reschedule for the same week if we can, otherwise next slot." Healthy answer B: "We play if we have four of five, GM runs a side scene for the missing player when they return." Unhealthy answer: "We don't really have one, it depends."

The third answer means the table will collapse the first time two players cancel in the same week, because no one knows what's supposed to happen.

Guildhall captures this as a declared cancellation policy on the listing form. The three options above are the default choices; a GM picks one before publishing, and the player sees the choice on the Quest Board before applying.

3. "What's a normal session length, and what's the long-session ceiling?"

Stated length and real length diverge here too. A four-hour session that's "usually four to five" is actually a five-hour session. A four-hour session that's "sometimes runs to seven if combat gets weird" is a five-and-a-half-hour session for anyone with an early next-day commute, school run, or partner who'd prefer you came to bed. Find out the ceiling, not just the floor. The ceiling is what you have to plan your evening around.

Guildhall captures this as session length + variance on the listing form. A listing that says "4h target, 5h ceiling" carries different weight than "4h target, 7h ceiling." The Timetable surfaces the realized average after the first six sessions for the same reason.

System and Edition (2 Questions)

System matches matter less than you think. Edition expectations within a system matter more than you think. A 5e table running with three years of homebrew tacked on is a different game from a 5e table running rules as written, and players who don't surface that gap before character creation lose the first three sessions to rules arguments.

4. "Which edition specifically, and what's the homebrew load look like?"

For D&D this means 5e (2014 PHB), the 2024 revision, or a hybrid where the GM is using one and letting players pick from the other. For Pathfinder it means PF2e Remastered or pre-Remastered. For Call of Cthulhu it means 7th edition or earlier. For other systems it means the specific edition and any major variant rules. The follow-up matters more than the edition itself. "Homebrew load" is the right phrase. A GM running mostly RAW with one or two house rules is one kind of table. A GM with a 40-page custom document is a very different kind of table. Both can be excellent. They are not the same product, and your character concept may not survive translation.

Ask for a one-paragraph summary of the homebrew. If you get a link to a 40-page document and a "read it before session zero," that's actually a green flag. The GM has organized the variant rules and expects players to engage with them.

Guildhall captures this as edition + homebrew-weight on the listing form. "Homebrew load: light / moderate / heavy / homebrew system" is one of the declared fields, with a free-text field for the GM's one-paragraph summary and an optional document link. The GM who picks "heavy" and links the document is exactly the GM you want to find before character creation.

5. "Are you using any optional rules from the DMG or GM's Guide that I should know about?"

This is the question that catches the second wave of mismatches. A GM who uses flanking, milestone leveling, and a custom inspiration economy is running a meaningfully different combat experience from a GM who uses none of those. If you've never played with flanking, this is the moment to find out you'll be playing with flanking. Variant rules are small individually and compound quickly.

In an organized-play context (Adventurers League in the US, AL chapters in the UK, EU, and Australia, or Pathfinder Society chapters worldwide) variant rules are constrained by the campaign documents and you can read them in advance. Outside organized play, it's a conversation.

Guildhall surfaces a "common variant rules" checklist on the listing form: flanking, milestone vs XP, lingering injuries, custom inspiration economy, gritty rest. The GM ticks the ones in play before publishing. It doesn't capture every house rule (no field could), but it captures the four or five that meaningfully change the combat shape.

Content Boundaries (3 Questions)

Content boundaries (not "content restrictions" or "filters") are the most under-discussed part of joining a new table, and the part that does the most damage when it goes unaddressed. The GM has a sense of what they will and won't put on screen. The other players have ranges that may or may not overlap with the GM's. You have your own. You need to find out where the table sits before the first session, not during a scene that's already in motion.

6. "What's the safety toolkit you use, if any?"

The phrasing matters. "Safety toolkit" is precise. It refers to the tools (Lines and Veils, X-card, Script Change, Stars and Wishes) the GM uses to handle content that needs to come off the table. The GM either uses some of these or doesn't. Either answer is informative. A GM who says "we use Lines and Veils plus an X-card during session zero, X-card available mid-session by Discord DM" has thought about this. A GM who says "we just trust each other to speak up" is running a different kind of table, and you should know which one before session one.

Both can work. The mismatch is the problem, not the choice.

Guildhall captures this as the 22-boundary five-tier ladder on every listing. The GM declares each of 22 content categories as hard no, prefer not, fine, on theme, or prefer, and players see the declared ladder before they apply. It replaces the open-ended "we use X-card" conversation with a structural read that doesn't require a DM exchange.

7. "What's already off the table going in, before session zero?"

Some content is GM-decided regardless of player input. Sexual violence on-page, harm to children depicted, real-world political content. Most GMs have a small list of things they personally won't run. Ask for it. The list itself is useful, and a GM who has one is a GM who has thought about why they have one.

If the answer is "nothing's off the table, we'll work it out in session zero," that's a yellow flag, not a red one. It usually means the GM is open and hasn't pre-decided. It also means session zero has more work to do, and the table is more likely to hit a content mismatch in session four when it surfaces unprompted.

Guildhall captures this as the GM-locked tier of the same 22-boundary ladder. Anything the GM marks "hard no" on the listing is off the table before session zero begins, declared upfront, and players who can't live with that filter themselves out before applying.

8. "How does the table handle it if someone hits a hard no mid-session?"

The mechanism matters more than the principle. Anyone can say "we'd respect it." The question is what physically happens at the table when a player flags a hard no. Does the scene pause? Does the GM fade to black and check in by DM? Does the X-card live in the Discord chat where any player can drop it? "We'd respect it" is not a mechanism. The mechanism is what holds the table together when the moment comes.

Tools like the Lines and Veils protocol and Script Change exist precisely so the table has a vocabulary for the moment when it matters. Ask which one, and ask what happens in the next ten minutes after it's invoked.

Guildhall's listing form asks the GM to declare their mid-session protocol from a short list (pause and check in, fade to black + DM, X-card in chat, Script Change beats), so a player sees the GM's declared mechanism before applying. The mechanism stays GM-owned. The listing makes it visible.

Playstyle (3 Questions)

Playstyle mismatches are the slowest-killing campaign breakers. They don't show up in session one. They show up in session eight when the heavy-RP player realizes the table treats combat as the main event and the heavy-combat player realizes nobody else is excited about the dungeon. Both players were misled by the same listing, in opposite directions.

9. "What's the rough mix of combat, role-play, and exploration at this table?"

Ask for percentages or fractions. "About 40% combat, 40% role-play, 20% exploration and downtime" is a usable answer. "A good mix" is not. The GM may not be able to give you a clean breakdown until they think about it, and that's fine. Their attempt to answer is the data.

Match this against your own preferences. If you're a heavy-RP player and the table is 60% combat by minutes-at-the-table, you'll spend most sessions rolling initiative for fights that don't move your character forward. If you're a combat-focused player and the table runs three-hour shopping scenes, you'll spend most sessions waiting.

Guildhall captures this as playstyle-mix sliders on the listing form: combat, role-play, exploration, and downtime as percentages declared by the GM before the listing publishes. The compatibility score weighs these sliders against the player's stated preference; mismatches are a structural signal before anyone messages anyone.

10. "Theater of mind or grid? And if grid, what's the VTT?"

This is partially logistics, but it's mostly playstyle. Theater-of-mind combat moves faster, abstracts positioning, and rewards descriptive play. Grid combat slows down, formalizes positioning, and rewards tactical play. Neither is wrong. They produce different experiences from the same rules.

The grid-VTT landscape today is roughly: Roll20 and Foundry as the two heavyweights, Owlbear Rodeo for lighter sessions, TaleSpire for 3D grid play, Above VTT as the in-browser overlay for the official D&D Beyond character sheets. All of them work cross-country. None of them require you to be in the same time zone as the rest of the table.

If you've only played one, joining a table that uses another is a transition, not a continuation. Find out which one before character creation, because a bladesinger built for grid play moves differently than one built for theater of mind.

Guildhall captures this as VTT + combat-mode on the listing form. The GM declares the platform, the player sees it before applying, and the mismatch between "I have Foundry" and "the table runs Roll20" surfaces in the listing rather than after onboarding.

11. "Where does the table sit on character optimization? Casual builds welcome, or are most players hitting common multiclass dips?"

Optimization tolerance is a spectrum, not a binary. The relevant question is whether your build will feel underpowered or out-of-place. A table where three players are running optimized builds and you bring a single-class Champion fighter for the flavor will feel like you're contributing less in combat than you actually are. A table where everyone is running flavor-first builds and you bring a Hexadin will feel like you're solving every encounter alone.

Neither is bad. The mismatch is bad. The GM usually knows where the table sits, and a one-line answer ("most players are optimization-curious but not minmaxing, two multiclass dips is normal, full coffeelock would be weird") is more useful than ten paragraphs of "anything's fine."

Guildhall captures this as an optimization-tolerance slider on the listing form. Five points from "flavor-first, no multiclass dips" to "optimization is expected." Declared before the listing publishes, weighted in the compatibility score, visible to the player before applying.

Group Composition (2 Questions)

The people you'll be playing with matter as much as the GM. The other players' shared history is the table's actual culture. You're not just joining a campaign. You're joining whatever the existing players have built together. Guildhall is building toward a future where The Ledger captures table tenure and recent turnover structurally, so a listing surfaces "running 14 months, two seats turned over" without anyone having to ask. Today, you ask.

12. "How were the other players found, and how long have they been playing together?"

A table assembled entirely fresh from r/lfg has a different chemistry than a table that's been running for two years and is replacing one seat. The fresh table has zero shared history, more flex on culture, and higher session-three collapse risk. The mature table has established norms (good and bad) and lower flex. You should know which one you're walking into.

Ask the follow-up: "Any seats turned over recently? Why did the previous player leave?" The previous player's exit reason is often the most predictive single fact about what's actually difficult about this table. If three players have left in six months and the reasons rhyme, you're about to learn why.

13. "What's your prior table history as a GM? How many campaigns, how many have made it past level 5?"

A GM running their first online campaign and a GM running their twelfth are different products. Both can be excellent. The first-time GM may bring more energy, more preparation per session, and more openness to player input. The veteran may bring better pacing, clearer rulings, and less new-GM volatility. Either is fine to join. The mismatch is between the GM the listing implies and the GM you're actually getting.

If the GM has run organized play (Adventurers League chapters in the US, UK, EU, or Australia, or Pathfinder Society chapters worldwide), that's a different signal than home-brew-only history. Organized play GMs have run for strangers many times. They've built habits around recruitment and turnover.

Past level 5 matters specifically. Most D&D campaigns die between levels 3 and 5. A GM who has run multiple campaigns past that point has solved the problem most GMs don't solve. That's worth knowing.

Guildhall captures this as The Ledger: GM-side reputation tracking campaigns started, campaigns completed, max level reached, and organized-play history. Pre-launch, this is on the roadmap; the listing schema captures it as soon as The Ledger goes live, and Founding GMs carry the badge into the reputation surface from day one.

Logistics (2 Questions)

Logistics questions are unglamorous and load-bearing. The setup the table uses is the setup you'll use. If it's incompatible with what you've got, you'll know in week one.

14. "What's the VTT and voice setup? Anything I'll need to install or pay for?"

Foundry tables ask players to install the client and may ask for a small one-time license fee. Roll20 is browser-based and free at the basic tier. Owlbear Rodeo is light-weight and free. TaleSpire is paid and asks players to own a copy. Theater of mind in Discord doesn't need a VTT at all. Voice is usually Discord, occasionally a table uses something else. None of this is hard, all of it is good to know before session zero so you're not troubleshooting a VTT install during the first hour of the first session.

Guildhall captures this as VTT + voice tool + cost-to-player on the listing form. A listing that declares "Foundry, players need to install, no license fee, GM hosts" is doing the player a courtesy. So is one that declares "TaleSpire, players need to own a copy."

15. "Physical dice or digital? Any expectations on cameras?"

Dice expectations vary. Some tables use the VTT's roller. Some require physical dice rolled on camera. Some don't care. Cameras-on is becoming more common as a presence norm. Cameras-off is still standard at plenty of tables. Ask. If you're not comfortable being on camera for four hours, find out before session one whether that's negotiable.

Guildhall captures cameras-expected as a yes/no/optional field on the listing form and dice as a separate field (VTT roller / physical on camera / either). Small fields. They prevent a session-one surprise.

Commitment Level (2 Questions)

These two questions are about what happens when reality intrudes on the campaign. They're often skipped, and they're often the questions that would have prevented the most damage if asked.

16. "Is this a campaign with an intended length, an open-ended sandbox, or a series of mini-arcs?"

A campaign with an intended length (a published adventure, a homebrew arc with a planned ending) has a different commitment shape than an open-ended sandbox. The published-adventure table can tell you "we're running an Eberron arc, probably 30 to 40 sessions, aiming to finish by spring." The sandbox table tells you "as long as people are having fun." The mini-arc table tells you "we run six-session arcs and decide at the end whether to continue." All three are valid. They demand different things from you.

If your life shape allows for a contained six-month commitment but not an indefinite one, the sandbox table will frustrate you and you'll frustrate them. The reverse is also true.

Guildhall captures this as campaign-shape on the listing form: closed-arc with estimated session count, open-ended sandbox, or mini-arcs. The estimated end date is a declared field, so a player can compare against their own commitment window before applying.

17. "If a player drops at level 6, what's your usual move? Recruit a replacement, run with four, write them out?"

This is the attendance policy question for the worst case. The GM has done this before or hasn't. If they have, they have a default move. If they haven't, you're about to find out what happens to a campaign mid-collapse with no contingency. Recruitment mid-campaign is a different problem than initial recruitment, and a GM who has solved it once will solve it again. A GM who hasn't will pause the campaign for six weeks while they try.

Pair this with question 12. If the table has had recent turnover, the GM has either solved this problem or watched the campaign collapse around it.

Guildhall captures this as a declared drop-and-replace policy on the listing form. "Recruit replacement, NPC the seat for two sessions, write the character out" are the three default choices. The GM picks one before publishing, the player sees the choice on the Quest Board.

What to Do With the Answers

You won't get clean answers to all 17. That's fine. A GM who answers 12 of them well and admits "haven't thought about that" on three is a better bet than a GM who has a polished answer for everything. Polished-answer-for-everything is a sales mode, and you're not buying a product.

Sort the answers into three piles:

• Green: specific, operational, drawn from experience.
• Yellow: general or aspirational but coherent.
• Red: vague, defensive, or contradictory.

Three or more reds and you're looking at a table that's likely to collapse by session three. Mostly yellows with a few greens, and you're looking at a normal first-online-campaign GM doing their best. Mostly greens, and you've found a good table.

The biggest red flag isn't any single answer. It's a GM who treats the questions themselves as a problem. A GM running a table they're proud of welcomes a player who vets it. A GM running a table they're hoping will work resists being vetted. You're going to spend forty hours of your life in this game over the next six months. The two minutes it takes the GM to react to question 1 will tell you which kind of table you found.

Why Guildhall is building this triage into the listing itself

The honest read on the 17 questions above is that most of them describe things a good listing should already declare. Cadence target vs. realized cadence. Cancellation policy as a picked option, not a vibe. Session length plus variance ceiling. Edition plus homebrew weight. The 22-boundary content ladder before session zero, declared by the GM and visible to the player before the application. Playstyle mix as a slider. VTT and voice setup as a field. Campaign shape with an estimated end. Drop-and-replace policy as a declared default.

That's the bet Guildhall is built around. A Quest Board listing is the GM filling in those fields before publishing. The Timetable shows the realized cadence after the first six sessions, not just the target. The 22-boundary five-tier content ladder on every Quest Board listing replaces the open-ended "we use X-card" conversation with a structural read. The compatibility score weighs the player's stated preferences against the listing's declared values and surfaces mismatches before either side spends a DM exchange finding them. The Ledger, once live, carries GM and player reputation across campaigns so the questions about prior history answer themselves.

That doesn't replace the 17 questions for tables you find on r/lfg, Discord LFG channels, r/UK_TTRPG, or a hobby-shop notice board. Those listings still ask you to do the vetting work yourself. The questions above are what you ask when the listing leaves the work to the player. When you find a Guildhall listing instead, the green/yellow/red triage is already there, declared structurally, before anyone messages anyone.

For more on what session zero should cover once you've joined, see The Session Zero Template That Prevents Table Collapse. For where to look for listings worth applying to, see How to Find a D&D Group Online. For the view from the other side of the listing, see How to Recruit D&D Players.

The right table starts at the Guildhall, but until the platform is live for your region, it starts with seventeen good questions.