Key takeaways
- The log exists to move obligations from one shift to the next. Every entry that needs action gets an owner and a deadline, or it is just a diary.
- Use the same six sections on every page: header, numbers, people, guests, facility and food safety, and open items.
- Write incidents as facts with times and names. Severe work injuries have hard reporting deadlines: 8 hours for a death, 24 hours for a hospitalization, amputation or loss of an eye[2].
- Every promised callback goes in the open-items list, including calls that came in while the restaurant was busy or closed. Card numbers never go in the log[3].
Why the log is the restaurant's memory
Every restaurant has a log book. In a lot of them it is a spiral notebook under the register holding three weeks of “busy night, all good” and one entry nobody can read. Then a guest calls on Tuesday asking why nobody rang her back about Saturday's overcharge, and the Saturday closer is off until Thursday. The log failed at its one job, which is carrying obligations from the shift that created them to the shift that has to finish them.
The food code expects a person in charge on site during all hours of operation[4], so at every shift change one person in charge hands over to the next. The log is that handover in writing. It matters more in restaurants than in most workplaces because the people change quickly: restaurant and bar workers had a median of 2.2 years with their current employer in January 2026, against 3.9 years across the private sector[5]. The manager who knows the backstory of table 12's complaint may not be there next month.
Source: US Bureau of Labor Statistics, 2026[5]
Show the data
| Workers | Median tenure (years) |
|---|---|
| Restaurants and bars | 2.2 years |
| All private sector | 3.9 years |
Phones add another gap. Since July 31, 2024, Google no longer shows a Business Profile's call history[6], so there is no outside record of who rang your listing and when. If a call left something unfinished, the only record is the one your team writes down.
Six sections on every page
Use the same headings in the same order on every page, whether the log is a bound book or a shared document. A manager scanning a week of pages should find every staffing note in the same place without reading the rest.
| Section | Record | Leave out |
|---|---|---|
| Header | Date, shift, manager on duty, weather, events nearby, anything unusual about the day | A narrative of the evening |
| Numbers | Sales and covers against forecast, labor notes, comps and voids over your threshold with reasons | Figures already in the point-of-sale report |
| People | Call-outs, late arrivals, early outs, staff injuries, illness reports, praise, conversations that need follow-up | Opinions about someone's private life or health beyond what the job needs |
| Guests | Complaints and what was done, recoveries, VIPs, regulars' feedback, lost and found | Guest card numbers or security codes |
| Facility and food safety | Equipment faults and service tickets, 86s, short deliveries, temperature exceptions and corrective action | Routine readings that belong on the temperature log itself |
| Open items | Every promised callback, repair, follow-up or decision, with owner and deadline | Anything without an owner |
Keep it short. A good closing entry takes ten minutes, and most of that is the open-items section. If managers are writing a page of prose every night, they will stop by the third week. The daily flash report should carry the numbers in detail; the log only needs what explains them, such as the private party that ran late or the fryer that went down at 7:40.
The open-items list makes the log work
Each open item has four parts: what is owed, who owns it, by when, and the outcome once it is done. The closing manager copies any item still open to the top of the next page, so the opening manager sees it before reading anything else. An item is closed only when its owner writes the outcome and initials it. Crossing it out does not count.
Example open item: “Call back Dana R., 555-0142, re: charged twice for 2-top on Sat. Owner: Marco (AM manager). By: Mon 12 pm. Outcome: refunded $46.20, apologized, offered dessert on next visit. MR 11:20.”
Callbacks are the items that most often die between shifts, and guests notice. In a Cornell survey of 1,230 frequent diners, respondents often found it hard to reach a restaurant when they needed to change a reservation[7]. A guest who did get through and was promised a call back has already done the hard part. Missing that call is how a fixable complaint becomes a one-star review.
- Caller
- SI Employee
- System
- Your team
01Caller
Complaint call at 9:40 pm
Lines are busy at close, so the call is forwarded to the overflow.
02SI Employee
Details taken
Name, number and the problem in the caller's words; no promises about refunds.
03System
Summary by email
The manager on duty gets the summary, recording and transcript in the inbox.
04Your team
Logged as open item
Closer writes it under open items with an owner and a deadline.
05Your team
Called back and closed
Opening manager calls before lunch, writes the outcome, initials it.
Example. The overflow step applies only where calls are forwarded when lines are busy or the restaurant is closed.
Incidents: write facts, not opinions
Incident entries are the ones most likely to be read later by someone outside the restaurant: an insurer, an inspector, a lawyer or a labor investigator. Write them on the shift they happen, in plain words, with times and names. Kitchens are not as dangerous as construction sites, but injuries are routine; food services and drinking places recorded 2.4 injury and illness cases per 100 full-time workers in 2024[8].
Time and place
When it happened and exactly where: “8:52 pm, dish pit, next to the three-compartment sink.”
Who was involved and who saw it
Names and roles of the people involved and any witnesses, with phone numbers for guests.
What happened, in plain words
What you saw or were told, attributed: “Jordan said he slipped on water from the sprayer.” No guesses about fault.
What was done
First aid, who drove whom to urgent care, whether the area was closed off, whether food was discarded.
Who was told, and what is next
GM, owner, insurer, health department as needed. Add the follow-up to open items with an owner.
Restaurants are on OSHA's list of partially exempt industries for routine injury and illness records[9], which is one reason the log is often the only written account of a kitchen injury. The exemption does not cover severe cases. Every employer must report a work-related death, in-patient hospitalization, amputation or loss of an eye[10], within 8 hours for a death and 24 hours for the others[2]. If an entry describes one of those, the GM or owner needs to hear about it that night, not at Monday's meeting.
Illness reports belong in the people section too. Under the food code, food employees must report symptoms such as vomiting, diarrhea, jaundice or sore throat with fever to the person in charge[4]. The habit is weak in practice: in CDC research, 1 in 5 food workers had worked at least one shift in the previous year while sick with vomiting or diarrhea, and very few managers said they asked sick workers about those symptoms[1]. Logging every report, and what the manager decided, builds the habit of asking. The decision itself follows your employee illness policy; guest injuries follow the steps in handling guest injuries and incidents.
Guest messages and phone callbacks
Not every call belongs in the log. The ones that do are the calls that left something unfinished: a promised callback, a complaint, a large party or event inquiry waiting for the right person, a lost item, an allergy question passed to the chef. Your telephone SOP decides who answers and where the host's call sheet lives; the log is where anything still open at close ends up.
- Write the caller's name and number, what they asked for, what they were told and who owns the next step.
- Never write card numbers or security codes. PCI guidance says the card security code may not be stored after authorization, even encrypted[3].
- Copy over any message that arrived while the restaurant was closed or the lines were full, so it does not live only in one person's inbox.
- Close the loop in the log, not in a text thread. Texts disappear with the phone that sent them.
If you forward overflow or after-hours calls to an SI Employee, each call lands in the AssistCall inbox with a summary and transcript, and the person you choose gets the summary by email. Those summaries are a feed into the log, not a replacement for it. The closing manager reads the evening's summaries and copies anything that needs a person into open items with an owner (see what it does). The pizzeria Friday example follows one of those handoffs: a party order taken at 7:12 p.m. on a Friday and called back by the owner at 10 a.m. the next day.
Example: one page from a Friday close
| Section | Entry |
|---|---|
| Header | Example: Fri, PM shift, manager on duty Priya S. Rain from 6 pm. Concert at the arena, doors 7:30. |
| Numbers | Example: 212 covers vs 190 forecast. Sales over forecast; rain pushed walk-ins to the bar. Comp: one entree, wrong temperature, table 31. |
| People | Example: Sam called out sick at 3:10 pm (vomiting), excluded per policy, Lee covered. Jordan slipped in the dish pit at 8:52, no injury, mat replaced. |
| Guests | Example: table 14 waited 28 minutes for entrees; manager visited, comped dessert. Regulars at 22 asked about Thanksgiving pre-orders. |
| Facility and food safety | Example: fryer 2 tripped breaker at 7:40, reset, ran fine after. Fish delivery short 10 lb halibut, credit requested. |
| Open items | Example: 1) Call back Dana R. re double charge, owner Marco, by Mon 12 pm. 2) Electrician for fryer 2 circuit, owner GM, book Mon. 3) Pre-order flyer for regulars, owner AGM, by Wed. |
The opening manager reads the open items first, initials the page, and calls Dana before the lunch rush. The GM sees the fryer item on the quiet-day review and books the electrician, because a breaker that trips once on a Friday will trip again on a Saturday. Sam's illness report is the entry that matters most for food safety, and it took one line.
Paper, app or shared document
Any format works if it has fixed sections, one copy, and a habit of reading it. Paper is fast and survives a dead tablet, but it cannot be searched and it lives in one building. A shared document or a log feature in your scheduling or team app can be searched, read from home and kept safely, but only if managers actually write in it before they leave. Pick one. Two logs means nobody reads either.
Keep old logs. Entries about call-outs, early outs and schedule changes sit next to records the Labor Department says to keep: payroll records for at least three years, and time cards and work schedules for two[11]. Keeping the log at least three years costs a shelf or a folder, and it is often the only record of why a shift ran short. Restaurant recordkeeping covers the rest of the retention schedule.
Make reading it part of the job. The opening manager reads and initials every page before service. The GM reviews the week's pages once a week and closes anything older than a day, as described in the GM's weekly rhythm. And the log should appear on the closing manager checklist, as the last item before the lights go off.
Frequently asked questions
Should the manager log be paper or digital?
Either, as long as there is one log with fixed sections and every manager reads it at the start of the shift. Digital logs are easier to search and keep; paper survives a dead tablet. Running both is the one setup that reliably fails.
Who writes in the manager log?
The manager or shift lead in charge of each shift, before leaving. Chefs can add kitchen items under facility and food safety, but one person signs each page so there is no doubt who handed over.
How long should we keep manager logs?
At least three years is a sensible floor, because entries about hours and schedule changes sit next to payroll records the Labor Department says to keep for three years and time cards and schedules for two[11]. Keep longer if your lawyer or insurer advises it.
What should never go in the log?
Card numbers and security codes[3], guesses about fault in an incident, and personal or medical detail beyond what the job needs. Write what happened and what was done.
Do restaurants have to keep OSHA injury logs?
Full-service, limited-service restaurants and bars are partially exempt from routine OSHA injury and illness records[9], but every employer must report a work-related death within 8 hours and an in-patient hospitalization, amputation or loss of an eye within 24 hours[2].
References
Centers for Disease Control and Prevention (2026). Restaurants Can Manage Sick Workers to Help Prevent Outbreaks (opens in a new tab) ↑
Legal Information Institute (Cornell Law School) (2026). 29 CFR 1904.39 - Reporting fatalities, hospitalizations, amputations, and losses of an eye (opens in a new tab) ↑
PCI Security Standards Council (2018). Information Supplement: Protecting Telephone-Based Payment Card Data (v3.0) (opens in a new tab) ↑
US Food and Drug Administration (2022). Food Code 2022 (sections 2-101.11 and 2-201.11) (opens in a new tab) ↑
US Bureau of Labor Statistics (2026). Employee Tenure, Table 5: Median years of tenure with current employer by industry (opens in a new tab) ↑
Google Business Profile Help (2024). Changes to Google Business Profile chat and call history (opens in a new tab) ↑
Cornell University Center for Hospitality Research (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑
US Bureau of Labor Statistics (2024). Industries at a Glance: Food Services and Drinking Places, NAICS 722 (opens in a new tab) ↑
Occupational Safety and Health Administration (2026). 29 CFR 1904 Subpart B, Appendix A - Partially exempt industries (opens in a new tab) ↑
Legal Information Institute (Cornell Law School) (2026). 29 CFR 1904.2 - Partial exemption for establishments in certain industries (opens in a new tab) ↑
US Department of Labor, Wage and Hour Division (2026). Fact Sheet #21: Recordkeeping Requirements under the FLSA (opens in a new tab) ↑