Does AS9100 mandate specific NCR forms or software tools?

No. AS9100 does not mandate a specific NCR form, template, or software tool.

It requires that nonconformities be controlled through a defined process and that records are maintained appropriately. In practice, auditors and customers usually care far more about process discipline, traceability, approvals, record control, and evidence of disposition and follow-up than about whether you use paper, ERP, QMS software, MES, or a standalone NCR application.

What AS9100 typically expects in practice

Your NCR process usually needs to support the following, whether managed manually or digitally:

• clear identification of the nonconformance
• containment and segregation, where applicable
• disposition decisions and authority
• traceability to part, lot, serial, order, operation, supplier, or job context as needed
• review and approval records
• links to corrective action when required
• record retention and revision control

If your form or system cannot support those basics reliably, the issue is not that it is the wrong brand or format. The issue is that the process and records may be inadequate.

Paper, spreadsheet, or software?

Any of them can be workable in some environments. None is automatically acceptable.

A paper form may be sufficient in a smaller or lower-volume setting if document control is strong and retrieval is manageable. A spreadsheet may work temporarily, but often becomes weak on approvals, audit trail, access control, version control, and linkage to disposition, CAPA, or genealogy records. Dedicated software can improve control and visibility, but only if it is configured correctly, validated where required by your procedures, and integrated well enough that users do not create side systems outside control.

Brownfield reality

In regulated aerospace and similar environments, replacing existing quality and manufacturing systems just to standardize NCR handling is often a poor strategy. Full replacement frequently fails because of qualification burden, validation cost, downtime risk, integration complexity, entrenched ERP or MES dependencies, and long equipment and system lifecycles.

More often, plants keep existing ERP, MES, QMS, PLM, and document control systems and improve the NCR workflow around them. That can mean adding a focused NCR tool, extending the current QMS, or digitizing only the approval and traceability steps first. The tradeoff is that coexistence creates interface and master data risks, so ownership of record, synchronization rules, and change control need to be explicit.

What usually matters more than the form or tool

• Who can create, review, and approve NCRs
• How dispositions are controlled and authorized
• Whether affected inventory or WIP can be identified and contained
• How NCRs connect to MRB, deviations, concessions, supplier issues, and CAPA where applicable
• Whether records are complete, legible, retrievable, and protected from uncontrolled change
• Whether the system supports your actual workflow instead of forcing off-system workarounds

So the short answer is no, AS9100 does not require a specific NCR form or software package. It does require a controlled, effective, and auditable nonconformance process. Whether your current approach meets that bar depends on your procedures, system design, data discipline, and how well the process holds up under real operational conditions.