Incidents, training notes, equipment issues — captured once on the shift they happened, surfaced where the next shift needs them. The handoff your GM never writes, written by the people closest to the work.
Every multi-property operator has fought this war. A fryer breaks Saturday close, the floor manager writes a sticky note that disappears Monday morning. A new server passes solo on a Sunday brunch — the closing manager knows but the opening manager doesn't. A regular guest gets comped for a dietary mix-up, and three shifts later the next manager has no idea why their margin took a $148 hit.
None of this is data, exactly. It's context — and your reporting tools were never built to hold it. So it lives in heads, sticky notes, group texts, and gets lost.
The Logbook is the place where shift-level context becomes operations memory. Captured by the people who lived the shift, surfaced where the next shift needs it.
Equipment failures, guest disputes, walkouts, comped tables, manager overrides, anything outside a normal shift. Logged with the shift, the person involved, and the cost (if any).
"Priya passed her Saturday solo — ready for full sections." "Marcus needs a refresher on void protocol." Captured by the trainer or the shift lead — visible to whoever's running the next shift.
Fryer popping breakers. Walk-in cooler reading 2° high. POS terminal #3 freezing. Every fix logged, every recurrence flagged, every vendor visit timestamped.
"Big party at 7:30 — Henderson 14-top, anniversary, burrata note." "We're 86'd on salmon till tomorrow's delivery." The next manager opens the Logbook and sees what they need to know.
Lost about 25 minutes of fry capacity during peak. Electrician scheduled for Monday morning. Recommend not running fry-heavy specials Sunday.
Manager swipe Sofia R · $148 · resolved with the guest. Bride's mother is allergic to shellfish; kitchen had been told but the runner brought the wrong plate. Comped two starters, full bottle of house red, dessert on the house. Note for kitchen: bag allergy tickets bright red, runner check before fire.
Trainer note: move her off shadow rotation. Recommend giving her section 4 (the back patio) next Friday — small section, good for a confidence shift. Her check average was within 8% of the floor average tonight, with zero comp requests and a 23% wine attach.
The Logbook isn't a passive journal. Syphor reads what your team logs and uses it the same way it reads your POS and KDS — to find patterns.
Twenty-minute demo with the founder. Bring a recent shift that's still in your head. We'll show you what the Logbook would have kept.