Build a responsibility map, not just a crew list
A list of names tells you who is present. A responsibility map explains who may approve a change, who carries it out and who must hear about it. Identify the event lead, competition lead, head referee, venue liaison, technical lead, broadcast producer and player liaison. On smaller events, one person may hold several roles, but the responsibilities still need to be distinct.
Assign a deputy or escalation route for each critical function. If the only person who knows the network configuration is collecting a delivery, the event has a coverage gap. Share essential documents securely and keep a practical offline copy of the contact sheet, schedule and emergency arrangements. Avoid distributing unnecessary personal information to every volunteer or contractor.
Plan movement before planning presentation
Schedule load-in around building access, vehicle limits, unloading capacity and installation sequence. Networking cannot be fully tested while its switches are still behind stage equipment in a delivery vehicle. Confirm who receives each shipment, checks it against the inventory and signs for any damage. Distinguish delivery completion from technical acceptance; they are different milestones.
Design player movement from arrival to check-in, practice, call, match and departure. Include accessible routes, private welfare space and a process for accompanying staff. Keep public access separate from sensitive competition and production positions where appropriate. Accreditation should express permissions clearly without revealing personal details that do not need to be visible.
Use one operational schedule with clear views
Keep a controlled master schedule while giving each department an appropriate working view. The competition team needs match dependencies; broadcast needs segment timing; venue staff need access and audience milestones. These views must derive from the same current plan. Include a version identifier and publish updates through one agreed channel rather than maintaining several competing spreadsheets.
Identify the critical path: tasks whose delay moves the next essential milestone. Add realistic crew breaks, meal access and shift handovers. Fatigue reduces judgement and increases the chance of quiet errors, especially during repetitive station resets and overnight installation. Local employment, contractor and working-time requirements still apply when the production schedule is under pressure.
Rehearse decisions as well as cues
Run a tabletop exercise before the technical rehearsal. Ask what happens when a player is late, a station fails during warm-up, a result is disputed or the venue restricts access unexpectedly. The aim is not to script every incident. It is to expose missing authority, unclear communication and assumptions that two departments have interpreted differently.
Then rehearse the practical sequence with actual operators. Call players, verify station readiness, obtain referee clearance, cue broadcast and confirm the match start. Use concise, acknowledged messages. A cue is not complete because someone transmitted it; the receiving role must understand and accept the action. Establish a separate route for urgent safety communication so routine chatter cannot bury it.
Handle incidents without losing the record
Record the time, observed facts, affected systems, action owner and next update point. Keep speculation separate from evidence. The incident lead should coordinate recovery while the appropriate official retains authority over competition or safety decisions. Do not ask a broadcast producer to make an electrical safety assessment, or a technical operator to determine a disciplinary sanction.
Communicate what is known, what is being checked and when another update is expected. An update can acknowledge continuing investigation without inventing a resolution time. If conditions become unsafe, follow the venue's emergency arrangements and the instructions of responsible personnel. Programme continuity is subordinate to the safety of participants, crew and visitors.
Close the event deliberately
Load-out needs a release sequence, not a rush to remove whatever is nearest. Preserve required results and incident records, confirm recording transfers and make systems safe before dismantling. Check hired equipment against the inventory and record outstanding returns. ISO 20121 offers a framework for event sustainability management; practical choices include consolidated transport, reusable signage and planned waste handling rather than last-minute disposal.
Hold a short debrief while evidence is available. Separate immediate fixes from structural changes, assign owners and carry lessons into the next specification. The useful output is not a long list of complaints but a small set of changes with clear reasons and accountable follow-through.
Final handover rehearsal
- Every critical role has coverage and an escalation route.
- Player calls depend on verified station readiness.
- Schedule changes reach all affected departments.
- Incident messages distinguish facts from assumptions.
- Load-out and record retention have named owners.