1. Logistics Tracking System
  2. Process
  3. Correct scope and reconcile effects
Process · Correct scope and reconcile effects

Correct scope and reconcile effects

Preserve executed history while checking corrections and receipt outcomes against linked records.

Step by step

  1. Request correction Load Owner

    Load Owner identifies the load, current scope and reason. Dispatcher reads its revision, ordered stops and related operation receipts before changing anything.

    • Identifies current and prior scope
    • Updates Loads, Load stops, Operation receipts
  2. Distinguish execution Dispatcher

    Dispatcher separates draft scope from a route already accepted or acted on. An unexecuted Draft load may be Cancelled; earlier accepted work remains in its record history.

    • Cancels only unexecuted work and preserves prior effects
    • Updates Loads, Load stops, Load assignments
  3. Review changed scope Operations Reviewer

    Dispatcher checks the successor load revision and changed stops before planning the corrected route. An Operations Reviewer may record an independent approve, reject or return decision with a reason against that revision.

    • Checks the changed revision and records any independent decision
    • Updates Review decisions, Loads, Record attachments
  4. Reconcile receipt Operations Reviewer

    Operations Reviewer compares a Pending or Failed receipt's expected revision and effect references with the linked local records. A matching effect can be marked Completed; a discrepancy becomes needs review.

    • Confirms linked effects or records discrepancy
    • Updates Operation receipts, Loads
Load Owner
Requests and explains the correction; Dispatcher checks physical and planned scope; Operations Reviewer records independent decisions when needed and reconciles effects; Admin governs access.

Set up Logistics Tracking System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started