Quality & InspectionFree templatePDF, Excel, Word exportAerospace

AS9100 Quality Manual Template: Policy, KPI and Procedure Examples

This template gives you a ready-to-edit AS9100D quality manual with an example quality policy, a KPI table and a procedure format. Fill in the fields, export to Word, and adapt the wording so it describes how your shop really works.

Fill in

Live preview
Download:

AS9100 Quality Manual Template with Policy and KPI Examples

Quality Manual

Acme Aerospace Machining Ltd 12 Industrial Way, Wichita, KS Document revision: Rev A, 2026-10-21 Aligned to AS9100D / ISO 9001:2015 requirements.

1. Scope of the quality management system (clause 4.3)

CNC machining, anodizing coordination and assembly of aerospace structural components built to customer drawings.

Exclusions: Design and development (clause 8.3) is excluded because the organisation builds to customer-supplied design data and holds no design authority.

The QMS applies to all activities, products and services that affect aerospace customer requirements. Where a requirement cannot be applied, the justification above must not affect product conformity.

2. Quality policy (clause 5.2)

Acme Aerospace Machining Ltd is committed to delivering conforming products on time to aerospace, space and defense customers. We will:

- meet customer, statutory and regulatory requirements, including counterfeit part prevention and product safety awareness; - continually improve the effectiveness of our QMS; - set and review measurable quality objectives each year; - provide the people, equipment and training needed to deliver quality.

Approved by: Sam Rivera, General Manager. Communicated to all employees and reviewed at each management review.

3. Roles and responsibilities (clause 5.3)

Top management: Sam Rivera, General Manager, accountable for QMS effectiveness and resources. Management representative: Jordan Lee, Quality Manager, responsible for QMS maintenance, reporting performance to top management and ensuring awareness of customer requirements, with organisational freedom to resolve quality issues.

4. Process map and interaction

Core processes: contract review, planning and production control, purchasing and supplier control, production and special process control, inspection and FAI, delivery, nonconformance and corrective action, calibration, internal audit and management review. Each process has an owner, inputs, outputs, risks and measures defined in its procedure.

5. Quality objectives and KPI examples (clause 6.2)

KPITargetFrequencyOwner
On-time delivery to customer promise date95%MonthlyOperations manager
Customer returned quality (PPM)Below 500 PPMMonthlyQuality manager
First article inspection first-pass yield90% or higherQuarterlyQuality engineer
Supplier on-time and quality performance90% or higherQuarterlyPurchasing manager
Corrective actions closed on time90% or higherMonthlyQuality manager
Internal audit findings closed by due date100%QuarterlyManagement representative
Calibration overdue items0MonthlyMetrology lead

6. Documented information and procedure format (clause 7.5)

Each procedure uses this structure: 1 Purpose. 2 Scope. 3 References (clauses, customer flowdowns). 4 Definitions. 5 Responsibilities. 6 Method (step by step, who does what, which record is produced). 7 Records and retention. 8 Measures. 9 Revision history.

Write in short imperative sentences, name roles rather than people, and link every step to a record or system transaction so an auditor can see evidence.

7. Operational control and aerospace requirements

Procedures cover: contract review, configuration management, risk management, work transfers, first article inspection to AS9102, production process verification, control of special processes and nonconforming product, counterfeit parts prevention, product safety, foreign object damage prevention, and on-time delivery management.

8. Performance evaluation and improvement

Performance is monitored using the objectives above. Internal audits are planned by process risk and performance, management review inputs follow clause 9.3, and corrective action uses a root cause method such as 8D or 5 Whys, with effectiveness checks.

Approval

Management representative / Date
Top management / Date
Document control / Date

AS9100D does not require a document named 'quality manual', but it requires a documented scope (4.3), the quality policy (5.2) and defined processes. Many organisations keep a manual because auditors and customers expect one. Replace the example text with your own facts, and keep it short; do not copy another company's manual or the standard's wording.

Procedures that match your ERP

Get help mapping your quality procedures to real ERP transactions and reports. Optional.

Optional. The tool and every export work without this. No spam.

How to use the template

Fill the company details, scope, exclusions and targets at the top. The scope should name the products, services and sites covered, and any exclusion should be tied to a requirement that genuinely does not apply, for example design and development if you only build to print. Export to Word and replace example sentences with your own language. Then link each process to a procedure and each KPI to a data source, ideally your ERP, so numbers are produced without manual spreadsheets.

  • Keep the manual under ten pages
  • Reference procedures instead of repeating them
  • Make every KPI traceable to a system report

Quality policy and KPI examples

An AS9100 quality policy must fit the organisation, commit to meeting requirements and to continual improvement, and provide a framework for objectives. Short is better: four or five commitments that employees can remember. KPIs should tie to those commitments. Common aerospace measures are on-time delivery, customer returned PPM, FAI first-pass yield, supplier performance, corrective action closure and calibration compliance. Targets in the table are examples; set yours from your baseline and customer scorecards, not from someone else's manual.

How to write procedures people follow

A procedure that sits in a binder fails the first shop floor audit. Write it from what people do: list the real steps, the role that performs them and the record that proves it. Use the ERP transaction or form name, not a vague description. Add a risk note where a step can fail, since AS9100 expects risk-based thinking. Test the draft by having an operator walk through it. If they say they do it differently, either change the practice or the document, and never leave the gap.

  • One procedure per process, not per clause
  • Name roles and records, not people
  • Review each procedure at internal audit

Common mistakes

The usual errors are copying a template word for word, listing exclusions that are not justified, writing KPIs nobody measures, and building documents that do not match the ERP workflow. Another is forgetting aerospace-specific items such as counterfeit parts prevention, product safety, work transfer and FOD control. Keep customer flowdowns in a separate register so the manual does not become outdated.

Frequently Asked Questions

Does AS9100D require a quality manual?

No document with that name is mandatory in AS9100D, but you must keep documented information on the QMS scope, the quality policy and objectives, and the process descriptions. Most organisations still keep a short manual because customers and auditors expect one place to see them.

What is a good AS9100 quality policy example?

A good policy is short and specific: commit to meeting customer and regulatory requirements, deliver on time, prevent counterfeit and nonconforming parts, and improve the QMS continually. Avoid slogans. It must be communicated to staff and available to interested parties.

Which KPIs should an AS9100 shop track?

Typical measures are on-time delivery, customer returned PPM, FAI first-pass yield, supplier quality and delivery, corrective action closure rate, internal audit closure and calibration compliance. Pick measures that you can pull automatically from your ERP and that link to customer scorecards.

How long should the manual be?

Short is better. Eight to fifteen pages is common, with detail held in procedures. The manual should state scope, policy, roles, process map and how the QMS meets the standard, then refer to procedures for method.

If you want KPIs, procedures and audit answers drawn directly from your ERP and quality records, Netray can build a private AI layer that works inside your own network.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

TermsAS9100