Catering Dispatch. User manual.

1. Prepare flight data for the correct station and service date. Review the flights and correct missing or stale information.
2. Plan missions by reviewing driver shifts, mission requirements, and assignment suggestions. Resolve unassigned flights or conflicts.
3. Coordinate release with dock and kitchen users as applicable. Confirm the correct driver, load, dock, and vehicle.
4. Execute the mission from the driver's mobile mission screen. Drivers follow the listed galley steps, record required evidence, and update status.
5. Monitor and close out using the dispatch board, tracking, tower, and reports. Record delays, cancellations, and operational changes accurately.

The system supports operational coordination; it does not replace airline, airport, security, food-safety, or company procedures. Follow local SOPs and supervisor direction whenever they differ from this guide.

1. Open your organization's Catering Dispatch web address.
2. Choose Dispatch for dispatcher/office access or Driver for mobile driver access, when the sign-in screen offers the choice.
3. Enter the username and password provided by your administrator, then choose Sign in.
4. If prompted to change your password, create a new one before continuing.
5. Use Sign out when you finish on a shared device.

Accounts are provisioned by an administrator; if you do not have an account or see an account-linking message, contact dispatch/admin. Do not share passwords.

Your navigation is limited by the permissions on your account. Common work areas include:

• Dispatcher: Dispatch board, Tracking, Call-offs, Messages, Fleet, Reports, Drivers; manager/admin-only sections may include Settings, Flight Data, Delay Intelligence, and Admin.
• Driver: My Missions, Messages, mission execution, GPS/location sharing, delay reporting, and required acknowledgments.
• Tower: Operations, Callbacks, Swaps, Live map, and Records; edit access varies by configuration.
• Dock: Outbound docks, driver/dock coordination, checklist/release functions, and tier-specific tools.
• Kitchen: Food-check assignments and a station monitor, with alerts requiring acknowledgment.
• Manager/admin/regional: Additional station, configuration, fleet, reports, users, and multi-station capabilities according to granted privileges.

If the expected screen is missing, ask an administrator to confirm your role, station access, and account status.

Where a station selector is available, verify the active station before changing or reviewing operations. Some users can access only stations explicitly granted to them. Navigation may collapse to save screen space; reopen it with the sidebar control.

1. Open Dispatch.
2. Confirm the station shown in the navigation and select the correct service date.
3. Check that the board displays the expected flight activity before assigning work.

The board includes actions for importing flight data and synchronizing available live-flight information. The exact buttons and data sources may depend on station configuration and permissions.

1. Use the configured import/sync action for your station.
2. Review the result and compare the flight list against your authorized schedule source.
3. Check flight number, route, aircraft/tail, ETA, ETD, gate, service type, and mission type.
4. Correct incomplete or inaccurate records using the board's edit/add flight actions, if your role permits.
5. Recheck the board after a schedule update, aircraft swap, or major timing change.

Do not assume an empty or unchanged board means no flights. Confirm the selected date/station and data refresh status. Do not clear flights as a routine refresh; clearing deletes that station/date's flight records and cannot be undone.

Use the available views to match the operational question:

• List: scan and edit flight rows/cards.
• Timeline: see missions and timing relationships across the day.
• Pucks: compact mission overview.
• Gates / Airport map: visualize gate or airport positions where configured.
• Aircraft: inspect aircraft movement/turn information where available.

Use search and filters such as all, alerts, unassigned, active, or cancelled to focus the board. Return to All before concluding that a flight is absent.

Before assigning, look for warnings, unassigned flights, timing conflicts, missing drivers, expired or inconsistent flight data, aircraft/tail changes, international requirements, and mission/service mismatches. Open a flight's details when you need more context.

1. Open the correct station/date in Dispatch.
2. Check that active drivers and shifts are present and accurate.
3. Review pending/unassigned flights and their mission/service details.
4. Use automatic pairing/assignment if offered, then inspect the proposed assignments before relying on them.
5. Manually assign or adjust missions when necessary, observing shift coverage, truck capacity, boarding times, travel/reload gaps, and any station-specific rules.
6. Confirm each flight has the appropriate driver, and confirm any split or special mission instructions.
7. Monitor the board after assignment; adjust for late schedule updates, call-offs, vehicle problems, and operational changes.

Auto-assignment is a planning aid, not a substitute for operational judgment. It uses configured shifts, mission durations, timing windows, truck capacities, reload and travel buffers, and special qualifications. Review unassigned flights and any exception indicators rather than assuming every flight was paired.

The board and driver mission view use statuses such as Pending, In progress, Complete, and Cancelled. Use the status shown on the app and local SOP. A mission should not be marked complete unless the assigned work has actually been finished.

When times, gates, tails, service, or aircraft details change:

• Verify the updated data and whether it changes the driver plan.
• Communicate consequential changes through the approved channel (including Messages when appropriate).
• Check whether an assignment, dock, mission step, or connection needs to be updated.
• Record the change or delay using the appropriate workflow so later users can see the operational context.

Delete/cancel only when authorized and after confirming the exact flight, station, and date. The board's clear flights action removes all flights for the selected date/station and is explicitly destructive. Prefer correcting an individual flight or marking it cancelled where appropriate.

1. Sign in to the Driver portal with the credentials provided by dispatch.
2. Complete any required password, van, fleet point-of-inspection, or dock-change acknowledgments.
3. Turn on GPS/location sharing and allow the browser permission. The app may require location to access mission work and to share progress with dispatch.
4. Open Missions and review the active mission, the rest of today's flights, and any new dispatch messages.
5. Confirm flight number, aircraft/tail, route, ETA/ETD, boarding time, gate, dock, service type, and any international/split-mission note. Raise discrepancies before proceeding.

The mission card shows the job's timing and required steps. Mission steps are configured by the operation and may differ by mission type (for example, separate First Class and Coach steps).

1. Select Start mission when you are ready to begin the first step.
2. Complete the displayed galley/service step in accordance with local procedure.
3. Take and save a photo for the galley/step if required by station configuration. If required evidence is missing, the system may prevent step completion.
4. Select the action to complete the current step. Verify the status advances to the next step.
5. Repeat until all required steps are complete and the mission is closed.
6. Report a delay through the mission's Report delay action when applicable, and message dispatch about urgent changes.

• Never interact with the screen while driving. Stop in a safe, approved location first.
• GPS/location must be enabled for location-dependent workflows. If permission is denied, enable location in device/browser settings and reload/reopen the app.
• A message from dispatch may trigger a sound, vibration, or on-screen notification. Open Messages to read and respond.
• If the mission card says No open missions, stand by for dispatch and check Messages. Do not take an unassigned flight without confirmation.
• If your assignment is split, follow the exact role-specific instruction on the mission card; contact dispatch if unclear.

1. Open Dock and review the drivers/flight groups shown.
2. Confirm the driver's open flights and intended dock.
3. Assign the appropriate dock number. If there are no open flights, resolve the assignment with dispatch rather than assigning a dock speculatively.
4. Confirm the assigned dock is visible to the relevant users.

1. Confirm the correct flights and driver are grouped for release.
2. Review food-check status and any kitchen alert or outstanding request.
3. Confirm required checklists and load details per local procedure.
4. Complete the release/checklist action only when the load is ready and verified.
5. Ensure the release is reflected on the dock screen and notify dispatch of exceptions.

A release in the app is an operational record; it does not replace physical inspection or required paperwork.

Use Tracking to monitor available driver/vehicle locations and operational activity. Location accuracy and freshness depend on device permission, GPS, browser support, connectivity, and the driver's app being active. Confirm by radio/phone when a safety-critical decision cannot rely on the map alone.

Dispatch alerts can identify conditions such as an unassigned flight, a mission not started, or work not complete within configured time windows. Treat alerts as prompts to investigate, not proof of cause. Open the flight and contact the responsible operator before taking corrective action.

Drivers can report a delay from the mission screen. Managers may use Delay Intelligence to review delays by date, station, category, responsibility, investigation status, and evidence. Record facts and times accurately. Distinguish confirmed causes from hypotheses, and add corrective actions when required.

Dispatch and drivers can use Messages for operational coordination. Check unread indicators and acknowledge important instructions using the channel/process required by your station. Messages supplement, but do not replace, required radio/phone contact for urgent or safety-critical matters.

Use Call-offs to review or process staffing call-off information as permitted. After a call-off, confirm coverage on the shifts/driver list and reassess affected missions. Follow established attendance procedures.

Fleet screens support vehicle availability and inspection-related workflows. Complete required inspection/point-of-inspection steps before operating a vehicle. Report damage, defects, or out-of-service status through the approved process; do not rely on the board alone for vehicle safety.

Managers/dispatch users with permission can review driver accounts, shifts, and staffing details. Ensure the correct driver is active, has the proper station/role, and is scheduled for the correct shift. Do not edit user access or credentials unless authorized.

Use Reports for the reports available to your role and station. Select the correct dates and station, then verify filters before exporting or sharing. Treat reports containing employee, flight, or operational information as internal unless approved for external distribution.

Settings and Admin are permission-restricted. They can affect mission steps, timing buffers, alerts, station setup, accounts, integrations, and other operational behavior. Change only values you are authorized to manage; document material configuration changes and verify the result with an appropriate test or supervisor.

• Keep passwords private; sign out on shared devices.
• Verify station, date, flight, driver, and dock before making operational changes.
• Never use a destructive action to solve a data-refresh problem.
• Use radio/phone and local escalation procedures for urgent, safety-critical, or time-sensitive matters.
• Do not treat a suggested assignment, alert, or location marker as authoritative without verification.
• Capture and share only appropriate operational photos; follow company privacy and data-retention rules.
• Follow airport security, ramp safety, food safety, and vehicle procedures at all times.

• Confirm login, station, and service date.
• Refresh/import flight data and verify against the authorized schedule source.
• Review gates, aircraft/tails, ETA/ETD, service and mission type.
• Confirm drivers, shifts, vehicles, and special qualifications.
• Run or review assignments; resolve unassigned flights and warnings.
• Coordinate dock/kitchen readiness and communicate exceptions.

• Sign in, complete required acknowledgments, and enable GPS.
• Confirm flight, aircraft, gate, dock, boarding time, service type, and instructions.
• Start the mission only when ready to perform the work.
• Complete each configured step; capture required photos.
• Report delays and changes; message dispatch as needed.
• Confirm all steps are complete before closing the mission.

• Correct driver and flights are grouped.
• Correct dock is assigned.
• Food check and load are verified.
• Alerts, requests, and acknowledgments are resolved.
• Required physical checks and paperwork are complete.
• Release is recorded and exceptions are communicated.