How often should high-risk aerospace procedures be reviewed?

High-risk aerospace procedures are commonly reviewed at least annually, but there is no single universal interval that applies to every plant, program, customer, or regulator. The correct review frequency is usually the shortest applicable interval set by customer flowdowns, regulatory obligations, the organization’s QMS, internal risk classification, and any change or failure event affecting the process.

For procedures that affect product conformity, safety-critical characteristics, special processes, frozen planning, inspection acceptance, FOD control, torque, bonding, heat treatment, or other high-consequence operations, a calendar review alone is not enough. These procedures should also be reviewed when there is a meaningful trigger.

Typical review triggers

• Engineering drawing, specification, bill of material, or routing changes
• Customer requirement or flowdown changes
• Regulatory, certification basis, or quality system requirement changes
• Nonconformances, escapes, audit findings, complaints, or CAPA activity
• Tooling, equipment, fixture, gage, software, material, or supplier changes
• Process drift, recurring rework, operator confusion, or repeated deviations
• Changes to MES, ERP, PLM, QMS, maintenance, or inspection system logic
• Long periods of non-use, new operators, or loss of experienced personnel

What “review” should mean

A credible review is more than confirming that a document is still present in the system. It should check whether the procedure matches the current approved engineering definition, process capability, equipment condition, inspection plan, training requirements, and actual shop-floor execution.

In brownfield aerospace environments, the procedure may be represented in several places: a controlled document in the QMS, work instructions in MES, routings in ERP, manufacturing planning in PLM, inspection plans in a quality system, and maintenance requirements in an EAM or CMMS. A review that updates only one system can create a traceability problem.

Common failure modes

• The controlled procedure is revised, but the MES or digital work instruction still shows the old step sequence.
• ERP routings are changed for scheduling or costing, but the approved manufacturing planning is not reconciled.
• Operators are trained to a previous revision and no retraining record is created.
• Local redlines, tribal knowledge, or temporary deviations become normal practice without formal approval.
• CAPA closes the immediate issue but does not update the procedure, inspection plan, or training material.
• The review is completed administratively without verifying how the work is actually performed.

For high-risk procedures, many organizations use an annual formal review plus event-driven reviews. Some procedures may require more frequent checks, especially during rate increases, process transfers, new product introduction, poor yield, recurring nonconformance, or after major system changes. Lower-risk procedures may be reviewed on a longer cycle if the QMS permits it and the risk assessment supports it.

The review interval should be documented, justified, and controlled through change management. Approval authority, evidence of review, impacted systems, training impact, effective date, and superseded revisions should be traceable. This does not guarantee audit acceptance or compliance outcomes, but it gives the organization a defensible control structure.