Nonconformance and CAPA: A Quarterly NCR Review That Changes Only What It Should

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

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.

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
• Google Drive
• HubSpot
• 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.