A kitchen log is a sheet somebody writes on at the moment something is checked: a temperature, a delivery, a sanitizer strength, a tray of food thrown out. Each one answers a question that can't be answered afterward. Was the walk-in cold on Tuesday night? Did the chili cool fast enough? Which case of chicken was that? The made-up restaurant on this page keeps fourteen, and its trouble was never the checks. It was not knowing which logs it had, who filled them in, or where last month's went. Below is the whole list for a made-up restaurant, grouped by what they're for, with a link to a template for each, which ones to start with, and a checklist to download. Which of them your kitchen must keep, and the limits on each, come from your health department's code.
The short version
- A log is written when the check is made, by the person who made it.
- Temperature logs: receiving, coolers and freezers, cooking, cooling, reheating, holding, thawing.
- Equipment logs: thermometer calibration, sanitizer, dish machine.
- Housekeeping logs: cleaning, waste, pests, employee illness.
- Every log needs a place it lives, a person who owns it, and someone who reads it.
- Start with the ones tied to food that can make someone sick.
- TaroStack keeps receiving, lots and waste as records. More below.
The list
| Log | What it records | When | Who |
|---|---|---|---|
| Receiving | Each delivery: supplier, items, temperatures of cold and frozen food, condition, lot or date codes, accepted or refused | As each delivery arrives | Whoever signs for it |
| Cooler and freezer temperatures | Each unit's reading, and what was done if it was out | Opening, mid-shift, closing | Opening and closing cook |
| Cooking | Final internal temperature of each batch of the foods your plan names | Each batch | Cook |
| Cooling | Start time and temperature, and the readings at the checkpoints | Each batch cooled | Cook |
| Reheating | Temperature reached and how long it took | Each batch reheated for hot holding | Cook |
| Hot and cold holding | Temperature of food on the line, the steam table, the salad bar | As often as your plan says | Line cook |
| Thawing | Method, water temperature if under running water, food temperature at the end | Each case thawed | Prep cook |
| Thermometer calibration | Each thermometer checked, adjusted or replaced | Weekly, and after a drop | Kitchen manager |
| Sanitizer | Strength in each sink, bucket and machine, by test strip | Each time it's mixed | Dish and prep |
| Dish machine | Wash and rinse temperatures, or sanitizer strength | Each shift | Dish |
| Cleaning | The tasks done, by day, week and month, initialed | As each is done | Everyone |
| Waste | What was thrown out, how much, why | As it happens | Everyone |
| Employee illness | Who reported what symptoms, when, and when they came back | As it happens | Manager |
| Pest sightings and service | What was seen where, and the pest company's reports | As it happens, and each visit | Manager |
The frequencies are this made-up kitchen's own. Yours come from your code and your own plan.
The temperature logs
Seven of the fourteen follow food from the back door to the plate, and each has a template with its limits explained:
- Receiving: food receiving log template.
- Coolers and freezers: temperature log template.
- Cooling: cooling log template.
- Reheating: reheating log.
- Holding: hot and cold holding temperatures. A kitchen that holds food by the clock keeps a different record: time as a public health control.
- Thawing: food thawing log.
This kitchen folds its cooking log into something else: a column on the prep sheet. That's fine as long as the temperature is written somewhere with a time and initials.
The equipment logs
Three logs are about the tools the other logs depend on.
- Thermometers: a thermometer that reads four degrees low makes every temperature log wrong. See thermometer calibration log.
- Sanitizer: sanitizer concentration log.
- Dish machine: dish machine temperature log.
The housekeeping logs
- Cleaning: cleaning log template.
- Waste: waste log template. It's the only one of the fourteen that pays for itself directly: a month of it shows what's being over-prepped.
- Pests: pest control log template.
- Employee illness: kept by the manager, in the office, not on the wall. Ask your health department what it has to contain.
Date labels on food in the walk-in aren't a log, and they do a log's job: see date marking in the Food Code.
Making them work
One place each. A log lives where the check happens: the receiving log at the back door, the cooler log on the cooler, the sanitizer log at the dish area. A log in the office gets filled in from memory at the end of the shift, which is the same as not keeping it.
One owner each. "Everyone" is fine for cleaning and waste. For the rest, a named job on a named shift.
Somebody reads them. A manager initials each log once a week. That's when a walk-in creeping up a degree a day gets noticed, and it's what makes the people filling them in believe they matter.
An out-of-range reading needs a second line. What was done about it. A log with a 46°F reading and nothing beside it is worse than no log.
Keep the old ones. A month to a binder, the binders on one shelf, for as long as your health department says.
Start with five. A kitchen with none shouldn't start with fourteen. Receiving, cooler temperatures, cooling, sanitizer and thermometer calibration cover the checks where a miss can make someone sick. Add the rest a couple at a time, when the first ones are being filled in without reminding.
Get the checklist
Download the kitchen logs checklist. One sheet and a read-me: the fourteen logs, what each records, when it's filled in, who does it and where it's kept, with a column to tick the ones you have. Change the rows to match your kitchen. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
Fourteen clipboards record that things were checked. They don't know about each other. The receiving log has the lot of Tuesday's chicken. The cooling log has a batch of chicken soup. Nothing on paper says the soup was made from that chicken, so when the supplier phones about the lot, somebody reads three binders and guesses.
How TaroStack does it
TaroStack isn't a temperature logger. It keeps the part the clipboards can't: what came in, what it became, and what was thrown out.
Receiving records the lot and its dates. Scanning a supplier's GS1-128 case label fills in the lot and the use-by date.
Your own checks are fields on a receipt, a lot or a batch: a temperature, a tick box, initials.
Each batch notes which lots it used, automatically.
Waste carries a reason (expired, spoiled, damaged), so it can be reported by reason and item.
One report for a supplier's recall: which lots came in, which batches used them, and what's still on your shelves.
| The question | Clipboards | In TaroStack |
|---|---|---|
| Which lot of chicken came in Tuesday | The receiving log | On the receipt |
| What was made from it | Not written anywhere | The batches that used the lot |
| What was thrown out this month, and why | Add up the waste sheets | Waste, by reason and item |
| Is any of that lot still here | Check the walk-in | Stock by lot |
TaroStack doesn't take temperatures and doesn't replace the logs your health department asks for. Lots, receiving and waste reasons are on every plan, from $9.99 a month (50 items) or $39 a month (3,000 items). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
