Keep inspection results, corrective actions, risk controls, and calibration evidence connected to the affected products and revisions.
Click to enlarge Save bounded lot-genealogy evidence, assign containment and recovery work for every affected lot, and extend scope without erasing earlier evidence. Complete response work and an explicit coverage assessment before independent closure. Available in the app, REST and MCP; physical recovery still requires verification.
In the APIApprove exceptions for a specific item revision and lot with a quantity limit, expiry and conditions. Record usage without exceeding the allowance, preserve independent decisions, and withdraw or correct records without erasing history. Available through the app, REST and MCP.
In the APIBind a supplier’s sample lot to an exact item revision. Track required inspection and characteristic coverage, freeze actual results, and preserve independent decisions and resubmissions. Available in the app, REST and MCP without automatically releasing production.
In the APITrack instruments, owners, locations and calibration intervals. Filter by status or due window, search the register, and export the visible equipment list for scheduling and review.
In the APIRecord passing and failed calibrations with dates and notes. Attach a private PDF, PNG or JPEG certificate, reuse recorded evidence, and download original files through authenticated access. History exports retain certificate metadata.
In the APISelect dates and quality areas to download linked CSV evidence, private calibration certificates and a SHA-256 manifest from one consistent snapshot. Explicit scope notes and whole-export limits prevent silent omissions.
In the APITrace inspections potentially affected by a failed calibration. Record an impact assessment, track required reinspections and their replacement evidence, and document containment resolution without rewriting the original checks.
In the APITurn a rejected inspection into a tracked nonconformance with containment, ownership and a due date. Route disposition through independent review and verify execution before closing the case.
In the APIExecute an NCR's rework decision with assigned instructions, partial completion and repeat cycles. Link fresh revision-matched inspections, preserve measured evidence, and require independent verification before the NCR can advance.
In the APICarry out an NCR's scrap decision with quantity-controlled partial disposal, methods and supporting records. Preserve correction history and require independent verification before the NCR can advance.
In the APIInvestigate linked failures, record root cause, and assign containment, corrective and preventive actions. Track independent approval and effectiveness evidence alongside the case history.
In the APIAssess failure modes against a product revision using severity, occurrence and detection scores. Retain mitigation evidence and residual risk, with independent review before approval.
In the APITurn an approved process FMEA into production controls with specifications, measurement methods, sampling, reaction plans and inspection bindings. Keep coverage and approval evidence with the plan.
In the APIRecord lab dips, fit checks, inspections, and tests against the relevant product or material. Follow successive rounds and their results in one history.
In the APIClose a check with a real decision: approve, use as is, rework or scrap. The disposition is a field with rules, not a comment someone has to interpret.
When the spec moves on after a check passed, the approval is flagged as stale rather than silently continuing to look valid.
Keep certificate issue and expiry dates with the relevant record. Filter by expiry to find certificates that need renewal.
A sample is the as-built instance of a design: the physical thing that exists, tied to the record it was built from and to the checks run against it.
Model lots that consume lots, then answer the recall question — every shipped lot affected by one bad batch — in a single call.
In the APITrack hours, cycles, or distance against a usage limit. Calculate remaining life from the recorded usage to support maintenance planning.
In the APIStart with your product model, connect the records, and bring your team into the same workflow.
