Learning objectives
After this lesson, you should be able to
- Define a finite load lifecycle
- Attach evidence and permissions to each transition
- Make exceptions visible without forcing progress
States need entry and exit rules
Lead, qualified, contacted, negotiating, offered, booked, dispatched, in transit, delivered, invoiced, and paid should each have a clear owner and evidence threshold.
- Use immutable event history
- Require carrier authority before consequential actions
- Keep documents with the related transition
- Route exceptions instead of skipping states
Measure stalled work
A dashboard should show what is waiting, why, who owns it, and the next safe action—not just counts of completed loads.
Apply the decision protocol
Use a fictionalized or fully permissioned operating scenario. Build five columns: observed facts, supplied facts, assumptions, controlling sources, and unresolved questions. Do not advance a consequential action while a required fact, authorization, qualification, or safety condition remains unresolved.
- Demonstrate: Define a finite load lifecycle
- Demonstrate: Attach evidence and permissions to each transition
- Demonstrate: Make exceptions visible without forcing progress
- Name the decision owner, evidence standard, stop condition, and next review time
Practice with evidence
Create a one-page decision record and ask a peer to challenge the source, version, applicability, missing facts, incentives, and proposed communication. Revise the record rather than defending the first answer. Preserve the initial and corrected versions so an editor can see what the exercise actually taught.
- Cite every externally verifiable claim
- Separate uncertainty from error
- Escalate beyond the lesson's stated competence boundary
- Remove private, proprietary, or personally identifiable information
Correct and transfer the learning
After the scenario, compare the decision to the current source and the stated objective. Record the misconception, the evidence that corrected it, the operational control that would prevent recurrence, and the conditions that would require the answer to be researched again.
Knowledge check
What should happen when evidence required for a state transition is missing?
Reveal the answer
Keep the load in its current state and create an owned exception.
Changing the label does not resolve the underlying requirement.