Industry Knowledge
Event security staffing: how guard companies plan a crowd event
Event security staffing for guard companies: how to scope the event, place officers, brief the team, run the day and report back to the client after.

Event security staffing means deciding how many officers a crowd event needs, where each one stands, what each one does, and how the team talks and reports during the day. For a guard company, a good event plan has six parts: a clear scope from the client, a post map, a staffing roster with backups, written post orders, a briefing, and a report after the event. This guide walks through each part for holiday markets, parades, concerts, games and corporate events.
Key points#
- Start with the client's written scope: dates, hours, expected crowd, entrances, and what the client wants officers to do and not do.
- Build a post map before you build a roster, so every officer has a named post, a task and a relief plan.
- Write event post orders for each post, and get every officer to read and confirm them before the event.
- Brief the whole team in person on the day, and keep one clear chain of command for radio calls.
- Close the event with a written report for the client: hours worked, incidents, and what to change next time.
Step one: get the scope in writing#
Most event problems start with a vague request. "We need some guards for the market" is not a scope. Before you quote or schedule, ask the client for:
- Dates and hours, including setup, opening, closing and teardown.
- The expected crowd and how it changes through the day.
- Entrances and exits, with a site map if one exists.
- Duties: bag checks, ticket checks, wristbands, crowd flow, stage or backstage access, cash escort, parking, patrols of vendor stalls.
- Limits: what officers must not do, such as touching guests, holding people or entering certain areas.
- Other teams on site: police, fire, medical, the venue's own staff, other contractors.
- Contacts: the client's on-site lead and a backup, with phone numbers.
Put the answers in your contract or event agreement. If the client changes the scope later, you have a record to price and staff against.
Step two: draw the post map#
A post map is a simple drawing of the site with every post marked. Mark each entrance, each fixed post, each roving patrol route, the command post and the first aid point.
For every post, decide:
- what the officer does there,
- whether it needs a supervisor nearby,
- whether it needs a radio, a flashlight, a vest or other gear,
- who relieves the officer for breaks.
Entrances and exits usually need the most attention because that is where crowds bunch up and where screening happens. Roving officers fill the gaps: they watch for crowding, lost children, medical problems and arguments before they grow.
Step three: build the roster and the backups#
Only now turn the map into a roster. Each post becomes one or more shifts, and each shift needs a named officer. Then add:
- Relief officers who cover breaks so no post goes empty.
- A supervisor for each area, who knows the plan well enough to make calls on the spot.
- Backups on call for officers who cancel or do not show up.
Check licenses and training before you assign anyone. Some events need officers with specific state licenses, crowd management training or first aid. A scheduling tool that flags clashes and approved time off saves you from double-booking officers who already work a regular site that day.
Step four: write event post orders#
Regular post orders describe a site that stays the same every day. Event post orders describe a site that exists for a few hours. Keep them short and specific:
- The post and its task, in one or two sentences.
- What to allow and what to refuse, for example bag sizes, re-entry, outside drinks or drones.
- How to handle refusals: what to say, when to call a supervisor, and when to step back.
- Emergency steps: lost child, medical call, fire, severe weather, evacuation route, and a suspicious item.
- Who to call: the supervisor's radio call sign and the client's lead.
Send the post orders before the event, and have each officer confirm they read them. On a busy day there is no time to explain the rules post by post.
Step five: brief the team on the day#
Hold a short briefing before doors open. Cover the map, the timeline, the chain of command, radio channels and call signs, the known risks for the day, and the client's priorities. Hand out post assignments in writing.
Keep radio use simple: short calls, plain words and one person in charge of each channel. If police or event staff share the site, make sure your supervisors know who their counterparts are and where to find them.
Step six: run the event and write it down#
During the event, supervisors walk their areas, rotate breaks and watch for posts that are overloaded. Officers report anything unusual as it happens: injuries, ejections, lost children, damage, threats and near misses.
Write incidents up during or right after the shift, while details are fresh. Photos, times and names of witnesses make a report useful. A short incident report taken on the spot is better than a long one written from memory the next day.
After the event: report back to the client#
Within a day or two, send the client a summary: hours worked by post, incidents and how they were handled, and what you would change next time. That report is often what wins the next event. Clients who can see their own reports and time cards in a client portal have fewer questions about the invoice.
Then hold your own short review. Which posts were overloaded? Which officers stood out? What should the post orders say next year?
Common mistakes to avoid#
- Staffing by headcount instead of by post. A number from last year means little if the layout changed.
- No relief plan. Officers who cannot take a break leave posts empty anyway.
- Late post orders. Officers who read the rules at the gate make inconsistent calls.
- Mixed chains of command. If officers take orders from the client, the venue and your supervisor, nobody is in charge.
- No written record. Without reports, you cannot answer a complaint or price the next event well.
Frequently asked questions#
How do I know how many officers an event needs?#
Start from the post map, not from a headcount. Count the posts that must be covered at the busiest time, add relief officers for breaks and supervisors for each area, then add backups. Check any local permit or venue rules that set staffing levels, and ask the client what the venue required in past years.
What should event post orders include?#
Each post needs its task, what to allow and refuse, how to handle a refusal, emergency steps, and who to call. Keep them short enough to read in a few minutes, and have every officer confirm they read them before the event.
Who is in charge at an event, the client or the guard company?#
Agree on this in writing before the event. Most events work best with one security supervisor directing officers, and one client lead who makes decisions about guests and the event itself. Police and fire take charge of emergencies in their own areas.
What should I send the client after the event?#
Send a short report with hours worked by post, a list of incidents and how each was handled, and suggestions for next time. Attach full incident reports for anything serious.
- Events
- Operations
- Scheduling