Action Map — Cold-Chain Check | I Wayan Usada

Probe the core before signing — never accept on paperwork alone

Critical because: 43% of last quarter's problem pallets were temperature abuse discovered after acceptance — the signature happened before the probe.

SME: named failure #1Frequency: every palletObservable: yes (probe logged)

Practiced in moduleGate 2 scenario: choose probe points on the pallet diagram; surface reading 7.9 °C vs core 9.4 °C — feel the consequence of trusting the surface.

Practiced in explainer90-second scene 4–5: "The surface lies" — needle animation from surface to core with the 8 °C threshold line.

Job aidChill-dock card: core-probe point diagram + 2–8 °C decision strip, printed at every receiving station.

Built-in mistake (distractor source): "Logger says 3.5 °C, paperwork is complete — sign and move on." Module consequence: written-off pallet discovered two days later at the customer DC.

Decide borderline readings by protocol, not by mood

Critical because: 31% of rejections were unnecessary — over-cautious receivers guessing on readings like 8.5 °C surface instead of probing or escalating.

SME: named failure #2Frequency: every borderline loadObservable: yes (rejection note field)

Practiced in moduleBorderline incidents A–C: core 8.4 °C → reject protocol; missing logger + driver claims → hold-and-escalate; each choice plays its consequence before feedback.

Certification7-of-8 randomized scenario bank, pass ≥85% (6/7 = 85.7%) — every item is a borderline call, none is recall trivia.

Job aidDecision table: in-range / out-of-range / no-data × accept / reject / hold-escalate, laminated at the goods-in desk.

Built-in mistake (distractor source): rejecting a good load "to be safe" — module shows the ripple: dock backlog, driver detention, cost write-off with zero risk reduction.

Protect the clock: return loads to the chill while escalating

Critical because: 26% of failures were dock delays — loads left on the ambient dock past 30 minutes while someone "checked with the supervisor."

SME: named failure #3Frequency: shift peaksObservable: yes (chill-door movements)

Practiced in moduleGate 3 interaction: incident C puts you at minute 28 of a congested peak dock — the return-to-chill action is one click, the naive wait plays the temperature creep.

Practiced in explainerScene 6: clock overlay counting to the 30-minute line while the pallet slides back to the chill door.

Covered by structure, not teachingThe escalation path itself lives in the pathway map (who to call, in what order) — receivers practice the *behavior*; the org chart is a reference, not a lesson.

Built-in mistake (distractor source): "Park it in the sun, I'll be right back after the call" — module consequence: core crosses 8 °C while the learner watches the timer.

Document every decision — including the rejections

Critical because: paper protects the next shift and makes the 90-day numbers measurable; undocumented borderline calls were invisible in the baseline data.

SME: supporting habitFrequency: every decisionObservable: yes (record fields)

Practiced in moduleGate 4 fill-the-record interaction: select the correct fields into a rejection note; wrong field sets are shown before feedback.

Job aidRejection-note field checklist on the reverse of the decision table.

Deliberately thin in teachingReceivers already fill records daily — the module adds only the two commonly-skipped fields. Over-teaching this would spend credibility earned elsewhere.

What was cut — and why that is the point

Action mapping is subtraction. These candidates failed the Friday-dock test and were removed from the module:

Cut: refrigeration-cycle theoryCut: HACCP regulation historyCut: full company SOP walkthroughCut: product-category catalogue

Where it went instead: the HACCP anchor points survive as one-line references inside the decision-table job aid; theory depth was referred to the existing annual refresher. The module's ~10 minutes are spent entirely on the four behaviors above.

This is what the SME and I agreed the request did not mean: Operations asked for "a short training about receiving chilled goods" — the map turned a content request into three practiced behaviors plus one supporting habit.