Documentation & Post-Incident Review
Supervisors turn responsible service into a defensible system through records. This chapter covers documenting refusals and incidents, tracking staff certifications, writing clear house policies, and reviewing incidents to improve.
Documenting refusals and incidents
When staff refuse service to an intoxicated guest or a minor, or when an incident occurs, they should record it in an incident log or report: the date and time, the reason for the refusal (visible intoxication, invalid or expired ID, minor), the actions taken, and any witnesses. This record shows the establishment acted responsibly and is valuable if the incident is later questioned. Recording nothing leaves no proof the right action was taken; publicly naming a guest is inappropriate.
Tracking certifications and policy
Keeping records of who is certified, when they trained, and when their certification expires proves the operation met its training and regulatory obligations and supports its defense in a dram-shop matter. Many certifications expire and must be renewed, so tracking dates matters. A strong written house policy backs this up by spelling out the carding threshold, drink-limit and pacing guidance, refusal procedures, and how to document incidents — so every shift enforces the same standard instead of improvising.
Learning from incidents
A post-incident review examines what happened and why so the operation can strengthen its policies, training, pacing, and monitoring and prevent a repeat. Its purpose is learning and prevention, not simply blaming one server or closing the file, and it has internal value whether or not authorities request it. A supervisor who reviews incidents, updates policy, and re-trains staff closes the loop that keeps responsible service improving over time.