Step by step
Do this first.
Run the event
Deliver
Run the event
Swipe
Brief an hour before
T minus 60: brief organizers and volunteers; check venue, connectivity, check-in, meals.
Open with the rules
Open: show the event code, explain conduct, challenge, submission fields, deadline, and demo format.
Build and check progress
Build: teams form, create repositories, record members; run a midpoint check.
Check in before meals
Meals: serve only after individual check-in and record each redemption.
Lock submissions on time
Lock submissions at the stated time. No private extensions.
Demo, close, upload evidence
Demos with a fixed time per team, then close with results timing and feedback. Upload evidence before you leave.
Check-in and meal service
Next chapterRead the full chapter
Recommended 10-hour structure
• T–60 minutes: organizer and volunteer briefing; venue, connectivity, check-in, incident, evidence, and meal checks. • Opening: display the event code, explain conduct and originality rules, challenge, submission fields, deadline, and demo format. • Build block: teams form, create repositories, and record members. Run at least one midpoint project and participation check. • Meal window: serve only after individual check-in and record one redemption at the point of service. • Submission lock: close at the stated time. Late changes require a documented platform-wide exception, never a private extension. • Demos: use a fixed time per team and record the demo evidence. Remote judges can review the required video and repository asynchronously. • Close: explain results timing, feedback, follow-up, and conduct reporting. Upload closing evidence before leaving where connectivity allows.
Do not improvise prizes, reimbursement promises, partner claims, public voting for main awards, or special access for a favored team. Do not receive or redistribute a winner’s prize: b54 or the approved prize partner delivers it directly. Record incidents and material exceptions while details are fresh.


