Early warning signs that an organization is not ready for AS9100 usually show up long before anyone calls a registrar. They tend to fall into six areas: culture and leadership, process discipline, documentation and records, nonconformance and risk management, data and systems, and change control.
1. AS9100 is treated as a “badge,” not a way of working
Clear warning signs:
- Talk about “getting the certificate fast” with little discussion of sustaining the system over the equipment lifecycle.
- No executive sponsor who understands what AS9100 will require from operations, engineering, and IT.
- Management delegates everything to a single “quality person” with no cross-functional ownership.
- Quality is treated as a department deliverable instead of an operations responsibility.
Consequence: you may be able to write a manual and pass one audit, but surveillance audits, customer audits, and real operational issues will quickly expose gaps.
2. Processes exist only as tribal knowledge or outdated documents
AS9100 expects defined, repeatable, and controlled processes. Warning signs:
- Operators “know how we really build it,” but work instructions, routers, or travelers are frequently ignored or outdated.
- Multiple versions of the “same” work instruction exist in email, shared drives, and paper binders, with no clear master.
- New employees learn almost entirely by shadowing, with minimal documented standard work or training records.
- Engineering changes are communicated informally (verbal, chat, text) and take weeks or months to show up in controlled documents or routings.
Consequence: auditors will quickly find inconsistencies between procedures, actual practice, and records. More importantly, product risk increases whenever key people are absent.
3. Document control and records management are weak
In regulated aerospace environments, poor document and record control is one of the strongest indicators of AS9100 unpreparedness.
- There is no clear method to identify the current revision of procedures, work instructions, drawings, or specifications at the point of use.
- Legacy paper and PDF systems coexist informally with MES/ERP/QMS, without a defined master source of truth.
- Retention, retrieval, and backup rules for records (inspection results, certificates of conformity, travelers, FAI packages) are undefined or inconsistently applied.
- Audit trails are incomplete; you cannot reliably say who changed what, when, and why.
Consequence: even if product quality is acceptable, the inability to prove control and traceability will create major audit findings and customer concern.
4. Nonconformance and CAPA are ad hoc and reactive
AS9100 assumes you already have a functioning system to identify, control, and correct problems. Warning signs:
- Scrap, rework, or concessions are tracked only in spreadsheets or not at all, and the numbers do not match finance or production data.
- MRB decisions are not consistently documented; rationales and risk assessments are often missing or informal.
- Repeated issues are handled with quick fixes (more inspection, retraining) instead of documented root cause analysis and corrective actions.
- CAPA exists as a form, but there is no systematic follow-up to verify effectiveness.
Consequence: an auditor will see repeated issues with weak or recycled corrective actions and will question your ability to sustain conformity as you scale or change product mix.
5. Traceability and configuration control are fragile
Many aerospace plants operate in brownfield environments with mixed systems and partial digitization. Early warning signs that traceability is not ready for AS9100 expectations:
- Genealogy (which lot, which serial, which supplier) is reconstructable only by a few experts using a mix of ERP, spreadsheets, and paper search.
- There is no reliable method to link work orders to purchase orders, test data, and as-built configurations across multiple systems.
- Configuration baselines for complex assemblies are unclear; different departments use different BOMs or revision levels.
- Rework, repair, and deviations are not consistently pushed back into configuration records and travelers.
Consequence: any field issue, escape, or customer complaint will be difficult to contain and investigate, and your ability to perform effective recall or impact analysis will be questioned.
6. Internal audits are superficial or non-existent
Internal process audits are central to AS9100. Warning signs:
- No established internal audit program, or it exists only as a checkbox activity driven by a template.
- Auditors are untrained, or they are the same people who own the processes they are “auditing.”
- Findings focus on documentation format rather than whether processes are effective and followed.
- Corrective actions from internal audits are weak or remain open for long periods without escalation.
Consequence: if your internal audits do not surface real issues, the first certification or customer audit will, often at greater cost and with more disruption.
7. Change control and validation are not scaled for aerospace
AS9100 expects disciplined change management that respects product risk and long equipment lifecycles. Warning signs:
- System changes (ERP, MES, QMS, PLM) are made without documented impact assessment on quality records, traceability, and data integrity.
- No clear process to validate software changes that affect production records or compliance-critical data.
- Process changes are implemented on-the-fly by supervisors or programmers without formal review, risk assessment, or customer notification where required.
- Legacy equipment and software are modified without configuration records or rollback plans.
Consequence: in a regulated aerospace context, this undermines confidence in your data, genealogy, and evidence trail, and it can create major nonconformities in an AS9100 audit.
8. Data and systems cannot reliably support evidence needs
Brownfield plants often struggle here. Warning signs that your systems will not support AS9100 evidence requirements:
- Key data is scattered across ERP, MES, spreadsheets, shared drives, and email with no clear ownership or integration strategy.
- Basic questions (scrap by part, complaints by customer, process capability by feature) require manual data pulls and reconciliation.
- Electronic records and signatures (if used) are not governed by clear access control, audit trail, and backup practices.
- Attempts to “fix everything” by replacing core systems all at once have stalled due to downtime risk, integration complexity, or validation burden.
Consequence: even if you write compliant procedures, you may not be able to produce timely, reliable evidence of conformity or effective control during audits or customer investigations.
9. Resource constraints and competing priorities are ignored
Early signs that the AS9100 initiative will stall:
- No dedicated time or resources for process owners to help design and document the system; they are expected to do it “on the side.”
- Significant open issues on capacity, late orders, or major ERP/MES projects with no realistic integration plan into the AS9100 timeline.
- No plan to train operators, engineers, and supervisors on their practical roles in the quality management system.
- Supplier quality and purchasing are not involved, even though external providers are a major AS9100 focus.
Consequence: documentation may be created, but it will not reflect how work is actually done, and adoption on the shop floor will be poor.
10. How to use these warning signs constructively
Seeing several of these signs does not mean AS9100 is impossible. It means the sequence and scope need to be realistic:
- Stabilize key operational processes and basic quality controls before pursuing certification timelines.
- Start with a focused gap assessment against AS9100 that includes operations, engineering, IT, and supply chain, not just quality.
- Prioritize issues that affect traceability, document control, nonconformance management, and change control ahead of cosmetic fixes.
- Be cautious about large-scale system replacements as the primary path to compliance; in long-lifecycle aerospace environments, these efforts often fail under validation, integration, and downtime constraints.
Used early, these warning signs can help leadership decide when to slow down, sequence work, or invest in foundational capabilities before committing to an AS9100 certification date.
