Operation reconciliation

A delayed response can leave Dispatcher uncertain whether an action finished. The operation receipt retains a stable operation key, action, expected revision and result state. External and effect references help Transport Supervisor connect that attempt to the work it was intended to perform.

Reconciliation begins with those records. The supervisor examines the linked effects and records the discrepancy when an outcome remains unresolved. A failed receipt moves to Needs review for further investigation. Reading and comparing evidence should establish the outcome before the team considers a separately authorized correction.

• Keep the attempt identifiable. Dispatcher uses the same operation identity when following up a request. The expected revision connects the action to the load state that was checked. A failure reason helps the next person understand the obstacle without treating a changed screen as proof of success.
• Review the actual effects. Transport Supervisor compares local linked evidence with the authoritative source. Pending, Completed, Failed and Needs review distinguish the recorded outcomes. Unresolved effects remain visible for investigation, with enough reference information to continue the inquiry.
• Preserve correction evidence. An excepted load needs a reviewer decision before correction or cancellation. The compensating receipt stays alongside the original evidence. The supervisor limits cancellation to unexecuted scope and coordinates any externally controlled effect with its responsible source.

Agree how operation keys are formed and how the team searches for an existing attempt. Identify the authoritative source for each action, including the duty interval provider when an import is involved. Decide what evidence Transport Supervisor needs before concluding that local records match the external result.

Set the handoff for unresolved cases and name the person covering the supervisor’s queue. Agree how a correction reason describes the affected load and the allowed scope. Auditor should be able to follow the original attempt and the later decision without relying on a private message thread.

Rehearse a duty import whose response is lost after processing begins. Dispatcher searches for the existing operation key. Transport Supervisor compares the saved receipt and linked effects with the source outcome. If the expected effect cannot yet be confirmed, retain the discrepancy and leave the case visible for review.

Repeat with an excepted load that has not been dispatched. The independent supervisor records a cancellation decision for the unexecuted scope and the team retains a compensating receipt. Compare that case with a load that already has a physical pickup: the earlier movement evidence must remain, and any external reversal needs the responsible source’s process.

Finish by asking Auditor to explain the sequence from the records alone. The explanation should identify the original attempt, the review reason and the eventual verified outcome. If those links are unclear, fix the handoff before increasing operating volume.

• Operation Receipts Default List — Action attempts with outcome, revision and failure details.
• Review Decisions Default List — Reviewer decisions and reasons attached to the load revision.

Use Exception reconciliation, or return to Duty interval import when the disputed action concerns driver activity.