Quality & InspectionFree templatePDF, Excel, Word exportAerospace and Defense

Out-of-Tolerance Calibration Impact Assessment Template

When a gage is found out of tolerance at calibration, you must assess the validity of earlier measurements. This template records the finding, the affected product and the decision in a form auditors expect.

Fill in

Live preview
Download:

Out-of-Tolerance Calibration Impact Assessment Template

Out-of-Tolerance Calibration Impact Assessment

Company: Acme Precision Ltd Report no: OOT-2026-014 Date found: 2026-10-19

Instrument

Gage ID: CAL-0045 Description: Digital caliper 0-150 mm Last good calibration: 2026-04-20

As-found result

At 100 mm the caliper read +0.06 mm against a limit of +/-0.03 mm. All other points within limits.

Use of the instrument

Used on Op 30 in-process checks of bracket BRK-1001, outside width 100 mm +/-0.25 mm.

Affected product

Lots 4417 to 4452 (about 3,600 pieces). Final inspection used a separate calibrated CMM.

Impact review

QuestionAnswerEvidence
Was error larger than the allowed tolerance?
Was the error significant versus the product tolerance?
Was product later verified by another method?
Has any affected product shipped?

Risk conclusion

Re-inspect affected product

Corrective and preventive action

Adjust and recalibrate caliper, shorten interval from 12 to 6 months, retrain operators on zero check.

Approvals

Metrology / Date
Quality engineer / Date
Quality manager / Date

A starting point for your quality system, not a replacement for it. Follow your own procedure and customer contract requirements on notification of nonconforming product.

Automate product traceability for OOT events

Optional review of how lot genealogy in your ERP can speed impact assessments.

Optional. The tool and every export work without this. No spam.

What the standards require

ISO 9001 clause 7.1.5.2 requires an organization to determine whether the validity of previous measurement results has been adversely affected when equipment is found unfit for its purpose, and to take appropriate action. AS9100 adds similar expectations. The assessment should cover the time since the last good calibration or verification.

  • Define a trigger: any as-found reading beyond the permissible error
  • Identify product measured with the gage since the last good result
  • Decide and record the action with evidence

How to complete it

Fill in the gage and the as-found data from the calibration certificate. Describe how and where the gage was used, then list the lots or serial numbers inspected since the last good calibration. Judge whether the error was significant against the feature tolerance, not just the gage limit. Choose a risk conclusion and document corrective action, such as adjusting the gage or shortening the interval.

Practical tips

Use traceability data from the ERP, such as lot and serial genealogy, to find affected product quickly. If the error was small compared to tolerance and a downstream check used a different instrument, the impact may be negligible, but write down the reasoning. Feed repeated out-of-tolerance findings back into interval reviews.

Frequently Asked Questions

Do I need to notify the customer?

It depends on your contract and the impact. If nonconforming product may have shipped, many customer and aerospace requirements demand prompt notification. Check your quality agreement and escalate to quality management.

How far back do I look?

Back to the last calibration or verification where the gage was known to be in tolerance. If you have interim checks showing it was good later, you may shorten the window with documented evidence.

Is every adjusted gage out of tolerance?

No. Adjustment of a gage that was within tolerance as found is not an out-of-tolerance event. Always record as-found data before adjusting, otherwise you cannot tell.

Can I save the form?

Yes. Fill the fields and export to PDF or Word, then store it with the calibration record and any related CAPA.

Netray can help trace affected lots from your ERP inspection and shipment history, running on your own infrastructure.