Defence Supplier Corrective Action (CAPA) Management

Overview#

A complete Corrective and Preventive Action lifecycle engine for defence supply chains, replacing spreadsheets and email chains with an auditable, four-eyes-controlled workflow.

Quality assurance managers and procurement officers at defence contractors and government acquisition agencies use this capability to raise, track, and close supplier non-conformance actions against a single source of truth. When a non-conformance is found, a corrective action is opened against the supplier, issued with a gap-free reference number, and driven through a strict, predictable lifecycle until an independent verifier signs it off. Nothing is lost, nothing is editable after the fact, and every state change is recorded with a tamper-evident hash.

The engine closes the loop on procurement risk automatically. The moment an action is opened, the affected supplier is flagged as disqualified so no new work orders can be awarded while the issue is unresolved. Once every open action against that supplier has been verified closed, the disqualification clears on its own. Teams get continuous assurance without manual status meetings, and auditors get an immutable evidence trail they can export on demand.

Key Features#

• Gap-free reference numbering: Every action receives a unique per-organisation, per-year reference in the A-YYYY-NNNN scheme, allocated by an atomic counter so numbers are sequential, never reused, and never skipped, even under concurrent load.

• Enforced lifecycle state machine: Actions move through a directed set of states, OPEN to IN_PROGRESS to PENDING_VERIFICATION to CLOSED, with an early VOID path for cancellations. Illegal jumps are rejected, so a record can never be quietly back-dated or short-circuited.

• Automatic supplier disqualification: Opening an action immediately flags the supplier as disqualified, blocking new work-order awards while the issue is live, with the reason recorded against the originating reference.

• Automatic reinstatement: When the final outstanding action for a supplier is verified closed, the disqualification flag clears on its own, pointing back at the closure that resolved it.

• Four-eyes closure control: The person verifying a closure must differ from both the action owner and the original creator. This separation-of-duties gate is enforced before any write occurs, so a violation leaves no side effects.

• Root cause and evidence capture: Each record holds the finding, root cause, root-cause category, severity, due date, owner, and a list of evidence references, keeping the full investigation context in one place.

• Tamper-evident audit trail: Every operation produces SHA-256 before and after row hashes forwarded to the security monitoring pipeline, giving a verifiable, reconstructable history suitable for regulatory inspection.

• Strict tenant isolation: Every operation is scoped to the calling organisation, and the disqualification side effect always uses the caller's organisation, so actions and their consequences never cross between customers.

Use Cases#

Defence and aerospace quality and procurement teams use corrective action management wherever supplier non-conformance must be tracked to a verified, audit-ready close.

Defence prime contractors#

A quality manager at a prime contractor logs a non-conformance found during incoming inspection of a sub-tier part. The action is raised against the supplier, the supplier is disqualified from new awards automatically, and the action is worked through investigation and remediation until an independent quality lead verifies the fix. The prime keeps a defensible, time-stamped record for every flow-down requirement.

Government acquisition agencies#

A procurement officer at an acquisition agency needs assurance that vendors meet contractual quality obligations before further orders are placed. Open actions automatically gate new work, and the immutable hash-backed trail provides the evidence acquisition auditors require without bespoke reporting.

Aerospace and NATO-aligned suppliers#

A supplier operating under aerospace and NATO quality requirements needs corrective action and root cause analysis records that map cleanly to clause-level obligations. The enforced lifecycle and mandatory verifier step produce records that line up with audit expectations out of the box.

Multi-tier supply chain assurance#

• Quality assurance managers raising and tracking non-conformance actions across many suppliers
• Procurement and contracts officers gating awards on unresolved actions
• Compliance and audit teams exporting evidence for inspections and contract compliance reviews
• Supplier relationship managers monitoring open versus reinstated supplier status

Integration#

The capability is exposed through the platform GraphQL surface, with operations to raise an action, list actions for a supplier, and drive lifecycle transitions, alongside a per-supplier view that surfaces outstanding actions. Each record returns its reference, supplier, status, owner, due date, and evidence so customer systems can present or reconcile it directly.

• GraphQL operations: A customer plugs raising, listing, and transitioning actions into existing quality or procurement portals, so analysts never leave their primary tool. The supplier view exposes outstanding actions inline with supplier records.

• REST and webhooks: Standard authenticated REST endpoints and event notifications let an external quality management or ERP system react to lifecycle changes, for example pausing purchase-order creation when a supplier is flagged.

• OAuth2 and JWT authentication: Access uses OAuth2 bearer tokens with JWT, so customer identity providers and existing single sign-on stay the source of truth, and clearance level travels with the authenticated session.

• SIEM forwarding: Before and after row hashes for every operation are forwarded to the security monitoring pipeline, so a customer's existing log and audit tooling receives a tamper-evident stream with no extra wiring.

• Normalised models: Actions, suppliers, and audit events share consistent, normalised shapes across the platform, so the same supplier and reference identifiers join cleanly to certificate, waiver, and supplier-graph capabilities a customer already uses.

The benefit to the customer is a single, connected record of supplier corrective action that their existing identity, procurement, and audit systems can read from and write to without custom middleware.

Open Standards#

• AS9100D (Aerospace Quality Management Systems): Corrective action is a required element of clause 10.2. The lifecycle, root cause capture, and verified closure align with that obligation for aerospace and defence suppliers.

• AQAP 2110 (NATO Quality Assurance Requirements for Design, Development and Production): Encodes the corrective action and root cause analysis obligations expected of NATO-aligned suppliers, with the mandatory verifier step supporting independent sign-off.

• ISO 9001:2015, clause 10.2 (nonconformity and corrective action): Provides the structural basis for the OPEN, IN_PROGRESS, PENDING_VERIFICATION, and CLOSED lifecycle, ensuring each non-conformance is investigated, acted on, and verified.

• EU RESTRICTED classification marking: The recognised EU classification level is enforced as the minimum clearance for all corrective action operations, so records carry and respect the marking applied to defence supply chain data.

• SHA-256 (FIPS 180-4 secure hash): Before and after row hashes use the SHA-256 standard, giving widely verifiable, tamper-evident integrity for the audit trail.

• OAuth2 and JSON Web Token (JWT): Authentication and clearance propagation follow these widely adopted authorisation and token standards, so existing identity infrastructure interoperates directly.

Security & Compliance#

• Clearance gating: Every operation requires at least EU RESTRICTED clearance, checked at the service layer before any data is read or written. Callers without sufficient clearance are refused.

• Separation of duties: The four-eyes closure control guarantees that no single individual can both own or create an action and sign off its closure, satisfying defence audit expectations without manual workflow configuration.

• Immutable, exportable evidence: SHA-256 before and after hashes on every state change produce a tamper-evident record that can be exported for regulatory inspections and contract compliance reviews, and any alteration after the fact is detectable.

• Consistent side effects: If supplier disqualification cannot be applied when an action is opened, the action is rolled back with a compensating transition, so the system never shows an open action against a supplier that was not flagged.

• Tenant scoping: All reads, writes, and the disqualification side effect are bound to the calling organisation, preventing any cross-customer exposure of supplier or corrective action data.

Last Reviewed: 2026-06-01 / Last Updated: 2026-06-04