Party Session Blueprint | Repeatable Runbook
Turn captain notes, stream links, and spectator gates into a predictable routine.
35 views
0
Turn captain notes, stream links, and spectator gates into a predictable routine.
Every strong session follows the same loop: prep the bankroll, review crew notes, confirm spectator settings, stream (if desired) with the link saved in the manage view, rotate players on a schedule, then settle and document the outcome.
The blueprint keeps things simple for players in their 50s and younger alike. With a short checklist and scheduled rotations, nobody has to guess who is live, which gate is active, or when the next settle will happen.
15 minutes • Before going live
5 minutes • Right after pressing Launch party
1-3 hours • During gameplay
10 minutes • When you are done playing
5 minutes • End of session
Before going live
Use captain notes as the single source of truth.
Key Activities:
💡 Best Practice: Pin the briefing in Discord or your preferred chat so late arrivals can read it.
Right after pressing Launch party
Let everyone know the party is live.
Key Activities:
💡 Best Practice: If you stream, enable the compliance toggle so moderators know you acknowledged local rules.
During gameplay
Stick to the plan even when variance hits.
Key Activities:
💡 Best Practice: Observers should handle chat moderation so players can focus on the reels.
When you are done playing
Debrief before the memory fades.
Key Activities:
💡 Best Practice: Use the Download ledger button while the data is fresh.
End of session
Follow the settlement routine from the payouts article.
Key Activities:
💡 Best Practice: Close idle parties the same day so live cards never show outdated ROI.
About 30 minutes outside of gameplay
Daily Tasks:
Skills Needed:
Organization and steady communication
1 hour blocks
Daily Tasks:
Skills Needed:
Focus and willingness to take feedback
Flexible
Daily Tasks:
Skills Needed:
Multitasking and friendly tone
Protocol:
Observer lead posts an update, captain pauses large bets, and the link is re-added once the platform reconnects.
Example:
““Kick went down—holding spins for 2 minutes, relinking shortly.””
Purpose: Prevents panic from viewers and teammates.
Protocol:
Refer to the timers noted in crew notes. If someone needs extra time, reschedule the rest of the lineup in writing.
Example:
““@NexusMage swap with @SpinDoc tonight; notes updated for tomorrow.””
Purpose: Keeps expectations clear even when plans change.
Protocol:
Captain or observer lead handles the request in the manage view, then acknowledges the outcome in chat.
Example:
““Manual approval sent to @CoachCarol—refresh your lobby.””
Purpose: Shows viewers that access is controlled, not chaotic.
Solution:
Schedule a recurring reminder for the captain before each session.
Prevention:
Treat crew notes like a flight plan—no launch without it.
Solution:
Switch back to Manual approvals immediately and audit who joined during the gap.
Prevention:
Double-check gate settings during the Prep phase.
Solution:
Download it after every settle and store it in a shared drive.
Prevention:
Make ledger export part of the wrap-up checklist.
Yes, but close and settle every day so stats stay accurate. Many teams prefer relaunching with a fresh slug to keep ledgers clean.
No. Streaming is optional. If you do, add the link once and the platform surfaces it everywhere the party appears.
Point them to the latest crew notes. That document is the contract for the session.
Rotate session start times weekly and capture everyone’s availability in crew notes so nobody feels ignored.
We're sorry this wasn't helpful. Our support team can assist you further.
Contact Support