For organizers of a recurring tech event, between editions
Quiet MonthsThe Discord is a graveyard eleven months a year. Decide what that should mean.
Plan the gap between editions of one recurring event. Free in your browser: how much the standing space gets in the quiet months and who owns it, how last edition's attendees get brought back, how the space survives an organizer leaving, where local groups stop being yours, carry rate beside newcomer share, and the three gates. A run writes the between-editions plan, or the dated handoff document. Every threshold is yours to set.
1 The event, the space and who is around free
2 The gap, worked out free
What the page flags
Cadence, bringing attendees back, handoff
The quiet notice to post
The accounts that change hands
Routed out, and the local line
3 Between-editions plan or handoff document metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Owner and register
Routed out
Cadence
Bringing attendees back
Handoff
Cut from the menus
Measurement
What would flip it
Gates
Caveats
The page's check of this reply
4 Saved plans
How it works
The quiet months reshape around one honest answer: who has recurring hours when nothing is being produced. Dormant-but-open is the floor, not zero - the archive and member list stay, with a dated notice that the space is quiet until build-up. A pulse needs an owner who can hold its rhythm; continuous programming needs someone on duty, or the space becomes a conduct obligation nobody answers. Closing the space and reopening it fresh each edition throws the member list away.
Bringing people back is one contact timed to the next opening by default, a participation ladder when the event compounds, and a local cohort only when the audience really spans cities and someone local runs it. If anyone outside the team would run an event under your name, that is governance, not this plan. The handoff is one written page: every account, who holds it today and after, and the member list's owner and retention decision - never a successor added as a second admin while a personal account stays owner.