1. Catering Order Management
  2. Features
  3. Venue handoffs
Feature · Venue handoffs

Venue handoffs

Track the receiving partner, submission and decision on each event handoff.

OverviewPending Venue Handoffs
Catering Order Management · Venue handoffs

Pending Venue Handoffs

Approval waits for the venue coordinator

New
Handoff numberCatering orderHandoff channelHandoff statusHanded off at
VH-90529CO-48100HC-168Submitted24 Oct
VH-25451CO-52706HC-465Submitted13 Oct
VH-87295CO-49974HC-471Submitted12 Oct
VH-62290CO-57725HC-659Submitted25 Oct
VH-28625CO-47746HC-783Submitted07 Oct
6 of 6 records
HC-168Venue handoffs · VH-90529
Submitted
Catering orderCO-48100
Handed off at24 Oct
Example screen with sample data

What you can do

Venue handoffs in daily work

A partner venue needs the event handoff before the kitchen dispatches the order. The coordinator creates a handoff with a channel and partner reference, then submits it for decision. Its status distinguishes a draft from a submitted, approved, rejected or completed handoff. Event documents can stay linked to the catering order for the receiving team.

The handoff record identifies an order, its channel and the reference used by the receiving partner. Its status records the team’s handoff decision; the partner’s actual receipt still needs to be checked through the agreed channel. The Venue Coordinator compares the handoff with dispatch and setup on the same order.

How the work is organized

  • Identify the partner. Put the agreed channel and partner reference on the handoff.
  • Decide before service. Review a submitted handoff before marking it approved.
  • Confirm arrival. Check dispatch and setup records against the handoff’s order.

What to agree during setup

Agree which partner reference identifies the event, who can submit a handoff, and who approves it. Decide how the venue team confirms receipt and records completion. The order, company and handoff record should agree, especially when several events go to the same venue.

Pilot an event delivered through a venue kitchen. Give the Venue Coordinator the partner reference and channel, then ask the Catering Approver to review a submitted handoff. Rehearse a rejected reference and its correction.

Check the handoff on an actual case

Review a submitted handoff against the event date, venue address and planned dispatch. The approver records the handoff decision in its status. On completion, the venue coordinator checks the partner reference and the setup event against the catering order. A rejected handoff returns to the coordinator for correction.

The Venue Coordinator should find the submitted record in Pending Venue Handoffs and compare it with the order. After a decision, check the dispatch and setup events before marking the handoff completed.

What your team sees

  • Pending Venue Handoffs — Use this list to identify the records that need attention.
  • Dispatched And Delivered Events — 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
Venue handoffs
Handoffs of an event to venues, partner kitchens and logistics providers.
Catering orders
Catering orders from event enquiry through headcount planning, kitchen prep, delivery and billing.
Kitchen and logistics events
Kitchen prep, packing, dispatch and venue set-up events for a catering order.
Event documents
Event documents: banqueting event orders, menu sheets, allergy notes and signed delivery dockets.

Who uses it

Permissions
Venue Coordinator
, Catering Approver.
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.

How to get started