Documenting Line Cooks

What's different about documenting a line cook

A line cook's record runs on measurements the kitchen already produces — ticket times, temperature and cooling logs, prep sheets, waste and yield — and on station standards that almost never involve a guest, which makes the evidence stronger and the documentation habit rarer than anywhere else in the building. The BOH file in most restaurants is empty not because there is nothing to write, but because the chef fixes the problem on the line instead of recording it.

That has a specific cost. When a cook is eventually let go, the file shows a hire packet and a termination, while the chef can describe eighteen months of the same three problems. Every one of those problems had a number attached to it at the time.

The standards worth documenting

Standard	How it is measured	Where the number lives
Ticket times by station	Average and outliers during a defined window, against a posted standard	KDS or expo timing report; manual expo log if you have no KDS
Re-fires and remakes	Count and reason, tied to the station	Re-fire log or POS re-fire tag
Temperature and cooling	Actual readings and log completeness	Temp log, cooling log, probe records
Prep accuracy	Yield and quantity against the prep sheet	Prep sheet, walk-in count
Waste	Product discarded, quantity, reason	Waste sheet, discard log
Spec adherence	Portion weights and plate build against the spec book	Line checks, plate audits, spec photos
Station setup and breakdown	Mise complete at open, station clean and labeled at close	Line check sheet, closing checklist
Labeling and dating	Containers labeled, dated, rotated	Walk-in audit
Equipment handling	Knife safety, fryer and slicer procedure, PPE where required	Line check, incident records
Attendance and shift readiness	Clock-in versus the pre-shift line check	Labor export, line check timestamp

Two of these — spec adherence and labeling — are the standards that separate a cook who is fast from a cook who is reliable, and neither shows up in a ticket time report.

Evidence this role generates

• KDS or expo timing export for the shift and the window, not a daily average. The daily average hides the 7:15–8:30 collapse that everyone remembers.
• Cooling and temp logs — the physical page, photographed the night you notice a gap. Kitchen paper does not survive.
• Prep sheet with the assigned quantity and the actual, plus who signed it.
• Waste sheet with product, quantity, and reason. A cook with a consistently high protein waste line has a measurable, coachable problem.
• Line check sheet at open and at close, with the manager initial and the time.
• Walk-in audit — unlabeled or undated containers, photographed with the date visible.
• Spec book and plate photos — the reference that turns "the plate was wrong" into a comparison.
• Camera over the line — useful for equipment and safety incidents, and it overwrites like everything else. Export the day it matters.

Photograph paper logs the same shift. This is the single most common reason a BOH record cannot be substantiated later: the evidence was a page on a clipboard that got wet, replaced, or thrown out during a deep clean.

Recurring situations

Situation	What it usually becomes
Cooling or temp log gap with product discarded	A food safety write-up citing the internal standard, with the retrain recorded
Ticket times outside the standard across multiple shifts	A coaching conversation with the numbers first; a performance improvement plan if it is capability rather than conduct
Repeated re-fires for the same error	A coaching note tied to the spec, then the written step if the spec was retaught and the error persisted
Prep sheet signed for work that was not done	An accuracy and integrity record — write what the sheet said and what the walk-in count showed, and nothing about intent
Station left unbroken-down at close	A verbal warning against the posted closing standard, per documenting a verbal warning
Knife or equipment injury	An incident record the same shift, per documenting an employee injury on shift, regardless of whether the cook waves it off
Walking off the line mid-service	Both an incident record and an attendance occurrence, per when an employee walks out mid-shift

Coaching before discipline

Kitchens coach constantly and record almost none of it, which is why the first written document in a BOH file so often reads as a surprise.

A usable line cook coaching note is anchored to the measurement:

3/12, 2:15 p.m., before open. Diego M., grill. Pulled the KDS export for 3/8 and 3/11, 6:30–8:30 p.m. Grill average 19 and 21 minutes against the 12-minute posted standard, at 140 and 155 covers, both nights with a full line and no equipment down. Walked the station: proteins were being pulled from the low-boy one order at a time rather than par-stocked at the top. Rebuilt the mise plan together — 12 portions par at the station, restocked at the 7:00 p.m. lull. Diego said the low-boy layout changed after the equipment swap in February and nobody reset the par. Follow-up 3/26, same export, same window.

The value of that note is not that it warns anyone. It is that it records the standard, the measurement, the conditions, the actual cause, and a date to check — which means if nothing improves, the write-up that follows has something real behind it. The short-note format is on restaurant employee coaching, and the coaching note generator produces it fast enough to do before service.

Examples

Prep sheet accuracy. "3/19. Diego M., prep and grill. Prep sheet for 3/19 shows 40 portions of marinated chicken thigh completed and initialed at 2:40 p.m. Walk-in count at 4:10 p.m. by chef R. Owens: 22 portions, one labeled container dated 3/19. Line ran out at 7:50 p.m.; 9 tickets re-fired to an alternate protein between 7:50 and 8:35 p.m. Diego stated: 'I marked it before I finished and got pulled to the fryer.' Standard: prep sheet initialed at completion, per the posted prep procedure. Action: written warning for the sheet, coaching on the fryer pull with the chef. Follow-up 4/2."

Spec and yield. "Line check 3/22, 4:45 p.m. Sauté station, Diego M. Portioned 6 oz protein spec; three plates weighed at 7.8, 8.1 and 7.6 oz. Waste sheet for the week shows 11.5 lb protein loss against a 4 lb trailing average. Spec book photo reviewed with the cook on the line. Coaching, not discipline. Re-weigh at line check on the next three shifts he works sauté. Follow-up 3/29."

Sanitation and labeling. "Walk-in audit 3/25, 11:20 p.m., after close. Diego M. closed the walk-in. Seven containers unlabeled and undated on the middle rack; two containers with 3/18 dates still in rotation. Photographed with the audit timestamp. Standard: labeling and rotation SOP §2, acknowledged 1/16. Prior: coaching 3/4, same standard. Action: written warning. Follow-up: walk-in audited at close on his next four closing shifts."

None of those three examples could be moved to the page about servers, which is the test a role page has to pass. The FOH counterpart, with entirely different evidence, is documenting servers.

Consistency across shifts

Kitchen standards drift by shift more than by manager. The AM chef runs a line check and the PM sous does not; the weekday standard for labeling is enforced and the Saturday standard is whatever survives the rush. Then a cook gets written up on a Tuesday for something nobody mentioned on Saturday, and the record cannot answer the obvious question.

What holds it:

1. A posted standard with a number on it. Ticket time targets by station, portion specs, line check times. A standard the cook cannot read is not a standard you can enforce.
2. The same line check at open and close, every shift, initialed. It takes four minutes and it is the artifact that makes every other kitchen record possible.
3. Conditions in the record, always. Covers, staffing, equipment status. Omitting them is the fastest way to write something a cook can dismantle.
4. The same threshold in writing for every station. If grill gets coached at 15 minutes and sauté gets written up at 14, the file shows inconsistency before it shows performance.

The other six record types a restaurant file needs, across FOH and BOH, are on the pillar guide.

Conclusion

The kitchen already produces the evidence; documenting a line cook is mostly a matter of moving it into the employee's record with the conditions attached. Ticket times against a posted standard, log readings with the actual number, prep sheets checked against the walk-in, and a photograph of the paper before it disappears.

Turn the facts into a document with the write-up generator, or record the conversation first with the coaching note generator. When the gap is capability rather than conduct, the performance improvement plan is the right instrument and the PIP generator builds it with real check-in dates.

Docu-Coach™ keeps the BOH record in the same history as everything else, so a cook's file is not the only empty one in the building — better documentation and more consistent records, not legal advice.

See it against a real service at /demo.