Hosting guide / The invitation is part of the game

Host the First Remote Session

A smooth evening does not need an elaborate production. It needs a shared plan, a forgiving first game and a clear way to ask for help.

Step 01 / Agree on the essentials

Plan around the people joining

Start a short conversation before choosing a game. Ask about available devices, account preferences, reading comfort and the amount of uninterrupted time people can offer. Make it easy to answer privately. Someone should not have to describe a disability, household situation or financial constraint in a group chat to get a workable alternative.

Choose a session format together. A live game needs an agreed start and finish; an asynchronous game needs expectations about turn frequency and reminders. Do not assume friends in different time zones want to stay awake late just because a platform is always available.

Step 02 / Remove surprises

Test the route to the table

Rehearse with someone using the least familiar setup. Follow the invitation from the beginning, including sign-in, installation if needed, joining a room and finding a seat. A successful host account is not evidence that guests can reach the same table. Check whether a membership or expansion changes the invitation process.

Test audio separately from game controls. Headphones may reduce echo, but offer text communication when voice is not comfortable or available. If you use Discord, Zoom or another communication service, send its link alongside the table link and explain whether joining it is optional. Do not silently add another required account at the last moment.

Conceptual 3D arrangement of a laptop, headphones and a large readable join-table control

Step 03 / One useful invitation

Send everything in one place

An invitation should explain what to open, when to arrive and what to do if something fails. Write the time with an explicit time zone, and distinguish account setup from the game’s actual start. Avoid scattering essential instructions across several chat threads. Send any rules resource as an optional preparation aid unless everyone has agreed otherwise.

Keep room links within the intended group. A public post can invite unwanted spectators or players, depending on the platform’s permissions. Check room visibility and sharing settings rather than assuming an unfamiliar-looking link is private.

Copy this invitation structure

Game: title, edition and expected experience level.
When: date, start, time zone and planned finish.
Beforehand: accounts, software and any costs.
Join: the private table and communication links.
Support: who to message if joining fails.
Fallback: a simpler game or a new date.

Fill in real details before sharing. Never include passwords in a public invitation.

Step 04 / Start gently

Play a practice round openly

Begin with the goal of the game and the shape of a turn, then show the interface actions needed for the first move. Let each person inspect something, make a selection and find the confirmation control. If hidden information allows it, use an open practice round and reset afterward. Explain whether accidental moves can be undone before anyone commits one.

Avoid teaching every unusual rule at once. Point out where reference information lives and introduce exceptions when they become relevant. Experienced players should offer help without directing every decision. The first session succeeds when newcomers can make their own choices, not when the host demonstrates perfect play.

Soft-lit 3D concept of a simple practice table with face-up cards and a highlighted turn marker

Step 05 / Keep the session recoverable

Expect a pause, not a failure

Agree on a reconnect signal and a place to communicate if the game closes. Before refreshing, check whether the platform saves state and whether a timer will continue. Pause where possible rather than making a missing player’s decisions without permission. Never ask someone to reveal a password or send a screenshot containing private account information.

Protect the agreed finish. If a long strategy game is running over, discuss saving, stopping or scheduling a continuation instead of assuming everyone can stay. A clear break is kinder than an unspoken expectation to finish at any cost.

Finish by making next time easier

Ask two simple questions: what felt comfortable, and what should change? Invite private feedback as well as a group answer. Someone who stayed quiet during play may still have struggled with small text, turn pace or overlapping speech. Record the agreed changes without keeping sensitive personal details.

Only then discuss another session. Rotate hosting if people want to share the work, and make declining an invitation normal. Consistency comes from a repeatable, welcoming routine—not a calendar that nobody feels allowed to question.

Prepare a hosting question Check access and group culture →