Extract data from non-conformance reports
Unstract reads non-conformance reports, CAPA reports, 8D reports and quality control checklists, typed, scanned or filled in by hand, and sends each part, lot, defect and disposition to your QMS or ERP.
same bore defect as NCR-26-0352 in Aug - open SCAR
FORM QP-830-01 REV D · BRIGHTWATER PRECISION COMPONENTS
{ "ncr_number": "NCR-26-0418", "supplier": "Halvorsen Castings LLC", "part_number": "HB-2207-A", "lot_number": "HC-261019-03", "qty_inspected": 250, "qty_nonconforming": 18, "disposition": "Return to supplier", "capa_number": "CAPA-26-0093", "due_date": "11/24/2026", "confidence": 0.94}
Trusted by manufacturing and quality teams around the globe
Every NCR is filled in at a bench, a dock or a customer's site
A typed report exported from the quality system is the rare one. Most nonconformances reach the quality office on paper, from whoever found them.
Written on a clipboard at the dock, then scanned with grease on it
Your form, a supplier's form and a customer's 8D, each naming the defect box its own way
A recount at the bench, with the old quantity crossed out
A customer complaint sent as one file with the 8D, photos and the lot's certificate
A week of quality control checklists from the line in one export
A quality engineer retypes each report into the QMS by hand, so a supplier's third bore defect this quarter looks like its first until someone runs the numbers.
Unstract reads each report in its own layout, pulls the part, lot, defect, quantities and disposition, checks them against the lot and the PO, and sends the record to your QMS or ERP with repeats flagged.
Parse, extract and route quality reports on one platform
Turn the report into text, the text into a record, and the record into a tracked corrective action. Each product works alone; together they run the whole intake.
Parse non-conformance reports with every box, tick and note in place
Capture the full text of an NCR, a CAPA report, an 8D or a quality control checklist, whether it came from the plant's scanner, a supplier's email or a customer's portal. Each value stays beside its label: the inspector's handwritten defect description, the ticked disposition box and the struck-out quantity all keep their place, so a rework mark is never read as scrap.
Pass the text to your own LLM, or make parsing the first step of an NCR intake workflow.
Learn more about LLMWhispererTurn non-conformance reports into records that flag repeat defects
NCR form data extraction starts with the fields your quality team tracks: every NCR, CAPA or 8D comes back in one JSON structure, whether the form says defect, nonconformity or D2. CAPA report data extraction covers the root cause, each corrective and preventive action with its owner and due date, and the effectiveness check. Records are checked as they come out: a nonconforming count larger than the inspected count, a lot that isn't on the PO, or a defect already reported against the same part arrives flagged with the reason.
Call it as an API from your inspection app, run it as an ETL pipeline from a shared inbox or folder, or make it one step in an orchestrated intake.
Learn more about Document StudioRun NCR intake from the inspection bench to a tracked CAPA
Describe your non-conformance report intake in plain English and Flow's agents build the workflow. Reports are picked up from inspection, the line or a supplier's email, each one is read, the lot and quantities are checked against the PO, and every defect is compared with earlier NCRs for the same part and supplier. The record goes to your QMS or ERP, and a repeat opens a corrective action. You approve the workflow once, and it runs the same way on every report.
Set the points where a quality engineer takes over: a repeat defect, a lot missing from the PO, a report with no disposition ticked, an unsigned form. Only those reports stop, with the reason attached. Unstract reads and routes the report; your QA team still decides the disposition and the root cause.
Learn more about FlowRead your NCRs today. Route them to quality when you're ready.
Start for free to parse and extract your own non-conformance reports now. Automating NCR intake begins with a consultation.
Non-conformance reports, CAPA and 8D reports, and the checklists behind them
Documents
- Non-conformance reports (NCRs)
- Supplier non-conformance reports
- Internal NCRs from the line
- Customer complaint reports
- CAPA reports
- Corrective action reports
- Preventive action records
- 8D reports
- Supplier corrective action requests (SCARs)
- Quality control checklists
- Receiving inspection reports
- In-process inspection sheets
- Material review board records
- Deviation and concession requests
- Hold and quarantine tags
- Effectiveness check records
Fields captured
For the teams that find, decide and close every nonconformance
Every NCR in the QMS the day it's written, with the disposition, owner and due date, so open reports and overdue CAPAs show up on one list.
Defects counted by supplier, part and lot as reports arrive, so a third repeat triggers a corrective action request instead of another NCR.
Return-to-supplier quantities matched to the PO and lot, so the credit or replacement is claimed before the invoice is paid.
NCRs, root causes and effectiveness checks kept against each part, ready for an audit or a customer's request for the 8D.
Nonconformances logged the day they're found
Defect history stays inside your quality team
Non-conformance reports hold your defect histories and your supplier performance records: which parts fail, how often, and which suppliers cause it. A customer reads that as risk, a competitor reads it as a weakness, and a supplier reads it as leverage in the next price talk.
- Encrypted in transit and at rest.
- Quality reports are never used for model training.
- Access by role, plant and supplier, with every correction and disposition change recorded against the NCR.
- You set retention: reports are kept for the period your quality system and your customers require, then deleted.
- Self-hosted deployment for manufacturers that keep defect and supplier data inside their own network.
What quality teams ask about reading NCRs and CAPAs
A CAPA (corrective and preventive action) report records how a nonconformance was handled after the fact: the problem, the containment, the root cause, the corrective action that fixes this case, the preventive action that stops it recurring, an owner and due date for each, and an effectiveness check that proves it worked. Unstract reads each of those as its own field.
Yes. Document Studio returns the CAPA number, the linked NCR, the root cause, each action with its owner and due date, and the effectiveness check result as JSON, whether the report is your own form, a supplier's response or a customer's 8D.
Send reports to Unstract from a shared inbox, a scanner folder or an API call. LLMWhisperer reads each one with its boxes and ticks in place, and Document Studio returns the part, lot, quantities, defect and disposition as a record for your QMS or ERP.
Yes. LLMWhisperer reads handwriting from the bench and the dock, knows which disposition box is ticked, and keeps a struck-out quantity apart from the corrected one. Crooked scans and phone photos are read the same way.
Yes. Corrective action report OCR doesn't need a template per sender. Document Studio finds each field by what it is, so a supplier's SCAR response, a customer's 8D and your own CAPA form all come back in the same structure.
Yes. Each discipline from D1 to D8 is captured as its own field: the team, the problem statement, containment, root cause, corrective actions, verification, prevention and closure, with dates and names where the report gives them.
Yes. Quality control checklist OCR reads each check with its pass or fail mark, the measured value, the shift and the inspector's initials. A failed check can open an NCR in the same run.
No. Unstract reads the report and routes it. Your QA team or material review board decides whether a part is used as is, reworked, scrapped or returned, and your engineers find the root cause. Unstract puts the facts in front of them with any repeat defect flagged.
Each new NCR is compared with earlier reports for the same part, supplier and defect. A match comes back flagged with the earlier NCR number, so a quality engineer can raise a corrective action request instead of logging the defect again.
Yes. Document Studio deploys an endpoint per report type: POST an NCR, CAPA or 8D and get the fields back as JSON. Batches of old NCRs can run through the same extraction from a folder or bucket.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Every NCR is encrypted in transit and at rest, kept out of model training, and deleted on the schedule you set. Manufacturers that keep quality data on their own network can self-host; see the Trust Center.
A quarter of NCRs, a few CAPA or 8D reports and the fields your QMS or ERP expects. In a consultation we set up the intake around them, and most teams see their own reports read within days. To try extraction now, start for free and upload one report.
Bring a quarter of NCRs and CAPAs to the consultation
Internal, supplier and customer reports, with the 8Ds and checklists behind them. We read them in front of you and show which defects repeat.