Chapter 4 — Quality management for shipment data
Lesson map
Lesson 04 published. Map, example, EX016.
flowchart TD
N0["Learning outcomes"]
N1["4.1 Expectations"]
N2["4.2 The quality cycle"]
N3["4.3 Cost of poor quality"]
N4["4.4 Fixing proof of delivery"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX016"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["4.1 Expectations"]
N2["4.2 The quality cycle"]
N3["4.3 Cost of poor quality"]
N4["4.4 Fixing proof of delivery"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX016"]
[Learning outcomes]
|
v
[4.1 Expectations]
|
v
[4.2 The quality cycle]
|
v
[4.3 Cost of poor quality]
|
v
[4.4 Fixing proof of delivery]
|
v
[Worked example] --> [Exercise EX016]
Learning outcomes
You will (1) define quality expectations for shipment data; (2) build a quality management cycle; (3) prioritise issues by cost.
4.1 Expectations
Lucía works with the operations steward to define quality expectations for shipment data. Each shipment must have a valid customer, origin, destination, promised delivery window and status. Tracking must show collection, depot arrival, departure and delivery events. Proof of delivery must include time and signature or photograph. She bases the dimensions on Wang and Strong and the measurement approach on ISO 8000-8, recording for each expectation how it will be measured and what threshold applies. The steward reviews each threshold with depot supervisors before adoption.
4.2 The quality cycle
She sets up a cycle: define rules, measure results daily, analyse failures weekly, improve causes and review rules quarterly. This mirrors improvement cycles used in operations, which helps operations staff accept it. Results feed a dashboard for the steward and a weekly summary for the owner. Lucía notes that the cycle's value lies in the improve step; measuring without fixing causes merely documents decline in more detail. Lucía writes the cycle as a one-page procedure, and the steward follows it from the first week, holding a short meeting each Friday to analyse failures.
4.3 Cost of poor quality
To prioritise, Lucía estimates the cost of quality failures. Missing proof of delivery leads to disputed invoices that finance writes off. Wrong destination codes lead to misrouted shipments and re-delivery costs. Late tracking events lead to customer service calls. Using synthetic figures based on typical volumes, she shows that missing proof of delivery costs most. The governance group agrees to tackle it first, since its effect on revenue is direct and measurable. Lucía shows the estimated annual cost of each failure type in a simple chart for the group.
4.4 Fixing proof of delivery
Lucía investigates missing proofs. Most come from one carrier whose drivers use paper notes scanned days later, and some from Corran drivers whose handheld devices lose signal in rural areas. The carrier agrees to adopt Corran's mobile app. Corran devices are updated to store proofs offline and send them when signal returns. After two months, missing proofs fall markedly, and disputed invoices decline. Dr. Achebe notes that costing quality failures made prioritisation straightforward. Lucía records the before and after figures in the quality log.
Worked example
Lucía defines shipment and tracking expectations with measurements, sets a define-measure-analyse-improve-review cycle, ranks missing proof of delivery as costliest and fixes carrier paper notes and offline device storage.
Synthetic case. Figures are synthetic; Wang and Strong (1996) and ISO 8000-8:2015 are real.
Errors and limits
Measuring quality without fixing causes only documents decline.
Exercises
- EX016 — Proof contents. What must proof of delivery include? Rubric: 3 = time and signature or photograph;; 2 = partly correct;; 1 = partial;; 0 = none.
- EX017 — Costliest failure. Which failure cost most? Rubric: 3 = missing proof of delivery;; 2 = partly correct;; 1 = other;; 0 = none.
- EX018 — Carrier cause. Why were a carrier's proofs missing? Rubric: 3 = paper notes scanned days later;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX019 — Device fix. How were Corran devices fixed? Rubric: 3 = store proofs offline and send later;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX020 — Cycle value. Where does the quality cycle's value lie? Rubric: 3 = the improve step;; 2 = partly correct;; 1 = measure;; 0 = none.
Continue studying — lesson 04 (chapter 04 of 12)
← Chapter 03 · Course chapter index · Chapter 05 →
Continue to the next authored lesson.