These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Commissary Kitchen Management
- Features
- Client bookings
Client bookings
Follow each client request through kitchen use and completion.
OverviewCompleted Bookings×
Commissary Kitchen Management · Client bookings
New
Completed Bookings
Bookings
| Reservation number | Client | Kitchen | Starts at | Ends at | Status | |
|---|---|---|---|---|---|---|
| BKN-86707 | CUS-049 | KTC-1164 | 04 Oct | 07 Oct | Completed | |
| BKN-44940 | CUS-230 | KTC-8069 | 12 Oct | 18 Oct | Completed | |
| BKN-81451 | CUS-222 | KTC-5051 | 11 Oct | 20 Oct | Completed | |
| BKN-13834 | CUS-056 | KTC-8394 | 08 Oct | 11 Oct | Completed | |
| BKN-43252 | CUS-021 | KTC-8803 | 10 Oct | 17 Oct | Completed |
6 of 6 records
CUS-049Bookings · BKN-86707
CompletedKitchenKTC-1164
Starts at04 Oct
Ends at07 Oct
What you can do
Give every request a clear owner
A booking joins a client organization to a named kitchen and start and end dates. It also carries attendee count, slot rate and lifecycle status. Property Manager uses that record to follow a request from intake through confirmation, kitchen use and completion. The client record keeps contact information beside the operational history.
Requested calls for the coordinator’s capacity and overlap check. Confirmed is a commitment the front desk can prepare for. In progress identifies kitchen time being delivered. Completed closes the operational booking, while Cancelled records one that will not proceed. Those values distinguish a future request from a confirmed commitment.
How the work is organized
- Client identity. Keep the organization’s name, email and phone on one record.
- Booking identity. Use the booking number to connect charges, payments, add-ons and tasks.
- Lifecycle review. Let status and interval show the next decision due.
What to agree during setup
Decide who creates and changes clients, who owns booking intake, and who approves a requested interval. Property Manager manages clients and bookings; Front Desk Agent can view them and capture linked work. A confirmation decision should use the same client and kitchen identity that later records will reference.
Set a practical rule for changes after confirmation. A changed end date can affect kitchen availability, task timing and charges. The editor should inspect linked records before promising the new interval. On cancellation, review open tasks and pending financial records against the booking. Agree how the team tells the client which booking number to use for follow-up.
Check the handoff on an actual case
A food business requests a kitchen for a planned production window. Property Manager creates or selects the client, chooses a kitchen and enters the interval, attendee count and slot rate. Kitchen Coordinator checks capacity and other active intervals. Once confirmed, Front Desk Agent can prepare a cleaning or client service task tied to it. Finance Officer can later record a booking charge and payment against that booking, preserving the event behind each amount.
During the booked window, Property Manager marks the booking in progress. The team records service work and add-on activity against it. Before completion, Property Manager reviews posted charges and confirmed payments and agrees with Finance Officer how to handle any remaining amount. The completed booking remains available for financial and operational follow-up.
What your team sees
- Requested Bookings — Client requests awaiting a kitchen decision.
- Confirmed Bookings — Committed kitchen time ready for preparation.
- Completed Bookings — Finished sessions available for financial review.
Follow the work through
Use request and confirmation for intake, then booking delivery for work after confirmation.
What it keeps track of
Data model- Bookings
- Kitchen bookings with client, kitchen, dates, rate, attendee count and lifecycle status.
- Clients
- Client organizations and contacts that book shared kitchen time.
- Kitchens
- Bookable commissary kitchens with type, station capacity and operational status.
- Booking charges
- Charges posted against a booking, with usage date, description, amount and status.
- Payments
- Payments received against a booking with amount, reference and status.
- Add on bookings
- Add-on bookings captured against a booking, with add-on type, name, start and attendee count.
- Service tasks
- Cleaning, maintenance and client service tasks for a kitchen and booking.
Who uses it
Permissions- Property Manager
- Owns booking intake and lifecycle changes.
- Kitchen Coordinator
- Approves feasible requests.
- Front Desk Agent
- Records linked work.
- Finance Officer
- Handles charges and payments.
- Operations Reviewer
- Examines evidence.
Set up Commissary Kitchen Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.