What is a Event Security Agreement?

It is used by security and staffing providers and event organisers who want the terms recorded before work starts or money changes hands, rather than reconstructed from memory afterwards. Putting it in writing is what turns an understanding into something either side can rely on.

There are 19 fields here, grouped into 6 areas — parties and contact details, scope and deliverables, payment and financial terms, dates, timing and duration, event logistics, and legal protections and risk. Each is a term that causes argument when left unstated, which is why the generator asks for it rather than leaving a gap in the document.

The recurring failure in this kind of arrangement is cover short on the night with no penalty agreed for it. Events have a hard deadline and no second chance. The clauses that matter are the ones dealing with cancellation, postponement, final numbers and what happens if a supplier fails to appear.

The preview updates live as you complete each field, so you can review the exact language before downloading it as PDF or Word. Treat the result as a well-organised first draft: sound in structure, but worth an attorney's review where the sums involved are significant or the situation is unusual.

What matters most in a event security agreement

Minimum call-out hours

Staffing agreements normally carry a minimum booking period. State it, along with the overtime rate.

Incident reporting

Require written incident reports, which matter for insurance and any subsequent claim.

Security personnel must be licensed

Door supervisors and security staff require licensing in most jurisdictions. Confirm current licences before the event.

When you need a event security agreement

  • When the incident reporting and insurance position has value: Where something is still owed after the end of the event, that obligation needs its own words. Anything expected to survive the end of the agreement has to say so.
  • When you already have the agreed staffing plan and licences held: If there is a brief, plan, specification or schedule, attach it. An agreement that refers to a record nobody has attached is only half a record.
  • When money changes hands: Record what the organiser owes, when each staffed shift falls due, and what follows a late payment. These are the clauses relied on most often and left vague most often.
  • When the parties are in different places: Naming the governing law and the forum in advance prevents a costly preliminary fight about where any dispute is even heard.
  • When more than one person is involved: Where several people share the obligation, the event security agreement should say whether they are liable together, separately, or both. That single word decides who can be pursued for the whole amount.
  • When the counterparty is new to you: With no track record between the parties, the written terms do the work that familiarity would otherwise do. That is exactly when precision pays for itself.

What to include in a event security agreement

This generator collects 19 details. Here is what each group covers and why it matters when the document is relied on.

Parties and contact details

Everything else in the document hangs off these names: the supplier carries the obligations, the organiser carries the payment, and both need identifying precisely enough to be found later.

Client Name
The full legal name of the client commissioning the work. Use the registered company name rather than a trading name so the party is identifiable if the agreement is ever enforced.
Client Address
The client's registered or principal business address. This is the address used for formal notices, invoices and any legal service of documents.
Vendor Name
The supplying business's legal name as it appears on its invoices and registration.
Vendor Address
The vendor's business address for purchase orders and notices.

Scope and deliverables

This is the section that decides arguments. Describe the event operation in staffed shifts and against the agreed staffing plan and licences held, so that whether it has been delivered is a question of fact rather than opinion.

Description of Services
What the provider will actually do, described specifically enough that a third party could judge whether it was delivered.

Payment and financial terms

Payment terms are relied on more often than any other clause and left vague more often than any other clause. State the amount, the trigger, the deadline and what follows a late payment.

Total Fee
The full amount payable, broken into deposit and balance so both sides know exactly what falls due and when.
Deposit
The upfront amount securing the booking, and whether it is refundable. Say plainly what happens to the deposit on cancellation.
Payment Schedule
When each payment falls due, tied to dates or milestones. A clear schedule is the most effective protection against slow payment.

Dates, timing and duration

Where the supplier depends on the organiser for something, say what happens to these dates when it arrives late. Otherwise the delay attaches to the wrong party.

Effective Date
The date the agreement takes effect. This can differ from the signature date, and it is the date obligations start running from.
Event Date
The date of the event, including the year. For multi-day events list each date covered.

Event logistics

Access times, headcount and setup windows are what suppliers commit their own costs against. Fix the deadline by which each is confirmed.

Event Type
The kind of event, which drives staffing, licensing and insurance requirements.
Event Location
The venue name and full address, plus the specific rooms or areas being used.
Guest Count
The expected number of attendees and the deadline for confirming final numbers, since pricing usually depends on it.
Setup Time
Access times for setup and breakdown. Venues frequently charge for overrun, so agree the window in writing.
Performance Hours
The exact hours of performance or service, and the rate for overtime beyond them.
Cancellation Policy
The refund position at each stage before the date. A sliding scale tied to notice given is fairer and more enforceable than a flat no-refund rule.

Legal protections and risk

Naming the governing law and the forum here avoids a preliminary fight about where a dispute over the event operation is even heard.

Force Majeure
Which extraordinary events excuse performance. Post-2020 clauses commonly name epidemics and government orders expressly rather than relying on general wording.
Insurance Requirements
The cover each party must carry, the minimum limits, and whether the other party must be named as an additional insured.
Governing State
The state whose law governs the agreement. Choose a state connected to the parties or the work, as a wholly unconnected choice may not be respected.

Completing this event security agreement

Defining the end of the event

Say what has to be true for the end of the event to have happened and who confirms it. An undefined completion test is the reason obligations sit open long after the work is finished.

Planning around cover short on the night with no penalty agreed for it

Since this is the common failure in this kind of arrangement, decide now who absorbs it. A clause of two sentences here is worth more than a page of general good intentions.

Signing and keeping it

Every party named should sign and date, and each should keep their own copy. Electronic signatures are valid for the great majority of agreements — retain the audit trail showing who signed and when.

Filling in every blank

Unfilled placeholders are read against whoever produced the document. If a field genuinely does not apply, write "not applicable" rather than leaving a gap.

Getting the numbers right

Write key figures out in full where the amount is central, and state the currency if either party is outside the country. Both are cheap precautions against an expensive misunderstanding on a event security agreement.

Common mistakes to avoid

  1. No cancellation scale. A single cancellation figure is rarely fair or enforceable. Tier it by how far out the cancellation falls, since that is what actually determines the loss.
  2. Overlooking third-party consents. Where a landlord, lender, insurer or regulator has to agree, get that consent before the end of the event rather than assuming it will follow.
  3. No cap on liability. An uncapped exposure on a modest fee is a bad trade for the supplier. Set a cap that reflects the real value at stake, and carve out the things that should never be capped.
  4. Signing before the agreed staffing plan and licences held is settled. The agreement leans on the agreed staffing plan and licences held, so that needs to be confirmed and attached at signature rather than promised for later. A contract pointing at something nobody has produced yet is an agreement to agree.
  5. No dispute step before litigation. A short escalation clause — a conversation, then mediation, then proceedings — resolves most disagreements far more cheaply than starting at the end.

How to use this event security agreement generator

  1. Fill in the form. Enter the 19 details requested. Where an entry depends on a count — staffed shifts, dates, amounts — put the number in rather than a description of it. Nothing is sent to a server — the document is assembled in your browser.
  2. Read the preview. Read the preview as though you were the organiser rather than the supplier. Anything ambiguous is easier to fix now than to argue about after the end of the event.
  3. Download and sign. Take the PDF for signing or the Word version for further edits. Make sure the signed copy reaches everyone named, since a document held by only one side is hard to rely on.

Event Security Agreement — frequently asked questions

Who is liable if a guest is injured by event security?

It depends on employment status and whether staff acted within their authority. Where security is supplied by a contractor, that contractor is usually responsible for its personnel — but organisers can still face claims as the occupier responsible for the event. Verify licensing and liability insurance, define the scope of authority in the contract, and require incident reports as a matter of course.

How detailed does the event security agreement need to be?

Detailed enough that someone who was not part of the conversation could read it and tell whether each side has done what it promised. That is the standard a court applies, and it is a useful test to run over your own draft before signing.

What is the most important thing to get right in a event security agreement?

The description of the event operation. Almost every later clause — price, timing, whether the end of the event has been reached — refers back to it, so an imprecise description there weakens the whole document. State it in staffed shifts and attach the agreed staffing plan and licences held rather than relying on a general description both sides read differently.

Which state's law should govern this event security agreement?

Choose a state with a genuine connection to the parties or the subject matter — where a party is based, or where the work or property is located. A choice with no connection at all may not be respected, and for property or employment the local state's rules will often apply regardless of what the contract says.

What makes a cancellation policy enforceable?

It has to reflect genuine loss rather than operate as a penalty. A sliding scale — non-refundable deposit, then an increasing share of the balance as the date nears — mirrors the real cost of turning away other bookings, which is why it holds up far better than a blanket no-refund rule.

What does the force majeure clause actually cover?

Only the events it names. General wording about circumstances beyond a party's control has been read narrowly by courts, which is why clauses written since 2020 tend to list epidemics, government orders and venue closures expressly. Add the specific events that would realistically stop performance in your situation.

What happens if the venue becomes unavailable?

This is what the force majeure clause is for. Say expressly whether the fee is refunded, held against a new date, or partially retained to cover work already done. Name venue closure and government restriction as triggers rather than relying on generic wording.

When is the final guest count due?

Typically seven to fourteen days before the event. Fix the date in the contract and state that numbers may be increased after it subject to availability, but not reduced. Suppliers commit to staffing and stock based on that figure.