Event Staff Guide: How Your Team Should Look for Different Event Sizes

You have tickets to sell, suppliers to manage and a room to open on time. Then someone asks how many event staff you need. It's tempting to start with attendance and divide it by a staffing ratio. That gives you a number, but it doesn't tell you whether anyone will be free to fix a ticket problem while the rest of your buyers wait outside.

Start with the work that happens at the same time. Assign someone to each essential post, plan who covers breaks and exceptions, and check the arrangement with the venue and your specialist suppliers. Attendance changes the workload. Your layout, arrival pattern and program decide where that workload lands.

This event staff guide explains how that changes across a small paid workshop, a multi-room conference and a large outdoor event. The sample rosters are planning examples, not industry ratios, legal minimums or claims that a particular crew will be safe for your event. You'll also see how to budget the hours, hire people for specific jobs and brief them well enough to make decisions without calling you for everything.

For context on attendee expectations, the Freeman/PCMA trends insights discuss what people value in an event. Those preferences can inform service priorities, but they don't establish how many staff your event needs.

Start with attendance, arrival patterns and complexity

A sold-out training day and a late-night show can have the same ticket count and need very different teams. At the training day, questions may be about badges, session choices and dietary requirements. At the show, entry may involve age checks, ticket scanning and security screening. Those are separate jobs even when they happen at the same door.

Use these size bands to find the relevant examples in this guide. They aren't definitions used by regulators, and the boundary between them doesn't determine your safety obligations.

• Small events, roughly 50 to 100 attendees, often have a single room and a short chain of decisions.

• Medium events, roughly 100 to 500 attendees, may need dedicated entry, production and floor leads because several activities overlap.

• Large events, above that range, often involve more zones, contractors and public-safety coordination. A simpler layout can still be easier to operate than a smaller, complicated site.

The first thing you want to do is walk through the buyer's arrival. Where do they join the queue? Who answers a ticket question? Can someone who needs assistance reach the entrance without crossing a vehicle route? Then walk through the program, the breaks and the exit. Record the posts that must stay covered, including the ones your venue or contractors provide.

Now add the work the public won't see. Someone needs to receive deliveries, brief temporary workers, check rooms before opening and reconcile equipment after closing. The UK's Health and Safety Executive explains in its event management guidance that safety management also matters during build-up and breakdown. Having fewer attendees doesn't make a loading dock or equipment move harmless.

Build the staffing plan alongside your schedule and budget. Our event planning checklist and event budget guide can help you put the work in order and budget the hours.

Give each part of the event an owner

You need named responsibility before you need a complicated organisation chart. A small crew can combine compatible roles. As the event grows, the same responsibilities split into separate jobs. In either case, the person taking a decision must know what they can approve and when they need help.

• The event lead keeps the operating plan current, coordinates suppliers and decides ordinary program changes. Name a deputy for when the lead is unavailable.

• The entry lead owns the queue, ticket checks and exception desk. They agree admission and refund escalation rules with the organiser before doors open.

• The floor lead manages room readiness, directions, transitions and reports from ushers. They know which spaces are open and who can authorise a room change.

• The production lead coordinates technical crew and speakers or performers. Technical work goes to people qualified for the equipment and task.

• The safety and security leads agree their responsibilities with the venue and relevant authorities. Screening, crowd management and emergency response shouldn't be assigned casually to whoever is free.

• The medical provider sets the clinical staffing and response arrangements for the event. Ordinary guest-services staff need to know how to call that help and clear access, not make clinical staffing decisions.

There are other jobs, of course. Catering, cleaning, transport, sponsor support and accessibility arrangements all need owners when they apply. The useful question is whether those owners can reach the person who decides a change that affects them.

Suppose the program runs late and a sponsor wants its activation to stay open longer. The floor lead shouldn't promise an extension before checking the venue booking, supplier hours and security cover. A clear decision path prevents a friendly answer from becoming an unplanned bill.

Staffing a small paid event

A small event is where role sharing can save real money. It's also where one missing person can expose how much of the plan depended on them. Keep the crew lean by combining jobs that happen at different times, rather than hoping someone can do two things at once.

Suggested team structure

Imagine a paid workshop with 75 attendees, a venue-provided room and a speaker who needs microphones and slides. An illustrative roster could have an event lead, two entry staff, a floor runner and technical support. Whether those are separate hires depends on the venue contract and the actual tasks. Confirm specialist safety, security and medical arrangements separately; they aren't covered by this service roster.

One entry staffer scans tickets while the other resolves names, answers questions and directs people. After the arrival rush, the second person may help with a room reset. That only works once the entry lead confirms late arrivals and ticket exceptions can still be handled. The runner can help the speaker before the session, then manage directions during a break. They can't leave the room halfway through a technical task because someone needs more cups.

If the venue supplies a technician, find out when that person is present and what they will do. "AV included" may mean installed equipment rather than an operator standing by throughout your program. Likewise, a staffed reception desk may serve the whole building rather than your event. Put the agreed coverage in writing so your roster doesn't count people you haven't actually booked.

Cross-train for specific tasks

Cross-training is useful when the second task is clearly defined. Show the runner how to replace a microphone battery or reach the technician. Show the entry team how to direct a late arrival without interrupting the speaker. Let people practise the task, then check they can do it.

It becomes risky when "everyone helps with everything" hides a missing skill. Don't turn a door assistant into an electrician or a first-aid provider because the crew is small. Identify the work that needs a specialist and pay for that coverage. If the budget can't support the program safely, simplify the program before cutting the specialist.

For a compact indoor site, a tested staff group chat may be enough for routine updates. Check coverage in the actual rooms and make sure the team can hear or notice an urgent call. If the venue has poor reception or the program is loud, agree a more reliable arrangement with the venue. Keep a printed contact sheet and a practical way to reach help if the usual channel fails.

Here's how the workshop plan might change during the day. Before doors open, both entry staff prepare the desk and test access. During arrivals they stay at entry. Once the queue clears, one helps reset the refreshment area while the other covers late buyers. At the break, the runner guides people back to the room and the entry person returns if questions build up.

This is an example to work through with your crew, not a reported case study. The point is that role sharing has a release condition. The person moving to another task knows who has taken over and what would bring them back.

Staffing a medium event with several rooms

More rooms create more simultaneous work. Even when the total audience is manageable, your lead can't watch the lobby, settle a speaker issue backstage and check a breakout room. This is usually the point where dedicated entry and floor leads become useful.

Suggested team structure

For an illustrative 350-person paid conference with three rooms, start with an operations lead and deputy, an entry lead with a tested scanning crew, a floor lead with room cover, and a production lead with the technicians the program requires. Add the separate specialist provision agreed for your event. Don't add these labels together and treat the total as a recommended staffing number.

At entry, separate routine ticket checks from problems that take longer. Someone searching an inbox, querying a transferred ticket or asking about an order should be able to get help without holding up every valid scan behind them. Put a decision maker at the exception desk, or make one immediately reachable. A help desk that can only say "I'll ask the organiser" hasn't removed the delay.

In the rooms, decide who cues speakers, checks capacity and notices a problem. One floor assistant might cover neighbouring rooms between sessions. During simultaneous sessions, their assignment needs to reflect what actually requires a continuous presence. Accessible routes, room changes and agreed support arrangements should be part of that plan.

A short lead briefing before opening helps because each department hears what changed. After that, use updates when a decision affects another team. If the keynote runs over, production tells operations what the delay means, operations confirms the revised program, and floor staff tell attendees the same thing. A busy radio channel full of commentary makes this harder, so keep routine reporting separate from urgent calls where your equipment permits.

Size the scanning crew around the arrival window

Total attendance isn't the same as demand at the door. A conference where buyers arrive throughout the morning has a different entry problem from one where most people arrive just before a headline session. Use your own previous check-in records where available, and ask the venue what other entrances or activities share the space.

For a worked example only, suppose you expect 240 people to arrive during a 20-minute period. That's 12 arrivals a minute. In a rehearsal with your devices and ticket process, suppose a staffer completes three routine admissions a minute. The arithmetic suggests four scanning positions just to match that assumed flow. It leaves no spare capacity for uneven arrivals, device problems or someone stepping away. This isn't a safe-capacity calculation or an industry benchmark; both inputs are invented to show the method.

Test again with the real setup, allow operational headroom and keep the exception desk separate. Then check whether scanning is the slowest part. If bag screening, age checks or the shape of the entrance limits flow, adding ticket scanners won't fix the queue. Review the whole entry plan with the people responsible for those steps.

Check the entry plan on the real site

Take the entry lead through a short rehearsal before you finalise the booking. Start outside the building, not at the scanning table. Show them where the queue is allowed to form, where accessible entry works and which routes must remain clear under the venue plan. Ask the venue who acts if another activity blocks that space.

Then run a few ordinary tickets through the process. Include someone who has the wrong email open, a buyer arriving separately from their group and a person who needs assistance. You're checking whether each person knows where to go, rather than trying to prove a best-case scan speed. A rehearsal in a quiet office can hide problems with glare, noise, signage and connectivity at the actual door.

Agree what the entry team does when the queue changes. Who watches its length and reports it? Who can move available relief to the door? Who talks to security if the screening queue is growing? Who approves a pause in entry if the venue needs one? Those decisions belong in the shared entry plan, with the responsible people involved.

It's also worth checking the end of the arrival window. If you plan to release most of the door crew, define who stays for late buyers and when admission closes. Tell that person what to do when a ticket holder arrives after a session starts. Otherwise, the savings you planned at entry may turn into repeated interruptions inside the room.

Plan the transitions as carefully as the sessions

At a multi-room conference, the busiest moment may be when every session finishes together. People ask directions, visit refreshments and try to enter the next room while a speaker is still packing up. Position floor cover for that period and make sure rooms are released for entry before staff direct people inside.

If one session is likely to attract more demand than its room can accommodate, decide the response beforehand with the venue and program team. The assistant at the door needs a clear capacity limit and an approved alternative. They shouldn't be expected to improvise extra seating or open another space. Track the questions people ask repeatedly; a sign or an attendee message may remove avoidable work before the next transition.

Staffing a large or complicated event

As your site gets bigger, organise the team around departments and zones so people have a supervisor they can reach. There isn't an attendance number that automatically requires a particular command structure. Complexity, risk and the arrangements agreed with emergency services matter more.

FEMA's special-events contingency planning course explains how an Incident Command System can support response to an incident at a special event. That's a shared structure for coordinating decisions and resources. If your partners use it, agree how your event team works with them. Calling your ordinary event director an incident commander doesn't give them authority over public emergency services.

Make zone and supplier responsibility explicit

For an outdoor festival with several stages, you might have separate leads for entry, stages, site operations, transport and guest services. Each needs a defined area, staff assignments and a route to event control. Security and medical providers need their own professional supervision, with clear contact arrangements into that event structure.

Mark boundaries on the site plan. If the shuttle queue is beyond the main gate, decide who monitors it and who acts when it grows. If a sponsor activation creates a queue near a circulation route, agree who can pause the activity. A supplier isn't automatically responsible for everything happening outside its stand, and your crew shouldn't assume another department can see the problem.

At department level, appoint deputies who can carry out real decisions rather than simply relay messages. A lead who works every show minute and every overnight changeover becomes a single point of failure. Your cover plan needs to work while that person is resting or dealing with an incident elsewhere.

Ask the medical provider to recommend provision using the event's audience, duration, conditions, access and risk assessment. Previous patient demand can inform that professional assessment, but a generic patient rate isn't enough for an organiser to calculate a clinical team. Confirm treatment locations, how staff summon help and how emergency vehicles reach the site.

For security and crowd management, agree duties, deployment and any required qualifications with the provider, venue and relevant authority. Check who monitors density and circulation, who controls admission and who has authority to stop an activity. Your ordinary ushers need a clear reporting role rather than an assumption that they'll manage a difficult situation themselves.

Outdoor staffing also needs a weather decision plan. The US National Weather Service recommends that organised outdoor activities have a lightning safety plan, including who monitors conditions and decides to stop. Its guidance cautions against giving weather monitoring to someone already occupied with running the activity.

Apply that separation to your event. Name a competent monitor, agree the provider and authority input you need, and document who authorises a pause, sheltering or reopening. Production needs enough notice to stop work, floor staff need approved instructions for attendees and security needs to protect access routes. Check that proposed shelter is suitable; an ordinary rain cover should never be assumed to provide lightning protection.

Crowd-manager rules vary by location and venue. Massachusetts has specific requirements for certain licensed assembly venues; they are not a universal event staffing ratio. Confirm the rules and approved occupancy that apply to your own site. Its Crowd Manager requirement overview is a starting point for the Massachusetts requirements, rather than a substitute for checking your event with the relevant authority.

Brief the team on decisions they will actually face

A good briefing lets someone act when the event stops matching the plan. Reading the whole operating manual aloud won't do that. Send role information before the shift, then use the on-site briefing to show people their location, supervisor and escalation route. Leave time for questions and a quick practice.

• Walk the areas relevant to each role, including accessible routes, exits and places where public access is restricted.

• Test how staff contact their supervisor and how they summon emergency help. Practise giving a precise location using the same names as the site map.

• Explain admission exceptions, complaints and payment questions. Set out what the staffer can decide and which person approves anything beyond that.

• Rehearse a realistic disruption for each team. Entry might practise a ticket that won't scan; floor staff might practise a room change under the agreed procedure.

• Confirm specialist instructions with the responsible provider. General staff report concerns and follow the event plan; technical, medical and security tasks remain with appropriately trained people.

Formal training depends on the role and local requirements. Don't assign a bundle of emergency-management courses to every temporary worker simply because your audience crossed a size band. A team lead may benefit from planning training while a door assistant needs competent instruction for their actual task. Check that required certifications are current, and that training includes the venue arrangements rather than stopping at a certificate.

Test whether the briefing was understood

Ask a staff member to explain their first task back to you. Then give them a simple situation from their role. A ticket doesn't scan and the queue is building. A guest reports that a route is blocked. A speaker asks to change the room. You want to hear the action, the person they contact and the limit of their authority. If they can repeat the presentation but can't answer that, the briefing needs another pass.

A useful radio report starts with who is calling and where they are, then says what help is needed. "Entry desk to entry lead, a buyer needs an admission decision" gives the lead a task. A long public discussion of the buyer's personal details does not. Agree plain location names and keep sensitive details off open channels. Don't invent codes that new staff have to decode under pressure.

Give the team a place to find the current instructions after the briefing. That could be a printed role card or a shared document they can reach on site. Mark the version or issue time and tell leads how changes will be confirmed. When a decision affects several teams, get an acknowledgement from each relevant lead rather than assuming a message in a busy chat was read.

Keep the final briefing separate from last-minute recruitment. Someone arriving just as doors open still needs the instruction and checks required for their role. Assign a supervisor to induct replacements so the rest of the team can continue opening the event. If no one can do that, the replacement isn't yet usable cover.

Accessibility deserves more than a line at the end of the briefing. In the US, the Department of Justice's effective-communication guidance explains the need to communicate effectively with people who have communication disabilities and highlights staff training. Ask what support is needed, arrange appropriate services and tell frontline staff how to obtain them. A general guest-services worker shouldn't be presented as a substitute for a qualified interpreter or other specialist service.

Use the event logistics checklist to assign an owner and deadline to setup, entry and teardown tasks before you brief the team.

Use ticketing tools to reduce avoidable door work

Your staffing software, ticketing system and communications equipment do different jobs. Choose each for the problem you need it to solve. A roster tells you who is working. Ticketing access lets the right person handle admissions. A radio or phone gets a message to someone. Having all three installed doesn't mean the team has rehearsed the handoff.

Loopyah's ticketing tools let you give door staff check-in access so they can scan QR tickets on their own phones. You can add event team members without sharing your login. That connects the person doing the work to the access they need, while keeping broader administration with the appropriate team members.

Set up those permissions before the event and practise with the real devices. Check charging, venue connectivity and the admission process you intend to use. Agree the supported contingency with your provider and venue rather than assuming a tool works offline or that a shared screenshot is a complete backup. Keep private buyer information away from general staff chats.

When a ticket problem reaches the exception desk, record enough to resolve it without making the buyer repeat the story. Staff need to know who can approve admission, amend an order or handle a refund query under your policy. Technology removes repetitive steps; your team still needs authority and a clear response when the usual flow doesn't work.

For ticketing, attendee messaging and seating, Loopyah's event software connects the attendee information your team uses. Keep crew scheduling and staff communications in the tools you have selected for those jobs.

If you also need to review your promotion tools, see Event marketing tools. Use the event planning checklist to check when each staffing task needs to be ready.

Budget staff hours before you approve the roster

A roster can look affordable because it only shows the hours the public is inside. Price the whole assignment. Include briefing, setup, required checks, breaks and relief, close-down, and whatever minimum calls or overtime terms apply to your hires. Ask suppliers to make those assumptions visible in their quotes.

For an illustrative calculation, five staff booked for six paid hours each means 30 paid hours. At an assumed $25 an hour, that's $750 before any other applicable costs. Those figures are invented planning inputs, not wage guidance or a market rate. If the same five people are needed for an extra hour of briefing and close-down, the calculation becomes 35 hours and $875. The extra $125 was part of the job all along; leaving it out of the budget doesn't remove the work.

Now add actual employer costs, agency charges, travel, meals, training and any relevant taxes or insurance with your finance adviser or supplier. Confirm applicable pay and break rules locally. For a fixed supplier package, check what happens if the event overruns and who must authorise an extension.

Combine compatible work before cutting a post

When you need to reduce the labour bill, start with the schedule and program. Could deliveries arrive in an agreed window so someone isn't waiting all day? Could fewer concurrent rooms reduce technical coverage? Would clearer pre-event directions reduce routine questions at entry? Those changes remove work or prevent overlap.

Then review role sharing against the time plan. It may be reasonable for a trained entry assistant to help pack materials after admissions close. It isn't reasonable to count them as available for pack-down while they still cover the only open entrance. Keep required safety provision and essential service posts covered. A lower bill that depends on someone missing a break or leaving a required post is an incomplete budget.

Hire for the task, and agree the terms clearly

Write job briefs around the actual work. "Friendly event staff" doesn't tell an agency whether you need ticket scanning, speaker liaison, queue direction or someone authorised to handle difficult admission queries. Specify the venue, reporting time, expected finish, physical requirements, equipment, supervisor and skills needed. Describe support and reasonable adjustments through the appropriate hiring process.

Ask who is providing staff supervision and what happens if someone doesn't attend. With an agency, confirm the replacement process, contact number and realistic response time. With freelancers, confirm availability and terms in writing. For roles that require licences or qualifications, check the documents relevant to your location and task rather than accepting a general assurance that the person has worked events before.

Volunteers need a separate decision. Don't treat unpaid labour as the automatic solution to a commercial event's staffing budget. The US Department of Labor's guidance on nonprofit volunteering distinguishes qualifying charitable service from commercial activity and sets limits even within nonprofits. Check the employment position for your organisation and jurisdiction before offering free admission in return for work. A job title or a willingness to help doesn't settle worker status.

Choose returning staff deliberately. Someone who knows the venue may need less orientation, but they still need the current instructions. Tell them what changed since the previous event so familiarity doesn't turn into confidently following an old plan.

Ask suppliers to confirm the gaps between their teams

Before accepting quotes, compare the actual duties in each one. Your venue may provide building security while your contractor handles event screening. Your technical supplier may operate the stage while the venue controls power access. Those divisions can work well, but someone needs to confirm where responsibility changes and how the teams contact each other.

Hold a short planning conversation with the leads who will be there. Ask each one what they need from the others before they can start work. A technical crew might need an empty room and a confirmed loading slot. The entry team might need barriers placed and ticket permissions tested. Record those dependencies in the operating schedule so an early delay doesn't surprise everyone later.

Check names as well as company names. "The venue will handle it" isn't useful to a temporary staffer holding a radio. Name the on-duty venue contact, their deputy and the route for urgent requests. If the supplier changes the lead before the event, update the sheet and repeat the relevant briefing.

Don't make informal additions to a crew member's job during the event without checking with their supervisor. The person being helpful may be leaving a required task, working outside their competence or creating extra chargeable hours. A clear request through the lead protects the relationship as well as your budget.

Schedule breaks, relief and shift handovers

Your staffing plan should name the person covering each essential post during a break. If the answer is always the event lead, check what the lead must stop doing to provide that cover. Relief that exists only when everything is quiet disappears exactly when the team needs it.

Stagger breaks around the actual demand pattern and applicable requirements. Confirm the arrangements with staff and suppliers before the day. At a long event, allow for fatigue when you assign driving, equipment work and public-facing duties. Don't plan a busy day on the assumption that a late finish has no effect on the following shift.

For a shift change, give the incoming person the current situation rather than the whole history. What is open? Which equipment has a problem? Is a guest waiting for a decision? What changed in the program? Record the next action and its owner, then have the incoming person confirm they've taken over. Keep sensitive incident and personal information in the appropriate restricted record.

Your plan also needs a no-show response. Decide which discretionary work can pause, who can provide trained relief and when a supplier must replace someone. If absence removes essential cover, the relevant activity may need to wait. Don't quietly dilute the plan and hope the gap goes unnoticed.

Review what happened before booking the next crew

After the event, compare the plan with the work people actually did. Ask each lead where cover was missing, where staff were waiting without useful work and which questions kept reaching the organiser. Review arrival records and reported queues in context. Fast scanning doesn't prove entry worked if security screening was congested further outside.

Check paid hours against the booked schedule and investigate overruns. Was the crew slow to clear the room, or did the venue release the loading route late? Did a lack of authority turn routine ticket problems into long conversations? The right fix may be a clearer policy or supplier agreement rather than more staff.

Record specific changes while the event is fresh. Replace "need more people" with the post, period and task that lacked cover. Keep safety and incident reviews with the responsible specialists, including near misses and changes they recommend. When you return to the roster for the next event, you'll have evidence for the hours you keep and the ones you change.

Build the final staffing sheet

Before confirming your hires, make one sheet your leads can actually use. List each post, its location and hours, the named person, required skills, supervisor and relief cover. Add the contact method and the decisions that need escalation. Link the current site plan and operating schedule so staff aren't working from conflicting versions.

For example, a line on the sheet might read: entry exception desk, main lobby, arrival window through admission close, named assistant, reporting to the entry lead. The role note would say that the assistant checks order details and routes admission decisions to the lead. The relief field names the trained person taking over during a break. Use your actual times and names when you fill it in.

That is more useful than writing "registration team" beside the whole morning. It tells the assistant what they own, tells the lead where a problem will arrive and exposes whether the relief person is already committed elsewhere. Give each essential post the same treatment. Then let the department leads check the sheet against their own bookings, including venue staff and contractors, so you don't count the same person twice under different job titles.

Keep the sheet short enough to consult during the event. Detailed supplier instructions and specialist plans can stay in their proper documents; the staffing sheet should tell the person holding it where the current instruction is and who can answer.

Walk that sheet through the busiest period with your venue and leads. If a buyer needs help, a room change is announced and someone takes a break at the same time, does each job still have an owner? Resolve those clashes while you can still change the booking.

Then confirm the roster, access and briefing arrangements with the people doing the work. Your event team should know where to report, what they own and who will answer when they need a decision. That's the preparation that makes a lean crew credible.