--- title: "Equipment Calibration and Instrument Quarantine | Kylon" description: "A plant quality team runs instrument status, outside lab visits and voided calibrations in one Kylon room, with a person approving each change before it is written." url: "https://kylon.io/use-cases/equipment-calibration" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Equipment Calibration: Every Instrument Cleared or Quarantined on Its Own Record Use Case8 min read # Equipment Calibration: Every Instrument Cleared or Quarantined on Its Own Record Each instrument gets its status from its own class, due date and certificate. Agents work Airtable, SharePoint and the lab mail in one Kylon room, plan outside lab visits and handle voided calibrations, and the quality manager approves every status. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Four dozen instruments, three classes and due dates a day apart Every month the quality team decides which instruments stay in service. Each gauge, torque wrench and pressure transducer has a class, a calibration interval and a grace window, and its status depends on its own due date and on whether the outside lab's certificate has arrived. Several instruments come due within a day or two of each other, which is exactly where a status gets copied from the wrong row. The inputs live in different places. The instrument register is an Airtable base, class thresholds sit on a SharePoint procedures list, certificates arrive in the quality mailbox in Outlook, and the second plant, which joined last year, still sends its technicians' notes from Gmail. The coordinator's monthly report is a document in Google Drive, written from all four and checked against none of them. ## Who works in the room People - Quality manager Owns the calibration policy, approves every status and quarantine before it is written, and signs the monthly summary - Calibration coordinator Drafts the monthly report, books the outside lab's visits and sends the replies - Metrology technician Recalibrates instruments in-house and reports each result to the room Agents - MycoDisposition lead Reads each instrument with its own class threshold, due date and certificate, proposes status and quarantine reason, and re-runs instruments when something changes AirtableSharePointOutlook[Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) - RyanLab visit planner Groups due instruments into the lab's visit days, proposes the calendar events, and drafts a reply only when the coordinator asks for one AirtableOutlook[Gmail](https://kylon.io/integrations/gmail) - AdaReport checker Checks the coordinator's draft report and Myco's close calls line by line against the instruments table, the calibration records and the procedures list Google DriveAirtableSharePoint The quality team runs one calibration room for both plants. Myco is the default agent, so a message that names no one, such as a supervisor's Slack report of a dropped height gauge, lands with Myco. Questions about visit dates go to Ryan, who owns the lab schedule. When a set of dispositions is approved, Myco opens a thread for Ryan whose first message lists the instruments that need the lab, with their classes and locations, and Ryan leads that thread from there. ## A month of calibration decisions, in order The policy and the allocation rules sit in the cycle folder and in the room guidelines, so all three agents work from the same version. Each step ends with a person. ```mermaid flowchart TD disp["Myco proposes each instrument's
status from its own record"] ok1["Quality manager approves
before Airtable is written"] plan["Ryan groups due instruments
into the lab's visit days"] dates["Calibration coordinator
approves the dates"] report["Ada checks the draft report
against the instruments table"] fix["Coordinator corrects the report,
quality manager confirms"] moved([The lab moves a visit or a
technician recalibrates in-house]) failed([A reference standard
fails its recheck]) rerun["Myco re-runs only the
instruments it names"] voids["Myco lists every record
made with that standard"] reply["Ryan drafts the single reply
for the coordinator to send"] okvoid["Quality manager approves the
voids, decides on product impact"] back["Myco runs each instrument
back through the policy"] close["Myco builds summary rows per
class from the table at close"] sign["Quality manager signs the summary"] disp --> ok1 --> plan --> dates --> report --> fix fix --> rerun & voids moved -.- rerun failed -.- voids rerun --> reply --> close voids --> okvoid --> back --> close close --> sign class disp,plan,report,rerun,voids,reply,back,close agent class ok1,dates,fix,okvoid,sign person class moved,failed event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Monthly dispositions | Each instrument gets a status and, where needed, a quarantine reason, from its own class threshold, due date and certificate | Myco, from Airtable, SharePoint and Outlook | The quality manager approves before Airtable is written | | Lab visit plan | Due and quarantined instruments are grouped into the lab's visit days under the allocation rules | Ryan | The coordinator approves the dates before any Outlook event is created | | Draft report check | The coordinator's report is compared with the instruments table, the calibration records and the procedures list | Ada | The coordinator corrects the report and the quality manager confirms the Airtable fixes | | Reschedule and in-house work | A moved lab visit or an in-house recalibration updates only the instruments and events it names | Ryan and Myco | The coordinator sends the single reply to the lab | | Technician recheck | Records made with a failed reference standard are voided and those instruments go back through the policy | Myco | The quality manager approves the voids and decides on product impact | | Close-out | Summary rows per class are built from the table as it stands at close | Myco, checked by Ada | The quality manager signs the summary | A typical calibration month. Instrument ids, classes and dates shown here are illustrative. ## When the lab moves a date or a reference standard fails Changes reach the room as email and chat. The lab's scheduler asks to move a visit by three days. A technician recalibrates a bore gauge in-house and sends the result. A correction memo says one calibration record carried the wrong as-found reading. Myco re-runs only the instruments named, writes a one-line note on each record saying what changed, and proposes canceling any lab visit that an in-house recalibration or a fresh certificate has made unnecessary. A failed reference standard reaches further. When the lab reports that the master set one of its technicians used failed its own recheck, every calibration done with that set is in doubt. Myco lists those records, voids them once the quality manager approves, and sends each instrument back through the policy as if no certificate existed, which usually means quarantine until it is recalibrated. Ryan drafts the single reply the quality manager asked for, with the count and the instrument ids, and the run history keeps every step for the next audit. ## What the checks catch - Two instruments due a day apart, each judged on its own class and due date, never on the row above it - No reply when a request asks for none, and exactly one reply, on the named thread, when it asks for one - Voided calibration records followed by a fresh pass through the policy for every instrument they covered - A lab visit still booked for an instrument that has since been recalibrated in-house - Close-out counts per class taken from the current table, not from the first pass of the month ## What stays with people - Approving each status and quarantine reason before Airtable changes - Sending every reply to the lab, which Ryan prepares as an Outlook or Gmail draft - Deciding what a voided calibration means for parts already made with that instrument - Signing the monthly compliance summary ## Integrations in this workflow Kylon is not a calibration management system and does not replace one. It sits across the tools the quality team already runs and keeps the coordination between them in one place. The SharePoint and Airtable connections are a lasting grant the quality manager approved for this room, while Ryan drafts mail through the coordinator's own account, checked on every call. - Airtable - [Gmail](https://kylon.io/integrations/gmail) - Google Drive - Outlook - SharePoint - [Slack](https://kylon.io/integrations/slack) - **Airtable** holds the instruments table, the calibration records and the monthly summary rows - **SharePoint** keeps the procedures list with each class's interval, grace window and tolerance - **Outlook** receives the lab's certificates and carries the visit calendar and the lab's scheduling thread - **Gmail** carries the second plant's technician notes, including in-house recalibration results - **Google Drive** holds the cycle folder: policy, allocation rules, the draft report and correction memos - **Slack** is where line supervisors report a dropped or damaged instrument ## Where to start Pick one plant's instruments and one month. Connect the Airtable base that holds your register, give Myco the SharePoint procedures list, and add an automation that flags any instrument the day its due date passes. Then write the rule that matters most into the room guidelines: agents propose statuses, quarantines and visit dates, and the quality manager approves each one before anything is written or booked. > “Each instrument is judged on its own row, and the lab hears from us once, on the thread that asked.” ## 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. Set-up prompt Set up our equipment calibration desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Airtable, Gmail, Google Drive, Outlook, SharePoint and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the quality manager, the calibration coordinator and the metrology technician. Help me invite them to this Room. 3. Build an Instrument Register App with Instrument, Class, Next due and Status, one record per instrument. Fill it from our Airtable base and flag any instrument whose due date has already passed. 4. Read each instrument against its class threshold we set on the SharePoint procedures list, its due date and any certificate in the Outlook quality mailbox or Gmail. Propose a status and, where needed, a quarantine reason for each instrument. Show any instruments with close due dates side by side so nothing is copied from the wrong row. 5. Propose nothing written to Airtable, no Outlook event created and no lab reply drafted until the quality manager approves each status and quarantine reason. 6. Write the approval order and who approves which write or send into this Room's guideline so every instrument follows the same path. 7. After one clean month, offer to turn the daily due-date check into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Engineering Change Orders: Each Change Decided on Its Own Record, With Dates That Hold A weekly change board decides thirty change orders on their own records, with effective dates set from stock on hand and supplier commit dates. Agents prepare and check each one in a Kylon room, and the board chair approves every disposition. ManufacturingApprovals & reviews ](https://kylon.io/use-cases/engineering-change-orders)[ ### Lot Recall Traceback: Each Shipment Traced and Notified, From First Notice to Close Shipment dispositions, notice batches, the coordinator's notification log and every customer acknowledgment run through one Kylon room. Agents trace each shipment across Airtable and Salesforce, and nothing reaches a customer until a person sends it. ManufacturingCompliance & riskEmail operations ](https://kylon.io/use-cases/lot-recall-traceback)