A rejected refrigerated load is expensive. A load that should have been held but gets released can be far worse.
The operational failure usually starts before the truck arrives. Product requirements live in a quality manual. Temperature instructions sit in an email. The carrier accepts a tender without seeing the sanitation rules. At delivery, a receiver finds a temperature or trailer-condition problem, but nobody knows who can release the freight.
That is exactly the gap an FSMA sanitary transportation workflow should close. The rule is not a generic “keep food cold” checklist. The FDA says it applies to shippers, receivers, loaders and motor or rail carriers involved in transporting human and animal food, with requirements covering vehicles and equipment, transportation operations, training and records. It is designed to prevent practices such as inadequate refrigeration, poor cleaning and inadequate protection of food during transportation. The FDA’s sanitary transportation rule summary explains the scope, requirements and exemptions.
1. Assign food-safety responsibility before pickup
The first control is not a sensor. It is a responsibility map.
For each lane and product profile, name the party responsible for the sanitary specification, trailer inspection, pre-cooling, temperature monitoring, prior-cargo disclosure, cleaning evidence, seal control, delivery assessment and exception disposition. Do not leave those duties buried in a carrier agreement that dispatch never sees.
The regulation permits parties to reassign certain duties through a written agreement. It also requires covered operations to be overseen by competent supervisory personnel. The operating requirements in 21 CFR 1.908 spell out how shipper, loader, carrier and receiver responsibilities connect. That makes the written agreement an operating control, not legal wallpaper.
Build the responsibility map into your managed transportation program. Then connect it to a carrier-selection control that screens equipment capability, sanitation procedures, training and record access before the first tender.
2. Turn the product profile into written freight specifications
A carrier cannot execute requirements it never receives. For every covered product profile, translate food-safety requirements into a short transportation specification that operations can actually use.
- Required trailer type and condition
- Cleaning method, acceptable prior cargo and evidence required
- Pre-cool target and the point at which it must be verified
- Operating-temperature range and monitoring method
- Loading pattern, segregation and allergen cross-contact controls
- Seal process and authorized seal exceptions
- Delivery checks, rejection triggers and hold-release authority
Give the specification a controlled ID and revision date. Attach that ID to the order, load tender and bill of lading. A practical supplier routing guide can carry the same requirements upstream so vendors do not improvise at the dock.
Use a full truckload transportation service that can confirm the operating specification before dispatch. A tender acceptance that only confirms rate and appointment is incomplete. For covered food, the carrier should also acknowledge the current sanitary and temperature requirements tied to that load.
3. Verify equipment, cleaning and pre-cooling before release
The loader is the last practical gate before product enters the trailer. Treat that gate seriously.
The load should not be released until the trailer is suitable, clean and—when required—pre-cooled. Capture the trailer number, refrigeration-unit identity, inspection time, interior condition, odor or residue result, cleaning evidence, pre-cool reading and seal number. If prior cargo matters, verify it before loading, not after a claim.
A checkbox that says “trailer clean” is weak evidence. Use time-stamped photos and structured fields. Require the person performing the check to record the actual reading and the instrument used. Lock the tender specification to the inspection so an old form cannot be reused for the wrong product.
Do not automate judgment out of this gate. A system can block dispatch when a required field is missing or a reading is outside the approved range. A trained human still decides whether equipment condition, residue, odor or a sanitation document is acceptable.
4. Automate condition evidence; keep humans on hold and release
Manual handoffs fail because the evidence is scattered. The TMS has the tender. Quality has the product profile. The carrier portal has the trailer inspection. Telematics has the temperature trace. The receiver has the delivery exception. When those records cannot be joined by load ID, the organization has data but no defensible workflow.
Automate the boring joins:
- Push the approved product specification into the tender through the TMS, API or EDI connection.
- Require structured equipment, cleaning, pre-cool and seal evidence before dispatch release.
- Ingest temperature or condition data against the same shipment identifier.
- Create an exception when a required record is missing, a seal changes or a reading exceeds the configured limit.
- Route the exception to the designated qualified person and preserve the decision with supporting evidence.
The regulation is blunt on the final point: when a possible material temperature-control failure or other condition could make the food unsafe, it must not be sold or distributed until a qualified individual determines it remains safe. The dashboard may raise the flag. It should not invent the disposition.
Illustrative example — run your own numbers. A shipper moves 100 temperature-controlled loads per month. If one load each quarter enters a preventable hold, and product, freight and recovery exposure totals $20,000 per event, the annual exposure is $80,000. That is not an industry benchmark or a savings promise. It is a simple way to compare workflow cost with the risk of missing evidence and delayed decisions.
5. Train carrier personnel and retain usable records
Training is not satisfied by emailing a policy. When a written agreement makes the carrier responsible for sanitary conditions, carrier personnel must receive adequate training when hired and as needed thereafter. The training provision in 21 CFR 1.910 requires records showing the date, type of training and people trained.
Connect each required task to a role and training record. A dispatcher confirming a temperature requirement, a driver checking a trailer and a receiver evaluating an exception do not need the same instruction. They do need to know the control they own, the evidence they must capture and the person to call when reality does not match the plan.
Records must also be retrievable, not merely retained. The record provisions in 21 CFR 1.912 specify retention periods and prompt availability; electronic records accessible from the facility are treated as onsite, while offsite records generally must be produced within 24 hours. Build your archive so a load file can be reconstructed by shipment, carrier, product specification and exception—not by searching five inboxes.
6. Audit the workflow, not just the temperature trace
A continuous temperature graph can look beautiful while the process around it is broken. Audit the complete control chain: current written specification, carrier acknowledgment, correct equipment, sanitation evidence, pre-cool verification, seal continuity, temperature or condition record, receiver assessment, exception disposition and retention.
Add a small set of sanitary-transport measures to the carrier performance scorecard: first-pass evidence completeness, pre-pickup exception rate, unauthorized seal changes, temperature-data availability, response time to holds and corrective-action closure. Score the behavior that prevents risk, not just on-time delivery.
Here is the damaging admission: this approach is not equally useful for every shipment. The FDA lists exemptions, including certain fully enclosed food that does not require temperature control for safety. Small or simple operations may not need a new platform. And neither a broker nor software should make the food-safety release decision for the shipper’s qualified person. Confirm applicability with food-safety and legal specialists; do not turn an operations article into a compliance opinion.
Map the control chain before the next exception
Bring your product transport profiles, carrier agreements, sanitation and temperature requirements, plus the last 90 days of exceptions. Easy Logistics can map the tender-to-release workflow, show where evidence breaks, and price the transportation or automation support needed to close those gaps.