Host Toolkit • Clear listings, factual recaps, moderated workflow

Publishable meetup notes—without the guesswork.

We publish adult-friendly tabletop club listings and league recaps for ages 40–60. This toolkit helps hosts submit consistent details, avoid speculation, and understand how our verification and moderation process works.

What we publish
Meetup listings, verified schedule updates, and factual league recaps with host + format highlights.
Moderation expectations
No rumors, no personal data, no accusations. Keep it date-stamped and attributable.
How verification works
We confirm key facts (time/place/format) and may request a source before publishing.

Moderated workflow (quick view)

  1. 1Submit details using the correct form.
  2. 2Editor checks completeness + tone.
  3. 3Verification (when needed) via follow-up.
  4. 4Publish with a clear timestamp and credits.
Illustration of a tabletop game host toolkit: calendar, checklist, and dice

Include these basics

  • • Date/time + timezone
  • • Venue + accessibility notes
  • • Format (casual/league/campaign)

For recaps, add

  • • Attendance range
  • • Games played + highlights
  • • Standings (if league)

Tip: If you’re unsure about wording, follow the format guidelines to reduce back-and-forth.

Format labels (use one)

Pick the label that best matches how the table runs. Clear format = fewer surprises for new members and cleaner moderation.

Game Night

casual / planned games

A scheduled lineup (or a short list) with a clear start time. Great for newcomers who want structure.

Newcomers should expect

  • Host introduces the plan and seats tables within 10–15 minutes.
  • Teach or rules refresh is included.
  • Games finish by (or near) the posted end time.

Host must include

  • Primary game(s) + player counts
  • Teach level: beginner-friendly / experienced
  • Start time, late-arrival policy, and end-time target

Listing example: “Tue 7pm — Teach & play Ticket to Ride (4–5p), backup: Azul (4p)”

Open Play

drop-in / choose-a-game

A drop-in window where attendees self-organize tables. Best for regulars; still workable for new folks when the process is explicit.

Newcomers should expect

  • Arrive, check in, and join a forming table.
  • Game choice happens on-site (bring suggestions).
  • Teach depends on who’s at the table.

Host must include

  • How seating works (sign-up sheet? shout-outs?)
  • Recommended arrival window
  • Whether game library is provided

Listing example: “Thu 6–10pm — Open Play. Arrive by 6:30 to get seated; we have a 40+ game library.”

League

standings / recurring

Competitive or semi-competitive play with tracking (wins, points, seasons). Choose this whenever there are standings.

Newcomers should expect

  • Rules are enforced consistently.
  • Pairings or table assignments may be fixed.
  • Results are recorded at the end.

Host must include

  • Season dates + weekly time
  • Scoring/pairing method + tiebreakers (if any)
  • New player entry rules (late join? byes?)

Listing example: “Weds 7pm — Wingspan League (8-week season). Swiss pairings; 3 rounds; results posted weekly.”

Campaign

story / continuity

Ongoing progression across sessions (legacy games, RPG arcs, narrative co-ops). Choose this when continuity matters.

Newcomers should expect

  • Some context recap is needed before play.
  • Commitment expectations (number of sessions) are stated.
  • Drop-ins may be limited depending on the story state.

Host must include

  • Session count or expected run length
  • Required experience (new start vs mid-campaign)
  • Table size + how absences are handled

Listing example: “Sat 2pm — Gloomhaven Campaign (Session 3/12). 4p table; newcomers OK if you can arrive 15 min early for recap.”

Quick rule for borderline cases

If there are standings: label it League.

If continuity changes future sessions: label it Campaign.

If you’re scheduling specific games: label it Game Night.

If the group chooses games on arrival: label it Open Play.

Submit a Meetup

Use this form to create a clear listing for moderation. Your draft stays on this device until you send it.

Privacy policy

Shown in the listing unless you request initials only.

Used only for clarifications during moderation.

By continuing you agree to our handling of personal data as described in Policies → Privacy Policy.

Email it

Prefer recaps? Use Submit a Recap.

Submit a Recap

Share factual outcomes, host notes, and standings. Submissions are reviewed before publishing. For privacy expectations, see Privacy & Names.

If you include names, please confirm permission below. Initials are okay.

Want to update a published recap later? Use Correction Policy.

This form creates an email to contact@domain.com. You can also submit from League Recaps.

Host Toolkit

Host notes that prevent confusion

Use the notes below to set expectations without sounding strict. We prioritize punctual starts, respectful table volume, realistic teaching capacity, accessibility clarity, and venue policy accuracy.

Before you post

  • Start time: list a firm start and a realistic arrival window (e.g., “Arrive 6:15–6:25, teach at 6:30”).
  • Seat count: state max players per table and whether you can split into two tables.
  • Noise level: “quiet teach,” “normal café,” or “lively bar” so people can self-select.
  • Venue policies: confirm purchase minimums, outside food rules, and age restrictions before submitting.

Moderation note

If a policy or accessibility detail is uncertain, say so plainly. We’ll follow up before publishing.

During play: table etiquette

  1. 1Start on time. If you can’t hold the seat past a certain minute, say it up front (“Seats held until 6:25”).
  2. 2Respect teach focus. Keep side talk low during rules; save debates for after the first round.
  3. 3Call your turns. A quick “I’m done” speeds up play and helps mixed-experience tables.
  4. 4Keep the table tidy. Dice trays, shared discard spots, and clear zones reduce accidental reveals.

Teach capacity (be honest)

A good listing sets expectations for pace and complexity. Use ranges, not promises.

  • Light teach: 5–10 min (party games, simple engines).
  • Medium teach: 10–20 min (midweight euros, co-ops).
  • Heavy teach: 20–35 min (multi-phase, high rules density).

Tip: If you’re teaching a heavy game, reduce player count or plan a short “learning round.”

Accessibility & comfort

  • Note step-free entry, elevator access, and accessible restroom availability if you know it.
  • Share lighting/noise realities (TVs, music, trivia nights, peak hours).
  • Include parking/transit basics and any paid validation details.

Copy/paste host note

Use this as a starting point and customize specifics.

We’ll start teaching at [TIME] and aim to begin play by [TIME].
Please arrive 10–15 minutes early so we can seat everyone.
Venue note: [PURCHASE MINIMUM / OUTSIDE FOOD / AGE LIMIT].
Table volume: [QUIET / NORMAL / LIVELY].
Accessibility: [STEP-FREE? RESTROOM?].

Venue policies we expect in listings

Food & drink

Minimum purchase, outside food rules, and whether table service interrupts play.

Age & ID

21+ hours/areas, wristbands, or any event-night restrictions.

Table use

Reservation needs, time limits, and whether we can push tables together.