Cold Chain Excursion Review: Every Shipment Dispositioned Against Its Stability Budget

Minutes out of range, a budget per product and a manifest that has to agree

An excursion review looks simple on paper. Each shipment's data logger shows how long the product sat outside its labeled range, each product carries a stability budget of allowed minutes, and minutes spent earlier in the lot's journey count against that budget. A shipment within budget is released, one close to the limit goes to a QA reviewer, and one over budget is rejected.

In practice the logger files land in Box, the shipment and product records live in Airtable, carrier reports arrive in the logistics team's Outlook mailbox, and receiving staff post in Slack when a logger is missing. The manifest the warehouse works from is assembled from all of it in a spreadsheet. A budget revision or a late logger download means someone recomputes minutes by hand and hopes every dependent field moved with them.

Who works in the room

The QA team keeps one Kylon room for excursions with Myco as its default agent, so a question about a shipment's minutes or disposition reaches Myco without a mention. The room guidelines send manifest questions to Ryan and anything addressed to a carrier or consignee to Fin. Myco reads Box and writes Airtable through a lasting grant the QA lead approved for this room. Fin drafts into the logistics mailbox through a grant the distribution coordinator approved, and each draft waits there for a person to send it.

A week of excursions, from logger file to close-out

The excursion procedure and the current budgets sit in a Drive folder the room guidelines point to, so every agent works from the same version. Each step ends with a person.

When a report or a budget changes mid-week

Most changes arrive as messages. A receiving clerk posts in Slack that a missing logger turned up at the bottom of a tote. A carrier emails a temperature trace for a leg the shipment logger did not cover. A QA reviewer is out for the rest of the week, so her open shipments are proposed to the others within their load. Myco treats each message as the source for that change, re-runs only the shipments it touches and leaves a note on every changed record saying why it moved.

A budget revision is the change most likely to leave something behind. The stability memo states the new budget in hours, so the figure is converted to minutes and rounded down as the procedure says, and it has to land on the product row as well as on every open shipment of that product. A shipment that moves from quarantine to release also has to give its reviewer back. Ryan checks those side effects before the QA lead approves, and every agent turn that uses a tool keeps a step-by-step run history, so an auditor can see which logger file and which budget figure produced each disposition.

What the checks catch

• Minutes carried with a fraction after a budget revision, when the procedure rounds down to whole minutes
• A released shipment that still names a QA reviewer, which leaves work open on someone's list
• A revised budget applied to the shipments but not to the product's own row in Airtable
• A carrier email accepting liability for an excursion, which settles the claim but does not make the product releasable
• A manifest line whose disposition disagrees with the approved record, or a shipment missing from the manifest altogether

What stays with people

• Approving every disposition and reviewer assignment before Airtable is updated
• Deciding borderline cases where the logger data is incomplete or the trace is ambiguous
• Sending every carrier and consignee notice, which Fin prepares as a draft in Outlook or Gmail
• Signing the weekly close-out

Integrations in this workflow

Kylon is not a quality management system or a temperature monitoring service, and it replaces neither. It sits across the tools the QA team already uses and keeps the coordination between them in one place.

• Airtable
• Box
• Gmail
• Google Drive
• Outlook
• Slack

• Airtable holds the shipment and product tables, with dispositions, reviewers and stability budgets
• Box stores the logger downloads and temperature reports for each shipment
• Outlook is the logistics mailbox where carrier reports arrive and claim notices go out as drafts a person sends
• Gmail carries disposition notices to consignee sites, each one a draft the coordinator sends
• Google Drive keeps the excursion procedure, the budget memos and the draft manifest
• Slack is where receiving staff outside the room report missing loggers and damaged packaging

Where to start

Start with one product family and one week of shipments. Connect the Airtable base that holds your shipments and products, point the room at the Box folder where logger files land, and put the one rule that matters in the room guidelines: an agent may total minutes and propose dispositions, and the QA lead approves every release and reject before a record changes.

“The arithmetic was never the hard part. Keeping every field that depends on it in step was.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.