Incident Reports, Records and Team Debriefs

Why Record an Incident?

An incident record helps staff and management reconstruct what happened. Memories fade, employees change jobs and a complaint or lawsuit may arise much later. A timely factual account can support an explanation of reasonable care, identify gaps and help coordinate future action.

A record is evidence, not a guarantee of a successful defence. An unrecorded event does not legally cease to exist: witness testimony and other evidence may still establish it. Conversely, a polished log entry cannot make inadequate service safe or prove an action that never occurred. Documentation should reflect the real intervention.

The course recommends a dedicated incident-report log or system. Establish a clear procedure for which events need reporting, where records are stored, who writes them and who reviews them. Relevant events include refused service, suspected underage purchases, fake ID concerns, injuries, threats, ejections, impaired-driving concerns and other unusual safety issues.

Write While Details Are Fresh

Deal with immediate safety needs first. Once the incident is resolved, make the entry promptly, preferably while observations and words are fresh. Record the incident time and the time of writing if they differ. If a worker did not witness part of the incident, identify the source of that information rather than writing it as a personal observation.

Use concrete descriptions. “The customer swayed while standing and dropped the payment card twice” is more informative than “customer was a mess.” Quote significant statements accurately, and distinguish a direct quote from a paraphrase. Record uncertainty honestly: “approximately 10:20” is better than inventing an exact time.

Avoid diagnoses, insults and speculation about motives. A report can record that a patron stated they had diabetes; staff should not write that they confirmed a medical diagnosis. Likewise, smelling cannabis does not establish when it was consumed or the person’s degree of impairment.

What the Record Should Include

The course advises obtaining statements from at least two unbiased witnesses where possible. Seek their accounts rather than telling them what to write. Lack of two witnesses is not a reason to omit a report. Record who was available and preserve each person’s independent observations.

Worked Incident Entry

“At approximately 22:15, table 8 patron in grey coat stood and stumbled into the chair. Speech was slurred during an order for another beer. I informed manager Patel and declined further liquor service at 22:18. Bartender Lee was notified. Remaining beer was removed without resistance. Patron said, ‘My sister can pick me up.’ With the patron’s agreement, the sister was contacted. At 22:40 I saw the patron leave with her in a blue vehicle; I did not observe arrival home. Witnesses were Lee and customer Morgan, whose contact information is attached.”

This original example distinguishes observation, action and an unverified outcome. Improve it with drink-sale records and further relevant details that staff actually know. Do not add a BAC estimate, a diagnosis or a claim that the sister was sober unless there is a factual basis for the statement.

Preserve Supporting Information

Keep relevant sales receipts, till records, staff notes and witness statements together or cross-reference their locations. If surveillance is relevant, ask the authorized manager to preserve it before routine deletion. Follow the establishment’s privacy and access procedures; an incident report is not a reason to circulate a patron’s personal information casually.

Use a system that protects records against loss and makes later corrections clear. For a paper log, legible permanent entries and identifiable corrections support integrity. For an electronic system, restricted access, dated entries and a record of changes are useful controls. The official course does not mandate a particular cryptographic database, encryption product or notebook binding as the only lawful method.

Never secretly rewrite an earlier account to improve the establishment’s position. If new information becomes available, add a dated supplement explaining its source. Keep the original record and identify the author of each entry.

Retention and Follow-up

The SIR manual recommends retaining incident records for at least six years, allowing for delayed lawsuits. Treat this as the course’s recordkeeping guidance, not a promise that every possible claim expires after six years. Management should follow applicable requirements and preserve records connected with an ongoing complaint or claim.

Notify management after an incident. The manual also discusses informing the insurer when an incident may lead to a claim. Staff should follow the establishment’s reporting procedure so the appropriate person can handle that communication promptly.

Debrief the event with the team. Ask whether observations were shared, the refusal reached all service points, backup was available and the departure plan was practical. Use identified gaps to revise policies, orientation or cross-training. Documentation closes the response cycle by turning an individual incident into a specific improvement.

Sources checked October 9, 2026

Official SIR manual, July 2026; BC Liquor Control and Licensing Act.