---
title: "Documenting an Overservice Incident"
description: "What to record when alcohol service becomes a question: the observations, the pour count and timing, the refusal, the transport offered, and who was told."
url: https://www.docu-coach.com/restaurant-overservice-incident-documentation
markdown: https://www.docu-coach.com/restaurant-overservice-incident-documentation.md
datePublished: 2026-09-12
dateModified: 2026-09-12
pageType: guide
---

# Documenting an Overservice Incident

> What to record when alcohol service becomes a question: the observations, the pour count and timing, the refusal, the transport offered, and who was told.

## Key takeaways

- Document the observable indicators you noticed, the time you noticed them, what the POS shows was served and when, the decision you made, exactly what was said, what you offered the guest, and how they left — without writing a conclusion about how intoxicated anyone was.
- You are not qualified to state a blood alcohol level and nothing in the record should imply that you did.
- Refusals happen weekly in a competent operation and almost never get written down, so the only alcohol-service documents that exist are the ones created after something went wrong.
- A bar with a file full of dated refusals is telling a very different story than a bar with one report from the worst night of the year.
- Reconstructing "how many did she have" from memory at 1 a.
- is the single least reliable thing a manager can put in a record, and the POS already has the answer with timestamps.

Write what you observed and what you did — never a conclusion about how intoxicated anyone was.

## An overservice record is a set of observations and actions

**Document the observable indicators you noticed, the time you noticed them, what the POS shows was served and when, the decision you made, exactly what was said, what you offered the guest, and how they left — without writing a conclusion about how intoxicated anyone was.** You are not qualified to state a blood alcohol level and nothing in the record should imply that you did.

This is the record most bars have none of. Refusals happen weekly in a competent operation and almost never get written down, so the only alcohol-service documents that exist are the ones created after something went wrong. A bar with a file full of dated refusals is telling a very different story than a bar with one report from the worst night of the year.

## What to capture, the same night

| Capture | What good looks like |
|---------|---------------------|
| Time you first noticed | The clock time, not "later in the night" |
| Observations | Specific and physical: speech, balance, coordination, repetition, spillage, volume, interaction with others |
| Who observed | You, the bartender, a server, a security contractor — by name |
| POS tab detail | Every item rung on that tab with times and the server or bartender ID. Export it |
| Known gaps | Drinks bought by others, a merged or moved tab, arrival state, service elsewhere before |
| Decision and who made it | "Service refused by MOD J. Ruiz at 10:52 p.m." |
| Exactly what was said | Both sides, in quotes, as close as you can recall it |
| What was offered | Water, food, a rideshare, a call to a companion, holding keys per your policy — and what was accepted |
| Guest's departure | Time, method, with whom, and whether anyone accompanied them |
| Others involved | The party, other guests affected, whether anyone intervened |
| Camera | Exported the same night, covering the bar and the exit |
| ID check | Whether an ID was checked, when, and by whom |
| Notifications | GM, ownership, security, and anything your policy requires — with times |
| Server training | Whether the staff involved hold current alcohol service certification, and the dates |

Export the tab. Reconstructing "how many did she have" from memory at 1 a.m. is the single least reliable thing a manager can put in a record, and the POS already has the answer with timestamps.

## What the record should say

**Not usable:**

> Guest at the bar got way too drunk, we cut her off, she got mad and left. Bartender should have caught it sooner.

Three problems in two sentences: a conclusion about state, no times or observations, and a disciplinary judgment inside an incident record.

**Usable:**

> Saturday 3/8. Bar, seats 4–5. Guest: female, approx. 30s, tab #1187 opened 8:42 p.m., name on card A. RENNER, ID checked at open by bartender K. Alvarez. Tab detail (exported 12:40 a.m.): 8:44 p.m. house red, 9:12 p.m. house red, 9:58 p.m. house red, 10:31 p.m. bourbon neat, 10:44 p.m. bourbon neat. Note: guest was seated with two companions on separate tabs; I cannot confirm whether drinks were purchased for her from those tabs. At approximately 10:47 p.m. I observed the guest repeat the same drink order twice within about a minute and knock over an empty glass reaching for her phone. At 10:49 p.m. she walked to the restroom and contacted the corner of table 6 with her shoulder; she steadied on the chair back. Service refused by me (MOD J. Ruiz) at 10:52 p.m. I said: "I'm not able to serve you another one tonight, but I'd like to get you some water and something to eat." She said: "This is ridiculous, I've had three." I offered water and the bar menu at 10:53 p.m.; water accepted, food declined. Offered to call a rideshare at 10:55 p.m. and again at 11:10 p.m.; declined both times. At 11:14 p.m. one of her companions, who had been drinking water since 9:30 p.m. per tab #1191, said he was driving her home. They left together at 11:18 p.m. through the front door. Witnesses: K. Alvarez (bartender), Dana R. (server), and the companion. Camera exported 8:30 p.m.–11:25 p.m. and saved to the office drive at 12:45 a.m. Notified GM 11:30 p.m. Alcohol service certification on file: K. Alvarez 2/14, current; J. Ruiz 9/2, current.

Notice what that record does not claim. It does not say she was intoxicated, it does not say she was over any limit, and it openly records that drinks may have come from other tabs. It documents what a manager saw and what a manager did, which is the entire scope of what a manager can document.

## What not to write down

- **"Drunk," "intoxicated," "wasted," "over the limit."** You did not measure it. Write the indicators.
- **A legal conclusion about liability, dram shop exposure, or fault.** Not yours to state, and asserting it in a report is worse than saying nothing.
- **An estimate presented as a count.** If the POS shows five, write five and note the gaps. Do not write "probably eight or nine."
- **Discipline of the bartender.** Separate document, separate decision, written after you know the facts.
- **Anything about the guest beyond behavior.** Appearance commentary, assumptions about their evening, or judgments about the party.
- **A quiet omission.** If service continued past a point you now question, record it. A record with an inconvenient line is credible; a tidy one that everyone knows is incomplete is not.

Alcohol service law, liquor authority obligations, and liability all vary substantially by state and locality. Have your policy — refusal procedure, transport offers, incident thresholds, retention — written with your own counsel before the night you need it.

## Which document this becomes

An **alcohol service incident record**, filed with the incident log and kept per your retention policy. Build it with the [incident report generator](/tools/restaurant-incident-report-generator); the general form is on [restaurant incident report](/restaurant-incident-report).

Write a record for refusals that go smoothly too. They take four lines, they demonstrate the standard is being applied, and they cost nothing.

Where it goes next depends on the facts. If other guests or staff were drawn in and it became a confrontation, that is [documenting an altercation](/restaurant-employee-altercation-documentation) as well, with separate accounts on the [witness statement form](/restaurant-witness-statement-form). If someone was hurt, it is also a [guest injury report](/restaurant-guest-injury-incident-report). And if the review shows a bartender missed an acknowledged standard, that discipline is written separately from the same facts — the role's standards and evidence trail are in [documenting bartenders](/restaurant-bartender-documentation).

## Follow-up

**Same night:** export the tab, export the camera, write the record, make the notifications.

**Next shift:** review it with the bar team as practice rather than punishment. What did we see, when did we see it, what would have moved the refusal fifteen minutes earlier.

**Monthly:** count your refusals. A bar that refused service twelve times in a quarter and documented all twelve is running a program. A bar with zero documented refusals is not refusing nobody — it is documenting nothing.

**Annually:** confirm certifications are current for everyone who serves, and keep the dates where the incident record can reference them. The other record types a restaurant file needs are on the [pillar guide](/restaurant-employee-documentation).

## Conclusion

**Observations, times, the tab detail, the words used, what you offered, and how they left.** No conclusions about anyone's state, no legal characterizations, and a record for the refusals that go fine as well as the ones that do not.

Build it with the [incident report generator](/tools/restaurant-incident-report-generator). Docu-Coach™ keeps alcohol service records in one dated history so a pattern — a night, a bartender, a section, a time of week — is visible while you can still act on it. Better documentation and organized records, not legal advice; liquor law and liability questions belong with your own counsel.

See it against a real bar shift at [/demo](/demo#trial).
## FAQ

### What should I document when we refuse service to a guest?

The time, who made the decision, the observations that led to it, exactly what was said to the guest and by whom, the guest's response, what was served and when according to the POS, what you offered — water, food, a ride, a call to someone — and how the guest left. A documented refusal is one of the most valuable records a bar can keep, and most bars keep none.

### How do I describe intoxication without stating a conclusion?

Describe the observable indicators and let them stand. 'Guest was slurring and unsteady on the way to the restroom at 10:40 p.m., knocked over a bar stool, and repeated the same drink order three times' is observation. 'Guest was drunk' is a judgment about a physiological state you did not measure. Trained servers already know these indicators; the record just needs them written down.

### Should I record the number of drinks served?

Yes, from the POS rather than memory, with times. The tab detail shows what was rung, when, and by whom, which is far more reliable than an estimate at the end of a Saturday. Note also what you could not see — drinks bought by other guests, a party that moved tabs, arriving already having been elsewhere — because those gaps matter and pretending they do not is worse than recording them.

### Does an overservice record mean disciplining the bartender?

Not automatically, and treating every incident as discipline is how you stop hearing about them. The incident record documents the event. Discipline is separate and appropriate only when an acknowledged standard was missed — service continued after a documented refusal, an unchecked ID, a pour that was never rung. Write the incident first and decide after.

### What if the guest leaves and drives?

Record what you observed, what you offered, what was said, and the time they left, along with who else was present. Whether to contact anyone beyond that is a question for your policy, your ownership, and your own counsel — not something to decide from a general guide. Have that policy written before the night it matters.

### How long should we keep alcohol service records?

Longer than ordinary incident records, because questions from a liquor authority or a claim can arrive well after the fact and the timelines vary by jurisdiction. Set one retention policy with your own counsel, keep the exported tab detail and the camera clip with the report, and apply it the same way at every bar you operate.

---
Start a 30-day free trial: https://www.docu-coach.com/demo.md
More pages for AI agents: https://www.docu-coach.com/llms.txt