Systems we plan to work with
Nothing is connected in this prototype. Every status below is honest: planned, not built.
Works with what you already use, or with paper
Many kitchens run on paper and memory. A photo of the printed order is enough to start, and every connection below is optional. Scan an order
Reading the event order
The event order is where every pull sheet starts. Read it from the system that prints it, so nobody retypes or photographs the BEO.
- CatereasePlanned
The event order: menu, guest count, room and times. The pull sheet fills itself, and a change to the order shows up before the crew pulls.
- TripleseatPlanned
Event orders and room bookings, so the crew sees the right room and the right time on their phone.
- CBORDPlanned
Campus dining and catering orders, for kitchens that run catering through campus dining.
Crew, schedule and clock in
Know who works each event without a second list, so leave by times and the crew sheet are right on their own.
- WorkdayPlanned
The worker roster: name, worker ID and department, so the crew sheet uses the same names as payroll. Clock in times could go back later, after a pilot.
- HumanityPlanned
The shift schedule: who works which event, start and end. It fills the crew sheet and the Leave by column.
Product names belong to their owners. No logos are shown until we have checked each company's press kit.