A bar shift handoff checklist the next manager can use

The close of day report and the handoff do different jobs. The report records what the register saw. The handoff tells the opening manager what is still unresolved and whose job it is. Copy the worksheet below into the shift log you already use. It needs no new software.

What should a manager finish before writing the handoff?

The closing manager should finish the point of sale close before writing the handoff, because the close report is the evidence the handoff points to. Square's close of day guide for restaurants, as checked in October 2026, is a useful reference. It lets a venue require four actions before the close: closing out open checks, adjusting tips, totaling cash drawers and clocking out team members. It also warns that open checks are not included in the report and that running the close settles card tips on closed checks.

Square describes the finished report as a rundown of the day: check details such as comped and voided checks, gross and net sales, payment methods, category sales and item sales. Other systems name and order these steps differently, so follow your own system's procedure.

Save or link the report with the handoff instead of copying figures from memory after everyone has left. Write the business date and the shift, not only the clock date. A close that runs past midnight lands on the next calendar day, and the opening manager needs to know which service the note describes.

What goes on a shift handoff worksheet?

A shift handoff worksheet needs six fields for each exception, with one row per exception. Copy these into your log:

• Business date and shift: the service being closed, even when the clock is past midnight.
• What happened: one observable exception, in plain words.
• Evidence: the report, check number or note that lets the next manager verify it.
• Next action: one question or decision, starting with a verb.
• Owner and check time: one named role and a time before the issue goes stale.
• Closed when: the evidence that will show the action happened.

Leave a field blank only when it does not apply. "All good" does not replace checking the close, and a row with no owner is a row nobody is expected to close.

What does a filled-in handoff row look like?

The row below is a fictional example. The bar, the shift and the details are invented to show the format, not taken from a real venue.

• Business date and shift: Tuesday close.
• What happened: two voids on the bar terminal have no reason recorded.
• Evidence: the close of day report and the void detail for those two checks.
• Next action: ask the closing bartender what happened to both drinks.
• Owner and check time: Wednesday's opening manager, before service.
• Closed when: the explanation is written in the row, and any change to the void reason list or any coaching note has its own owner.

A row like this is a prompt for a conversation, not evidence against anyone. A missing void reason can be a setup gap, a training gap or a busy moment, and the conversation is how you find out which. Where to escalate is your operation's call. Keep cash details and staff names in your normal access-controlled log, not a shared public document.

What else belongs in a bar shift handoff?

A bar shift handoff should hold anything that needs a decision before the next service. Most rows fall into one of five kinds:

• Open service work: an unresolved guest issue, an open check or a promised follow-up, with the responsible manager named.
• Cash and payment differences: a drawer variance, a missing tip adjustment or a settlement question. Link the report instead of guessing why the number moved.
• Comps and voids needing context: the check and the reason, then a question about what happened. The weekly comp and void review handles the pattern across shifts.
• Stock and equipment: an item likely to run out before the next delivery, a broken tool or a safety issue, with the temporary plan.
• People and training: a specific task the next manager must verify, written as an observation rather than a judgment about a staff member.

How does the next manager close the loop?

The next manager closes the loop by reading the open rows before the pre-service meeting and writing the result in the same row. Decide which rows can be fixed now, which need someone outside the venue and which were reporting errors. Add the outcome and the date it closed. If the same exception keeps appearing, carry the rows into the weekly operating review so the team changes the process rather than writing the same note every night.

Keep the handoff short enough to finish on a busy night. If every normal event becomes a row, the real exceptions get lost. If nothing is ever written, the next manager inherits surprises. Start with what needs a decision before the next service, and adjust the form after a week of using it.

When does software help with shift handoffs?

Software helps with shift handoffs when the rows stop being read or closed, not before. A shared log and the point of sale report are enough while the next manager reads them every shift. CoreTAP reads voids and discounts from the point of sale and puts each finding on an actions list, assigned to a role with a date and closed with an outcome. It does not total the cash drawer, count stock or have the conversation for you, so keep the written handoff even when a pattern is found automatically.