Session management
A repeatable checklist for hosts, from planning to handover.
Use this checklist manually today. Watchpost session commands and automated announcements are proposed features.
Before opening
- Confirm the host, supporting staff and expected start time.
- Check the correct ER:LC private server and current community rules.
- Prepare a clear announcement with the timezone and joining instructions.
- Agree who handles reports while the host is busy.
Publish a session code only where your community intends it to be visible. A join code and an API key are different things; never publish a server API key.
While the session is running
Keep one host responsible for the current session state. Record changes that affect participants, such as a pause, host change or early closure. If announcements are later automated, repeated clicks should update the same session rather than creating multiple active sessions.
Closing and handover
Tell participants when the session ends. Close any related staff duty records using the agreed process, note unresolved incidents and pass them to the next responsible person. Keep a short summary of what happened and what needs follow-up.
Release checks
Before adding automated hosting, test simultaneous host actions, failed announcements and a bot restart during an active session. The state shown to staff and the state announced to members must stay consistent.