Incident Reporting

How to Build Incident Records That Hold Up at Licensing Review

A Structured Approach to Venue Incident Reporting Approved by Police and Licensing

Most premises licences include a condition requiring an incident log. Few specify what good looks like. Free-text incident books, WhatsApp chats, and notes on the back of a refusals slip do not survive police follow-up or a licensing review. This guide walks through the structure of an incident record that holds up at review, what evidence you need to capture, and how to handle the awkward category of incidents where the original record turns out to be wrong.

See structured incident reporting in Paddl Try the Martyn's Law checker

Key takeaways

Free-text incident books fail at review. Use structured forms with category-driven fields.

Capture police reference, CCTV availability, evidence list, severity, and follow-up at the moment of recording.

Use append-only amendments rather than overwriting records. Tamper-resistant evidence carries far more weight.

A submitted-review-approved workflow provides quality control without compromising the audit trail.

Storing CCTV references against incidents (rather than separately) makes police follow-up dramatically faster.

The categories that matter

Different incident types attract different legal frameworks and different evidence expectations. Working with police licensing officers and prosecutors, the categories that come up most often are: violence and aggression (assault, sexual assault, stabbing, fight or affray, threatening behaviour), crime and security (theft, robbery, fraud, burglary, trespass, vandalism, arson, weapons), drugs and alcohol (drug-related incidents, drink spiking, overdose), health and safety (medical emergency, food tampering), welfare and conduct (harassment, anti-social behaviour, missing person, safeguarding concern), and other (property damage). A good incident report form starts by selecting one of these categories so the rest of the form can adapt: a stabbing record needs different fields from an ejection.

The fields every incident report needs

At minimum a structured incident record should capture: the date and time the incident started, the date and time it ended, the precise location within the venue, the incident type from your category list, a free-text description of what happened, the people involved (with names and contact details where known), witness details, the injury severity (none, minor, moderate, serious, life-threatening), which emergency services were called (police, ambulance, fire, none), the police crime or reference number if assigned, whether CCTV footage exists, evidence collected (CCTV footage, photos, witness statements, physical evidence), the immediate actions taken, whether the area was secured, follow-up required, and a priority classification. Capturing all of this at the moment of recording prevents the gaps that later turn into liability.

The amendment problem

Incident reports are often updated after submission: the police give you a crime reference, a witness comes forward, CCTV is recovered, an injury turns out to be more serious. The wrong way to handle this is to overwrite the original record. The right way is append-only amendments: the original record stays exactly as written, with a timestamped note appended for each amendment showing who added what and when. Licensing committees and courts treat tamper-resistant records very differently from records that have been modified after the fact. A record that has been overwritten loses much of its evidential weight.

Approval and review workflow

Some incidents need management review before they are considered final. A workflow that moves records through submitted, under review, and either approved or requires action provides natural quality control: a junior staff member writes the initial record at 1am, the manager reviews it the next morning, missing fields are completed, and the record is approved or sent back for correction. Reviewers should add notes via the append-only mechanism rather than editing the original. The audit trail captures every decision.

When the police ask

When police investigate an incident, they typically ask for the incident report, CCTV footage, witness statements, and the door supervisor records for the relevant time. A venue that can produce all of this within an hour is a venue that operates well in the eyes of police licensing teams. A venue that takes a week to assemble fragmentary records is not. Make sure your incident records can be filtered by date range, location, type, and police reference number, and that CCTV references are stored alongside the incident not separately.

What to do next

Adopt a structured incident form aligned with police categories

Use a category-driven form that adapts to the incident type. Violence, drug-related, theft, ejections, and welfare incidents each need different fields.

Make amendments append-only

Original records stay locked. Updates become timestamped notes attributed to the staff member who added them.

Tie incidents to door supervisor shifts

Each incident should reference the door supervisor or staff member on duty at the time. This gives police a contact and supports any prosecution.

Store CCTV references alongside incidents

When an incident is logged, capture the CCTV camera number, the timestamp, and whether footage has been preserved. This collapses follow-up time.

Frequently asked questions

What does a venue incident report need to include?

At minimum: date and time, location, incident type, description, people involved, witnesses, injury severity, emergency services called, police reference, CCTV availability, evidence collected, immediate actions taken, and follow-up required. Most premises licences require an incident log but rarely specify the structure. Building a structured form yourself protects the venue at review.

Should I use an incident book or a digital system?

A digital system. Incident books fail in three ways: handwriting can be illegible, pages get lost or damaged, and entries can be amended without an audit trail. A digital system with structured fields, append-only amendments, and exportable date-range reports is the standard licensing committees expect.

Do I need to report incidents to the police?

Some incidents must be reported by law (assault, weapons offences, drug-related deaths, safeguarding concerns). Others are at the operator's discretion but reporting builds the relationship with the local police licensing team that protects you at any future review. Even when you do not formally report, recording the incident in your own log is essential.

How long should I retain incident records?

There is no single legal retention period across all incident types. Practical guidance: retain records for at least seven years to support any civil claim. Where an incident relates to a child or vulnerable adult, retain in line with safeguarding retention policies (often longer). Where an incident has triggered a prosecution, retain for the life of the case plus appeals.

Premises Licence

How a Premises Licence Works for Late-Night Venues

Door Supervision

SIA Door Supervision: What Venues Must Verify Before Every Shift

Capacity & Refusals

Challenge 25, Refusals, and Capacity: The Three Records You Cannot Miss

Keep exploring

Related resources

Need expert help with your HACCP system?

Our hospitality consultants can review your HACCP plan, identify gaps, and help you build a system that satisfies EHO inspectors.

Talk to a consultant

Manage Nightlife Compliance digitally

Paddl helps UK hospitality businesses automate nightlife compliance compliance. AI-generated plans, digital records, and inspection-ready documentation.

Start free trial See Nightlife Compliance features