Automated Cold Chain Breach Logging
Every few minutes, WebRun opens CXT Software, checks the temperature documentation for each specimen leg, logs any reading outside the required range to a Google Sheet, and posts an internal Slack alert so a supervisor can decide whether the affected specimen is still viable.
How do I automatically log and flag cooler temperature breaches on specimen legs?
WebRun reads CXT Software temperature documentation every few minutes and compares each specimen leg against its required range. When a reading falls out of range, it logs the excursion to a Google Sheet with severity, driver, and duration, then posts an internal Slack alert so a supervisor can review whether the specimen is still viable.
- Every temperature excursion is logged with severity for audit
- Supervisors get an internal alert to review affected specimens
- Cold-chain trends by route and driver stay visible
Built for medical courier quality teams · clinical specimen logistics · cold-chain compliance leads · lab transport operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.cxtsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
CXT Software - read temperature readings per leg
cxtsoftware.com
WebRun checks temperature documentation for each specimen leg in CXT Software. - Open CXT Software and pull temperature documentation for active and completed specimen legs
- For each leg, compare the recorded temperature against the required range for that specimen type
- Flag any reading that fell outside the allowed range, with how long and by how much
- Note the specimen ID, the leg, the driver, and the breach detail
Done when Every leg with a temperature reading outside range is identified with the breach detail.
-
2
Google Sheets - log every breach with its detail
google.com
WebRun logs each cold-chain breach to the sheet with its severity. - Open the Cold Chain Breach Log sheet
- Append each breach as a new row with the timestamp, specimen ID, leg, driver, range, and peak reading
- Tag the severity by how far and how long the temperature strayed
- Keep the running log so trends by route or driver stay visible
Done when The breach log sheet holds a complete, severity-tagged record of every temperature excursion.
-
3
Slack - alert a supervisor to review
slack.com
WebRun posts each temperature breach to the quality channel for review. - Post an internal alert to the quality channel for each breach with the specimen ID, leg, and severity
- Put the most serious excursions first
- Ask a supervisor to review whether the specimen remains viable and to record the outcome
Done when A supervisor has an internal Slack alert for every temperature breach to review.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun decide if a specimen is spoiled?
No. WebRun logs the breach and posts an internal Slack alert, but a human supervisor reviews whether the specimen is still viable and records the outcome. The judgement call stays with your quality team.
Are these alerts sent to the client lab?
No. The temperature breach alerts go only to your internal quality channel in Slack. WebRun does not notify the client, the clinic, or the patient, so cold-chain reviews stay in-house until your team decides.
How does it know a reading is a breach?
It compares each leg's recorded temperature in CXT Software against the required range for that specimen type, then flags any reading outside range along with how far and how long it strayed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.