How to Write an Incident Report That Holds Up at a Licensing Hearing

Incident reports are legal documents. They get read by licensing officers, police, magistrates, and sometimes judges. A poorly written report can undermine your entire case at a licensing review. A well-written one can be the reason your premises licence survives.

Here is how to write incident reports that hold up when it matters.

Why incident reports matter

When a licensing committee reviews your premises licence - whether following a complaint, a police application, or a routine review - they will ask for your incident records. What they are looking for is evidence that you take your responsibilities seriously and respond to problems competently.

Good incident records demonstrate:

• You are aware of what happens at your venue
• You respond to incidents proportionately and promptly
• You learn from incidents and improve your procedures
• You cooperate with authorities

Poor or missing records suggest the opposite. Licensing committees have revoked premises licences specifically because venues could not produce adequate incident documentation.

What constitutes an incident

Log more than you think you need to. If in doubt, record it. Incidents that should always be documented include:

• Ejections - anyone asked to leave or physically removed
• Refusals of entry - especially where aggression is involved
• Assaults - on staff, patrons, or passers-by
• Drug-related incidents - seizures, suspected dealing, individuals under the influence
• Theft and criminal damage - inside or immediately outside your premises
• Medical incidents - injuries, collapses, ambulance calls
• Noise complaints - from residents, council, or police
• Underage attempts - individuals refused service or entry due to age
• Staff conduct issues - relating to licensing responsibilities
• Police visits - routine or incident-related

The anatomy of a good incident report

1. Date, time, and location

Be precise. "Saturday night" is not a date. "Saturday 15 March 2026 at 01:47" is.

Include the specific location within your venue: "main dance floor, near the DJ booth" is more useful than "inside."

2. Who was involved

Record everyone involved, to the extent you can identify them:

• Staff - full name and role (e.g., "Jamie Reid, Door Supervisor, SIA badge #12345678")
• Patrons - description if name is unknown ("Male, approximately 25, wearing a red jacket, approximately 5'10")
• Witnesses - names and contact details where possible
• Emergency services - officer names, badge numbers, ambulance crew identifiers

3. What happened

Write a clear, factual narrative. This is where most reports fail.

Good: "At 01:47, Door Supervisor Jamie Reid observed a male patron (described above) punch another male patron in the face near the DJ booth on the main dance floor. Reid immediately intervened, separating the two individuals. The aggressor was escorted to the front entrance and ejected from the premises at 01:50. The victim declined medical attention but was offered first aid."

Bad: "Fight on the dance floor. Kicked him out."

The difference is admissibility. The first version is a legal document. The second is a note on a napkin.

Rules for writing the narrative

• Use facts, not opinions - "the individual appeared intoxicated" is an observation; "he was definitely drunk" is an opinion
• Use specific times - for every significant action in the sequence
• Describe actions, not judgements - "I observed him staggering and slurring his speech" rather than "he was a mess"
• Include what you did - every action taken by staff should be documented
• Include what you did not do - if you chose not to call police, state why
• Write in the first person if you were involved, third person if you were not

4. Actions taken

Document every response action, with timestamps:

• Who intervened and when
• What de-escalation was attempted
• Whether the individual was ejected
• Whether police were called (and reference number if given)
• Whether an ambulance was called
• Whether CCTV footage was preserved
• Whether the area was secured or cleaned

5. Follow-up

Record any actions taken after the immediate incident:

• Was a banning order issued?
• Was CCTV footage reviewed and preserved?
• Were police provided with a statement?
• Was the individual identified subsequently?
• Were any procedural changes made as a result?

6. Sign-off

Every report should be signed (or digitally authenticated) by the person who wrote it, with:

• Their full name and role
• The date and time the report was completed
• A statement that the report is accurate to the best of their knowledge

Common mistakes

Writing reports the next day

Reports should be written as close to the event as possible. Memory degrades rapidly. A report written at 2am immediately after an incident is more credible than one written at noon the following day.

Courts and licensing committees know this. They will question the reliability of reports completed long after the event.

Inconsistency with CCTV

If your report says the incident happened at 01:47 but CCTV shows it at 01:32, your credibility is damaged. Check your timestamps against CCTV before finalising reports.

Missing reports

Having no record of an incident that police or residents can independently evidence is worse than a badly written report. It suggests either negligence or deliberate omission.

Editorialising

Keep personal opinions out of reports. "This troublemaker got what he deserved" will not help you at a licensing hearing. Stick to observed facts and actions taken.

Inconsistent format

Using a different format every time makes it harder for licensing officers to review your records. Standardise your format so every report covers the same fields in the same order.

Template structure

Every incident report at your venue should follow this structure:

1. Incident reference number (sequential, e.g., INC-2026-0047)
2. Date and time of the incident
3. Location within the premises
4. Persons involved (staff, patrons, witnesses, emergency services)
5. Narrative (factual, timestamped account of what happened)
6. Actions taken (timestamped response actions)
7. CCTV reference (camera number, time range preserved)
8. Police reference (if applicable)
9. Follow-up actions (banning orders, procedural changes)
10. Completed by (name, role, date, time, signature/authentication)

How many incidents should you be logging?

A busy nightclub should expect to log multiple incidents per week. If you are logging zero incidents over extended periods, licensing authorities will question whether you are actually monitoring your venue.

The absence of incident reports does not suggest the absence of incidents. It suggests the absence of a reporting system.

Further resources

• Licensing Act 2003 - the primary legislation for premises licences in England and Wales
• Home Office Revised Guidance issued under section 182 of the Licensing Act 2003 - statutory guidance
• Licensing (Scotland) Act 2005 - premises licences in Scotland

For structured incident logging with timestamps, staff attribution, CCTV references, and audit-ready exports, Holocron provides purpose-built tools for UK nightlife venues. Every incident is timestamped, attributed, and immutable - exactly what licensing authorities expect. Try the compliance assessment to see where your venue stands.