Transportation Operations SoftwareBook a product walkthrough
Menu

Airport recovery workflow

Recover a late airport trip without losing the thread.

Follow one arrival change through conflict, options, approval, acknowledgement, verification, and billing review.

Book a product walkthrough Bring us one real workflow
TOOSARoute planning workspace
Route operationsAirport movement plan
Planning

Route sequence: Airport curb, 06:20; Hotel stop, 07:10; Convention district, 08:05.

TOOSAAirport recovery workflow
Source changeArrival moved by 24 minutes

Duty 08 and the next passenger commitment need review.

  1. 01DetectConflict found
  2. 02Compare2 options
  3. 03ApproveNamed owner
  4. 04VerifyReadback ready

Recovery workflow

Late-arrival airport recovery

A generic airport pickup with an owned-vehicle plan, a downstream assignment, and conditional affiliate capacity.

Trigger

The arrival moves later. The original vehicle can no longer protect the next assignment and the passenger promise at the same time.

Affected state

  • Passenger job and current reservation version
  • Assigned driver and vehicle availability
  • Downstream duty and service-window conflict
  • Owned and affiliate capacity conditions
  • Customer communication and invoice context

Options for review

Feasible after checks

Reassign owned capacity

Protect the pickup with a compatible vehicle and require driver acknowledgement before commitment.

Conditional

Request affiliate capacity

Preserve the option while rate, service condition, and provider acknowledgement remain unresolved.

Failure state

Stop, preserve state, and escalate

If no option passes the required checks, or an approved update cannot be verified, leave the exception visible. Preserve partial and failed responses, then return the decision to a named operator.

Governed change sequence

  1. 01
    Observe
  2. 02
    Check
  3. 03
    Compare
  4. 04
    Approve
  5. 05
    Act
  6. 06
    Verify
  7. 07
    Record

Verification readback

  • Assignment response matched to the current record
  • Driver acknowledgement shown
  • Customer update status shown
  • Source record checked after the proposed update
  • Change reason carried to closeout

Controlled assistance

The sequence matters more than the label.

Useful assistance begins with source evidence and ends with verification. Approval is scoped to an exact action set; it expires when the relevant state changes.

  1. 01
    Observe
  2. 02
    Check
  3. 03
    Compare
  4. 04
    Approve
  5. 05
    Act
  6. 06
    Verify
  7. 07
    Record

Action boundaries

Observation is not authority.

Every consequential update needs a named owner, exact scope, readback, and failure path.

Observe or draftNamed approval requiredOutside the boundary
Observe or draftRead the source event and affected record versionNamed approval requiredReassign a driver or vehicleOutside the boundaryOperate or control a vehicle
Observe or draftApply timing, capacity, and availability checksNamed approval requiredCommit affiliate capacity or a rateOutside the boundaryOverride a safety rule
Observe or draftCompare service and commercial conditionsNamed approval requiredSend an external customer commitmentOutside the boundaryExceed configured authority
Observe or draftDraft role-specific updatesNamed approval requiredChange invoice-affecting actualsOutside the boundaryHide partial execution or failure

Bring one real workflow

Bring one change your team still recovers manually.

Describe the trigger, roles, decision, handoffs, and closeout without sending operational records.

Book a product walkthrough Bring us one real workflow