A documented restaurant offboarding workflow for managers

Restaurants tend to have a rough onboarding process and no offboarding process at all. Someone stops appearing on the schedule, their name gets removed from the group chat, and that is the whole procedure.

The cost of that shows up later — in a final-pay question, a POS login still active six months on, or a dispute where the only record of what happened is what two people remember differently. All four tracks below run at the same time, and the documentation one is the track people skip.

Track 1: final pay

• Final work date recorded accurately. Everything else keys off it.
• All hours captured, including the last shift, which is the one most likely to be missing from the timecard.
• Outstanding tips distributed, including any pool share for a period that had not yet been distributed.
• Accrued balances handled per policy and applicable rules. Whether unused time must be paid out varies — this is a decision to make deliberately, and it should be the same decision every time.
• Final-pay timing decided, not defaulted. Requirements can differ depending on whether the separation was voluntary. Check rather than assume.
• Outstanding deductions reviewed. What you may deduct from a final paycheck is more constrained than many operators expect. Where there is any doubt, ask counsel before deducting, not after.

Track 2: access and property

The security half. It is easy, it is quick, and it is almost always incomplete.

• POS login disabled — not shared with the next hire.
• Scheduling app, email, and any delivery-platform access removed.
• Keys and alarm codes returned, and codes changed if warranted.
• Uniforms, equipment, and company cards returned, with the return recorded.
• Manager-level access reviewed specifically. A departing manager typically has access to more systems than anyone has a list of.
• Vendor or supplier contacts notified where the person was an authorized contact.

Track 3: documentation, written the same day

This is the track that matters most and gets done least. Documentation written on the day is contemporaneous. Documentation reconstructed months later, once a dispute exists, is far weaker — and everyone involved knows it.

• Reason for separation recorded factually: resignation, end of season, or termination. Facts and dates, not characterisations.
• Any final conversation summarised the same day — what was said, by whom, who was present.
• Prior documentation consistent with the outcome. If a termination follows performance issues, the file should already contain them. Discovering it does not is a lesson for the next employee, not this one.
• Resignation in writing where the employee resigned, even if it is a text message. Save it.
• Rehire eligibility noted, decided once rather than rediscovered when they apply again next season.

Track 4: closing the file

• Personnel file completed and moved to terminated-employee storage.
• Retention clock started. Different records carry different retention periods, and I-9s in particular follow their own rule tied to hire and separation dates.
• Payroll record marked terminated so nobody is accidentally paid in the next cycle — a genuine and embarrassing recurring error.
• Benefits or leave administration notified where applicable.
• Headcount updated, because thresholds turn on it.

The seasonal-restaurant version

A restaurant that ends a season with twenty separations in a fortnight needs this to be a batch process, not twenty individual scrambles. Two things make that work: deciding rehire eligibility at the point of separation while you still remember, and closing access on a schedule rather than as people drift away.

The counterpart to this list is the onboarding checklist, and both are easier when the file structure they write into already exists — that is HR administration.

The test

A year from now, someone asks why a former employee left. Can you answer from the file, in under two minutes, with dates? If not, the gap is in track 3, and it is worth fixing before the next separation rather than after it.

This is an operational checklist, not legal advice. Final-pay timing, permissible deductions, and record retention are governed by rules that vary and that turn on your circumstances. Confirm with qualified counsel.