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.
