Skip to content

End-of-Shift Handover Report

Example prompt: "When the duty manager fills in the close-of-service form at the end of each shift, pull the takings, the covers count, any comps or breakages, and their service notes, combine it with what's in the bookings sheet for tonight, and post a handover note to our team Slack plus a short email to the owner."

The Problem

The cash-up at the end of a service is the moment when the four things that mattered tonight — what we took, how many covers we did against what we forecast, what we comped and why, what got broken and what went wrong on the floor — exist all in one head, and they leak by morning if they are not written down. In most independent restaurants the duty manager scrawls the takings on a paper sheet by the till, posts the headline number in a WhatsApp group, and the rest is verbal at the next shift's pre-service briefing — which means tomorrow's opening manager either does not know about the broken Cambro and the unhappy table 14 or hears about them at half-volume between two other things. The handover only catches the lot if the closing manager has the ten minutes at midnight to write it up, and at midnight after a 200-cover Saturday there are rarely ten minutes.

How GloriaMundo Solves It

We build a workflow that fires when the duty manager submits the close-of-service form — a Google Form with takings, covers, comps, breakages, and a free-text service-notes box. An integration step reads the form response and the matching row from the day's bookings tab in Google Sheets so the forecast covers and the actual covers can be compared. An LLM step assembles the handover post in a single Slack-ready format — takings and covers up top with the variance against forecast, comps and discounts with the reason where the manager wrote one, breakages and any cost note, then the service notes broken into floor and kitchen if the text reads that way. A second integration step posts the handover to the team Slack channel so the opening manager reads the same thing tomorrow morning, and a third sends a one-screen email to the owner with the headline numbers and the link to the Slack post. Glass Box preview shows the assembled handover before it lands so the first run can be sense-checked against what the duty manager wrote.

Example Workflow Steps

  1. Trigger (integration): A new response is submitted to the close-of-service Google Form by the duty manager after the last table leaves.
  2. Step 1 (integration): Read the form response — cash takings, card takings, covers count, comps and discounts with reasons, breakages with the item and approximate cost, and the free-text service-notes box.
  3. Step 2 (conditional): Dedupe on form_response_id against the 'Service Logs' tab so a Google Forms delivery retry or a manual replay does not post the same handover twice and does not log the same row twice.
  4. Step 3 (integration): Read today's row from the 'Reservations' tab of the bookings Google Sheet so the forecast covers and the actual covers can be compared, and pull the names of any no-shows the duty manager flagged in the form.
  5. Step 4 (llm): Assemble the handover post in a single Slack-ready format — takings and covers up top with the variance against forecast, comps and discounts with the reason where the manager wrote one, breakages with the cost note, service notes broken into floor and kitchen.
  6. Step 5 (integration): Post the handover to the team Slack channel so the opening manager reads the same pack tomorrow morning.
  7. Step 6 (integration): Send a one-screen email to the owner with the headline numbers — takings, covers vs forecast, comp total, breakage total — and a link to the Slack post for the detail.
  8. Step 7 (integration): Append a row to the 'Service Logs' tab in the bookings sheet keyed on form_response_id with the date, service, takings, covers, comp total, and breakage total so the weekly summary has a clean source to read from and so a re-fired trigger updates the existing row rather than appending a second one.

Integrations Used

  • Google Forms — the close-of-service form the duty manager fills in before locking up
  • Google Sheets — the 'Reservations' tab for today's forecast and the 'Service Logs' tab for the persistent record
  • Slack — the team channel where the handover lands so the opening manager reads one document tomorrow rather than three
  • Gmail — the owner's one-screen email with the headline numbers and the link to the Slack post

Who This Is For

Owner-operators and duty managers at independent restaurants, bistros, and gastropubs that run a paper cash-up sheet and a WhatsApp group for handovers — anyone who has lost a service note overnight because the duty manager went home at midnight and the opening manager started at 9am with only the headline number in their head.

Time & Cost Saved

The duty manager already does the cash-up; the workflow does not replace that, it captures it once in a form rather than scattering it across a paper sheet, a WhatsApp message, and three verbal handovers at the next pre-shift. The fifteen to twenty minutes a closing manager spends typing up a tidy handover at midnight is the minutes that get skipped first when the service ran long — and the handovers that get skipped are the ones where the breakage cost is never tracked and the unhappy table is never followed up. The workflow makes the handover the same five-minute job every night and puts it in the team channel so the opening manager and the owner are reading from one document by 9am rather than reconstructing the night from WhatsApp screenshots.