---
title: "Documenting Servers"
description: "What to document for servers: guest complaints, void and comp patterns, side work, section coverage, and which POS evidence backs each record."
url: https://www.docu-coach.com/restaurant-server-documentation
markdown: https://www.docu-coach.com/restaurant-server-documentation.md
datePublished: 2026-09-12
dateModified: 2026-09-12
pageType: guide
---

# Documenting Servers

> What to document for servers: guest complaints, void and comp patterns, side work, section coverage, and which POS evidence backs each record.

## Key takeaways

- A server's record is distinct because almost everything in it is measurable from the POS and almost all of it happens in front of a guest — table data, void and comp activity, side work completion, section coverage, and their own bank sit in one person's job at once.
- No other position in a restaurant generates that combination of revenue evidence and guest-facing exposure on the same shift.
- Server records are the easiest in the building to make factual, because the system already holds the numbers.
- Check average is a real standard and also the one most likely to be documented unfairly.
- If you are going to put it in a record, put the conditions in the same sentence.
- Servers leave a paper trail that most positions do not, and the trail expires.

Guest-facing, revenue-handling, and measured by a POS — the record for a server looks nothing like the one for the line.

## What's different about documenting a server

**A server's record is distinct because almost everything in it is measurable from the POS and almost all of it happens in front of a guest — table data, void and comp activity, side work completion, section coverage, and their own bank sit in one person's job at once.** No other position in a restaurant generates that combination of revenue evidence and guest-facing exposure on the same shift.

That combination cuts both ways. Server records are the easiest in the building to make factual, because the system already holds the numbers. They are also the easiest to make unfair, because a raw number without the section, the cover count, and the shift means very little.

## The standards worth documenting

| Standard | How it is measured | Where the number lives |
|----------|-------------------|------------------------|
| Void and comp activity | Percentage of net sales, plus count and timing (pre- vs post-payment) | POS void/comp report by server ID |
| Guest complaints | Complaints tied to a table and time, and how each was resolved | Manager log, comp record, guest recovery notes |
| Order accuracy | Modifier and remake rate against the section's covers | POS remake or re-fire tags, kitchen re-fire log |
| Side work and closing duties | Line-item completion against the posted checklist | Signed closing checklist, MOD verification |
| Section coverage | Tables transferred, tables left unattended, greet times | POS table timeline, host seating record |
| Bank variance | Variance to the cent against the issued bank | Server bank count sheet, cash-out report |
| Alcohol service | ID check practice, refusals, over-service escalations | Bar log, incident records, manager notes |
| Attendance and punctuality | Clock-in against scheduled start, coverage impact | Labor export, schedule |
| Upsell and check average | Only alongside cover count, section, and shift | POS sales by server |

The last row carries a warning. Check average is a real standard and also the one most likely to be documented unfairly. If you are going to put it in a record, put the conditions in the same sentence.

## Evidence this role generates

Servers leave a paper trail that most positions do not, and the trail expires.

- **POS server report** — sales, covers, voids, comps, discounts by employee ID for a specific shift. Export the shift, not a date range summary; the shift is what a record can cite.
- **Table timeline** — seat time, first order fired, entrée fired, check closed. This is how you turn "she ignored table 9" into a sequence.
- **Void and comp detail** — with reason codes and the manager approval, if your system requires one. Post-payment voids are the ones worth noting.
- **Server bank count sheet** — issued amount, counter, and close-out variance. If banks are not counted at issue, that is a procedure finding before it is an employee finding. The measurement discipline is on the [cash drawer shortage](/restaurant-cash-drawer-shortage-write-up) page.
- **Signed closing checklist** — the only artifact that turns side work from a complaint into a record.
- **Guest recovery log or comp reason** — a comp with "guest complaint — cold entrée, table 12, 7:40 p.m." attached is evidence; a comp with no note is not.
- **Camera over the server station and POS terminals** — overwrites fast in most restaurants. Preserve it the day you might need it.

Pull the POS reports the same night. Several systems retain shift-level detail for a shorter period than the summaries, and the detail is the part that makes a record specific.

## Recurring situations

| Situation | What it usually becomes |
|-----------|------------------------|
| Guest complaint escalated to a manager | An incident note with the table, the time, the words, and the resolution — then a coaching note or a write-up depending on what the facts show. A verified guest-facing miss uses the [restaurant rude-to-guest write-up](/restaurant-rude-to-guest-write-up) |
| Missing name tag, non-slip shoes, or posted FOH uniform | A same-shift appearance note, then coaching or a write-up per the posted standard — see the [restaurant dress-code write-up](/restaurant-dress-code-write-up) |
| Void or comp percentage well outside the store range | A documented review conversation first; a write-up only after the report has been shown to the employee and the pattern continues — see [void and comp abuse](/restaurant-void-comp-abuse-documentation) |
| Closing side work incomplete on repeated nights | A verbal warning against the posted checklist, then the written step. See [documenting a verbal warning](/restaurant-verbal-warning-documentation) |
| Section abandoned or a walk-out mid-service | An incident record plus an attendance occurrence — both, per [when an employee walks out mid-shift](/restaurant-employee-walk-out-mid-shift) |
| Bank short at cash-out | A cash handling record built from the count and the access list, not a theft allegation |
| Alcohol service issue | An incident record, because a liquor board question can arrive months later |
| Late clock-ins that push the greet | An attendance occurrence with the coverage impact, per the [attendance write-up](/restaurant-attendance-write-up) guide |
| Unapproved early-out or unauthorized/extended break | A same-shift punch note, then coaching or a write-up per the posted end or break length — see the [restaurant leaving-early write-up](/restaurant-leaving-early-write-up) |
| Refused a lawful section, side-work, or stay-until order | A same-shift order-and-quote note, then coaching or a write-up — see the [restaurant insubordination write-up](/restaurant-insubordination-write-up) |
| Posted a guest photo or complained about a shift or manager in public | A same-shift URL-and-caption note, then coaching or a write-up — see the [restaurant social media write-up](/restaurant-social-media-write-up) |
| Observed product walkout, unpaid comp, or tip-jar/till taking | A same-shift item-and-observer note, then coaching or a write-up — see the [restaurant employee theft write-up](/restaurant-employee-theft-write-up) |
| Unremitted tip-out or tip-pool skim | A same-shift tip-report note, then coaching or a write-up — see the [restaurant tip-theft write-up](/restaurant-tip-theft-write-up) |

## Coaching before discipline

Most server problems are correctable and most of them are not corrected, because the conversation happens on the floor between turns and nobody writes it down.

A useful server coaching note is short and anchored to a number the employee can see:

> 3/12, 3:50 p.m., before service. Dana R. Pulled the 3/8 and 3/11 server reports together. Voids 5.4% of net across both shifts against a 1.8% store average; 6 of 14 were post-payment re-rings. Walked through the correct sequence for a re-ring before payment. Dana said she has been re-ringing after payment "because the guest is already standing there." Agreed: any post-payment adjustment goes through a manager. Follow-up 3/26 — pull the same report.

That note does three things a floor conversation cannot. It shows the employee the same evidence a reviewer would see, it records their explanation, and it sets a date to check. The note format is on [restaurant employee coaching](/restaurant-employee-coaching), and the [coaching note generator](/tools/restaurant-coaching-note-generator) produces it in under a minute.

## Examples

**Guest complaint, with the timeline.** "Saturday 3/8. Dana R., server, Section 3. Table 12 (four-top, seated 7:05 p.m. per POS) asked for a steak remake at 7:38 p.m. Dana told the table 'that's not my problem' at approximately 7:40 p.m. — reported by guest to MOD at 7:52 p.m. and confirmed by Luis M. (expo), who heard it from the window. Entrée recomped $52. Guest left without paying an $84 bar tab. Policy: Handbook §4.2 Guest Service, acknowledged 1/12. Prior: coaching 2/18 (tone with expo). Action: written warning."

**Side work pattern.** "Closing checklist review, 3/1–3/28. Ale G. closed 9 shifts. Checklist incomplete on 3/7, 3/9, 3/16 and 3/23 — server station not restocked on all four, ice wells not drained on 3/9 and 3/23. Closing MOD completed on each occasion (J. Ruiz 3/7, 3/9; M. Okafor 3/16, 3/23). Cut times on those nights: 10:40, 10:55, 10:35, 11:05 — inside normal. Verbal warning issued 3/9; this is the written step."

**Bank variance with the condition recorded.** "Server bank, 3/14. Ale G., issued $50 bank at 4:00 p.m., counted at issue by J. Ruiz. Cash-out variance $18.75 short at 10:58 p.m., counted by J. Ruiz with M. Okafor witnessing, recounted once. No shared bank; sole sign-in. Two cash tabs closed to the wrong table between 8:40 and 9:10 p.m. per the POS timeline, both corrected by the employee. Coaching, not discipline: walked through tab assignment. Follow-up 3/28."

None of those three examples would work on a page about the line, and that is the test.

## Consistency across shifts

Server standards drift more than most because the measures are relative. A 4% void rate on a Tuesday lunch and a 4% void rate on a Saturday with a 200-cover section are not the same performance, and two managers reading the same report will reach two conclusions unless the standard says how to read it.

Three practices hold the line:

1. **Write the threshold down.** "Void rate reviewed against the trailing four-week store average, with a conversation at double the average" is a standard. "High voids" is a mood.
2. **Pull the report on a schedule, not when someone is annoyed.** A monthly review of every server's report means the record shows a process rather than a manager targeting one person.
3. **Record the conditions in the note.** Section, covers, shift, whether they were cut early or double-sat. It takes one sentence and it is the sentence that makes the record survive.

The kitchen side of this cluster is on [documenting line cooks](/restaurant-line-cook-documentation), and the standards there are not transferable. Everything a restaurant file needs across every role is on the [pillar guide](/restaurant-employee-documentation).

## Conclusion

**A server record is a POS report plus the conditions it happened under.** Table and time on every guest complaint, reason codes on every void, the posted checklist behind every side work note, and the section and cover count next to any number you are judging.

Turn the facts into the document with the [write-up generator](/tools/restaurant-employee-write-up-generator), or capture the conversation first with the [coaching note generator](/tools/restaurant-coaching-note-generator). The field definitions are on [restaurant employee write-up](/restaurant-employee-write-up).

Docu-Coach™ keeps the server's coaching notes, guest complaints, and discipline in one dated history so a pattern is visible while it is still coachable — better documentation and more consistent records, not legal advice.

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

### What should I document for a server?

Guest complaints tied to their tables with the table number and time, void and comp activity from the POS with the reason codes, side work and closing duty completion, section coverage and transfers, cash or bank variances if they run their own bank, alcohol service decisions, and the coaching conversations in between. The distinguishing feature of a server record is that almost all of it is measurable from the POS.

### Can you write up a server for bad guest reviews?

You can document a specific guest complaint that identifies a specific interaction — the table, the time, what was said, whether it was comped, and who handled it. An anonymous online review with no table and no time is not a record of employee behavior, and treating it as one puts your discipline at the mercy of a stranger's post. Use the review as a prompt to pull the ticket and the timeline, then document what you can verify.

### How do you document a void or comp problem without accusing a server of theft?

Cite the report, the numbers, and the pattern, and stop. 'Voids 6.2% of net sales across 12 shifts against a 1.8% store average; 9 of 41 voids were post-payment' is a fact from a report anyone can pull. Where the money went is a question for an investigation with witness statements and camera review, not a line in a performance write-up.

### What is the difference between documenting a server and documenting a bartender?

Overlap exists — both handle money, both serve alcohol, both face guests — but the evidence sources differ. A server's record runs on table data, section coverage, side work, and guest complaints, while a bartender's runs on pour cost, house till counts, and continuous alcohol service across a shift. Do not reuse one page's standards for the other; the measurements are not interchangeable.

### Should side work be documented?

Yes, and it is the most under-documented issue in full service. Incomplete closing duties are the recurring friction that ends careers without ever appearing in a file, because the closing manager finishes the work and says nothing. Log it against the posted checklist the night it happens and the pattern becomes visible in three weeks instead of three months.

### How do I document a server fairly when sections are not equal?

Record the conditions alongside the measure. Cover count, section, shift, and whether they were cut early or double-sat all change what a number means. A server with a 22% higher check average on a patio section in June has not necessarily outperformed anyone. Write the number and the context together, or the record invites an argument you will lose.

---
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