Most D&D recruitment posts fail before anyone reads them. The GM treats the listing as a sales pitch, writes a paragraph of vibes about the world, lists a Tuesday night slot, and then wonders why the players who show up vanish by session three. The listing is the front door of your campaign. If it filters for fit, your table holds. If it pitches for volume, you spend six weeks recruiting the same seat every month.

This guide is for organizers running tables online, recruiting through r/lfg, an LFG Discord, a hobby-shop board, or a tool like Guildhall's Quest Board. We will cover what a recruitment post is actually doing, the structure of a Listing that survives session three, the questions you should put in the post rather than save for session zero, and the section that most GMs skip entirely.

Why most D&D listings fail before session one

The reason recruiting feels broken is that the dominant template was written for awareness, not fit. Open r/lfg on any given afternoon and you will see fifty posts with the same shape: a system, a vibe, a day of the week, an invitation to DM. They read like trailers. They get applications from everyone whose Tuesday is free, which is exactly the wrong filter.

Tables collapse around four mismatches, and you can predict every one of them from what the recruitment post left out.

Schedule mismatch. Two applicants thought "weekly" meant every Tuesday. The other two thought it meant most Tuesdays. The post said weekly and nothing else.

System and tone mismatch. The GM is running a low-magic homebrew where a healing potion is a quest reward. Three of the applicants are excited to fly griffons by level five. The post said "5e" and gave a one-line setting pitch.

Content boundary mismatch. Topics that are a hard no for one player are taken for granted by another. No one mentioned them in the listing. Session zero was rushed. By session three someone has been ambushed by content they did not consent to.

Reliability mismatch. Some applicants treat a campaign as a recurring appointment. Others treat it as a "maybe if nothing else comes up." The post never asked, so it never filtered.

Every one of these is a listing problem first. Session zero is where these surface late, after you have invested an hour onboarding people who were never going to fit.

What a good D&D recruitment post actually does

Reframe the job. A Listing is not where you persuade people that your table sounds fun. It is where you tell them enough about your table that the wrong people self-select out before they apply. You want fewer applications, not more. You want applications that are already aligned on schedule, system, tone, and content boundaries.

A useful comparison.

The filter version takes longer to write. It takes less time to recruit against. The math is in your favor every time.

The structure of a recruitment post that holds up

There is a shape to listings that survive session three. It is not creative. It is sequential, it is honest, and it is built around the information an applicant needs to know whether to apply. Use it whether you are posting on Reddit, a Discord recruitment channel, or a Listing on Guildhall's Quest Board.

1. The one-line pitch

One sentence. System, setting flavor, length. "A six-month 5e campaign in a low-magic frontier setting, levels 1 to 8." If you cannot say it in one sentence, you do not know what you are running yet and the post is premature.

2. The schedule, exact

The single highest-yield filter. State the recurring day and time, the time zone, the session length, and what your version of "weekly" actually is. A real example: "Every Tuesday, 7 to 10pm ET, weekly. We skip the week of US Thanksgiving and the last week of December. If two or more players cannot make a session we reschedule to Thursday of the same week." That paragraph alone removes half the applicants who would have ghosted you by session three.

3. The setting and tone, with the dial labeled

Two short paragraphs. What the world is, what the table sounds like at its best, what the campaign is not. The "is not" sentence matters more than the "is" sentence. "This is not a grimdark campaign and it is not a pure dungeon crawl. Expect investigation, downtime, faction play, and combat that gets dangerous fast at low levels." An applicant who wants a hack-and-slash one-shot reads that and moves on. That is the listing doing its job.

4. Content boundaries, up front

Most GMs save this for session zero. That is too late. By session zero you have already invested in the wrong applicants. Put your content boundaries in the listing.

Use the preference ladder: hard no, prefer not, fine, on theme, prefer. List five to ten topics that matter for your campaign. You do not need to enumerate every possible subject. You need to name the ones your specific campaign is built around or built away from.

Example, drawn from a real low-magic frontier listing.

• On theme: debt, isolation, the slow grind of a town surviving winter, moral ambiguity in faction conflict.
• Fine: combat lethality, character death (with a path back into the campaign), grief, drinking.
• Prefer not: graphic torture as set dressing, harm to children as a plot device.
• Hard no: sexual violence, real-world political analogues used to score points.

That section costs you ten minutes to write and saves you the conversation that would otherwise have happened at session three after someone wrote a backstory that depended on a topic the rest of the table will not table.

5. The application question set

Three questions, no more. You are looking for signal, not for an essay.

A working set:

1. What is your current weekly availability look like through the end of the year, and are there any blocks of weeks you already know you will miss?
2. Describe a character you have played recently that you really enjoyed, in three sentences or fewer.
3. Looking at the content boundaries above, is there anything you would move up or down the ladder, and why?

Question one filters reliability. Question two filters tone fit faster than any setting paragraph. Question three is the most underrated. It surfaces the applicants who actually read the boundaries section and have something to say about it, which is the population you want.

6. The path off the table

The last paragraph. State, in writing, how you handle a player leaving the campaign. It does not need to be long. "If a campaign is not working for you, the expectation is that you tell me before the next session and we either work something out or part ways. Players who leave on good terms are welcome back to one-shots and future campaigns." Including this in the listing tells applicants you have run a table before, that you understand campaigns end, and that you are not the kind of organizer who treats a player leaving as a betrayal. The applicants who match that vibe are the ones you want.

How this maps onto the Quest Board on Guildhall

Guildhall's Quest Board takes the structure above and bakes it into the Listing flow itself, so an organizer does not have to remember to include each section. This is the part of the post where the tutorial gets concrete. The product is in Foundation Release; the description below is functional rather than a screenshot walkthrough.

When you create a Listing on Guildhall, the flow walks an organizer through fields that map to the structure in the previous section. System, setting summary, schedule (with explicit recurrence and time zone), session length, and capacity are required up front. Tone and table-level expectations have their own field rather than living inside a free-text pitch.

The content boundaries layer is where Guildhall does something that a Reddit post cannot. The Listing presents the full content topic set and asks the organizer to set each one on the preference ladder: hard no, prefer not, fine, on theme, prefer. Players applying to that Listing have already set their own ladder on their player profile. The Compatibility score on the application surfaces alignment and mismatch before the organizer reads a single paragraph of pitch. A hard no on the organizer side that an applicant has marked prefer is a blocking incompatibility and the application does not arrive in the first place. The filter is enforced by the platform, not left to memory at session zero.

The application question set is configurable per Listing. Three questions by default, with the option to write your own. The organizer sees applications ranked by Compatibility score, with the applicant's answers to the question set inline.

Two notes on how to use the Listing flow well.

First, do not undersell the schedule field. The platform stores the recurrence rule, but the description field still matters. Write the "what weekly actually means at this table" sentence there. The flow will not write it for you.

Second, treat the content boundary ladder as a contract you are choosing in advance, not as a wishlist. If you mark something prefer not and an applicant marks it prefer, that is not a failure of compatibility. It is the system telling you that this applicant's campaign is not your campaign. Move on without spending the cycle.

For organizers coming to Guildhall from r/lfg, the mental shift is that the Listing is doing the filter work you were previously doing by hand at session zero. The recruiting side of running a table gets shorter. The session zero conversation gets to be about the campaign, not about catching mismatches that should have been caught before anyone opened a character sheet.

What to do after the listing goes up

A few practical things.

Read every application end to end, even if the Compatibility score is low. Low-score applications occasionally surface a writer who would be a great fit in a different campaign you might run later. Note them.

Respond to every applicant, including the ones you are not taking. A one-paragraph "the table is full, thanks for applying, I will keep you in mind for the next campaign" is the bar. The TTRPG community is small. Organizers who ghost applicants get a reputation that shows up in future recruiting.

Hold a session zero anyway. The listing did the filter work. Session zero does the alignment work: characters, party connections, table expectations on dice, attendance norms, the path off the table reiterated face to face. For a copy-paste agenda and question set, see the Session Zero template on Campfire.

The honest version

A good D&D recruitment post reads like an honest job description for a campaign. It tells an applicant what the work is, when it happens, what the tone is, what is on the table, what is off the table, and how you handle it when the fit is wrong. It does not promise epic. It does not promise found family. It does not promise the most legendary campaign of all time. It promises a specific table run by a specific organizer on a specific schedule, with specific content boundaries, and an honest off-ramp.

The applicants you want are the ones who read that and recognize the table they have been looking for. The applicants you do not want are the ones who read it and move on. Both of those outcomes are the listing succeeding.

If you are reading this guide as a player and trying to figure out which listings to apply to, the player-side companion is here: How to find a D&D group online. The honest version applies to both sides of the table.

The right table starts at the listing.