The Pre-Shift Briefing Most UK Events Can't Prove Happened
Under the Green Guide, a steward who hasn't been briefed isn't a deployable steward. Most events fall short of the standard. Not because they cut corners. Because the workflow doesn't exist.
The pre-shift briefing is among the most legally exposed processes in UK event workforce management. It is also one of the most poorly documented. A safety officer at a typical festival can describe the briefing they delivered. They cannot, in many cases, produce the record that proves it happened, what it covered, who attended, or whether the steward confirmed they understood it. After an incident, that gap matters.
This post sets out what UK regulators actually require of pre-shift briefings, why the existing tooling (mostly WhatsApp and clipboard sign-in sheets) doesn't meet the standard, and what a defensible workflow looks like.
The legal definition of a deployable steward
The SGSA Green Guide is the foundation document. It defines a steward as someone who has achieved (or is undergoing assessment for) the Level 2 Certificate in Spectator Safety, is employed or contracted by the venue or event organiser, and is "appropriately attired, equipped, and briefed".
That last condition is doing a lot of work. "Briefed" is not aspirational. It is one of three formal criteria for legal deployment. A steward who has Level 2, has been issued kit, and has shown up but has not been briefed does not satisfy the definition. They cannot be deployed.
The SGSA Stewarding Factsheet 3 reinforces this. Factsheet 7 (updated January 2024) goes further: it places direct responsibility on ground management to brief all personnel involved in safety management.
Beyond the SGSA, the National Occupational Standard SKASS7 (Prepare Stewards and Venues for Spectator Events) is the documented competence framework against which stewarding supervisors are assessed. It requires supervisors to "assign the required number of stewards with the appropriate skills for the designated area" and to "brief additional deployments and late arrivals in accordance with the original briefing". That last phrase matters. Late arrivals are not exempted. They must receive the same briefing as the cohort that arrived on time.
For events at licensed premises, the SIA licensing boundary adds another layer. A steward directing crowds, providing information, or assisting with egress does not need an SIA licence. The moment they search bags, refuse entry on behavioural grounds, or physically intervene, they are carrying out a licensable activity. The SIA conducts compliance operations at events across the UK. Both the individual and the deploying organisation can face criminal prosecution for placing unlicensed staff into licensable roles.
The takeaway is structural. Deployment is not a question of "I sent them to a post". It is a question of whether the steward, on that post, at that moment, satisfied every relevant compliance criterion. Briefing is one of those criteria.
What the briefing must cover
Factsheet 7 specifies what a briefing must include. The list is not optional:
- Event type and timings
- Details of key safety, security, and medical personnel
- Any activities before or after the event
- Any security concerns
- VIP or special guest details (where appropriate)
- Any operational factors that may differ from previous events. Weather, ticketing, access changes, crowd-flow modifications.
That last point is the change-of-plan scenario. It is the most common failure mode in real-world stewarding. The original briefing covers the planned event. The day-of-event reality includes a wind shift, a delayed ticket gate opening, an unannounced VIP arrival, or a crowd-flow change. The briefing has to be re-armed. The understanding-check has to be re-run. The record has to capture both.
That second pass is where most operations break.
The understanding check
NOS SKASS7 requires supervisors to "check the stewards' understanding of the briefing". This is not a formality. It is a documented competence requirement. A supervisor who has briefed a cohort but has not confirmed comprehension has not, by the standard, completed the briefing.
In practice this means the briefing is a two-party event. The supervisor delivers. The steward acknowledges. Both halves have to be captured for the record to be defensible.
Local authority Event Safety Management Plan templates, used by councils across England and Wales for licensing decisions, take this further. The Tewkesbury Borough Council ESMP guidance, broadly representative of the templates in use elsewhere, recommends that "stewards sign a sheet after they have been read the briefing to say they have understood it". And that "a full stewards briefing should be written down and attached as an appendix to this event plan".
Note the language. "Sign a sheet". "Written down". "Attached". These are operational instructions to event organisers seeking permits. They are not theoretical.
Cascaded briefings: the over-50 problem
For deployments of fewer than 50 personnel, a single group briefing by the Safety Officer or Chief Steward can satisfy the standard. Above 50, the SGSA guidance is explicit. Cascaded briefings become necessary. The Safety Officer briefs supervisors. Supervisors brief their sections.
The factsheet adds: "It is recommended that these cascaded briefings should be scripted so they are consistent. This also provides a note which will form part of the event's record".
Three things in that sentence. Scripted. Consistent. Recorded. A cascaded briefing where every supervisor improvises their own version, off the cuff, with no script, is not a scripted briefing. It cannot be demonstrated as consistent. And there is no note for the record.
For a festival with 200 stewards across 8 zones, this is the largest single source of regulatory exposure. The briefing happens. Each supervisor delivers a version of it. None of those versions is identical. None is recorded. Post-incident, when an inquiry asks "what was the steward at Gate 4 told?", the answer is a paraphrase. Paraphrases are not records.
The record-keeping requirement
Factsheet 7 is unambiguous. "Records of all briefing and debriefing sessions must be kept and maintained as part of the Event Record". The records serve three documented purposes:
- To help refine and improve briefing content and delivery over time.
- To form a record for legal purposes, should a serious incident occur during the event.
- To contribute to the management's periodic safety audit.
Factsheet 8 (Management and HR) specifies what the steward record must include: duties and positions for each event, briefing and debriefing sessions attended, and assessment of progress. It adds that such records "should be readily available".
The HSE's Event Safety Guide (the Purple Guide) goes further. It notes that event logs and records "may be required at a later date to assist in the reporting of accidents and injuries". In post-incident investigations by HSE, police, coroners, or public inquiries, the questions are predictable: who was briefed, by whom, on what topics, at what time, did they acknowledge receipt? An immutable, timestamped audit trail is what answers those questions. A signed paper sheet that may or may not be locatable does not.
A defensible record, by definition, captures: the identity of the person responsible, a timestamp, the content delivered, the steward's acknowledgement, and sufficient context to reconstruct what was understood. Records must be appended only. Never altered, backdated, or deleted. The before-state matters as much as the after-state. Without it, you can confirm something happened but cannot reconstruct the history as it stood at the time of the event.
Why WhatsApp doesn't meet the standard
The widespread use of WhatsApp for shift coordination and briefing distribution in the UK events industry is not a minor procedural irregularity. It is a category of legal liability.
UK employment law analysis published in January 2026 lists the specific risks: lack of a structured audit trail, potential GDPR breaches, loss of institutional knowledge when employees leave, uncontrolled data sharing, and difficulty of disclosure in investigations. Employment tribunal cases citing WhatsApp messages rose from 48 in 2019 to 562 in 2024. A twelve-fold increase in five years. Regulators and courts are increasingly treating informal platform communications as formal evidence, and finding the evidence wanting.
For pre-shift briefings specifically, the WhatsApp problem has four dimensions:
- Chronology cannot be reconstructed reliably. Messages can be edited or deleted. Read receipts are unreliable.
- Identity of the briefer is ambiguous. A group message from "Ops" doesn't satisfy the SGSA "by whom" requirement.
- Acknowledgement is implied, not captured. A thumbs-up emoji is not an attestation of understanding.
- Disclosure is difficult. Messages live on personal devices that the organisation does not control.
A briefing record on WhatsApp, in short, gives the impression of compliance without actually meeting the standard. After an incident, that gap is the difference between a defensible position and an indefensible one.
Martyn's Law: a 2027 layer on top
The Terrorism (Protection of Premises) Act 2025, also known as Martyn's Law, received Royal Assent on 3 April 2025. Implementation begins in May 2027 after a two-year transition period. The Act applies to premises with a capacity of 200+ persons, with a more demanding "enhanced tier" for premises at 800+. Enhanced-tier venues must appoint a senior manager responsible for compliance.
For event workforce management, the implications are direct. Industry analysis published in April 2026 sets out the new baseline expectation: "auditable rosters linked to SIA licence checks, documented risk assessments and briefings per event, real-time incident tickets". The direction of travel is clear. More documentation, more traceability, tighter supply-chain scrutiny.
Martyn's Law also introduces a new training requirement: staff threat awareness and emergency response. That is another category of training record to maintain, verify per deployment, and surface in audit. The training-status visibility that today is a Green Guide and SGSA expectation will, from May 2027, be a statutory obligation.
In short, the briefing-and-record stack tightens, not loosens. Operations that are already running on WhatsApp and clipboards will not pass the new bar. The two-year window between now and May 2027 is the window for re-architecting the workflow, not for hoping the regulator will be lenient.
The five-question audit
Any UK event operations team can run this audit on their own next event. Pull last weekend's event record. Try to answer:
- Who was on every post at 19:00 on event day?
- Were they briefed before deploying?
- By whom? On what topics?
- Did they confirm they understood?
- Where is the record?
The answer should be available without a forensic search. If it isn't, the gap isn't operational. It is regulatory. And it is the gap that, after an incident, will determine whether your operation is defensible.
The good news is that the standards already tell you what a defensible record looks like. Briefing content captured per session, by whom and to whom, with steward acknowledgement, timestamped, immutable, and readily available. Cascaded briefings scripted for consistency. Late arrivals briefed in accordance with the original. Material changes re-armed and re-attested.
The bad news is that none of this works on WhatsApp.
How SafetyDocs Shifts handles each layer
SafetyDocs Shifts is built specifically for the briefing-to-attestation workflow these standards describe.
The eligibility grid colour-codes every steward against current credentials, so the supervisor cannot allocate someone to a post they are not qualified for. The briefing is delivered as a structured payload, scripted for consistency across cascaded supervisors. The steward acknowledges with a hashed, timestamped, two-party attestation that captures understanding. Late arrivals receive the same briefing through a single-steward attestation path. Material changes during the event re-arm the briefing for affected stewards, with fresh attestation captured for the record.
Every change writes back to the SafetyDocs ECM. Records are immutable. The audit trail is complete and readily available, for a periodic safety audit, an SIA compliance check, or a coroner's request after an incident.
It is, in short, the workflow the standards describe. We built it because the standards are not optional, and the existing tooling does not meet them.
If you are running a festival, an arena, or a venue with a public capacity over 200, and especially if you are over 800 and looking at Martyn's Law enhanced-tier compliance, Shifts is worth a conversation.
References
The regulatory and industry sources cited in this post:
- SGSA Green Guide, Stewarding Factsheet 3 (Role and Duties), Factsheet 7 (Briefing and Debriefing, updated January 2024), Factsheet 8 (Management and HR)
- National Occupational Standard SKASS7, Prepare Stewards and Venues for Spectator Events
- HSE Event Safety Guide (the Purple Guide)
- Local authority Event Safety Management Plan templates (e.g. Tewkesbury Borough Council)
- ESSA UK Industry Survey, November 2025
- MIA February 2025 Insights report
- Liveforce market analysis, March 2026
- Stephens Scown employment law analysis, January 2026 (WhatsApp tribunal data)
- Terrorism (Protection of Premises) Act 2025 (Martyn's Law)
- Coredinate event security analysis, April 2026
