Extract data from inspection reports

An inspection report is the record a quality inspector produces after checking a batch of goods against a specification. It states, characteristic by characteristic, what was required and what was measured, and it ends in a single verdict: pass or fail. It is not a non-conformance report, which opens after a failure to document one specific defect and drive a corrective action, and it is not a certificate of conformance, which is the supplier's own declaration that the goods meet spec. The inspection report is the independent check that decides whether a lot ships. Bureau Veritas inspects a 5,000-unit lot from Shenzhen Precision Components Ltd against purchase order PO-2026-3391 on 2026-06-27 and issues its report the next day, 2026-06-28. The verdict rests on the sampling plan. Under ISO 2859-1, an inspector pulls a sample sized to the lot and an acceptance quality limit, here 200 units at AQL 2.5, General Inspection Level II, and compares each unit against the acceptance and rejection numbers. Defects are graded critical, major, or minor, and the rule that decides the lot is not just a count: a single critical defect, a burr sharp enough to injure a user, fails the whole lot regardless of how few were found. Each characteristic in the report carries its specification_limit, its measured_value, and a unit, so a shaft diameter required at 12.00 mm plus or minus 0.05 and measured at 12.14 mm reads as an out-of-tolerance fail on its own row. Talonic reads the report and returns the supplier, the purchase_order_number, the item_inspected, the sampling_plan, the quantity_inspected, and the overall_status as fields, with the inspection_results and the defect_log as tables. The overall_status of fail is carried alongside the defect_count of 8, which is checked against the defect_log rows: 2 critical, 4 major, and 2 minor units foot to the reported total. Measured values keep their units, defect classes keep their severity, and the 2026-06-27 inspection date and 2026-06-28 issue date parse to ISO 8601, so a QC lead can trace the fail verdict to the exact characteristic behind it. Talonic captures the findings as recorded and does not itself pass or reject the lot.

What gets extracted from inspection reports

How extraction works for inspection reports

Inspection reports come from third-party agencies such as Bureau Veritas and from in-house QC labs in layouts that follow no single form, since ISO 9001 and ISO 17020 govern the process, not the field structure. Talonic classifies the report and maps it to the inspection schema in the Field Registry, so supplier.name, purchase_order_number, sampling_plan, quantity_inspected, overall_status, and defect_count each resolve to a field while inspection_results and defect_log return per row. Each characteristic row keeps its specification_limit, measured_value, unit, and pass/fail result, and each defect row keeps its class, quantity_affected, and disposition, so a rework-or-scrap decision is legible. The defect_count is checked against the sum of the affected units in the defect_log, and the overall_status enum is preserved exactly. Every value carries a confidence score and a source-region pointer under DIN SPEC 91491, so a receiving team can verify the fail verdict against the inspected characteristic. Talonic reports the inspection as recorded and does not re-adjudicate the pass/fail result.

Sample extraction

A pre-shipment QC inspection that fails on a critical defect

{
  "document_number": "QC-2026-3391-PSI",
  "document_date": "2026-06-27",
  "report_issue_date": "2026-06-28",
  "supplier.name": "Shenzhen Precision Components Ltd",
  "supplier.code": "SPC-4471",
  "purchase_order_number": "PO-2026-3391",
  "shipment.receipt_date": "2026-06-26",
  "shipment.quantity_received": 5000,
  "item_inspected": "Stainless drive shaft, part SDS-114",
  "item_identifier": "Lot 2026-24-B",
  "inspector.name": "Wei Chen",
  "inspection_body": "Bureau Veritas",
  "accreditation_number": "CNAS L-1123",
  "inspection_location": "Shenzhen, Guangdong, CN",
  "specification": "Drawing SDS-114 Rev C; ASTM A276",
  "sampling_plan": "ISO 2859-1, AQL 2.5, General Inspection Level II",
  "quantity_inspected": 200,
  "overall_status": "fail",
  "result": "One critical defect found; lot rejected pending rework and re-inspection",
  "defects_found": true,
  "defect_count": 8,
  "conformity_statement": "Inspected lot does NOT conform to Drawing SDS-114 Rev C",
  "corrective_action": "Segregate and rework burred units; supplier 8D report requested",
  "next_inspection_date": "2026-07-05",
  "inspection_results": [
    {
      "characteristic": "Shaft length",
      "specification_limit": "150.0 +/- 0.5",
      "measured_value": "150.2",
      "unit": "mm",
      "result": "pass"
    },
    {
      "characteristic": "Shaft diameter",
      "specification_limit": "12.00 +/- 0.05",
      "measured_value": "12.14",
      "unit": "mm",
      "result": "fail"
    },
    {
      "characteristic": "Edge finish",
      "specification_limit": "No sharp burrs",
      "measured_value": "Burrs present on 2 units",
      "unit": "visual",
      "result": "fail"
    }
  ],
  "defect_log": [
    {
      "defect_id": "D-1",
      "defect_description": "Sharp burr on chamfer edge",
      "defect_class": "Critical",
      "quantity_affected": 2,
      "disposition": "rework"
    },
    {
      "defect_id": "D-2",
      "defect_description": "Diameter above upper tolerance",
      "defect_class": "Major",
      "quantity_affected": 4,
      "disposition": "return to supplier"
    },
    {
      "defect_id": "D-3",
      "defect_description": "Surface scratch, cosmetic",
      "defect_class": "Minor",
      "quantity_affected": 2,
      "disposition": "use-as-is"
    }
  ]
}

Frequently asked