FahCel
Field Playbook · Rev 2026.1

The Cold-Chain Excursion Playbook

Six moves to defend a shipment the moment temperature breaks — and the paper trail that proves you did.

For
QA, logistics & ops leads
Read time
11 minutes
Pages
Cover + 4
Updated
fahcel.eu / playbookProof of cold, end to end
Part one · When the alarm fires

An excursion isn't a loss until you decide it is.

Most spoiled-product write-offs aren't caused by the temperature spike — they're caused by the hours of silence after it. These six moves turn a panic into a documented decision you can defend to a regulator, an auditor, or a customer.

80%
of excursion write-offs are avoidable with a same-shift decision
6hr
median delay between a breach and the first logged response
1×
the number of unbroken records an auditor actually wants
1

Freeze the record, not the panic

The instant an alarm fires, timestamp it against the sealed log. Don't move the pallet, don't open the door — capture the reading exactly as it stands.

Owner: on-site handler · < 5 min
2

Pull the full temperature history

Not just the peak. Duration and area-under-curve decide product stability far more than a single spike — export the whole interval from first load to now.

Owner: QA · pull sealed series
3

Run it against the stability budget

Compare cumulative time-out-of-range to the product's mean kinetic temperature allowance — the label limit, not a gut call. This is the yes/no gate.

Owner: QA · MKT / label spec
4

Make the release decision on the record

Release, quarantine, or reject — and write the reasoning beside the data that drove it. A decision without its evidence is a liability, not a defense.

Owner: QA lead · signed
5

Notify the chain in one message

Consignee, carrier, and receiving QA get the same disposition and the same attached record — no forwarded screenshots, no version drift.

Owner: logistics · < 1 hr
6

Close the loop with a root cause

Tie the breach to a cause — dwell at dock, failed reefer, door left open — and file it so the next shipment inherits the fix, not the failure.

Owner: ops · CAPA logged
FahCel · Excursion Playbook02 · The six-move protocol
Part two · Before the truck leaves

The pre-departure checklist that prevents most excursions.

Tape this to the dock door. Every box checked here is an excursion that never happens — and a line item an auditor never has to chase.

ALoad & seal

  • Pre-cool confirmed — trailer at setpoint before the first pallet, not after.
  • Logger placed & started — probe in the load, not the return air.
  • Setpoint vs. label match — verified against the product spec, initialed.
  • Seal + logger ID paired — recorded on the manifest before doors close.

BTransit & handoff

  • Alarm thresholds live — someone is on the receiving end of the alert.
  • Dwell limits set — max minutes on an open dock before escalation.
  • Receiver briefed — knows the disposition rule before arrival.
  • Record handoff planned — one file follows the goods, custody intact.
Rules of thumb · read before you argue with the data
REJECT-BIASA single peak tells you little. Duration and cumulative exposure decide stability — always pull the full curve before disposition.
CAUTIONThe gap is the risk. A 20-minute logging gap during a breach is treated as worst-case, not as “probably fine.”
CAUTIONReturn air ≠ product. Sensor placement changes the reading by degrees — trust the probe in the load.
DEFENSIBLEDecide on the shift. A documented same-day disposition beats a perfect analysis that lands three days late.
FahCel · Excursion Playbook03 · Checklist & thresholds
Part three · Questions that decide the disposition

The six answers an auditor will hold you to.

These come up in every excursion review. Settle them before the alarm, not after — the answers are what turn a judgement call into a defensible record.

What is a temperature excursion?

A temperature excursion is any period in which a temperature-sensitive product sits outside its labelled storage range during storage, transit or last-mile delivery. An excursion is not automatically a loss — it becomes one only when the disposition decision is made without the record needed to defend it.

What is the first thing to do when a temperature alarm fires?

Freeze the record, not the panic. Timestamp the alarm against the sealed log and capture the reading exactly as it stands — do not move the pallet or open the door. Disturbing the load before the reading is captured destroys the evidence the disposition decision rests on.

Does a single temperature spike mean the product is rejected?

No. A single peak tells you little on its own. Duration and cumulative exposure decide stability, so pull the full curve from first load to now and compare cumulative time-out-of-range to the product’s mean kinetic temperature allowance. Disposition follows the label limit, not the peak value.

How should a gap in the temperature log be treated?

As worst-case. A logging gap during a breach — say twenty minutes of missing readings — is treated as if the product was out of range for the entire gap, not as probably fine. The gap is the risk, and an auditor will read it the same way.

Where should the temperature logger be placed?

In the load, not in the return air. Return air is not product temperature, and sensor placement can change the reading by degrees. Place the probe with the goods, start it before the first pallet is loaded, and pair the logger ID with the seal on the manifest before the doors close.

How quickly should an excursion be dispositioned?

On the shift. A documented same-day disposition beats a perfect analysis that lands three days later, because the decision has to be defensible as well as correct. Record the release, quarantine or reject alongside the temperature curve that drove it and have the QA lead sign it.

FahCel · Excursion Playbook04 · Common questions
Where FahCel fits

Stop rebuilding the record after the breach.

This playbook is the manual version. FahCel runs the same six moves automatically — a sealed, unbroken temperature record from load to handoff, so the decision and its evidence are always in one place.

Move 1–3
Sealed hash-chained log — every reading timestamped and tamper-evident from first load.
Move 4
Disposition on the data — release / quarantine / reject signed against the curve that drove it.
Move 5
One-message handoff — the same record follows the goods, custody intact.
Move 6
Root cause on file — every excursion feeds the next shipment's fix.
See it on your lanes — a 20-minute walkthrough with your own shipment data.
Book a demo → fahcel.eu/demo