Readiness & Go-Live
Hajime runs an automated readiness checklist before you can start an event, catching the mistakes that otherwise surface as chaos on event morning. Learn what the required and recommended checks cover and how to force-start past warnings.
Readiness & Go-Live
Applies to: Organizers
Before you start an event, Hajime runs a readiness checklist: a set of automated checks that catch the mistakes that otherwise surface as chaos on event morning.
Publishing an event (opening it up for registration) has no readiness gate, so you can publish as soon as you're ready to accept registrations. It's starting/going live that the checklist controls.
Where to Find It
The Event Readiness panel appears on your event's page. It's collapsed by default; click it to expand and see every check, grouped as Required and Recommended.
[Screenshot placeholder: Event Readiness panel, expanded]
Required vs. Recommended
Checks come in two tiers:
- Required (blocking): must all pass before you can start the event. These cover the structural minimum: at least one speciality configured, a start time, at least one mat, at least one bracket, all brackets published, all brackets assigned to a mat, and schedules generated for every mat.
- Recommended (warning): won't block starting the event, but flag things worth fixing, such as an event description, venue or virtual flag, registration dates, mats with a scheduled start time, mat schedules fitting within the event window, empty or undersized brackets, speciality round timing, bracket seeding quality, and (computed asynchronously) athlete coverage across registrations and cross-mat athlete conflicts.
Many failed checks link straight to the screen that fixes them, whether that's mats, brackets, or the event edit form, so you often don't have to guess where a problem lives.
Force-Starting
In rare cases you may need to start an event with warnings still outstanding. Hajime allows a force-start with explicit acknowledgment of the warnings. Blocking checks cannot be bypassed this way: they represent states the platform genuinely cannot run an event in, such as no mats or no brackets.
[Screenshot placeholder: Force-start confirmation with warnings listed]
Some Checks Take a Moment
A couple of checks (athlete coverage, cross-mat conflicts) are more expensive to compute and load asynchronously after the cheap checks appear. If one fails to compute, a Retry button appears; use it rather than reloading the whole page.
Frequently Asked Questions
Can I start the event with warnings still showing? Yes, via force-start, as long as no blocking check is failing.
A check says my brackets aren't assigned to mats. Where do I fix that? Click the check itself; many failing checks link directly to the mats or brackets screen responsible for it.
Why does one check take longer to load than the rest? Athlete coverage and cross-mat conflict checks run more expensive queries and load in after the rest of the checklist. This is expected.
Next in this guide: Event Morning
Last updated: July 2026