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.
- Catering Order Management
- Features
- Order review
Order review
Record a named decision, reason and revision for each enquiry.
OverviewOrders Awaiting Approval×
Catering Order Management · Order review
New
Orders Awaiting Approval
Catering orders
| Order number | Event name | Order status | Revision | Order total USD | |
|---|---|---|---|---|---|
| CO-97107 | Event 636 | Enquiry Review | 930 | 240 | |
| CO-90515 | Event 238 | Enquiry Review | 290 | 740 | |
| CO-27298 | Event 870 | Enquiry Review | 320 | 680 | |
| CO-74802 | Event 216 | Enquiry Review | 120 | 680 | |
| CO-36992 | Event 544 | Enquiry Review | 430 | 650 |
6 of 6 records
Event 636Catering orders · CO-97107
Enquiry ReviewRevision930
Order total USD240
What you can do
Order review in daily work
An enquiry changes after the client adjusts headcount. The coordinator updates the order revision and sends the current event details for review. The approver sees the client, billing party, date, total and any open exception before deciding. A recorded decision includes the approver, reason, decision time and source revision.
A decision records what the Catering Approver decided, when, why and against which order revision. The decision and the order status are separate records. The Event Coordinator checks that the approved revision still describes the event before changing the order status.
How the work is organized
- Present the enquiry. Show the current order, its selections and any open exception to the Catering Approver.
- Record the decision. Keep the reason, approver and source revision with the order.
- Handle changes. Request a new decision after a material edit to an approved enquiry.
What to agree during setup
Agree which event changes require another decision and how approvers should handle a returned revision. The approval record must point to the catering order and its company. The team should decide who may change order status after the decision and who verifies the revision still matches.
Pilot an enquiry that changes after the first review. Give the Catering Approver the old and current revisions, then have the Event Coordinator explain which decision can support confirmation. Include a returned decision with a written reason.
Check the handoff on an actual case
Choose an enquiry in review, inspect its revision and record an approval or return with a reason. Reopen the order and confirm the decision refers to the expected revision. If the coordinator changes the headcount afterwards, treat the revised order as a new decision case rather than relying on the old approval.
The Catering Approver should open Orders Awaiting Approval, identify the current order revision and record the decision. The Event Coordinator checks Returned Or Rejected Approvals for a reason to correct the enquiry.
What your team sees
- Orders Awaiting Approval — Use this list to identify the records that need attention.
- Returned Or Rejected Approvals — Open the related records to check status and evidence.
Follow the work through
Follow the enquiry and review, menu and kitchen preparation, venue delivery, and payment and exception closeout paths. Use the data model when checking references and the role guide when assigning access.
What it keeps track of
Data model- Approval decisions
- Independent approval decisions taken on catering enquiries and exceptions.
- Catering orders
- Catering orders from event enquiry through headcount planning, kitchen prep, delivery and billing.
- Catering exceptions
- Issues raised against a catering order: ingredient shortages, venue access, deposit holds and food safety.
Who uses it
Permissions- Catering Approver
- , Event Coordinator.
- The Admin maintains access and company scope; the named team members own the records and decisions described above.
Set up Catering Order Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.