Skip to main content

Safety Officer

This guide is for the event safety officer.

If you want a one-page handout for event day, use the Safety Officer Card.

Your job

You are responsible for protecting people first and software second. Your job is to watch for unsafe behavior, stop unsafe activity immediately, communicate clearly with nearby staff, and log warnings in ASJudge when a warning is warranted.

What you will see

After login, you will land on the Safety Dashboard. That page shows every team, each team's warning count, the team's current navigation score if it is available, whether the automatic navigation deduction is active, a warning entry box with an Add Warning button, and a recent warnings list.

Warning threshold

ASJudge automatically applies a 10-point navigation deduction after a team receives more than three warnings, which means your warning entries have direct scoring consequences.

Basic workflow

Your basic workflow is to watch the event floor, intervene immediately if something is unsafe, make sure students and nearby staff understand the pause or correction, confirm which team was involved, enter a short warning reason in ASJudge, and allow activity to continue only when the area is safe again.

If you must stop a run

If you must stop a run, stop the activity first, protect students, staff, and bystanders, and tell the facilitator that the arena is paused. Let the arena staff handle schedule recovery after the scene is safe, then log the warning once the immediate hazard is under control.

Writing warning reasons

Keep warning reasons short and factual. A few words such as "crossed boundary line after instruction," "unsafe propeller handling," or "entered arena before clearance" are usually enough.

What not to do

Do not let schedule pressure override safety, do not delay intervention because you want software confirmation first, do not skip logging a real warning after the floor is safe again, and do not treat the dashboard like a substitute for direct verbal intervention.

Quick reminder

Your order of operations is always the same: stop unsafe activity, protect people, communicate clearly, log the warning, and restart only when it is safe.