Event team briefing template: roles, timings and escalation

An event team briefing template should tell everyone where they work, what they're responsible for, when they need to be ready, and how to get help. Use it before doors open to confirm those answers with the people doing the work, including venue staff and contractors whose decisions affect your attendees.

You've probably seen the awkward version. Someone reads the schedule out loud while half the team finishes setting up. A late arrival gets told to follow whoever looks experienced. Then the first ticket problem reaches three people, none of whom knows who can resolve it.

You can avoid a lot of that confusion with a short written briefing and a conversation that checks understanding. Below is a copyable template, a worked example for a paid evening event, and practical ways to handle late staff, changing instructions and problems that need a decision. The example is fictional. Its times, people and assignments illustrate the method, rather than prescribing staffing levels for your event.

What an event team briefing needs to achieve

The briefing connects your agreed plans to the people working today. By the end, a door assistant should know which entrance they cover, where ticket exceptions go, what happens when they take a break, and what they do if they notice a problem with the queue. They shouldn't have to infer those answers from a job title.

Your event brief explains the offer, objectives and approved commitments. Your production brief sets out what technical suppliers need to deliver. The team briefing draws the relevant instructions from those documents and makes them usable on this shift.

Keep the detailed run of show available to the people calling and operating cues. Most front-of-house staff need the doors time, programme milestones, late-admission arrangements and departure instructions. Reading every lighting cue to the registration team adds length without improving their decisions.

There's a commercial reason to take this seriously. A buyer who waits through several contradictory answers experiences the event through that confusion before they see the performance. Your team also loses time looking for someone who can help. Clear responsibilities let people resolve routine questions within their authority and pass exceptions to the right person.

The UK's Health and Safety Executive advises organisers to define crowd-safety responsibilities and make sure people understand them. Treat that as a planning reference, with your venue, competent advisers and local requirements determining the arrangements for your event. Handing someone a briefing doesn't establish that they're trained for a specialist task.

Prepare the instructions before gathering the team

Start with the version of the plan you'll actually use today. Check the venue agreement, staffing roster, ticket page, supplier arrangements and emergency procedures. Resolve conflicting information with the responsible lead before copying it into the briefing. If the ticket page says doors at 18:30 and the venue expects admission at 19:00, your team needs a decision and consistent attendee communication.

Ask each lead what their people need to know before taking position. The answer usually includes something that isn't obvious to the organiser. A scanner needs a charging arrangement. A stage assistant needs to know which door the speaker uses. The venue may need a particular route kept available while equipment arrives.

Walk the actual space with the relevant leads. Use the same location names on the briefing, signs and radios. "Main entrance" isn't much help when the building has two doors that different people call the main entrance. A description such as "ticket entrance on Market Street" gives a new staff member something they can find.

Separate settled instructions from unresolved requirements. A missing medical contact or unconfirmed admission procedure can't become "ask on the day" in a document you're issuing on the day. Record the person resolving it, the deadline and whether it prevents an affected operation starting. Only the authorised lead should confirm readiness for that operation.

Distribute the written briefing early enough for people to read it and ask questions. Offer a format they can use, and check language or access needs. HSE's safety communication guidance recommends suitable language, choosing an appropriate communication method and drawing attention to hazards before work begins. The written copy supports the conversation; people still need a chance to clarify what it means for their job.

Copy this event team briefing template

Copy the following sections into your working document. Replace the prompts with names and confirmed instructions. Where a detailed plan already exists, reference its current version and explain the immediate action your team needs. Don't paste an entire risk assessment into a briefing and expect everyone to discover their responsibilities inside it.

Event, shift and current version

• Event name, date, venue and rooms in use: enter the exact working names.

• Briefing owner, version and issue time: identify who maintains today's instructions.

• Shift arrival, briefing location, briefing time and position-ready time: distinguish each checkpoint.

• Doors, advertised start, interval, programme finish and shift finish: use one clock format and time zone.

• Current supporting documents: list the roster, site plan, running order and emergency arrangements.

• Changes since the previous version: state the instruction that changed and who needs to act differently.

People, locations and limits of authority

• Event lead and deputy: record the contact route and how cover transfers.

• Venue duty contact: name the person responsible for the venue matters you've agreed.

• Department leads: identify admission, audience support, production and other relevant functions.

• Each person's assignment: state their location, immediate task and reporting lead.

• Routine decisions they can make: describe the actual permission, including any limits.

• Decisions they must refer: name the decision owner and backup contact.

• Break and absence cover: identify who takes over, how they accept the handover and what happens if unavailable.

Opening checks and attendee information

• Required checks before admission: identify the responsible lead and how readiness is confirmed.

• Ticket scanning and exceptions: state the procedure and the location for questions needing investigation.

• Entry conditions: reference the approved ticket terms and venue rules staff will apply.

• Accessibility support: explain available arrangements, the contact and the route for an unexpected request.

• Late arrival, re-entry and interval arrangements: state the approved procedure for this event.

• Attendee questions: confirm timings, facilities, transport information and any promised inclusions staff should explain.

• Public updates: identify who approves messages and who communicates them to attendees.

Communication and escalation

• Primary communication method: list relevant radio channels or other agreed contact routes.

• Contact names: use names people recognise and avoid unexplained abbreviations.

• Message format: identify the recipient, your location, the observed problem and the help required.

• Acknowledgement: explain how the receiver confirms an instruction and reports completion.

• Routine escalation: identify the lead, deputy and next contact if neither responds.

• Communication failure: state the tested alternative and any restriction on working without contact.

• Restricted information: explain what needs a private channel and who can access the associated record.

Emergency arrangements and release

• Raising the alarm: state the event's agreed procedure and local emergency contact information.

• Immediate danger: explain actions under the agreed emergency plan without requiring routine management permission to raise an alarm or summon urgent help.

• Relevant locations: identify exits, agreed places of safety and where trained medical help can be found.

• Specialist responsibilities: identify authorised security, medical, technical and venue personnel.

• Emergency instructions: state who directs the response under the agreed arrangements and how authority may transfer.

• Staff questions and understanding check: record any unresolved question and the person answering it.

• Missing or late staff: name the person who briefs them before they accept an assignment.

• Position confirmation: record who confirms readiness and who releases each operation to begin.

Some entries will be short. Others need a linked procedure and a conversation. For example, your emergency section should reflect the plan agreed for that venue and event, including assistance arrangements. This template helps you communicate that plan. It doesn't supply a suitable emergency plan on its own.

Turn job titles into decisions people can make

"You're on tickets" sounds clear until a buyer presents a ticket that doesn't scan. Can the assistant admit them, investigate their order, change their name or offer a refund? Decide those boundaries before the team starts. Access to a screen doesn't automatically mean authority to change what's on it.

Write each assignment as a small piece of prose. "You cover the Market Street ticket entrance, scan eligible tickets and refer unresolved ticket questions to the help desk. The admission lead arranges your break cover." That tells a new person considerably more than a box labelled registration.

For Loopyah ticket operations, you can add admins and door staff without sharing your login. Door staff can receive check-in-only access and scan QR tickets using their own phones. Brief people on the access you've actually assigned, then confirm that they can use it before admission begins. Keep the organiser's administrative account separate from the access a scanner needs.

Agree who owns the decision when two teams meet. A door assistant might identify a late attendee, while the house manager decides when seating can happen and the stage team identifies a suitable programme moment. The assistant needs the approved admission instruction, not permission to interrupt the show to find out.

Also explain how people get help without abandoning their position. A scanner who walks away to locate the organiser may leave nobody checking the entrance. Assign a reachable lead, a cover arrangement or another agreed way to resolve the problem while maintaining the required operation. Staffing choices still depend on your event's risks, layout and workload.

A worked briefing for a paid evening event

Our fictional event is Makers After Hours, a paid interview evening in a venue with one audience room and a foyer. Tickets include the interviews and audience questions. There are no ticket sales at the door in this example. The venue has confirmed the intended layout separately, and the organiser has arranged the staffing and specialist support appropriate to the event.

Doors open at 18:30, the advertised programme starts at 19:00, the interval runs from 20:00 to 20:20, and the programme ends at 21:10. Audience departure and venue handback follow their agreed arrangements. These are planning assumptions for the example, not recommended durations.

Who leads and who covers

Nadia is the event lead. She approves routine event changes and attendee remedies within the organiser's agreed policies. Ellis is her deputy and takes that responsibility only when Nadia explicitly hands it over. Their names and current contact details appear in the actual working briefing.

Rosa leads admission and manages the ticket help desk. Ben and Amina scan at the Market Street entrance. Theo supports the queue and directs people to the help desk when required. Jo is the house manager and coordinates seating, interval return and audience departure. Karim coordinates speakers and the stage team using the separate run of show.

The venue supplies its named duty manager and the agreed specialist personnel. They receive the shared information relevant to their responsibilities, and Rosa confirms the contact route before admission. The named people above illustrate the relationships; they don't constitute a complete staffing prescription.

Ben and Amina refer ticket exceptions to Rosa. They don't promise refunds or create guest admissions. Jo coordinates late seating with Karim. Nadia decides an ordinary programme change after discussing its effects with the relevant leads. Emergency actions follow the agreed emergency arrangements, including specialist authority, rather than those routine commercial permissions.

Before doors open

Staff arrive at 17:45 and report to their lead. The shared briefing starts in the foyer at 18:00. People need to hear it, so leads arrange setup work around that meeting rather than expecting staff to listen while carrying furniture across the room.

After the shared briefing, Rosa walks the admission team through their positions and checks their devices and access. Jo confirms the seating route and the agreed late-arrival waiting area. Karim completes the stage checks with his team. At 18:20, leads report their assigned readiness checks and any outstanding issue.

Nadia and the venue duty manager review the required confirmations under their agreed responsibilities before Rosa begins admission. A scheduled doors time doesn't substitute for that confirmation. If admission cannot start as planned, Nadia approves the routine attendee update and Rosa communicates it through the agreed methods. Emergency communications follow the separate plan.

What the admission team says

For a valid ticket, Ben and Amina follow the established scanning procedure and direct the attendee towards the audience room. If a ticket needs investigation, they explain that Rosa can help at the marked desk. They don't announce order details across the foyer or debate the buyer's circumstances in front of the queue.

If someone asks to buy a ticket, the staff explain that this event isn't selling at the door. They refer any claimed prior arrangement to Rosa, who checks the record and seeks Nadia's decision when necessary. No staff member assumes a familiar face is on the guest list.

Jo confirms that late arrivals wait in the agreed area until she coordinates a suitable admission moment with Karim. Staff explain the arrangement politely and give confirmed information. They don't invent a waiting time when the programme moment is uncertain. Jo also handles requests that need an accessible alternative under the event's arrangements.

What happens at the interval and close

Before 20:00, Jo tells the relevant front-of-house people to prepare for the interval under the current running order. Rosa keeps a named person available for ticket questions. Breaks happen through arranged cover; the interval isn't an instruction for everyone to leave their position at once.

At 20:15, Jo checks readiness for the planned return and communicates any issue to Karim and Nadia. The team uses the confirmed return instruction. If the programme changes, Jo needs that decision before directing attendees back to their seats.

After the 21:10 programme finish, Jo coordinates departure with the venue team. Staff continue their assigned duties until their lead releases them. Karim follows the agreed conditions for technical removal. A quiet stage doesn't mean equipment can move through a route still used by departing attendees.

Brief accessibility support as an actual service

"Be helpful" won't tell a new assistant where an accessible entrance is or how someone can request support privately. Explain the arrangements you've confirmed, who knows the details and how to contact them. Ask the relevant person to walk staff through unfamiliar routes before opening.

W3C's accessible events checklist advises organisers to check access arrangements, invite requests and provide relevant information ahead of the event. Your team briefing should carry those confirmed arrangements into the onsite service. A service described on the ticket page needs an owner who knows how attendees access it.

Suppose an attendee asks for a quieter waiting location. The assistant can explain the available option and contact the support lead if they need more help. They shouldn't ask the person to justify a diagnosis in the queue. Different requests may require different arrangements, and some require a decision from the venue or a specialist.

Include emergency assistance arrangements in the relevant briefing with appropriate privacy. Don't assume the ordinary entrance route is suitable in an emergency or that an untrained assistant can provide physical assistance. Agree responsibilities with the people competent to plan and deliver them, then explain each staff member's part clearly.

Make escalation specific enough to use

A useful escalation instruction distinguishes a question from a problem requiring immediate action. For an ordinary ticket query, staff follow the help-desk route. If they observe a dangerous situation, they raise the alarm and follow the relevant emergency arrangements without waiting through the ticket-query chain.

HSE's event emergency guidance calls for clear responsibilities, staff understanding of alarm procedures and tested communication systems. Use your event's agreed procedure and local emergency numbers. A briefing should never tell someone facing immediate danger to wait for a manager's approval before raising the alarm or calling urgently needed emergency assistance.

For routine matters, specify the backup when the first contact doesn't answer. In our example, Rosa contacts Nadia about an admission decision. If Nadia has handed over to Ellis, Rosa contacts Ellis. The team knows the current deputy arrangement because Nadia announced it and the affected leads acknowledged it.

Avoid a universal instruction such as "wait five minutes, then escalate." The acceptable response depends on the issue, and an apparently minor queue problem can develop. Have the responsible leads define observable conditions that need prompt attention, such as a route becoming obstructed or a device problem affecting the agreed admission process.

Staff should report what they've observed rather than diagnose beyond their competence. "The queue is blocking the marked doorway" is useful information. "The crowd is safe" is a conclusion the observer may not be qualified to make. The responsible person needs a location, the condition and the assistance required.

Use a communication check before releasing people

Test contact between the actual positions people will use. A radio working in the foyer doesn't establish that someone can hear it backstage. Confirm the alternative if the main method fails, including whether an operation must pause until contact is restored. The responsible lead determines that restriction.

Practise one ordinary exchange. Ben calls Rosa, identifies the Market Street entrance and describes a ticket needing investigation. Rosa confirms she'll handle it at the help desk. Ben directs the attendee there and stays on scanning. Everyone can hear whether the contact names and location descriptions make sense.

For a changed instruction, ask the receiving person to repeat the action and timing. If Jo says late seating will use the next agreed pause, Ben repeats that instruction and asks what to tell waiting attendees. Jo corrects any misunderstanding before the team applies it. Repeating the instruction helps you catch misunderstanding. The responsible team still needs to check actual conditions before carrying out the action.

Don't turn a quick acknowledgement into a public test of confidence. Someone who hasn't understood should be able to say so. Ask specific questions about the person's task and listen to the answer. "Any questions?" often produces silence even when several people are unsure.

Run the briefing as a conversation about today's work

The person leading the meeting should arrive with decisions, then use the conversation to find misunderstanding. Starting with a long thank you and every detail of the event's history makes it harder for people to recognise the instructions they need. Explain the experience attendees bought and the parts of today's operation that protect it.

For Makers After Hours, Nadia opens by confirming the current document, the advertised start and the responsibilities that have changed since the previous shift. She introduces the leads people will contact, then asks those leads to explain the actions their teams need before opening. Each lead addresses the people doing the work rather than reading their entire department plan aloud.

Rosa explains where scanners work and how ticket exceptions reach her. Jo describes the seating and late admission arrangements. The venue representative covers relevant venue instructions, while the people responsible for the emergency arrangements explain the team's assigned actions. Technical details requiring specialist competence remain with the appropriate specialist briefing.

Then Nadia checks the points where teams depend on each other. Who tells Rosa that admission can begin? How does Jo contact Karim when late arrivals are waiting? Who covers the help desk when Rosa takes a break? If the answers differ between the two people involved, resolve that difference before either returns to work.

You can also ask people to work through an ordinary situation. "An attendee says their companion has the tickets and is already inside. What do you do?" In this example, Ben refers the query to Rosa without promising admission. Rosa follows the approved verification process. The question reveals whether Ben understands his boundary and whether Rosa has a process to follow.

Another useful question is what would prevent someone taking their position. Amina might explain that she hasn't received the correct access, or Theo might not know the waiting area Jo named. Those are preparation problems you can still resolve. If you rush the team through a general confirmation, you may only discover them when attendees arrive.

Record attendance and the version received, but avoid treating a signature as proof of understanding. Ask for the action in the person's own words where it matters. Someone can agree that a briefing was delivered while still being unsure which entrance they're assigned or who handles a disputed ticket.

Finish by confirming outstanding actions and the next readiness report. Each unresolved item needs a named person and a decision about what can proceed. The meeting can end while a lead completes a check, provided the team understands that ending the briefing doesn't release an operation that still lacks required approval.

Keep enough time afterwards for people to reach their positions, test contact and ask a private question. A briefing that finishes at the exact doors time leaves no room to fix the issue it has just uncovered. Plan that preparation into the shift before issuing the roster. If a staff member needs a demonstration, arrange it with the responsible lead and check the result. Ask what help they need. Repeating an unfamiliar procedure more loudly won't make someone competent to perform it.

Brief late arrivals before assigning their position

A late staff member needs the current instructions and a responsible person to check their understanding. Sending them straight to the busiest entrance transfers that work to someone already serving attendees. The new arrival also misses changes that may have happened after the written briefing was issued.

In our example, Rosa briefs an arriving replacement scanner before they start. She covers their position, access, ticket exceptions, communication, break cover and relevant emergency responsibilities. The replacement checks the actual device and contact route. Rosa records that they received the current version and confirms any unresolved training issue with the appropriate lead.

Arrange temporary cover while that happens. If suitable cover isn't available, the lead decides how the operation can proceed within the agreed requirements. Don't assume the remaining team can absorb another task safely or that attendance at a previous event counts as an induction to this venue.

The same principle applies to a shift change. The outgoing person explains live issues, agreed changes and anything still awaiting a decision. The incoming person accepts the assignment through the lead's handover arrangement. Someone leaving for a break shouldn't have to choose between walking away and waiting indefinitely for unidentified cover.

Keep personal information out of the shared briefing

The shared document needs working contacts and service instructions. It rarely needs attendee medical histories, full order records or a list of complaints attached to people's names. Limit distribution according to what each recipient needs for their job and use the agreed private route for sensitive matters.

The UK's Information Commissioner's Office explains data minimisation as keeping personal data adequate, relevant and limited to the purpose. Its guidance concerns UK data protection requirements; check the rules applicable to your event. The practical question for the briefing is whether this person needs this information to do their assigned work.

For example, front-of-house staff may need to know how to contact the access-support lead. They don't all need a named attendee's explanation of a health condition. Likewise, a radio request can identify a location and the required help without broadcasting payment details or a private complaint.

Update the team when instructions change

A revised document doesn't tell people who are already working that their instruction has changed. Name the person communicating the decision, identify affected roles and ask those people to acknowledge the revised action. Record the change in the current working copy so a later arrival receives the same information.

Suppose the interview starts later because a routine technical fault needs attention. Nadia confirms the programme decision with Karim. Jo receives the revised audience instruction, Rosa receives any effect on late admission, and the host receives approved wording. A scanner shouldn't learn about the delay from an attendee's social post.

Keep the reason concise and the action explicit. "Use the revised late-admission instruction confirmed by Jo" is actionable when Jo has communicated that instruction. "We're running behind, be flexible" leaves every person to invent a response. Give a next update point when the decision remains unresolved, and don't promise a restart time nobody has confirmed.

Close with the questions your team actually had

After the event, ask leads which instructions were unclear, which contacts were difficult to reach and which exceptions kept returning. Record the circumstances while people remember them. A complaint about the briefing is more useful when you know the missing instruction and the decision it delayed.

Before the next event, correct those specific gaps and check them against the new venue and roster. Reusing the structure saves preparation time. Reusing yesterday's contacts, access arrangements and assumptions can create exactly the confusion the briefing was meant to prevent.