Reefer FSMA Sanitary Transportation SOP: Pre-Cooling, Continuous Temperature Monitoring, and 12 Month Records

What the Rule Covers and Who It Reaches

The Sanitary Transportation of Human and Animal Food rule was issued under the Food Safety Modernization Act and is codified at 21 CFR Part 1 Subpart O, sections 1.900 through 1.934. It applies to shippers, loaders, carriers, and receivers engaged in transporting human and animal food by motor or rail vehicle in the United States, with defined exceptions. One exception matters to many fleets: the rule's definition of a non covered business includes a motor carrier with less than 27.5 million dollars in annual receipts. Food completely enclosed by a container that does not require temperature control for safety is also outside most of the requirements. A carrier below the revenue threshold may still be asked by shippers to follow the same practices by contract, so the SOP below is worth adopting either way.

The rule's core idea is simple. Food should not become unsafe during transportation because of a dirty vehicle, cross contact with a prior load, or a failure of temperature control. It does not prescribe one temperature for each product. Instead, it assigns responsibilities. The shipper decides what the food needs. The loader checks the vehicle before loading. The carrier follows the instructions and keeps the evidence. The receiver assesses whether the food arrived without significant temperature abuse. Responsibilities can be reassigned among the parties by written agreement, which is why the contract language for each customer matters.

Responsibilities Under 21 CFR 1.908

Section 1.906 requires that vehicles and transportation equipment be designed and maintained so they can be adequately cleaned and do not cause food to become unsafe, and that equipment used for temperature controlled food be able to maintain the needed temperature. Section 1.908 then divides transportation operations among the parties.

Under 1.908(e), the carrier also has duties beyond temperature. If requested, it must give the shipper information about previous cargo and the most recent cleaning for bulk vehicles, and it must develop and implement written procedures that cover cleaning, sanitizing, and inspecting vehicles, how it will comply with temperature control requirements, and how it will comply with bulk vehicle requirements where those apply. The temperature procedure is the subject of this guide.

The Pre-Cool SOP

Pre-cooling brings an empty trailer to the shipper's specified temperature before loading so the box itself does not warm the product at the start of the trip. A transport refrigeration unit is built to hold product temperature, not to pull down warm product, so pre-cooling is about the trailer, not the freight. A practical carrier SOP has six steps.

• 1. Confirm the instruction - Before dispatch, the load must carry the shipper's written operating temperature, any pre-cool requirement, and the required unit mode, continuous run or start stop. Dispatch cannot release a reefer load with a blank set point.
• 2. Inspect and clean - The driver performs the reefer pre-trip, checks the trailer for odor, residue, and debris, confirms drains and seals, and records the inspection against the trailer and load.
• 3. Set and verify - Set the unit to the specified set point and mode, with doors closed, and confirm the reading through telematics, not just the unit display.
• 4. Pre-cool to target - Run until return air reaches the set point or the shipper's specified pre-cool temperature, then record the time and reading. The TMS should capture the pre-cool start, the time target was reached, and the reading at arrival.
• 5. Load with doors managed - Back to a sealed dock door where available, keep the unit settings as the shipper or facility instructs during loading, and minimize door open time.
• 6. Record product condition - If the loader or driver notes product that appears out of temperature, record it on the bill of lading and in the TMS before departing, and contact dispatch.

Dispatch planning should allow time for pre-cool. A trailer that sat in summer sun needs longer than one parked in a cool yard. The insight on predictive pre-cooling in dispatch covers how to schedule that window from telematics data rather than guessing.

Continuous Reefer Telematics Logging

The rule lets the parties agree on how temperature maintenance will be demonstrated. A hand written log at pickup and delivery shows two moments. Continuous telematics shows the whole trip. Most modern reefer units and aftermarket telematics devices can report set point, return air, discharge air, unit mode, alarm codes, fuel level, and door open status at regular intervals. The carrier SOP should define which fields are required, the reporting interval, and what happens when the device is offline.

Return air is generally the best single indicator of trailer conditions during transit, while discharge air shows what the unit is supplying. A large and persistent gap between the two can indicate airflow restriction from poor load pattern, a blocked chute, or an evaporator icing problem. Set point changes during the trip should be rare and explained. Each one should generate an event in the TMS with the user or source that made the change.

The data only becomes evidence when it is tied to the load. That means the TMS must know which trailer was on which load, when the load started and ended, and which stops occurred in between. When trailer assignment changes at a relay or drop yard, the record must follow. Our ELD and EDI integration work maps telematics feeds to load, trailer, and stop records with a source stamp on every reading, so the delivery report shows exactly what the unit reported, not a reconstructed summary.

Example: a reefer load is specified at 34 degrees Fahrenheit, continuous mode, with pre-cool required. The telematics trace shows the trailer reached 34 return air 50 minutes after pre-cool started, the doors opened for 38 minutes at the shipper dock, return air rose to 39 during loading and recovered to 34 within 25 minutes of door close, then held within a small band for the rest of the trip. The values are illustrative, but a trace like this, attached to the load, is the kind of demonstration a shipper or receiver can evaluate quickly.

Door Open Events and Excursion Rules

Door open events explain most short temperature rises. A door sensor that reports open and close times lets the TMS separate an expected rise during loading and unloading from an unexplained rise in transit. The SOP should define what counts as an excursion for each temperature profile, agreed with the shipper where possible: a deviation size from set point, a minimum duration, and whether events during an open door at a scheduled stop are excluded. A door opening between stops, away from a known facility, should always generate an alert, both for temperature and for cargo security.

• Expected rise - Door open at a scheduled stop geofence, recovery within the agreed time.
• Transit excursion - Return air outside the agreed band for longer than the agreed duration with doors closed.
• Equipment alarm - Unit fault code, unit shutdown, or loss of power.
• Data gap - No readings for longer than the defined interval.
• Unscheduled door open - Door open outside any stop geofence.

The Exception Workflow in the TMS

Alerts that only reach a phone in a dispatcher's pocket do not create records. Each excursion type should open an exception on the load in the TMS with an owner, a timestamp, and a required resolution. The driver receives a message to check the unit and, when safe, confirm the set point, mode, and door status. Dispatch decides whether to divert to a repair vendor, notify the customer, or continue. Every action is logged on the exception with who did it and when.

Customer notification rules belong in the customer profile, not in someone's memory. Some shippers want a call on any transit excursion. Others want notice only for alarms or for deviations above a certain size. When the load delivers, the exception record, the telematics trace, and any driver photos travel with the delivery documents. If a receiver rejects product or a claim follows, the carrier can show the full timeline. Our TMS implementation practice configures these exception types, owners, and customer notification rules, and our reporting work produces weekly excursion summaries by customer, trailer, and unit model so recurring equipment problems surface early.

Training Records Under 21 CFR 1.910

When a carrier and shipper agree in writing that the carrier is responsible, in whole or in part, for sanitary conditions during transportation, section 1.910 requires the carrier to train personnel engaged in transportation operations. Training covers awareness of potential food safety problems that may occur during transportation, basic sanitary transportation practices to address those problems, and the responsibilities of the carrier under the rule. Training must occur upon hiring and as needed thereafter, and it must be documented with the date of the training, the name of the person trained, and a description of the training. FDA has made an online carrier training course available, and many carriers supplement it with their own SOP walkthrough.

Store training records in the driver qualification or HR system with an expiration or refresh date, and link the reefer SOP version each driver was trained on. When the SOP changes, the system should show who still needs the update.

Written Procedures and Record Retention Under 21 CFR 1.912

Section 1.912 sets the recordkeeping requirements. Carriers must retain their written procedures for 12 months beyond the time they are in use, written agreements assigning responsibilities for 12 months beyond the termination of the agreement, and training records for 12 months beyond the time the trained person stops performing the duties covered. Records may be kept as originals, true copies, or electronic records, and offsite storage is acceptable if the records can be retrieved and provided onsite within 24 hours of a request for official review.

The rule's retention requirements focus on procedures, agreements, and training. Load level temperature data is what you use to make the demonstration a shipper requests, and customers often specify how long they expect it kept. A sensible policy keeps temperature traces, door events, and exception records for at least the 12 month horizon, longer when customer contracts or claim windows require it. Back up the data, restrict who can edit an exception after closure, and log every export. Those controls align with our data protection practice.

FSMA 204 Traceability Is a Separate Rule

The Sanitary Transportation rule is not the FSMA 204 Food Traceability Rule. Subpart O addresses vehicle sanitation, temperature control, training, and related procedures. FSMA 204, codified separately, requires Key Data Elements for Critical Tracking Events on foods on the Food Traceability List and the ability to provide a sortable spreadsheet to FDA within 24 hours, with two year record retention. A reefer carrier hauling leafy greens, for example, may need to meet both. The data overlaps, since telematics timestamps and locations help confirm shipping and receiving events, but the requirements and retention periods differ. Our guide to FSMA 204 carrier TMS compliance covers the traceability side.

A 60 Day Rollout

Days 1 to 20, collect each food shipper's written temperature and sanitation instructions, review which agreements assign responsibilities to the carrier, and draft the written procedures. Days 21 to 40, add required temperature fields to load entry, map telematics feeds to loads and trailers, define excursion types, and pilot the exception workflow on one customer. Days 41 to 60, train drivers and dispatch with documented records, expand to all reefer customers, and run a mock request in which a customer asks for proof of temperature on a past load. Time the response and fix whatever slowed it down.

Related practice areas for this work include TMS Implementation, ELD and EDI Integration, Reporting, and Data Protection. Each practice page describes scope, deliverables, and how an engagement starts with a short discovery call.

How Strong Tower Consulting Helps

Strong Tower Consulting helps carriers turn a regulatory or operational requirement into a working system inside the TMS rather than a side spreadsheet that only one person understands. For reefer fleets that means written procedures that match how the operation actually runs, telematics data tied to loads, exception queues with clear owners, and records that can be produced quickly. Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. That separation keeps consulting advice vendor neutral and focused on the carrier operation.

To discuss your reefer fleet, your shipper instructions, and your current telematics setup, contact us or call 763-244-1373 and ask for Scott Elliott. A short call is enough to map the first pilot and the gaps to close before a customer asks for proof.

Frequently Asked Questions