Ingredient runners and prep tickets that match the line

High-volume Indian kitchens often separate guest-facing tickets from prep pulls—marinades, chopped mise, batch sauces, and pastry components that move before anyone taps “confirm” on a phone. If your kitchen display only shows guest orders, ingredient runners invent side channels: paper chits, shouted requests, or worse, memory.

This article defines when prep belongs on the same KDS, how to use colour and priority without noise, and how to close loops at end of service.

Spotlight

High-volume kitchens separate guest-facing tickets from prep pulls. If your stack only shows guest orders, ingredient runners will invent side channels—paper, voice, or worse.

Define whether prep tasks live in the same system or a parallel board, but never both without a rule.

Colour, priority, and verbs everyone uses

Use consistent priority language: rush, standard, hold. If the pass shows “hold” without a resume time, someone will guess wrong. Align verbs with what cooks actually say out loud—shared vocabulary beats clever jargon.

Sequencing for Indian menus

Gravies, tandoor batches, and fried components have different lead times. Prep tickets should show dependencies when one pull blocks another—especially for thalis and combo plates.

End of service

Close prep loops before you close the register. Leftover mise should map to tomorrow’s opening checklist. Digital systems make this auditable; use that visibility.

When prep should split to a second board

If prep volume routinely exceeds guest ticket volume before noon, consider a dedicated prep KDS or tablet—same data model, different filter. The failure mode to avoid is two truths: paper prep chits that contradict the screen. If you split, sync completion events back to one reporting layer so costing stays honest.

Runner routes and station layout

Map physical paths: cold prep → hot line → pass. Runners should not cross the fryer blind spot with raw proteins. If your floor plan forces awkward crossings, schedule staggered prep pulls so runners are not in the same square metre during rush. Time studies sound corporate; they prevent collisions.

Batching for thalis and combos

Combo plates often need four components firing on different timers. Prep tickets should list child tasks explicitly: rice, dal, veg, protein—each with expected ready time. If your system supports sub-tasks, use them; if not, standardise abbreviations on the ticket face so expo can read it at a glance.

Supplier variance and substitutions

When a crate arrives short or different spec, prep tickets should update before guest orders reflect those ingredients. Tag substitutions with “TEMP” and a date. Runners should not improvise swaps without a recorded note—food safety and guest trust both depend on traceability.

Integrating with inventory counts

If you count stock nightly, tie prep completions to depletion. Mismatches between what prep pulled and what inventory shows reveal theft, waste, or miscounts. You do not need perfect automation—just consistent IDs on tickets that map to SKU codes.

Training: shadowing and vocabulary

New runners shadow for at least five shifts with feedback on two dimensions: speed and read accuracy. Misread modifiers are worse than slow feet. Build a cheat sheet of house abbreviations: “HOT” for hold, “RFS” for ready for sauce—whatever matches your kitchen dialect.

Metrics that matter

Track prep-to-guest lead time, open prep tasks at peak, and refires caused by prep misses. If refires spike after prep changes, the issue is sequencing, not line talent. Weekly, review the top three prep failures; fix root causes in SOP.

Failure modes and recovery

When prep fails, guest tickets should show a clear “waiting on prep” state so captains do not promise plates. Recovery scripts belong in both KDS and QR messaging: honest delays beat silent stalls.

Cloud kitchens and commissary pulls

If you run central kitchens feeding multiple brands, prep tickets must include destination and brand tags. Cross-brand contamination is a process problem—solve with colour and barcodes, not hope. Reconcile commissary sends nightly against guest sales by SKU.

Technology adoption without friction

Choose tools runners will actually tap. If a tablet requires six taps to close a prep task, they will use paper. Pilot with one station, measure adoption rate weekly, and iterate. Success looks like fewer shouted requests, not more dashboards.

Seasonality and menu changes

Monsoon produce and festival imports change prep times. Update default prep durations in your system when ingredients shift—guest ETAs depend on honest upstream numbers. Document who owns those updates—usually the chef and inventory lead together.

Summary

Prep is the invisible half of digital ordering. When prep tickets are as legible as guest tickets, runners stop improvising, expo stops guessing, and guests get what they ordered—hot, complete, on time.

One last habit

End service with a five-minute huddle: open prep items, tomorrow’s pulls, and anything the morning team must not miss. The KDS can store it, but voice reinforces priority. Consistency here is how digital and physical kitchens stay aligned.

FAQ

Do we need a separate screen for prep? Only if traffic is high enough to justify it—otherwise tag prep lines distinctly on the same KDS.

How do we train? Pair new runners with a single expediter for a week; verbal shortcuts die when the screen is obvious.

What about multilingual crews? Post bilingual abbreviations where tablets get docked—clarity beats fluency when the pass is loud.

Checklist: prep ticket health

• Every prep task has an owner and a resume rule
• Guest tickets never hide critical prep notes
• End-of-night report shows open prep items
• Bilingual abbreviations posted at the pass

Closing

Ingredient runners and prep tickets work when the pass shows the same story the line already tells—without parallel paper reality, and without mystery pulls that never close on screen. That visibility is the whole point of putting prep on the system in the first place—otherwise you have only digitised chaos. Finish strong every night, and tomorrow’s prep starts calmer, with fewer emergency pulls and clearer ownership on every pull, every shift, every brand, every outlet.