Prep Station
For kitchen ops & catering teams
Opening work that actually finishes Not a checklist lost in the group chat
Prep Station runs checklists on any record, temperature logs with pass/fail, photo proof, recurring opens, and My Tasks for every cook, so the kitchen opens the same way every day.
No credit card required · My Tasks per person · Cancel anytime
Opening Checklist (BOH)
Downtown kitchen · window 06:00–09:00
To Do
3 tasks3 open / 1 closed
Turn on equipment
Jul 12, 06:15
Walk-in cooler temp
Jul 12, 07:00
Freezer temp
Jul 12, 07:15
Inspect prep area (photo)
Jul 12, 08:00
Why tasks and checklists in Prep Station
01
Open the same way every day
Recurring checklists with assignees replace the whiteboard that never gets wiped.
02
Prove the work
Temperature logs, photo proof, and pass/fail replace "someone said they did it."
03
One inbox for open work
My Tasks shows kitchen opens and CRM follow-ups in the same place for each person.
No credit card for the live demo
Complete a checklist and temp log in the demo
Cancel anytime
Serious kitchens do not run on “did you check the walk-in?” Group chats forget. Whiteboards lie. Audits do not.
When opening work lives in texts and memory, temps get skipped, photo proof never happens, and the GM finds out at the health inspection. Take the open seriously enough to assign it, prove it, and see who still owes it.
Take the open seriously
The checklist belongs on the record, the temp belongs in the log, and every cook sees their open work before the first tray goes out.
From list to done
Assign it, prove it, then unblock the next step
Checklists attach to real kitchen work. Structured completion captures the evidence. Dependencies keep the next task honest. My Tasks keeps each person focused.
Run an opening checklist and record a walk-in temp in the live demo.
Complete task
Walk-in cooler temp · Opening Checklist (BOH)
Recorded temperature (target 36°F · range 33–40)
In tolerance · task will complete
Also supported
Structured completion
Done means proven, not guessed
A checkmark is fine for unlocking doors. A walk-in needs a recorded temperature against a target and tolerance. Out of range fails the task so the audit trail stays honest.
- Checkmark, number, temperature, photo proof, or multi-step verification
- Temperature goals with min/max tolerance and pass/fail
- Photo capture when the open needs visual proof
My Tasks
Every person sees their open work
My Tasks is the personal inbox for assigned kitchen work and CRM follow-ups. Overdue, today, and this week counts sit next to the next-up list so nothing hides behind \"I thought someone else had it.\"
- Quick filters for today, overdue, week, failed, and closed
- Dashboard widget and nav summary with the same overdue / today / open counts
- Assignees by person or role, like @chef or @manager
My Tasks
Tasks assigned to you.
1
Overdue
3
Today
4
This week
Walk-in cooler temp
Call Westside Gallery re: Fri drop
Count dry goods after PO receive
Weekly deep clean · walk-in
Receiving · dependency chain
Count stays blocked until the PO lands
Receive PO #1842
CompletedDone · 11:42
Count dry goods after PO receive
BlockedWaiting on receive
Update par levels
PendingStarts after count
Dependencies & recurrence
The next step waits until the last one is real
Task dependencies keep inventory counts from starting before the PO is received. Recurring lists spawn the next open on schedule, like a daily temp log or weekly deep clean.
- Blocked status until the prerequisite task completes
- Recurring daily temp logs and weekly deep cleans
- CRM follow-ups land as real tasks with due dates
Before the first tray
Open like you mean the rest of the day
Temps logged, prep inspected, assignees clear. The same seriousness you bring to costing and delivery belongs on the morning open.
Tasks sit next to the rest of the operation
CRM follow-ups become real tasks beside kitchen opens on the CRM pipeline. Receiving work pairs with meal and production planning, and full-service teams run the same playbook on full-service catering. See pricing for plans.
Questions kitchen leads ask
Straight answers about checklists, completion types, recurrence, and My Tasks.
What can a Prep Station checklist attach to?
Any record. Put an opening checklist on a recipe, a closing checklist on a count session, or a standalone list for the kitchen. The same task system runs everywhere.
Is a checklist just a to-do with a checkmark?
No. Completion can require a checkmark, a numeric entry, a temperature log with pass/fail against a target and tolerance, photo proof, or multi-step verification.
Can tasks repeat on a schedule?
Yes. Recurring task lists spawn the next run on the schedule you set, like a daily temp log or a weekly deep clean.
Can one task wait on another?
Yes. Dependencies block a task until its prerequisite completes. "Count inventory" stays blocked until "Receive PO" is done.
Are CRM follow-ups real tasks?
Yes. Pipeline activities become tasks with due dates, assignees, and the same My Tasks inbox as kitchen work, so sales follow-ups do not live in a separate tool.
Where does each person see their work?
My Tasks shows open work assigned to you, with quick filters for today, overdue, this week, failed, and closed. The nav summary and dashboard widget surface the same counts.
Can managers see if checklists actually get done?
Yes. Task completion analytics show whether checklists are finishing on time, including failed out-of-tolerance temperature entries for audit.
Prep Station
Run the open like you run the event
Assign the checklist, require the temp or photo, unblock the next step, and let every cook see their work in My Tasks.
No credit card required · Cancel anytime