JavaScript required
We’re sorry, but Coda doesn’t work properly without JavaScript enabled.
Skip to content
Rams Kitchen - Research
From available published research
Risks, Effects & Mitigations
Limitations and Boundaries
Considerations
Users
Batching Heuristics
More
Share
Explore
Batching Heuristics
🍲 Ram’s Kitchen – Batching Heuristics
1. Grouping
Always
group orders by dish + pickup slot
(e.g.,
Veg Biryani @ 12:30
).
If multiple employees order the same dish in the same slot → cook them together.
2. Merging Slots
If the same dish appears in
adjacent slots within 15 minutes
(e.g., 12:30 & 12:45):
Merge them into one batch
if cooking together doesn’t make earlier orders late
.
Don’t merge if it risks delaying the earlier slot by more than
5–7 minutes
.
3. Batch Size Limit
Never cook more than
20 plates in one batch
(kitchen/stove limit).
If more orders come in, split into smaller manageable batches.
4. Prioritization
Work on orders in this order of priority:
Overdue
(⚠️ always handle first)
In Progress
(finish before starting new)
Placed
(start the earliest slot first)
Ready
(handover / wait for pickup)
5. Dynamic Updates
If
new orders arrive
for a dish you’re about to cook:
If they fall in the
same slot
, add them to the current batch.
If they’re in the
next slot but close enough (≤15 min)
, consider merging.
6. Walk-ins
Log all walk-in orders in the system as
Placed
so they join the same batching logic.
Don’t treat them separately → one unified queue avoids confusion.
7. Status Updates
Always update batch status:
Start Batch
→ moves all included orders to
In Progress
.
Complete Batch
→ moves them to
Ready
+ notifies employees.
Keeps everyone (employees + kitchen) aligned.
8. Alerts
Overdue orders must be
pinned red at the top
of the dashboard.
Use reminders if an order stays In Progress too long.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
Ctrl
P
) instead.
