--- title: "Nonconformance and CAPA Review With AI Agents | Kylon" description: "How a quality engineering team dispositions NCRs, builds the cost report, audits the CAPA tracker and applies late notices in one Kylon room, with people approving." url: "https://kylon.io/use-cases/nonconformance-and-capa" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Nonconformance and CAPA: A Quarterly NCR Review That Changes Only What It Should Use Case8 min read # Nonconformance and CAPA: A Quarterly NCR Review That Changes Only What It Should A quarterly NCR review where each lab, supplier or complaint notice changes only the records it names. Agents work the Airtable register with evidence from Box and HubSpot in one Kylon room, and the quality manager approves every disposition. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Active NCRs, lab evidence and complaints that close on their own schedule A quarterly NCR review asks three questions of every open nonconformance: what happens to the material, who pays for it, and does it need a corrective action. Answering them means reading the lab report behind each NCR, the customer complaint it may be linked to, and the supplier's response when a purchased part is involved. Some answers send the problem back to design engineering, because the root cause is a tolerance on the drawing rather than a process on the floor. Those answers live in four places. The NCR register is an Airtable base, lab reports and supplier responses land in Box, complaints sit in HubSpot, and the engineers keep their own CAPA tracker in Google Drive. Notices keep arriving after the review starts, and each one tempts someone to touch the whole register again, including the date that records when the review actually happened. ## Who works in the room People - Quality manager Chairs the quarterly review, approves each disposition and signs the close-out records - Quality engineers Own individual NCRs and CAPAs, keep the tracker and confirm changes to their own records - Supplier quality engineer Negotiates chargebacks and corrective actions with suppliers - Complaints lead Manages customer complaints in HubSpot and confirms when one closes Agents - AdaNCR reviewer Reads each active NCR with its lab report and linked complaint, proposes the disposition, and applies later notices to the NCRs they name and no others AirtableBox[HubSpot](https://kylon.io/integrations/hubspot) - RyanCost and recovery Builds the cost report by defect category, applies supplier chargebacks and drafts supplier correspondence for a person to send Airtable[Gmail](https://kylon.io/integrations/gmail)Google Drive - NovaTracker auditor Checks the engineers' CAPA tracker against the NCR register and checks the close-out records before they are signed Google DriveAirtable[Slack](https://kylon.io/integrations/slack) One room holds the quarterly review. Ada is the default agent, so an engineer's question about an NCR goes to Ada unless it names someone else. Anything about cost or a supplier routes to Ryan, who owns the cost report once it exists. Nova works from a thread Ada opens when the dispositions are written, and its first message is the brief: the approved register, where the tracker lives, and the withdrawn NCRs to leave alone. ## How the quarter's review runs The review procedure and the cost report template sit in the review folder. No stage closes until the person in the last column has signed it off. ```mermaid flowchart TD dispose["Ada proposes each disposition and
sets the reviewed date once"] approve["Quality manager approves
before the register is written"] cost["Ryan tallies cost by category
from the approved records"] tracker["Nova compares the CAPA tracker
with the register, line by line"] review["Quality manager
reviews the report"] correct["Quality engineers
correct their own lines"] notice([Notices arrive one by one,
each naming a few NCRs]) lab["Ada re-runs only
the NCRs it covers"] charge["Ryan updates recovery
on the NCRs it names"] complaint["Ada updates the linked
NCR and nothing else"] owner["Quality engineer who
owns the NCR confirms"] sqe["Supplier quality engineer
approves and sends"] clead["Complaints lead
confirms the closure"] closeout["Ryan writes one close-out
record per defect category"] sign["Quality manager signs
the close-out records"] dispose --> approve --> cost & tracker cost --> review tracker --> correct review & correct --> notice notice -->|lab revision| lab notice -->|chargeback| charge notice -->|complaint closed| complaint lab --> owner charge --> sqe complaint --> clead owner & sqe & clead --> closeout --> sign class dispose,cost,tracker,lab,charge,complaint,closeout agent class approve,review,correct,owner,sqe,clead,sign person class notice 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 | | --- | --- | --- | --- | | Quarterly disposition | Each active NCR gets a disposition and root cause category from its lab report and any linked complaint, and the reviewed date is set once | Ada, from Airtable, Box and HubSpot | The quality manager approves before the register is written | | Cost report | Scrap, rework and supplier-recoverable cost is tallied by category from the approved records | Ryan | The quality manager reviews the report | | Tracker audit | The engineers' CAPA tracker is compared with the register, line by line | Nova | Each engineer corrects their own lines | | Lab revision | A revised lab report re-runs only the NCRs it covers | Ada | The engineer who owns the NCR confirms | | Supplier chargeback | An accepted chargeback updates recovery on the NCRs it names | Ryan | The supplier quality engineer approves and sends the confirmation | | Complaint closure | A complaint closed in HubSpot updates the linked NCR and nothing else | Ada | The complaints lead confirms the closure | | Close-out | One close-out record per defect category, including categories with no NCRs this quarter | Ryan, checked by Nova | The quality manager signs all six | One quarter's review. NCR numbers, categories and costs are illustrative. ## A notice about three NCRs changes three NCRs Notices arrive one by one through the quarter. The lab revises a hardness result in Box. A supplier accepts a chargeback on two castings by email. A customer complaint closes in HubSpot after a credit is issued. Each names a small set of NCRs, and Ada applies it to exactly those records. The reviewed date stays where the quarterly review set it, because it records when the review happened, not when the last notice arrived. Withdrawn NCRs stay withdrawn. An engineer may withdraw a report raised in error, and it should not reappear in a disposition, a cost total or a close-out count. When the lab uploads a batch of revised reports at once, Ada can split the reading across parallel helpers and return one list of the NCRs whose results changed. If someone later asks why an NCR moved, the run history shows the notice, the record, the field and who approved it. ## What the checks catch - A reviewed date overwritten by a later notice instead of staying at the quarterly review date - A withdrawn NCR picked up by a disposition run, the cost report or a close-out count - A lab revision, chargeback or complaint closure applied to NCRs it does not name - A tracker line that shows a CAPA closed while its NCR is still open in the register - A missing close-out record for a defect category that had no NCRs this quarter ## What stays with people - Approving each disposition before the register changes - Deciding whether a nonconformance needs a CAPA, and whether design engineering owns it - Sending supplier correspondence, which Ryan prepares as a Gmail draft - Signing the six close-out records ## Integrations in this workflow Kylon is not a quality management system, and it is not trying to become one. The register stays in Airtable and the evidence stays in Box and HubSpot, while the room holds the review that ties them together. The quality manager owns the Box and HubSpot connections and gave Ada a lasting grant for this room. - Airtable - Box - [Gmail](https://kylon.io/integrations/gmail) - Google Drive - [HubSpot](https://kylon.io/integrations/hubspot) - [Slack](https://kylon.io/integrations/slack) - **Airtable** holds the NCR register, CAPA links, cost fields and the close-out records - **Box** holds lab reports, revised results and supplier corrective action responses - **HubSpot** holds the customer complaints linked to NCRs, and their closure status - **Gmail** carries supplier threads about chargebacks, with replies left as drafts for a person to send - **Google Drive** keeps the review folder: procedure, cost report and the engineers' CAPA tracker - **Slack** is where the lab and the production floor post quick updates, such as a revised report going up ## Where to start Begin with last quarter's register, where the answers are already known. Connect the Airtable base, point Ada at the Box folder where lab reports land, and give the room guidelines a single rule: an agent may propose a disposition or apply a notice to the NCRs it names, and the quality manager approves every change before the register is written. > “The review date says when we reviewed, and the withdrawn reports stay out of the numbers.” ## 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 quarterly NCR review desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Airtable, Box, Gmail, Google Drive, HubSpot and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the quality manager, the quality engineers, the supplier quality engineer and the complaints lead. Help me invite them to this Room. 3. Build an NCR Board App with columns Open, Lab review, Dispositioned and Closed, one record per active NCR. Pull the current open records from the Airtable register. 4. Read each active NCR with its lab report from Box and any linked complaint from HubSpot. Propose a disposition and root cause category for each. Flag any withdrawn NCR that appears in the run, any reviewed date that looks overwritten by a later notice, and any revision or chargeback applied to NCRs it does not name. 5. Draft the cost report by defect category and any supplier correspondence as Gmail drafts. Write nothing to Airtable and send nothing until the quality manager approves each disposition, the supplier quality engineer approves each chargeback, and the complaints lead confirms each complaint closure. 6. Write the approval order and who approves which change into this Room's guideline, so every notice and every close-out follows our rules. 7. After one clean quarter, offer to turn the tracker audit 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)[ ### 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. ManufacturingCompliance & riskScheduling & dispatch ](https://kylon.io/use-cases/equipment-calibration)