Skip to content

FOR LOGISTICS OPERATIONS

Loads change. Someone should own the change.

Follow one load from tender and appointment through carrier dispatch, proof of delivery and freight billing. Make the current instruction and the next owner clear.

  • The appointment changes after the carrier accepts
  • Delivered status arrives before usable proof of delivery
  • An accessorial request has times but no approval
Book an intro call

$1,500 fixedOne workflow · Edge assessment

A Trail Map (your reviewed report), three priorities and a 90-day plan.

5 business days after your evidence is in. The call is a free 15-minute introduction.
ProcessScout / TransformReal product · fictional data
Ask Sarah answering a prepared question about why a handoff is delayed, with sources cited (fictional demo data)

Fictional example · MES-011

Bill this load?
Open item
Detention approval missing
Owner
Freight billing lead
Explore the example
Real product, demo data. Mesa Freight Coordination is a fictional example.
David Bell
David BellProcessScout review lead

David brings 25 years of experience in operations and global finance, including Shell and Deutsche Bank. He was founder and CEO of JustPayroll through its 2024 acquisition.

David Bell leads the review approach. The analyst assigned to your assessment owns its recommendations and sign-off. Every paid Trail Map receives human review before delivery.

Meet David on LinkedIn ↗
A business owner and an advisor reviewing a process sketch at a desk
Walk one load from tender to freight bill with the desk that runs it.

HOW THE WORK MOVES FORWARD

Bring a normal load and a changed appointment.

  1. 01

    Bring one workflow

    Confirm the question and scope. Bring authorized source records, a complete walkthrough, supporting documents and a process owner who can answer the open questions.

  2. 02

    5 business days

    Five business days after your evidence checklist is complete. A named analyst reviews the evidence, assumptions, priorities and measurement design before the Trail Map is delivered.

  3. 03

    A 90-day plan

    Receive three priorities, a baseline, next steps and one starter asset: a supported SOP, control checklist, requirements specification or automation blueprint. A blueprint describes the proposed change; implementation has its own scope.

Explore the method

ONE WORKFLOW · FROM EVIDENCE TO A PLAN

One load. Five connected handoffs.

Mesa Freight Coordination is fictional. Follow 48 regional loads through appointment changes, carrier acknowledgement, POD and accessorial review before the freight bill is ready. Open a source or a row to inspect the evidence.

Mesa Freight Coordination / Freight-bill evidence

FICTIONAL EXAMPLE · MES-011

Bill this load?

Detention approval missing
THE WORKTODAYPROPOSED
Owner: Freight billing lead

Tap or click a source to explore.Fictional business · Proposed changes

FOLLOW THE SOURCE EVIDENCE

Follow the changed instruction to the carrier.

01 / 03

Hear the appointment change reach dispatch.

Follow the receiver’s update to the carrier desk. The load is only ready for the new plan when the revised instruction is acknowledged.

Mesa Freight Coordination / Workflow capture
ProcessScout Recorder Capture with permission
WORKFLOWLoad-to-freight-bill handoffWatch a changed appointment reach the carrier.
00:12Tender a load with separate appointment notesStep captured
00:29Change the appointment by phoneException
00:46Dispatch against an earlier instructionStep captured

Synthetic recording sequence · No live capture on this page

02 / 03

Follow tender through freight-bill readiness.

Trace appointment, dispatch, proof of delivery and accessorial evidence under one load reference.

Mesa Freight Coordination / Workflow map
01Tender a load with separate appointment notes↓Confirm carrier, load and appointment together
02Change the appointment by phone↓Own and acknowledge the load revision
03Dispatch against an earlier instruction↓Confirm the current instruction with the carrier
04Chase proof of delivery after arrival↓Attach legible POD to the load
05Resolve accessorials while building the bill↓Review authority and evidence before billing
03 / 03

Name the owner of the change.

Separate the carrier instruction, delivery-document chase and freight-bill decision so a changed load has a clear next action.

Mesa Freight Coordination / People & decisions
ACCOUNTABLEFreight operations manager
Carrier operations leadConfirms appointment and load revisions
Documentation leadObtains and links proof of delivery
Freight billing leadChecks accessorial authority and billing readiness

Proposed responsibilities for Mesa Freight Coordination. Confirm authority and backup coverage before use.

Confirm scope and permission before capturing work. Avoid credentials, payment-card details and unnecessary personal data. Read the capture guide ↗

Cover of the fictional Mesa Freight Coordination Trail MapEVIDENCE
TO DECISION
Open the report

SEE A FINISHED DELIVERABLE

A logistics report built around the load.

Mesa’s fictional sample has thirteen appointment changes, seven missing PODs and five accessorial requests without linked approval. The proposed 90-day plan gives each gap an owner and a measurement gate.

Report + evidence3 opportunities90-day plan

A fictional sample built from authored evidence. It shows the format, not a customer result.

BEFORE YOU DECIDE

Carriers and shippers control part of the handoff.

Map the evidence your desk can request, confirm and retain, and identify the external response it depends on. The assessment can clarify your exception queue and contract-specific checks while live dispatch and carrier decisions stay with their authorized owners.

THE EDGE ASSESSMENT

One workflow. Fixed scope.

$1,500USD / fixed assessment

Edge is $1,500 USD for one logistics workflow in one legal entity and operating unit. Confirm the load type, desk, records and participants before starting. Live dispatch, route optimization, transport compliance assurance and system changes are outside this assessment.

Three evidence-backed opportunities, or your fee back.

If ProcessScout cannot identify at least three evidence-backed opportunities from a good-faith intake, the assessment fee is refunded under the assessment terms. This is a deliverable guarantee, not a promise of realized savings.

Read the guarantee and refund terms ↗
Book an intro call

Five business days after your evidence checklist is complete.

Assessment scope, evidence and terms

A clear boundary

One legal entity, one business unit and one workflow. Up to three recordings, a leadership interview and an executive readout.

A reviewed decision pack

Current-state map, three priorities, baseline, 90-day plan and one starter asset: an SOP, control checklist, requirements brief or automation blueprint.

A useful follow-through

Check-ins at 30 and 90 days. Implementation and ongoing software subscriptions are separate purchases.

MAKE THE ASSUMPTIONS VISIBLE

What is repeated dispatch coordination costing?

Start with what the work costs now. Any reduction is your assumption.

ANNUAL COST OF THIS WORK TODAYAt default inputs$43,680

20 team hours / week on this work

Add an assumed time reduction to see what it would be worth. It stays an assumption, not a result.

Illustrative planning model using your inputs, not measured customer performance. Hours are per person per week. Any time reduction is your assumption and starts at zero; its value is capacity at the entered rate, not a cash saving. Excludes implementation, adoption and ongoing costs.

See the calculation

Annual work cost = hours per person per week × people × loaded hourly cost × 52 weeks. Assumed capacity value = annual work cost × your assumed time reduction. This is not a promise of returns; the assessment fee and any implementation costs are not deducted.

Bring the load change that keeps your team chasing. Book 15 minutes.

Book an intro call

Mesa Freight Coordination · FICTIONAL EXAMPLE

Follow the load after the appointment changes.

The authored loads belong to one coordination desk. Exception categories overlap; business-clock duration includes waiting and does not estimate detention cost, labor or cash collection.

Cohort
48 completed regional full-truckload movements
Delivery-to-bill-ready duration
504 business hours across 48 loads; mean 10.5 hours
Changed appointments
13 of 48 loads after tender acceptance
Missing POD at first review
7 of 48 loads
Unapproved accessorials
5 of 9 requests lack linked shipper approval

What this changes in the model

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.

Mesa Freight Coordination · FICTIONAL EXAMPLE

Check what makes the freight bill ready.

Fictional record MES-011 · E02 / Authored proof-of-delivery and accessorial workbook

Additional charge
detention
Supporting evidence
arrival and departure times
Shipper approval linked
No
POD at first review
missing

Selected from the sample’s authored record register. Download the source records.

The workbook separates a carrier’s request from an approved charge. Actual contracts and delegated authority determine the required evidence; no universal detention rule is asserted.

Load
MES-011 · appointment revision 2
POD at first review
Missing; request legible proof linked to this load
Accessorial question
Detention request has times but no linked shipper approval
Billing review
Confirm charge basis, authority and supporting evidence

What this changes in the model

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.

Mesa Freight Coordination · FICTIONAL EXAMPLE

Watch a changed appointment reach the carrier.

The fictional walkthrough covers one appointment change and its downstream proof requirements. A paid assessment uses the desk’s actual load boundaries, contracts and authorized records.

Start
Receiver moves the delivery appointment after tender acceptance
Handoff
Coordinator updates notes and phones the carrier desk
Gap
Dispatch instruction still carries the earlier appointment
Proposed check
Named owner records carrier acknowledgement of revision 2

What this changes in the model

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.

Mesa Freight Coordination · FICTIONAL EXAMPLE

Process

Thirteen loads have changed appointments after tender acceptance. The proposed handoff identifies a revision owner and carrier acknowledgement before the changed instruction is treated as current.

AS-IS

Tender → change → dispatch → chase

E01 · load event register

PROPOSED TO-BE

Confirm → acknowledge → deliver → review

Validate with the workflow owner before changing the live process.

Follow the evidence

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.

Mesa Freight Coordination · FICTIONAL EXAMPLE

Business rules

Five of nine accessorial requests lack linked shipper approval. Record the charge basis, required authority and supporting times or documents before deciding that a request can be billed.

AS-IS

Accessorial approval sits outside the load

E02 · accessorial review workbook

PROPOSED TO-BE

Charge reason + authority + evidence

Validate with the workflow owner before changing the live process.

Follow the evidence

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.

Mesa Freight Coordination · FICTIONAL EXAMPLE

Systems

The authored desk updates the appointment in one place and calls the carrier separately. A shared load reference and acknowledgement can make the handoff visible without promising a TMS integration.

AS-IS

Load board, calls, carrier email

E03 · appointment-change walkthrough

PROPOSED TO-BE

One load-linked instruction history

Validate with the workflow owner before changing the live process.

Follow the evidence

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.

Mesa Freight Coordination · FICTIONAL EXAMPLE

Data flows

Seven completed loads lack proof of delivery at first freight-bill review. Link a legible POD to the correct load and retain the appointment history needed to interpret an accessorial request.

AS-IS

POD and appointment versions are separate

E01 · load and POD links

PROPOSED TO-BE

Load ID + revision + delivery evidence

Validate with the workflow owner before changing the live process.

Follow the evidence

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.

Mesa Freight Coordination · FICTIONAL EXAMPLE

Organization

Name who confirms the revised appointment with the carrier, who obtains POD and who reviews the charge. A shared dispatch inbox cannot acknowledge an instruction on a carrier’s behalf.

AS-IS

Changed loads bounce between desks

E03 · carrier handoff

PROPOSED TO-BE

Carrier resolver and billing reviewer

Validate with the workflow owner before changing the live process.

Follow the evidence

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.

Mesa Freight Coordination · FICTIONAL EXAMPLE

Standards

Delivery status, proof of delivery and authority for additional charges are separate evidence. The proposed checklist makes all three inspectable before freight-bill preparation.

AS-IS

Delivered status is treated as bill-ready

E02 · freight bill checklist

PROPOSED TO-BE

POD and accessorial readiness check

Validate with the workflow owner before changing the live process.

Follow the evidence

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.

Mesa Freight Coordination · FICTIONAL EXAMPLE

From evidence to a practical decision.

01

Give each changed load a confirmed revision.

Name a revision owner and record the carrier’s acknowledgement of the current appointment and instruction.

Owner: Carrier operations lead · Measure: Changed loads without acknowledgement and time spent reconfirming the current instruction.
02

Link proof of delivery before billing review.

Pilot a delivery-evidence queue with a documentation owner, legibility check and load reference.

Owner: Documentation lead · Measure: Loads without usable POD at first review and delivery-to-freight-bill-ready time.
03

Keep accessorial requests separate from approved charges.

Record the charge basis, evidence and shipper authority, then route unresolved requests to the freight billing lead.

Owner: Freight billing lead · Measure: Requests missing authority, returned billing packs and disputed charge evidence.
Read the full sample

Illustrative records. Proposed changes require validation, an accountable owner and approval before implementation.