What goes on a kitchen pre-shift prep checklist?

A kitchen pre-shift prep checklist covers four things: temperature verification, station setup to par, a sanitation baseline, and date-labeled prepped product. It is the bridge between an empty kitchen and the first fired ticket. A restaurant prep sheet, also called a kitchen prep list, lists every ingredient and menu component the back of house has to prep before service. It keeps the BOH team aligned and makes sure each station starts the shift with the right quantities of sauces, garnishes, portioned proteins, and cut produce.

The standard pre-shift sequence runs in a fixed order, confirmed across operator-facing sources like the StaffedUp restaurant prep sheet guide and the WebstaurantStore kitchen prep list guide:

1. Temperature verification first. Before pulling any inventory, log the temps of all walk-ins, lowboys, and freezers. If a unit failed overnight, the kitchen manager needs to know before spoilage costs a full prep day.
2. Equipment heat-up. Turn on exhaust hoods. Preheat ovens, fryers, and flat tops so they reach operating temp while the team preps.
3. Sanitation baseline. Mix sanitizer buckets to the correct concentration and distribute to every prep station.
4. Par execution. Review prep pars, run the freezer pull sheets, and prep up to par for forecasted covers.
5. Date labeling. Label every prepped TCS item with a prep date and a discard date.

The four pillars worth calling out:

• Temperature verification. Per the FDA Food Code 2022, Section 3-501.16, cold TCS foods (time/temperature control for safety foods) must be held at 41°F or below. Operating practice is to run walk-in coolers between 35°F and 41°F and freezers between -10°F and 0°F. A cooler reading inside the danger zone (41°F to 135°F) at open is the single most expensive miss on this checklist. See the cold-holding temperature requirements for the full breakdown.
• Sanitizer ppm. The sanitation baseline has hard numbers an inspector will check. Chlorine sanitizer on food-contact surfaces runs 50 to 100 ppm. Quaternary ammonium (quat) runs 150 to 400 ppm. Quat test strips read best at 65°F to 75°F water. A pre-shift checklist should capture the actual ppm reading, not a yes/no checkbox. "Sanitizer mixed: yes" tells a DM nothing. "Quat: 250 ppm, tested" is evidence. The sanitizer concentration log covers the testing method.
• Date labeling. Per FDA Food Code Section 3-501.17, ready-to-eat TCS food prepared in-house and held longer than 24 hours must carry a discard date and stay at 41°F or less for a maximum of 7 days. The prep day counts as day 1, so the discard date is prep date plus 6. The FDA does not mandate a label format, which is exactly where multi-unit chains lose consistency: 30 stores, 30 label conventions. The date labeling and FIFO rotation guide standardizes it.
• Station setup to par. An organized prep station is the cornerstone of an efficient kitchen. When every utensil, ingredient, and component is in its place, cooks move through tickets without leaving the line.

How pre-shift prep differs from the line check

Pre-shift prep is station setup before the first ticket. The mid-shift line check is a temp-and-quality verification during service that catches temperature drift. They are different tasks with different owners. This table maps it out:

| Task | When | Scope | Owner | Question it answers |
|---|---|---|---|---|
| Kitchen pre-shift prep checklist | Before first ticket | Station par, temps, sanitizer, labels | Prep cook or kitchen manager | Is the line ready to fire? |
| Mid-shift line check | During service, pre-dinner changeover | Temp drift, hot-hold, quality, taste | Line cooks or shift lead | Is the line still in spec? |
| Whole-restaurant opening checklist | Store open | FOH, BOH, facilities, register | Opening manager | Is the whole store ready to open? |

For the mid-service side, see the mid-shift line check. For the full store open, see the whole-restaurant opening checklist. One note: a pre-shift meeting (the lineup or huddle on specials and 86'd items) is a separate thing from the prep checklist. The checklist is physical station readiness. The huddle is the verbal brief.

Sample kitchen pre-shift prep checklist

Here is a sample fast-casual kitchen pre-shift prep checklist to run before the first ticket. It is restaurant-vocabulary only and grounded in what a prep cook actually touches. Use it as a starting point and adjust the items to your menu and station layout.

1. Log walk-in cooler temp. Confirm at or below 41°F. (FDA Food Code 3-501.16)
2. Log lowboy and reach-in temps at each station. Confirm at or below 41°F.
3. Log freezer temp. Confirm 0°F or below.
4. Turn on exhaust hoods. Preheat ovens, fryers, and flat tops to operating temp.
5. Mix sanitizer buckets and record the ppm reading. Quat 150 to 400 ppm, or chlorine 50 to 100 ppm. (Test strips read best at 65°F to 75°F water.)
6. Pull the prep par sheet. Subtract quantity on hand from par. The difference is what to prep today.
7. Execute the freezer pull for proteins thawing for tomorrow.
8. Prep each station to par: sauces, garnishes, portioned proteins, cut produce.
9. Date-label every prepped TCS item with prep date and discard date (prep date plus 6, max 7 days). (FDA Food Code 3-501.17)
10. Stock and align each station: utensils, pans, squeeze bottles, backups within reach.
11. Verify the hand-wash sink is stocked: soap, towels, hot water.
12. Confirm first-in-first-out (FIFO) rotation in the walk-in. Oldest product front.
13. Check the 86 board and note any items the line cannot fire today.
14. Photo the finished line and prepped product as completion proof.

Number 14 is the item a static PDF cannot do. A printed prep sheet has no way to capture a timestamped photo of the set line. You can grab the same structure as a downloadable kitchen prep list template to start, then move it onto a tablet when you need the photo proof and the multi-store view.

Setting par levels so prep matches forecasted covers

A par level is the optimal amount of an ingredient you need on hand to meet demand for a specific day and shift. The prep math is simple: par minus quantity on hand equals quantity to prep. The WebstaurantStore prep list guide and the Qwick kitchen prep list template both anchor the formula the same way.

Pars are not static. They flex with forecasted covers. A Friday dinner par for portioned chicken is not a Tuesday lunch par. Multi-unit operators adjust pars by daypart and by store volume tier, which is exactly where a static spreadsheet breaks. A 200-cover store and a 600-cover store cannot share one prep sheet. The kitchen manager owns par-setting and signs off on completion.

This is also where the math itself causes misses. When a prep cook does par minus on-hand in their head, it is one more place to round wrong. Bacari restaurants eliminated manual calculations by moving the math into the checklist instead of a clipboard. When the form runs par minus on-hand, the prep quantity is right the first time, and it is the same across every unit. The point is not that Xenia forecasts demand. It does not. Pars are configured by the manager, and the form does the subtraction.

How does Xenia track checklist completion?

Xenia runs the pre-shift prep checklist as a daily ops checklist with photo proof, timestamps, and live completion tracking. The completion percentage becomes the kitchen's pulse, and the DM sees it across every store in one view. By the time the line is set, the DM can see which kitchens hit 100% and which one is sitting at 73% with the missing items flagged. The DM calls that store first.

A few mechanics make this work for a prep checklist:

• Temp capture without a clipboard. Items 1 through 3 of the sample list (walk-in, lowboy, freezer temps) can log automatically. Dave's Hot Chicken paired Bluetooth thermometers across all walk-ins, hot-holds, and line stations at 321 locations after migrating from RizePoint. The prep cook does not write a temp on a clipboard. Auto-log temps, auto-alert if out of range, no manual data entry.
• Follow-up plus photo on a failure. If the walk-in reads 44°F at open, the checklist branches: "Walk-in is over range. What did you find? Photo required." The cook describes it and photographs the thermostat. Evidence is captured at the moment of failure, not reconstructed later. The platform stores the photo as evidence. It does not read or grade the photo content.
• Sanitizer ppm and date labels as captured fields. The ppm reading goes in as a recorded value. The label goes in as a photo. So "Quat: 250 ppm" and a photo of the labeled prepped product sit in the record. When the health inspector asks, the trail is already there.

Here is how that compares to a paper prep sheet:

| Capability | Paper prep sheet | Xenia tablet checklist |
|---|---|---|
| Completion proof | Initials on a clipboard | Timestamp plus photo per item |
| Real-time DM visibility | None until a store walk | Live completion % across every store |
| Multi-vertical reuse | One sheet per kitchen | One template, deployed to every unit |
| Temp capture | Handwritten, easy to skip | Auto-logged via Bluetooth thermometer |

One more thing worth being honest about: this is recurring shift-aligned task tracking, not a scored compliance audit. The prep checklist is not weighted or graded. It is the daily task the kitchen already does, made visible. A common adoption pattern is that teams start with daily ops, then graduate to weighted audit scoring once the daily ops habit is the foundation.

Where do operators see results?

Operators see results in three places: prep consistency across units, faster manager mornings, and a food-safety trail that builds itself. The wins are concrete, and they come from named customers, not hypotheticals.

• Prep consistency. Bacari restaurants eliminated manual calculations by moving par-minus-on-hand math off the clipboard. The prep quantity is right the first time, and the same across every unit.
• Automatic temp capture. Dave's Hot Chicken runs Bluetooth thermometers across all walk-ins, hot-holds, and line stations at 321 locations. Items 1 through 3 of the prep checklist log themselves.
• Faster manager mornings. Mezeh cut manager phone calls by 60%. The DM stops calling stores to ask if prep is done. The completion dashboard shows it. That number is specific to Mezeh, not a blanket promise.
• Time to value. Tempstop went paperless in 14 days. That is a paper-to-digital migration reference, not a prep-specific claim.

The multi-unit consistency angle is the whole point for a chain. One template, deployed to every kitchen, with the same par fields, the same temp thresholds, the same label convention, and the same photo requirements. A 30-store chain stops having 30 different prep conventions. The DM sees variance in one dashboard instead of finding it on a store walk. For more on how this fits the broader workflow, see how Xenia handles restaurant task management across multiple units and how the prep habit connects to the closing checklist at the other end of the shift.

How to roll out a pre-shift prep checklist in Xenia

Rolling out a pre-shift prep checklist in Xenia takes one template, configured once, deployed to every kitchen, with par fields and photo requirements set per item. Here is the order of operations:

1. Start from your existing prep sheet. Upload the SOP or prep-list PDF to the AI Template Agent. It converts the document into a digital checklist with fields and conditional logic in minutes, instead of a manual build. It transforms an SOP you already have. It does not invent prep content from a vague brief.
2. Set the par fields. Add a par field and a quantity-on-hand field per item so the form calculates quantity to prep. This is the same pattern Bacari used to eliminate manual math.
3. Add temp items and pair Bluetooth thermometers. For walk-in, lowboy, and freezer items, pair Bluetooth thermometers so temps log automatically. Set the in-range threshold at 41°F for cold TCS.
4. Set follow-up questions and photo requirements. On any out-of-range temp, branch to "what did you find?" plus a required photo. Require a completion photo of the set line.
5. Set the sanitizer field to capture the ppm reading, not a yes/no checkbox.
6. Schedule it per shift. Assign the checklist to the opening kitchen shift across all locations. Use location hierarchy so each kitchen manager sees only their store and the DM sees the district.
7. Watch the issues view. Set the dashboard to surface flagged items and incomplete checklists, not just completion %. The issues view tells the DM where the next miss is forming, not just whether yesterday's tasks got done.

The reason this lands as an entry point: the pre-shift prep checklist is the task the kitchen already runs on paper. Made digital, it is consistent across units and visible to the DM without a store walk.