Skip to content

Plan and run an event

Every Snapdown event follows the same broad lifecycle. A league event and a standalone tournament differ mainly in where their participants come from; both can use the same divisions, competition methods, publishing tools, and event-day screens.

Use this page to decide what comes next. Each stage links to the detailed guide for the work you actually need to do.

Create the event, choose whether it lives independently or in a league, and set the event basics. The event’s competition setup determines which later choices you will see.

Set divisions, fixed weight classes when you use them, and the eligibility rules that determine where participants belong. Do this before registration, imports, or roster selection so entries land in the right place.

See Set up divisions and weight classes.

Choose the source that fits this event. The outcome is the same: a roster ready for the competition you plan to build.

Use the competition method chosen for each division. You can keep an event simple, or use different methods for different divisions when the event needs them.

Review the brackets or matchup groups before publishing. If current weights or a confirmed attendance list matter to the competition you are building, complete that event-day preparation before you build the affected groups.

5. Publish the matches you are ready to run

Section titled “5. Publish the matches you are ready to run”

Publishing turns the prepared competition into the matches and queues the room will use. A straightforward event can use automatic scheduling across its mats. For a more deliberate operation, you can build and publish selected divisions or brackets in separate waves, assign them to specific mats, and leave later groups unlaunched until their turn.

Snapdown does not have a separate session record. A session is an operating plan: configure the needed divisions, build their competition, then select and publish the divisions or brackets that are ready to run.

Use the event-day screens to load matches, score them, show the room what is next, and respond to changes.

When an event changes after publishing, use the focused troubleshooting guide for the specific change rather than rebuilding more than necessary.