Kitchen Operations
Restaurant Line Check Template
A restaurant line check template localised for Indian kitchens: station-by-station pre-service checks with FSSAI holding temperatures and fix-by times.
The dal that sat at 58°C for two hours
At 6:55 PM the first dinner ticket prints, and the dal makhani has been sitting in the bain-marie at 58°C since five o'clock. Nobody knows, because nobody probed anything between lunch close-down and the first order. FSSAI's catering standard requires hot holding at 65°C or above, and food between 5°C and 60°C is in the danger zone. Food below 65°C gets one window of up to two hours, then must be reheated by direct heat to above 75°C for at least two minutes and returned to hot holding; it cannot be reheated a second time. If nobody checks, it simply gets served.
The line check is the tool that catches this at 6 PM instead of 8 PM. It is a standard practice in American kitchens with almost no India-localised version written down, which is odd, because Indian kitchens with bain-maries, tandoors and aggregator dinner peaks need it more, not less.
What a line check actually is
A line check is a pre-service walk of every station by the chef or manager, done with a probe thermometer and a sheet, verifying two things at once: readiness and safety. Readiness means mise en place matches tonight's expected covers. Safety means temperatures, date labels and oil condition meet the standard.
It runs twice a day, before lunch (around 11:15 for a noon open) and before dinner (6:00 to 6:30 for a 7 PM ramp), and takes fifteen to twenty minutes. Most Indian kitchens already do an informal version, a quick "sab ready?" shouted down the line. The line check keeps the walk but replaces the question with a probe, and the nod with a written reading.
The FSSAI numbers that decide pass or fail
Every temperature on the sheet comes from FSSAI's catering guidance, so the same sheet doubles as inspection evidence. The detailed corrective-action sequence is in FSSAI's operational direction for catering establishments.
- Hot holding: 65°C or above. The FSSAI audit checklist specifies 70°C for non-veg, so a dal at 66°C passes and a chicken curry at 66°C fails.
- Cold items: 5°C or below. Foods of animal origin: 4°C or below. Frozen: −18°C or below.
- Hot food found below 65°C: it may remain below 65°C for up to two hours, once only. Then reheat it by direct heat to above 75°C for at least two minutes and return it to hot holding. Reheating in a bain-marie, under heat lamps, or by topping up with hot water is explicitly not acceptable; food that has been reheated once must not be reheated again.
- Cold display items may sit between 5°C and 10°C for a maximum of two hours, once, then discard.
The full set of storage, cooking and reheating numbers is in our FSSAI food temperature chart; the line check only needs the holding thresholds above.
The pre-dinner line check template, station by station
Run it 6:00 to 6:30 PM. Every line scores pass or fail, every fail gets a fix-by time, and readings are written as numbers, not ticks.
Tandoor station
- Tandoor fired and at working temperature by 6:15, per your kitchen's own standard; naan dough proofed and portioned for expected covers.
- Every marinade container carries a date and time label. Unlabelled means fail, no debate.
- Marinated non-veg holding in the chiller at 4°C or below; skewers, tongs and gloves at station.
Curry section and bain-marie
- Probe every gravy and hot-hold item and write the reading: 65°C minimum, 70°C for non-veg.
- Biryani in hot hold at 65°C or above. If it has been below 65°C for up to two hours, it gets one direct-heat reheat above 75°C for at least two minutes, then returns to hot holding; do not reheat it again. A bain-marie can hold temperature but cannot restore it.
- Bain-marie water level topped up and thermostat working; par of each gravy against tonight's expected covers.
Fryer
- Oil condition checked: dark, foaming or smoking oil fails, and the change gets logged against your oil-change schedule.
- Fryer at working temperature before the first ticket, not after it; batter and coating station stocked.
Cold section: chutneys, raita, salads
- Everything probes at 5°C or below, with dairy-heavy items like raita treated as high-risk.
- Summer rule for April to June and humid monsoon weeks: this station fails most often, usually because the chiller is overloaded or the door has been propped open through prep. Check twice.
- Garnish pars against covers: coriander chopped, onions sliced, lemon wedges cut.
Pass and packing
- For delivery-heavy kitchens: containers, lids and carry bags at par, and packaging genuinely spill-proof. Zomato's partner terms allow refunds for packaging failures to be charged back to the restaurant, so a leaking lid found at 6:20 is cheap and one found by a customer is not.
- Ticket printer loaded, aggregator tablets charged and online.
Pass, fail, fix-by: the rule that changes behaviour
A failed line item gets fixed before service, not during it. That is the whole discipline. Each fail gets a fix-by time and a named recheck. For example: paneer makhani probes 58°C at 6:10. Record when it fell below 65°C; if it is still within its one-time two-hour window, reheat it on the stove above 75°C for at least two minutes, return it to hot holding, and recheck at 6:35. Do not repeat that reheat. Done and recorded before the rush, this is a five-minute fix. Discovered mid-rush, it is a stalled station, a stack of late orders, and a kitchen prep-time metric sliding on exactly the night you can least afford it.
Writing readings instead of ticks has a second effect: it makes fake completion visible. "Dal 71°C" can be spot-checked in ten seconds; a tick cannot. If your sheets come back suspiciously perfect, read our guide on stopping pencil-whipped checklists. And a repeat failure, the same station failing two days running, is no longer a fix but an exception: equipment fault or process gap, escalated to the manager with the readings attached.
Where the readings should live
The line check readings are temperature records, and FSSAI inspections ask for exactly those. Rather than keeping a separate stack, feed the twice-daily line check into the same log as your storage checks; our food temperature log template shows the format that satisfies both uses.
Laminated sheet or phone
A laminated template and a whiteboard marker at the pass works in a single kitchen with a chef who cares. Its weaknesses are structural, though. The readings get wiped every night, so there is no history to spot the chiller that has been creeping up for a week. There are no photos of oil condition or a fogged compressor. The owner never sees the fails. And a second kitchen will run a subtly different sheet within a month.
A digital line check keeps the same twenty-minute walk but stores every reading with a timestamp, flags out-of-range numbers on the spot, and turns repeat failures into exceptions someone must close. That shape of checklist, numeric limits, photo proof and fix-by escalation, is exactly what Food Ops is built around; open the Food Ops demo and walk one line check on your phone before tomorrow's dinner service.