Handle a temperature excursion on a refrigerated load
A step-by-step response to a reefer temperature problem: protecting product, preserving evidence, notifying the customer, and preventing repeats.
The prompt
Help me respond to a temperature excursion on a refrigerated load.
Load: [LOAD NUMBER, CUSTOMER, COMMODITY, SET POINT AND ALLOWED RANGE, CONTINUOUS OR CYCLE MODE]
What happened: [e.g. "reefer alarmed at 2:10am, box temp rose to 48F for 3 hours"]
Where the load is now: [in transit, at receiver, rejected, at a repair shop]
Data available: [reefer download, telematics temperature log, pulp temperatures taken, seal number, pre-cool record]
Cause if known: [unit failure, fuel ran out, wrong set point, doors opened, shipper loaded warm product]
Customer requirements: [contract or food safety program terms, who decides product disposition]
Regulations in scope: [e.g. "US sanitary transportation of food rule", pharma GDP, or [CONFIRM]]
Give me:
1. Immediate actions in order: protect the product, get the unit repaired or the load transferred, take pulp temperatures, keep the seal intact unless told otherwise.
2. Evidence to preserve and how: reefer download, photos, driver statement, temperature logs, bill of lading set point.
3. Who to notify and what to tell them: shipper, receiver, broker, insurer.
4. A factual first notice message to the customer.
5. Points that affect liability: set point on the BOL versus the unit, pre-cool, product temperature at loading, how the alarm was handled.
6. Prevention: pre-trip reefer checks, fuel level rules, alarm response procedures, driver training.
Return a timeline template, the customer message, and a corrective action list.
Do not decide whether product is safe to sell; that is the product owner's call with their quality team. Mark unknown facts [CONFIRM] and do not speculate on fault in customer communications.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- in transit, at receiver, rejected, at a repair shop
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Plan a group project and split the work fairlyA fair task split, timeline, and team agreement for a school group project, including what to do if someone doesn't pull their weight.
- Plan an MFA or password manager rollout across the companyBuilds a phased rollout plan with pilot groups, user communications, support prep, and handling of edge cases.
- Plan stakeholder communication and engagementWho needs to know what, when, and how — and how to keep them engaged.
- Find where communication is breaking down on my projectDiagnoses communication gaps across meetings, channels, and teams, and gives you a simple plan to fix the flow of information.