Restaurant Manager Logbook: How to Build a Better Shift Handover

A restaurant can lose important information every time one manager hands the operation to another.

A broken refrigerator is mentioned verbally and forgotten. A guest complaint is resolved but never documented. A supplier short-ships a critical item, yet the next manager does not know. A staff member is close to overtime, but the evening manager discovers it too late. A recurring cash difference appears on three shifts without anyone connecting the pattern.

A manager logbook solves this by creating one controlled place for shift-critical information.

The goal is not to record everything that happened. The goal is to preserve the information the next manager needs in order to run the next shift better.

What a restaurant manager logbook is for

A useful manager logbook should create continuity across shifts.

It should answer:

What happened?
What still needs attention?
Who owns the follow-up?
When does it need to be completed?
What risk does the next manager need to know about?

If the logbook becomes a diary, it will be ignored. If it captures only exceptions, actions and handover information, it becomes an operating tool.

Use one source of truth

Do not split shift information across notebooks, WhatsApp messages, sticky notes, spreadsheets and verbal conversations.

Choose one official manager log.

It can be:

a bound physical logbook,
a shared digital document,
a spreadsheet,
a manager module inside restaurant software,
another controlled system the management team consistently uses.

The format matters less than having one recognized source.

Separate the logbook from routine checklists

An opening checklist confirms that required tasks were completed.

A closing checklist confirms that the restaurant was shut down correctly.

The manager logbook records what was unusual, unresolved or important enough for the next manager to know.

For example:

Checklist: “Walk-in temperature checked.”

Logbook: “Walk-in temperature higher than normal at 4:30 p.m.; maintenance contacted; product moved to backup cooler; technician expected at 8:00 a.m.”

The second entry carries operational meaning.

Start every entry with the basics

Each shift record should identify:

date,
shift,
manager on duty,
opening or closing time where relevant.

This makes future review easier and creates accountability without relying on memory.

Record sales exceptions, not every sales number

Detailed sales data belongs in the POS and daily sales report.

The manager logbook should record the context behind unusual performance.

Examples:

sales materially below forecast because of heavy rain,
dinner significantly above plan because of a local event,
delivery platform outage from 7:15 to 8:05 p.m.,
large group increased average check,
stock-out reduced sales of a signature item.

That context becomes valuable when reviewing trends later.

For the financial side, use our Restaurant Daily Sales Report guide.

Record staffing issues that affect the next shift

Useful staffing notes include:

call-outs,
late arrivals,
employees sent home early,
overtime risk,
training gaps,
station coverage problems,
injuries or incidents that require follow-up,
approved schedule changes.

Avoid unnecessary personal detail. Record only what management needs for operations, scheduling, compliance or follow-up.

Document performance issues objectively

Do not write emotional or vague statements such as:

“Ali was terrible tonight.”

Instead record a specific operational fact:

“Three ticket errors between 7:00 and 8:00 p.m.; retrained on modifier entry; supervisor to observe next shift.”

Objective language is more useful and safer.

Track stock-outs and low-stock risks

The next manager should know what could affect service.

Record:

item unavailable,
remaining quantity if important,
expected replenishment,
approved substitution,
menu items affected,
who is following up.

Example:

“Avocado below par; approximately 18 portions remain. Supplier confirmed delivery at 9:00 a.m. Do not accept online avocado add-ons until stock arrives.”

This is much more useful than simply writing “low avocado.”

Record supplier and receiving exceptions

Supplier problems should be logged when they may affect the next shift.

Examples include:

short shipment,
rejected product,
late delivery,
unapproved substitution,
missing credit,
price discrepancy,
quality issue.

Link the issue to the supplier record or receiving document where possible.

Our Restaurant Supplier Scorecard guide explains how repeated supplier issues should be reviewed over time.

Maintenance issues need status, not just description

A weak log entry says:

“Ice machine broken.”

A strong entry says:

“Ice machine stopped at 6:20 p.m. Unit isolated. Backup ice ordered. Service company contacted; technician due tomorrow 10:00–12:00. Opening manager to confirm arrival.”

The next manager should know:

what failed,
whether it is safe to use,
temporary workaround,
who was contacted,
expected repair time,
required follow-up.

Separate urgent maintenance from routine maintenance

Not every issue has the same priority.

A useful classification might be:

Critical: affects safety, legal compliance or ability to operate.
High: affects service capacity or product quality.
Routine: should be repaired but does not materially affect current service.

This helps the next manager prioritize attention.

See our Restaurant Equipment Maintenance Checklist for preventive maintenance structure.

Record guest recovery that may continue beyond the shift

Most guest complaints are resolved immediately and do not need a long log entry.

Record the ones that may require follow-up.

Useful information includes:

what happened,
what resolution was provided,
whether a refund or credit is pending,
whether the guest expects a manager call,
whether a delivery platform case is open,
whether the issue indicates a recurring operational problem.

Avoid recording unnecessary sensitive personal information.

Record food-quality incidents clearly

If there is a significant product-quality concern, record:

product involved,
time,
batch or supplier reference where available,
action taken,
whether product was isolated or discarded,
who was informed,
required follow-up.

Food-safety incidents should also follow the restaurant’s formal safety and regulatory procedures. The manager log does not replace required incident documentation.

Track cash and payment exceptions

Routine cash totals belong in the cash close.

The manager log should record meaningful exceptions such as:

cash over or short beyond tolerance,
drawer access issue,
card terminal failure,
mobile-payment outage,
unresolved refund,
delivery settlement discrepancy.

Example:

“Register 2 closed $38 short. Recount completed with shift supervisor. No explanation found. GM to review transaction history tomorrow.”

That creates a clear follow-up path.

Use the logbook to connect repeated exceptions

The biggest value often appears over time.

One late supplier delivery may be random.

Four late deliveries in two weeks reveal a pattern.

One missing delivery item may be human error.

Repeated missing sides on weekend evenings may indicate a packing-process problem.

A structured log makes those patterns visible.

Create simple categories

Categories make entries easier to scan.

A practical set might include:

Code	Category
SALES	Sales or demand exception
LABOR	Staffing or training issue
STOCK	Inventory or stock-out issue
SUPPLIER	Vendor or receiving issue
MAINT	Maintenance or equipment
GUEST	Guest recovery or complaint
CASH	Cash or payment exception
SAFETY	Safety-related issue
FOLLOWUP	Open management action

You do not need more categories than the management team can use consistently.

Use a severity level

A simple severity label helps the next manager scan the handover quickly.

For example:

Red: urgent before or during next shift,
Amber: important follow-up,
Green: informational.

In a digital system, these may be tags. In a paper book, simple symbols can work just as well.

Every open issue needs an owner

“Someone should call the supplier” is not an action.

Assign ownership:

Owner: Opening manager

or:

Owner: Kitchen manager

or:

Owner: General manager

Then add a due time or date if the issue is time-sensitive.

Separate closed issues from open issues

Managers should be able to identify unresolved work immediately.

Use a simple status:

Open
In progress
Closed

Do not leave completed issues looking active.

Closing the loop is part of the system.

Use an action register for important unresolved items

For larger operations, the logbook can feed a short action register.

Example:

Issue	Owner	Due	Status
Walk-in service call	Opening manager	8:00 a.m.	Open
Supplier credit	Purchasing	Friday	In progress
POS terminal replacement	GM	Monday	Open

This prevents multi-day problems from disappearing inside old shift notes.

Do not write private HR details in a shared log

A manager log is not the place for sensitive employee information.

Avoid unnecessary details about:

medical conditions,
disciplinary investigations,
personal conflicts,
compensation discussions,
other confidential matters.

If an HR issue needs formal documentation, use the appropriate confidential process.

Do not write passwords, PINs or security credentials

This seems obvious, but operational notebooks sometimes become dumping grounds for access information.

Never record:

POS admin passwords,
alarm codes,
safe combinations,
banking credentials,
employee passwords.

Use the restaurant’s approved secure credential process instead.

Use factual language

A manager log may be read later by owners, auditors, HR, insurers or other managers.

Write what happened, not what you assume happened.

Better:

“Three guest complaints about cold fries between 8:00 and 8:45. Fry station checked; holding time exceeded standard. Product discarded and fresh batch prepared.”

Weaker:

“Kitchen did not care tonight.”

The first entry supports action. The second does not.

Use timestamps for important incidents

Time matters when reconstructing an event.

Use timestamps for:

equipment failures,
service outages,
safety incidents,
major guest issues,
supplier arrivals,
system downtime.

This can help management connect cause and effect.

Link evidence where practical

In a digital log, link or reference:

maintenance ticket,
supplier invoice,
waste log entry,
cash reconciliation,
incident report,
POS report.

In a paper system, use a reference number.

The log should summarize the issue, not duplicate every document.

Build the logbook around exceptions

Do not write:

“Opened on time. Lunch was normal. Dinner was normal. Closed at 11.”

That creates noise.

Write only what the next manager needs.

If nothing unusual happened, a simple:

“No material exceptions. All open actions closed.”

may be enough.

A strong handover entry follows a simple formula

Use:

Issue → Impact → Action taken → Current status → Owner → Due

Example:

Issue: Fryer 2 ignition failure.

Impact: Fry capacity reduced during dinner.

Action: Unit isolated; service company contacted.

Status: Open.

Owner: Opening manager.

Due: Confirm technician by 9:00 a.m.

This structure removes ambiguity.

Connect the logbook to pre-shift meetings

The next manager should review the previous shift’s open items before the pre-shift briefing.

That way, important information flows into the team meeting.

For example:

stock-out becomes a menu availability note,
equipment issue becomes a station restriction,
large booking becomes a staffing priority,
delivery complaint pattern becomes a service focus.

Our Restaurant Pre-Shift Meeting guide shows how to turn those issues into a focused ten-minute briefing.

Connect the logbook to daily sales review

The sales report tells you what changed.

The manager log often tells you why.

If sales fell 12%, the log may show:

delivery platform outage,
equipment failure,
major stock-out,
weather disruption,
staffing shortage.

This combination is more useful than either report alone.

Connect the logbook to maintenance

Repeated equipment notes should move into the maintenance system.

If the same refrigerator appears in the log five times, the business may have moved beyond a minor repair issue.

The logbook should surface patterns, not become the permanent home for maintenance history.

Connect the logbook to training

Repeated employee errors may indicate a training-system problem.

If several employees repeatedly miss the same step, review the procedure and training material.

See our Restaurant Staff Training Checklist for a structured onboarding and sign-off process.

Use a daily review time

The general manager or owner should review the log at a consistent time.

For example:

morning review of overnight issues,
midday review of open actions,
end-of-day review of unresolved items.

The exact schedule depends on the operation, but open issues should not sit unread.

Use a weekly pattern review

Once a week, scan the log for repetition.

Look for:

repeat stock-outs,
repeat supplier failures,
repeat cash differences,
repeat equipment problems,
repeat guest complaints,
repeat staffing gaps.

This turns anecdotal problems into management priorities.

Measure closure rate for open actions

If the logbook includes action items, track whether they are actually being closed.

A simple measure is:

Action closure rate = Actions closed by due date ÷ Actions due × 100

Illustrative example:

20 actions due this week,
17 closed on time.

17 ÷ 20 × 100 = 85%

The purpose is not to create a score for its own sake. It is to identify whether handover actions are being completed.

Do not allow the logbook to become a complaint channel

Managers should not use the log to criticize other managers indirectly.

If there is a recurring leadership issue, address it directly.

Keep the log focused on:

facts,
operational impact,
actions,
follow-up.

Keep entries short but complete

A good entry may be two or three sentences.

Long essays make the log harder to scan.

The manager should include enough information for the next person to act without having to call for clarification.

A practical manager logbook template

Field	Purpose
Date / shift	Identifies the operating period
Manager	Identifies author / owner
Category	Allows quick scanning
Issue	States what happened
Impact	Explains why it matters
Action taken	Shows what has already been done
Status	Open, in progress or closed
Owner	Assigns follow-up responsibility
Due	Prevents indefinite delay

Example shift handover

STOCK — Amber

Chicken breast delivery was 12 kg short. Current stock is enough for approximately one normal lunch period. Supplier confirmed replacement at 2:00 p.m. Kitchen manager to verify delivery before dinner prep.

MAINT — Red

Dishwasher rinse temperature became inconsistent at 9:10 p.m. Unit removed from normal use and backup process activated according to site procedure. Service technician booked for 8:30 a.m. Opening manager to confirm safe operating status before use.

GUEST — Amber

Delivery order 4582 arrived missing two sides. Refund submitted through platform. Packing checklist reviewed with closing team. Evening manager to monitor first 20 delivery orders tomorrow.

CASH — Green

Use escalation rules

Some entries should trigger immediate escalation rather than waiting for the next manager.

Examples may include:

serious safety risk,
significant equipment failure,
suspected food-safety incident,
security issue,
major cash or payment discrepancy,
event likely to prevent the restaurant from opening.

The logbook is not a substitute for contacting the responsible person when urgent action is required.

Set retention rules

Decide how long manager logs should be retained based on operational usefulness, company policy and applicable legal requirements.

Do not keep sensitive information indefinitely without a reason.

For digital systems, control access and backup.

Train managers on what not to record

Managers should understand the difference between operational notes and confidential records.

A short training standard should cover:

objective language,
privacy,
security credentials,
legal or HR escalation,
food-safety documentation,
when a separate incident report is required.

Audit the logbook after the first month

After the system has been running, review:

Are entries useful?
Are managers writing too much?
Are important issues missing?
Are actions being closed?
Are categories working?
Are recurring problems visible?

Then simplify the format if needed.

The handover should take minutes, not an hour

A strong system reduces handover time because important information is already structured.

The outgoing manager should not need to remember every detail verbally.

The incoming manager should be able to scan:

red issues first,
open actions second,
important amber notes third.

Then ask questions only where clarification is needed.

The manager logbook is a continuity system

The restaurant does not stop when one shift ends.

Inventory, equipment, staff, guests, suppliers and open actions continue into the next shift.

A good manager logbook preserves that continuity.

It turns isolated incidents into shared operational knowledge, prevents follow-up from disappearing at shift change and gives management a record of recurring problems that need a real fix.

The best logbook is not the most detailed one.

It is the one managers actually use, read and act on every day.

Track the age of open actions

Open actions should not remain in the log indefinitely. Add an age or overdue flag so management can see which issues have survived multiple shifts without resolution.

Action age = Current date/time − Date/time opened

A recurring maintenance note that remains open for five shifts is a different management problem from a new issue reported tonight.

Use a daily open-action summary

At handover, show only unresolved items that still require attention. A short summary can include priority, issue, owner, due time and current status. This prevents important actions from being buried under closed historical notes.

Frequently asked questions

Should every shift write a manager log entry?

Yes, but a normal shift can simply state that there were no material exceptions and all open actions are closed. Do not create unnecessary narrative.

Who should review overdue logbook actions?

The general manager or designated operations owner should review overdue items and reassign or escalate them when the original owner cannot close them.

Can the manager log replace an incident report?

No. Safety, HR, insurance, food-safety or legal matters may require separate formal documentation. The manager log can reference the incident without replacing the required process.

Operational note: This guide is a general management framework. Safety incidents, HR matters, privacy obligations and regulatory records may require separate formal procedures depending on jurisdiction and company policy.