Connect981 – Content Dev

RSC Topic: Audit Readiness & Evidence Management

Ongoing audit-proof documentation, approvals, and revision histories.

  • What are typical OEM expectations for supplier AS9100 certification?

    Typical OEM expectations around AS9100 fall into a few patterns, but there is no universal rule. What is “required” depends on the OEM, the specific program or prime contractor, the part criticality, and whether you are a direct supplier or a sub-tier.

    1. Common OEM patterns for AS9100 expectations

    Across large aerospace OEMs and primes, you will usually see one or more of these patterns in supplier requirements:

    • AS9100 required for production & special processes: For hardware, assemblies, and special processes (heat treat, coatings, NDT, etc.), AS9100 certification from an accredited CB is often a baseline requirement for approved supplier status.
    • AS9100 strongly preferred, ISO 9001 sometimes accepted: Some OEMs will accept ISO 9001 with additional controls (more incoming inspection, higher audit frequency, limited scope of work) for lower-risk commodities or early-stage suppliers.
    • Design-responsible work usually requires AS9100: If you hold design authority, do significant engineering changes, or are a build-to-spec supplier, AS9100 (or equivalent aerospace QMS standard) is typically non-negotiable.
    • Service and MRO suppliers: For repair and overhaul, AS9110 or OEM-specific repair station approvals may be required in addition to (or instead of) AS9100.
    • Distributor and stockist expectations: Distributors may be expected to hold AS9120, but some OEMs accept AS9100 or ISO 9001 with additional traceability and counterfeit-part controls.

    These expectations are normally written into the OEM’s supplier quality manual, purchase order quality clauses, and supplier approval criteria. They are often flowed down from customer or regulatory requirements on specific programs.

    2. Where AS9100 is typically non-negotiable

    AS9100 certification (or an equivalent aerospace QMS standard) is most commonly treated as mandatory in these situations:

    • Flight-critical or safety-critical components, including structures, control surfaces, critical fasteners, and engine/hot section hardware.
    • Special process providers where OEMs must demonstrate control of process quality, traceability, and personnel qualification.
    • Design-responsible or build-to-spec suppliers contributing to type design or major design changes.
    • Key or single-source suppliers on certified or defense programs where risk and oversight expectations are higher.

    Even here, OEMs sometimes grant temporary or limited approvals to non-certified suppliers when there is no immediate alternative, but these are normally tied to:

    • Formal corrective actions and QMS upgrades.
    • Defined timelines for achieving AS9100 certification.
    • Increased OEM surveillance and more restrictive scopes of work.

    3. Where OEMs may allow alternatives

    In some cases, OEMs will accept alternatives to full AS9100 certification, with additional controls:

    • ISO 9001 with enhanced controls: Often used for non-critical hardware, build-to-print machining, or indirect materials. This usually comes with more incoming inspection, tighter lot acceptance criteria, and higher audit frequency.
    • OEM audits in lieu of certification: Small or niche suppliers may be allowed to operate without a formal AS9100 certificate if they pass an OEM QMS audit and accept limited approval or probationary status.
    • Program- or customer-specific carve-outs: Some defense or space programs allow specific supplier sets with their own approval rules; in those cases, program control plans and data requirements can matter as much as core certification.

    None of these alternatives remove the requirement to actually implement effective processes. OEMs still expect documented procedures, risk-based thinking, configuration control, and robust nonconformance management, regardless of the certificate on the wall.

    4. How OEMs actually evaluate suppliers beyond the certificate

    Even when AS9100 is listed as a requirement, most OEMs treat it as necessary but not sufficient. They typically look at:

    • Audit results and objective evidence: Internal audits, OEM/prime audits, and how well your processes are implemented versus just documented.
    • Nonconformance, escapes, and RCCA depth: The strength of your 8D/RCCA, containment speed, and evidence of systematic fixes.
    • Traceability and configuration control: Ability to show complete build history, revision control, and change management tied to engineering and planning systems.
    • Integration with existing systems: How your QMS and production systems coexist with legacy ERP, MES, PLM, and customer-facing portals and whether that causes data gaps.
    • Responsiveness and stability: Capacity, lead-time adherence, supplier OTD, and how you manage changes and disruptions.

    For brownfield plants with mixed systems, OEMs are very aware that AS9100-certified suppliers can still have fragmented processes, manual travelers, and weak data integrity. Certification is one input into risk classification, not a guarantee.

    5. Tradeoffs and risks for both OEMs and suppliers

    From the OEM’s perspective:

    • Requiring AS9100 across the board simplifies policy but can shrink the supplier pool, limit innovation, and create capacity constraints.
    • Allowing non-certified suppliers can increase supply options but adds audit load, qualification burden, and escape risk.

    From the supplier’s perspective:

    • Achieving AS9100 opens access to more OEMs and higher-value work but requires investment, ongoing internal audits, and disciplined change control.
    • Staying non-certified may be viable in niche or low-risk areas but constrains growth and can keep you in “high-surveillance” status with customers.

    In long-lifecycle aerospace programs, OEMs are cautious about swapping suppliers simply for certification reasons because re-qualification, FAI/AS9102 updates, and potential configuration changes carry cost, downtime risk, and documentation overhead. That is why you often see conditional approvals and phased AS9100 adoption expectations rather than abrupt cutoffs.

    6. Practical guidance if you are a supplier

    If you are trying to understand what a specific OEM expects, you should:

    • Review the OEM’s supplier quality manual and purchase order quality clauses for explicit AS9100/AS9110/AS9120 language.
    • Clarify with the OEM supplier quality engineer (SQE) how expectations vary by commodity, part criticality, and program.
    • Ask whether ISO 9001 plus OEM audit is acceptable short term while you pursue AS9100.
    • Plan QMS upgrades with realistic timelines, accounting for validation, system integration, and documentation updates across ERP, MES, and PLM, not just the certification audit.

    AS9100 certification is widely expected for serious participation in aerospace supply chains, especially on critical work, but it is only one component of how OEMs assess risk, approve suppliers, and maintain ongoing oversight.

  • How do you prove characteristic accountability during an audit?

    Proving characteristic accountability means demonstrating that every required characteristic from a drawing or specification is traced to a specific operation, inspection, and result, with no gaps. Auditors are looking for evidence that you know where each characteristic is made, where it is verified, and how nonconformities are handled, under effective document control.

    1. Start from the source: requirements and ballooning

    Most audits begin with the design or customer requirement:

    • Current, approved drawing or specification under document control.
    • Ballooned drawing or characteristics map (for FAI/AS9102 and similar contexts).
    • Characteristic list (CL) or index linking each balloon/ID to a requirement (dimension, note, spec, KPC/CTQ, etc.).

    To prove accountability, you must show that every characteristic on that list is accounted for in your routing, work instructions, or inspection plan. Any missing or ambiguous mapping is a typical audit finding.

    2. Map each characteristic to an operation and method

    The next expectation is a clear link from characteristic to process step:

    • Routing or traveler that lists operations where the characteristic is created or affected (e.g., machining, heat treat, coating, assembly).
    • Work instructions or control plans identifying how the characteristic is produced and controlled (e.g., tooling, fixturing, SPC, special process controls).
    • Inspection plan that shows how and where each characteristic is verified (100% vs sample, in-process vs final, gage type, method).

    For an auditor, characteristic accountability is often tested by picking a balloon number at random and asking you to show, without gaps:

    • Where in the routing it is made/affected.
    • Which work instruction step or control addresses it.
    • Where the inspection or verification is planned and recorded.

    3. Provide objective evidence: inspection and test records

    Traceability requires objective records, not just plans. Typical evidence includes:

    • FAI forms (e.g., AS9102 Form 3), linked to ballooned characteristics.
    • In-process and final inspection reports tied to specific operations.
    • Electronic inspection data (CMM output, SPC charts) with clear characteristic IDs.
    • Gage IDs, calibration status, and operator signoffs for each measurement step.

    To prove accountability, the record must allow you to answer, for any characteristic:

    • Who inspected it (or what system did the check).
    • When it was checked (lot, work order, date/time).
    • What the result was (pass/fail, measured value).
    • What happened when it did not meet requirements (NCR/MRB, disposition, rework).

    4. Show nonconformance and disposition linkage

    Auditors will also test accountability with defects:

    • Nonconformance records that reference the characteristic ID, drawing balloon, or requirement.
    • MRB and disposition records (use-as-is, repair, scrap, rework) tied to the specific work order / serials.
    • Evidence that re-inspection or validation occurred after rework/repair.

    If you cannot map a nonconformance back to a specific characteristic and forward to the affected units, your characteristic accountability will be considered weak.

    5. Maintain configuration control and revision traceability

    In regulated and aerospace environments, auditors also expect you to prove which requirements applied at the time of manufacture:

    • Document control showing which drawing/spec revision was active for each lot or serial number.
    • Change control records for when characteristics were added, removed, or reclassified (e.g., KPC, safety-critical).
    • Updated ballooning and characteristic lists when the design or spec changes.

    Without configuration control, you might have good inspection records that no longer match the current drawing, which undermines your evidence during an audit.

    6. Digital vs paper: brownfield system realities

    Most plants have mixed systems: ERP, MES, PLM, QMS, plus spreadsheets and paper. Auditors will care less about whether it is digital or paper and more about whether the links are:

    • Complete: no orphan characteristics with no assigned control or inspection.
    • Consistent: IDs match between drawing, plans, and records.
    • Traceable: they can follow a characteristic from requirement to result quickly.
    • Controlled: revisions and changes are documented and approved.

    If you use multiple systems (common in brownfield environments), you will need a clear integration or at least a documented cross-reference to show, for example:

    • Drawing/balloon numbers from PLM linked to operation and inspection steps in MES/ERP.
    • Inspection results in an SPC or CMM system mapped back to the same characteristic IDs.
    • NCR records in QMS referencing the same characteristic codes and work orders.

    Full system replacement purely to improve characteristic accountability is rarely practical in aerospace-grade contexts due to validation effort, qualification, integration risk, and downtime. Incremental improvements (e.g., a digital inspection layer or better characteristic mapping tools) are usually more realistic and auditable if implemented under change control.

    7. Common audit failure modes for characteristic accountability

    Typical gaps that auditors flag include:

    • Characteristics on the drawing that are missing from control/inspection plans.
    • Balloon numbers that do not match between the drawing, FAI, and inspection sheets.
    • Special / safety-critical / key characteristics not clearly identified or treated differently.
    • Inspection records that show generic feature descriptions without a clear link to the characteristic ID.
    • Reworked characteristics without evidence of re-inspection and acceptance.
    • No evidence of which revision of the drawing/spec was used for a given batch.

    8. Practical steps to strengthen your evidence before an audit

    To improve your ability to prove characteristic accountability:

    • Perform an internal review where you pick random characteristics and walk the full chain: drawing → characteristic list → routing/operation → work instruction → inspection plan → inspection record → NCR (if any).
    • Standardize characteristic IDs and ensure they are used consistently across all systems.
    • Ensure FAI/AS9102 packages are complete, with clear balloon-to-result mapping, and kept accessible.
    • Close gaps where certain notes, surface finishes, or specification references are not explicitly inspected or controlled.
    • Put changes under formal change control, including updates to ballooning, CLs, travelers, and inspection plans.

    The goal is that, when an auditor points to any characteristic, you can show a clear, documented, and controlled path from requirement to evidence without scrambling across multiple systems or relying on tribal knowledge.

  • How should FAIRs be linked to serialized parts in an aerospace ERP or MES?

    They should be linked indirectly first, and directly only where the manufacturing context justifies it.

    In practice, a FAIR is usually evidence that a part revision and its approved manufacturing process were demonstrated under a defined configuration. That means the primary link should normally be to the part number, revision, site or work center context, routing or process version where relevant, and the work order, lot, or first production run that generated the FAIR evidence. Serialized units should then inherit that relationship through genealogy and as-built records, rather than each serial number carrying a standalone FAIR record as if the FAIR were unique to that unit.

    If you attach FAIRs directly to every serialized part with no effectivity logic, you usually create duplication, confusion during revision changes, and weak auditability. If you never associate serialized units to the FAIR context at all, you lose traceability when someone asks which FAIR supported a shipped serial number and whether later process or design changes broke that linkage.

    Recommended linkage model

    • Link the FAIR record to the part number and revision.

    • Link it to the manufacturing definition in effect at the time, such as routing version, operation set, inspection plan, tooling set, or approved method, if your systems can represent that cleanly.

    • Link it to the originating production context, typically work order, traveler, batch, or the first serialized unit or units produced under that configuration.

    • Store effectivity dates or change-state boundaries so the system can determine when the FAIR is valid, superseded, or potentially impacted.

    • Link each serialized part to its as-built genealogy, which should include the work order, operation history, material lots, inspection results, and revision state. That genealogy is what lets you infer which FAIR package applies.

    Where a customer, internal quality process, or system design requires a direct serial-level pointer, use a reference link from the serial record to the governing FAIR identifier. But that serial-level link should still point back to a controlled FAIR object with revision and effectivity, not to a loose document attachment.

    What the ERP or MES should actually hold

    At minimum, the combined ERP and MES landscape should be able to answer these questions reliably:

    • Which FAIR package supports this part number and revision?

    • Which work order, lot, or first-run serials generated the FAIR?

    • Which serialized units were built under the same approved configuration?

    • What change events would require review, partial update, or new first article activity?

    • Can the FAIR references be traced to the exact inspection results, material certs, and process records used as evidence?

    If the system cannot answer those questions without manual reconstruction from PDFs, shared drives, and tribal knowledge, the linkage is too weak for a regulated aerospace environment.

    Direct serial linkage is useful in some cases

    Direct linkage at the serialized-part level can make sense when:

    • The first article was executed on one or a small number of specific serial numbers and those units are important as reference builds.

    • The product has highly individualized configuration, making lot or family-based inheritance unreliable.

    • Customer requirements or internal procedures expect a serial-level evidence chain.

    • The ERP or MES supports serial effectivity and controlled document associations well enough to avoid duplicate maintenance.

    Even then, the FAIR should still be managed as a controlled quality object with status, supersession, and change history. A plain file attached to a serial record is usually not enough.

    Brownfield reality

    In many aerospace plants, ERP owns the item, revision, order, and serial master while MES, QMS, or a separate FAI tool holds the execution details and FAIR package. In that case, do not force one system to become the source of truth for everything unless you are prepared for significant revalidation, migration effort, and disruption.

    A more durable pattern is:

    • ERP holds the serialized item master and order context.

    • MES holds execution, genealogy, and inspection transactions.

    • QMS or FAI software holds the FAIR object and approval workflow.

    • Integration links them through stable identifiers such as part number, revision, work order, operation, lot, serial number, and FAIR ID.

    This is less elegant than a single-platform model, but it is often more realistic in qualified environments with legacy systems, limited downtime windows, and long asset lifecycles. Full replacement strategies often fail here because the qualification burden, validation cost, integration complexity, and operational risk are higher than expected.

    Common failure modes

    • Using document attachments instead of controlled object relationships.

    • No revision or effectivity model, so obsolete FAIRs still appear valid.

    • Serial numbers exist in ERP, but execution evidence sits in MES with no reliable key mapping.

    • Partial FAI, delta FAI, or process-change triggers are managed outside the system and never reflected in linkage status.

    • Operators or quality staff manually enter FAIR references, creating inconsistency across serial records.

    • One FAIR is treated as permanently valid even after tooling, source, routing, or design changes.

    Practical recommendation

    Use a controlled FAIR record linked to part revision and manufacturing context, then relate serialized units through work order and genealogy. Add direct serial references only when needed for effectivity clarity or customer traceability. The best model is the one your ERP, MES, QMS, and document controls can sustain under change control, with validated integrations and clear ownership of master data.

    No single linkage pattern is correct for every plant. The right answer depends on how you manage revisions, serial effectivity, first article triggers, and system interoperability. But as a rule, FAIRs should support serialized traceability through a governed data model, not through ad hoc file attachments or one-off manual links.

  • What MRO records are auditors most likely to request during a Part 145 inspection?

    The short answer is that auditors usually start with the records that let them reconstruct what work was done, who did it, what data and parts were used, what inspections occurred, and who approved return to service or maintenance release. They are generally looking for traceability, record completeness, and evidence that your documented system matches actual practice.

    The exact records requested vary by authority, ratings, capabilities, product types, subcontracting model, and any prior findings. A line station, component shop, engine shop, and avionics repair operation will not all be sampled the same way. But in most Part 145 environments, the records most likely to be requested include:

    • Work package and job records: work orders, task cards, travelers, discrepancy records, inspection steps, sign-offs, dates, and labor entries.

    • Maintenance release or return-to-service records: the completed release documentation and the basis used to support it.

    • Approved maintenance data used for the work: revision-controlled manuals, instructions for continued airworthiness, repair data, engineering authorizations where applicable, and evidence the current version was available at the time of work.

    • Personnel qualification and authorization records: training, recurrent training, certifications where applicable, authorization rosters, and records showing who was permitted to perform, inspect, and approve work.

    • Tooling and test equipment records: calibration status, due dates, out-of-tolerance investigations where relevant, and evidence the equipment used was controlled.

    • Parts and material traceability records: receiving inspection, shelf-life control where relevant, batch or serial traceability, source documentation, and segregation of serviceable versus unserviceable material.

    • Component history and serialized records: removal/installation history, life-limited status where relevant, prior maintenance history available to the station, and tag or status documentation.

    • Nonconformance, rework, and corrective action records: discrepancy disposition, repair versus scrap decisions, concession or deviation control where allowed by your system, and evidence that corrective actions were implemented and closed.

    • Contract review and customer authorization records: evidence the work performed matched approved capability, customer scope, and any accepted limitations.

    • Supplier and subcontract process records: outside processing approvals, supplier controls, incoming acceptance, and how outsourced steps were traced back into the maintenance record.

    • Manuals, procedures, and change control records: current repair station manual procedures, revisions, distribution control, and evidence that changes were reviewed and implemented in a controlled way.

    • Training, occurrence, and internal oversight records: internal audits, remedial training, incident follow-up, and management actions tied to prior findings.

    What auditors usually test inside those records

    In practice, auditors are often less interested in the presence of a document than in whether the record set is internally consistent. They will often sample a completed job and test questions like these:

    • Does the work order match the capability and approved data used?

    • Were the people who performed and inspected the work authorized at that time?

    • Was the equipment used in calibration when the work was done?

    • Can installed parts be traced to acceptable source and receiving records?

    • Do discrepancies, rework, and inspections line up with the final release?

    • Do timestamps, signatures, and revisions make sense, or were records completed late or reconstructed?

    • Does the electronic system audit trail support the sequence shown on the paperwork?

    That last point matters more in digital environments. If your MRO records are split across ERP, MRO software, QMS, document control, and spreadsheets, auditors may request records from several systems for one sample event. In brownfield operations, the issue is often not missing data but conflicting data, weak revision control, broken links between systems, or manual transcriptions that are hard to validate.

    What tends to trigger deeper scrutiny

    Certain conditions usually increase the chance that an auditor asks for more records or expands the sample:

    • Missing or illegible sign-offs

    • Backdated or bulk-entered transactions

    • Gaps in serial, batch, or lot traceability

    • Use of superseded maintenance data

    • Expired training or authorization records

    • Calibration lapses or unresolved out-of-tolerance events

    • Manual workarounds outside approved procedure

    • Inconsistent status tagging for parts or assemblies

    • Outsourced processing with weak evidence of control or acceptance

    If those issues exist, the inspection can shift from document sampling to a broader review of your control system. That does not automatically determine an outcome, but it does increase the effort needed to explain and defend the record trail.

    Paper versus digital records

    Electronic records are generally acceptable only to the extent that they are complete, attributable, retrievable, protected from uncontrolled change, and supported by your procedures and actual practice. A digital system does not reduce scrutiny by itself. In some shops it improves traceability; in others it exposes integration debt that paper had been hiding.

    Full replacement of legacy systems is often not the practical answer in a regulated MRO environment. Many organizations run mixed platforms because replacing ERP, MRO, QMS, and document control systems at once creates qualification burden, validation cost, downtime risk, retraining effort, and new traceability gaps during transition. A more realistic approach is usually to tighten evidence trails across existing systems, define system-of-record ownership clearly, and control handoffs and change management.

    How to prepare for likely requests

    A useful way to prepare is to pick several closed work orders and verify that a reviewer can move from intake through execution to release without asking for undocumented tribal knowledge. If that cannot be done quickly, your issue is usually retrieval discipline, integration quality, or record governance rather than lack of software.

    At minimum, be ready to produce a coherent sample package showing:

    • the initiating work scope and discrepancy

    • the approved data used and its revision status

    • personnel authorization and training status

    • tooling and test equipment control

    • parts and material traceability

    • inspection and rework evidence

    • the final release decision and supporting sign-offs

    No single checklist guarantees what an auditor will ask for, because surveillance focus and sampling differ. But if your organization can consistently produce those record sets, with clear traceability and controlled changes, you are usually prepared for the most common Part 145 inspection requests.

  • Do organizations have transition periods between AS9100 revisions?

    Yes. When AS9100 is revised, there is normally a defined transition period, but it is not open-ended and it is controlled by IAQG and the accredited certification bodies, not by individual organizations.

    How AS9100 transition periods work

    For each new revision of AS9100 (e.g., from Rev C to Rev D), IAQG and accreditation bodies publish:

    • A date when the new revision is released and becomes auditable.
    • A start date when certification bodies may begin issuing certificates to the new revision.
    • A deadline after which certificates to the previous revision are no longer valid.

    Within this window, organizations are expected to:

    • Perform a gap assessment against the new revision.
    • Update their QMS processes, documented information, and quality manual.
    • Implement required changes on the shop floor and in supporting functions.
    • Train relevant personnel and be able to demonstrate competence.
    • Accumulate enough operational evidence to show effective implementation during an audit.

    What is and is not flexible

    Some aspects are fixed at the scheme level:

    • Deadlines: The transition deadline is set by IAQG and accreditation bodies. After that date, your old-revision certificate cannot be maintained.
    • Audit expectations: Certification bodies must audit against the new revision after defined cutover points.

    Some aspects can vary:

    • Audit scheduling: Your specific transition audit may be aligned with a surveillance or recertification audit, subject to your certification body’s rules and capacity.
    • Transition approach: How you phase changes across plants, product lines, or business units is up to you, as long as you can show effective implementation by the audit.

    Organizations should not assume that a long informal grace period exists beyond the published transition dates. Missing the formal deadline can result in suspension or lapse of certification.

    Implications for brownfield and regulated environments

    For aerospace and defense manufacturers with established MES, ERP, PLM, and legacy QMS tools, transitioning between AS9100 revisions usually means:

    • Updating document control rules, records retention, and evidence trails across multiple systems.
    • Adjusting audit trails, logs, and approvals to align with new or clarified requirements.
    • Revising procedures and work instructions in parallel with ongoing production to avoid downtime.
    • Coordinating changes with customer and regulatory requirements where they reference specific AS9100 clauses.

    Because these environments are highly validated and integrated, a full, big-bang replacement of systems during a revision transition is rarely practical. Most organizations layer incremental changes on top of existing infrastructure, with strong change control and impact assessment, to avoid re-qualification of entire stacks.

    Practical steps during a transition period

    Typical activities during an AS9100 transition window include:

    • Formal gap analysis against the new revision, with documented actions and owners.
    • Change-controlled updates to QMS documentation and linked procedures/work instructions.
    • Training plans and records to show personnel understand the revised requirements.
    • Internal audits targeted at new/changed clauses to generate objective evidence.
    • Risk assessment of any system or process changes introduced to meet the new revision.

    The level of effort and risk will depend heavily on existing process maturity, configuration management discipline, and how tightly your shop-floor and back-office systems are integrated.

  • What is the difference between Stage 1 and Stage 2 ISO 9001 audits?

    Stage 1 and Stage 2 ISO 9001 audits are two distinct steps in initial certification (and sometimes major scope changes), each with a different purpose and level of depth.

    Purpose of Stage 1

    Stage 1 is a readiness and adequacy review. The focus is on whether your quality management system (QMS) is designed and established well enough to proceed to Stage 2.

    Typical Stage 1 objectives include:

    • Confirming your scope, sites, products/services, and key processes.
    • Reviewing QMS documentation and structure (policies, procedures, process maps, documented information).
    • Checking that mandatory ISO 9001 requirements are addressed on paper and in your system design.
    • Assessing QMS implementation status and readiness for a full effectiveness audit.
    • Understanding your process landscape, including outsourced processes and critical suppliers.
    • Identifying areas where nonconformities or significant gaps are likely at Stage 2.

    Stage 1 often includes limited on-site presence or can be performed remotely, depending on the certification body and your risk profile. It is not a pass/fail certification decision, but if the gaps are severe, the auditor may recommend delaying Stage 2.

    Focus and depth in Stage 1

    Stage 1 is usually higher level and more document- and planning-focused:

    • Sampling is light; the auditor is trying to understand your system design and maturity, not prove full effectiveness.
    • They may walk through a small number of processes to verify that the QMS exists beyond documentation.
    • They look at how you manage documented information, high-level risk and opportunity, quality objectives, and the management review concept and schedule.
    • In brownfield environments, they often examine how ISO 9001 requirements are overlaid on legacy MES, ERP, PLM, and QMS tools.

    Outputs from Stage 1 typically include:

    • A list of concerns, potential nonconformities, and areas needing clarification before Stage 2.
    • Confirmation (or adjustment) of audit time, sites, and logistics for Stage 2.
    • Recommendations on whether your QMS is ready to move forward.

    Purpose of Stage 2

    Stage 2 is the full certification audit. The focus is on verifying that your QMS is implemented, used, and effective across the organization.

    Typical Stage 2 objectives include:

    • Confirming that processes operate as described in your QMS documentation.
    • Verifying that employees follow procedures and understand their responsibilities.
    • Checking that required records exist, are controlled, and provide traceable evidence.
    • Evaluating process performance, monitoring, measurement, and improvement activities.
    • Reviewing internal audit and management review outputs and follow-up.
    • Assessing how nonconformities, corrective actions, and risks are managed.

    The outcome of Stage 2 (including any nonconformities and your corrective actions) is what the certification body uses to decide whether to recommend ISO 9001 certification.

    Focus and depth in Stage 2

    Stage 2 is on-site (except in very specific circumstances) and is much more detailed:

    • Auditors trace requirements across functions: from customer and regulatory requirements, through design, planning, purchasing, manufacturing, inspection, delivery, and post-delivery.
    • They sample actual jobs, work orders, batches, and records to test traceability, process control, and evidence integrity.
    • They look at how legacy systems (MES/ERP/PLM/QMS, paper travelers, spreadsheets) are actually used, and whether controls compensate for known system limitations.
    • They probe effectiveness: not just that a procedure exists, but whether the process achieves planned results and is improved when it does not.

    Stage 2 generates formal nonconformities (major and minor), observations, and opportunities for improvement. Certification is only possible after acceptable closure of major nonconformities.

    Key differences in practical terms

    In operational and manufacturing settings, especially regulated ones, the differences can be summarized as:

    • Stage 1: Are you ready?
      • Focus: System design, documentation, scope, readiness.
      • Evidence: Procedures, policies, process maps, some early records.
      • Outcome: Go / delay on Stage 2, with a list of gaps to address.
    • Stage 2: Are you doing it and is it working?
      • Focus: Implementation, use in daily operations, and effectiveness.
      • Evidence: Real production records, NCR/CAPA data, internal audits, management reviews, training records, change control, system logs.
      • Outcome: Certification recommendation, subject to nonconformity closure.

    Dependencies and constraints in regulated manufacturing

    How Stage 1 and Stage 2 play out depends heavily on your environment:

    • System landscape: If you run mixed legacy systems and paper travelers, auditors will expect clear control of interfaces, data handoffs, and revision control. Weakness here may not block Stage 1, but will cause issues at Stage 2.
    • Validation burden: In aerospace or other regulated sectors, you are often layering ISO 9001 on top of existing AS9100, customer, or regulatory requirements. Auditors will look for alignment rather than full system replacement. Attempting to swap out MES/ERP/QMS entirely just before certification often introduces more risk than benefit.
    • Evidence maturity: For Stage 2, you need enough history of use: completed work orders, NCRs, corrective actions, internal audits, and management reviews. If those are thin or ad hoc, the auditor may delay certification even if documentation looks strong.
    • Change control and traceability: Where changes to processes, software, or tooling require qualification or re-validation, auditors will look closely at how you control such changes across Stage 1 and Stage 2. Aggressive last-minute changes to core systems before Stage 2 increase audit risk.

    Does a successful Stage 1 guarantee Stage 2 success?

    No. A clean Stage 1 report does not guarantee you will pass Stage 2 or obtain certification.

    • Stage 1 can miss implementation problems that only show up when auditors start sampling actual production records and following real jobs.
    • Weak internal audits and superficial management reviews might not be fully visible until Stage 2.
    • If you make significant process or system changes between Stage 1 and Stage 2 (new MES, new routing structures, reorganized quality reporting), auditors will expect evidence that those changes are controlled and effective.

    For leadership teams, the practical implication is that Stage 1 is a checkpoint on QMS design and readiness, while Stage 2 is the true test of operational discipline and evidence in your real, often brownfield, environment.

  • What information do regulators expect to see in MRO traceability records?

    In general, regulators expect MRO traceability records to let an auditor or investigator reconstruct the maintenance event from authorization through release. The record should make it possible to answer a basic set of questions: what item was worked on, why it was worked on, what was done, who did it, what data and parts were used, what inspections or tests were completed, what nonconformances or deviations occurred, and who approved the final disposition.

    The exact record set depends on the aircraft, component, jurisdiction, certificate or approval basis, customer requirements, and whether the work is line, base, shop, or component repair. There is no single universal template that satisfies every MRO context. Record sufficiency also depends on whether the work scope involves life-limited parts, critical parts, serialized assemblies, outsourced processes, software loads, calibration-sensitive measurements, or repair schemes that require approved data.

    What those records usually need to show

    • Asset and configuration identity: aircraft tail number, engine or module identifier, part number, serial number, assembly position, and current configuration relevant to the work performed.
    • Work authorization: work order, maintenance task, job card, discrepancy, service request, engineering instruction, or other approved trigger for the work.
    • Reason for maintenance: scheduled task, defect, inspection finding, service bulletin, airworthiness directive, removal cause, condition monitoring result, or customer request.
    • Applicable technical data: manual, task card, repair instruction, drawing, service bulletin, engineering order, and the exact revision or effective version used at the time of execution.
    • Execution details: what maintenance, overhaul, repair, inspection, test, cleaning, or modification was actually performed, including dates and, where required, times or usage values.
    • Personnel traceability: who performed the work, who inspected it, who certified it, and the basis of their authorization or qualification within the approved system.
    • Parts and material genealogy: installed and removed parts, serial and batch or lot data where applicable, alternates or substitutes used, shelf-life sensitive materials, and evidence of part eligibility.
    • Tooling and measurement evidence: critical tools, calibrated equipment, test sets, torque tools, measurement results, and calibration status where those affect acceptability of the work.
    • Inspection and test results: dimensional results, functional checks, NDT outcomes, acceptance criteria, pass or fail status, and any retest or rework history.
    • Nonconformance and disposition: defects found, damage mapping, deviations, scrap decisions, repair approvals, rework loops, concession or disposition references, and closure evidence.
    • Outside processing and supplier activity: subcontracted operations, certificates or reports received, receiving verification, and linkage between supplier records and the parent work order.
    • Release evidence: the final maintenance release, return-to-service statement, authorized signoff, and supporting basis for airworthiness or serviceability within the applicable framework.

    What regulators tend to care about most

    In practice, regulators and customers usually focus less on whether the record is paper or electronic and more on whether it is complete, attributable, legible, contemporaneous, controlled, and retrievable. A polished digital interface does not fix weak evidence. If record links are broken across ERP, MRO, QMS, document control, and supplier portals, the organization may still struggle to prove what happened.

    Common stress points include missing serial number linkage, unclear part eligibility, inability to show which procedure revision was followed, incomplete signoffs, poor control of rework history, and weak linkage between removed parts, installed parts, and final configuration. In an investigation, a gap that seems minor operationally can become significant if it prevents reconstruction of the event chain.

    Electronic records are acceptable, but only with controls

    Yes, electronic traceability records are widely used, but regulators generally expect the same evidentiary quality they would expect from paper, plus controls around access, audit trails, version control, data integrity, retention, and change management. If timestamps can be edited, user attribution is weak, or records can be overwritten without history, the system may not support the required level of trust.

    This is where brownfield realities matter. Many MRO organizations run a mix of legacy MRO software, ERP, QMS, spreadsheet-based tracking, scanned forms, and supplier email traffic. That can work, but only if the record chain is intentionally connected and governed. Full replacement is often not realistic in regulated, long-lifecycle environments because qualification burden, validation effort, downtime risk, integration complexity, and historical data migration all carry real operational risk. In many cases, a controlled coexistence model is more practical than a rip-and-replace program.

    What a defensible record set looks like

    A defensible MRO traceability record usually shows a closed chain from inducted asset to released asset or component, with each major event linked to approved data, accountable personnel, material usage, inspection evidence, and final disposition. It should also be possible to retrieve supporting records quickly, including prior maintenance history where that history affects current disposition.

    If your current process relies on multiple systems, the practical question is not whether every record lives in one application. The practical question is whether the organization can consistently produce a coherent, time-ordered evidence trail under audit or investigation without manual reconstruction that introduces doubt or delay.

    So the short answer is: regulators expect enough detail to prove identity, authorization, execution, conformity, and release, with reliable linkage across people, parts, procedures, inspections, and approvals. The exact fields vary, but the expectation for traceability, record integrity, and retrievability does not go away.