# AS9100 Document Control Procedure Example with KPIs and Audit Plan

> Source: https://netray.co/tools/as9100-document-control-procedure-and-template-pack
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

One editable AS9100 pack: document control procedure, process interaction table, KPI list, audit plan and schedule, with sample wording you can adapt.

## Category

aerospace-defense

## Industry

Aerospace

## Audience

- Quality manager
- Document controller
- Internal auditor

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Aerospace Components Ltd

#### Procedure number

**Key:** doc_no

**Type:** text

**Default:** QP-4.2-01

#### Revision

**Key:** rev

**Type:** text

**Default:** C

#### Process owner

**Key:** owner

**Type:** text

**Default:** Quality Manager

#### Document system

**Key:** system

**Type:** text

**Default:** ERP document module and controlled network drive

#### Record retention period

**Key:** retention

**Type:** text

**Default:** 10 years after last delivery, or longer if the customer requires

#### Audit start date

**Key:** audit_date

**Type:** date

**Default:** 2026-11-09

#### Lead auditor

**Key:** auditor

**Type:** text

**Default:** A. Singh

#### Audit scope

**Key:** scope

**Type:** text

**Default:** Contract review, production control, special processes, inspection

**Blocks:**

#### Document Control Procedure {{doc_no}} Rev {{rev}}

**Body:** Company: {{company}}
Process owner: {{owner}}

#### 1. Purpose and scope

**Body:** This procedure defines how {{company}} creates, approves, issues, changes, distributes, protects and retires documents of the quality management system, including documents of external origin such as customer drawings, specifications and standards. It applies to all sites and processes in the certified scope.

#### 2. Responsibilities

**Body:** The process owner ({{owner}}) approves this procedure and appoints the document controller. Process owners approve documents in their area. All employees use only the current released revision.

#### 3. Method

**Body:** a) Identification: each document has a number, title, revision, date and approver.
b) Review and approval: documents are reviewed for adequacy and approved before release.
c) Distribution: controlled copies are made available in {{system}}. Printed copies are uncontrolled unless stamped.
d) Changes: a change request describes the change; the revision history records what changed and why. Obsolete versions are removed from points of use and, if retained, marked obsolete.
e) External documents: customer and regulatory documents are logged, and revision status is checked when a purchase order or contract is accepted.
f) Records are kept in legible form, protected from loss, with retention of {{retention}}.

#### 4. Process interaction table

**Table:**

**Columns:**

- Process
- Input from
- Output to
- Owner
- Key records

**Rows:**

**0:** Contract review

**1:** Customer

**2:** Planning

**3:** Sales manager

**4:** Reviewed order, risk record

**0:** Planning and scheduling

**1:** Contract review

**2:** Production

**3:** Planner

**4:** Work order, routing

**0:** Purchasing

**1:** Planning

**2:** Receiving

**3:** Buyer

**4:** Approved supplier list, PO flowdown

**0:** Production and special processes

**1:** Planning, purchasing

**2:** Inspection

**3:** Production manager

**4:** Traveler, process records

**0:** Inspection and release

**1:** Production

**2:** Shipping

**3:** Quality manager

**4:** FAI, inspection report, CoC

**0:** Delivery and support

**1:** Inspection

**2:** Customer

**3:** Logistics manager

**4:** Packing list, delivery record

#### 5. KPI list

**Table:**

**Columns:**

- KPI
- Definition
- Target
- Frequency
- Owner

**Rows:**

**0:** On-time delivery

**1:** Lines shipped on or before promise date divided by lines due

**2:** 95%

**3:** Monthly

**4:** Logistics manager

**0:** Quality escapes

**1:** Customer returns per million parts shipped

**2:** Below 500

**3:** Monthly

**4:** Quality manager

**0:** Supplier on-time and quality

**1:** Receipts accepted on time divided by receipts due

**2:** 95%

**3:** Monthly

**4:** Buyer

**0:** First pass yield

**1:** Parts passing inspection first time divided by parts inspected

**2:** 98%

**3:** Weekly

**4:** Production manager

**0:** Corrective action closure

**1:** Corrective actions closed within due date divided by total due

**2:** 90%

**3:** Quarterly

**4:** Quality manager

#### 6. Audit plan

**Body:** Audit start: {{audit_date}}
Lead auditor: {{auditor}}
Scope: {{scope}}
Criteria: AS9100 and company procedures
Method: interviews, record sampling, process observation and trace of at least one order from contract review to delivery.

**Table:**

**Columns:**

- Time
- Process / clause area
- Auditee
- Auditor

**Rows:**

**0:** Day 1 09:00

**1:** Opening meeting, scope, context and risk

**2:** Top management

**3:** {{auditor}}

**0:** Day 1 10:30

**1:** Contract review and customer requirements

**2:** Sales manager

**3:** {{auditor}}

**0:** Day 1 13:30

**1:** Planning, configuration management

**2:** Planner

**3:** {{auditor}}

**0:** Day 2 09:00

**1:** Production, special processes, FAI

**2:** Production manager

**3:** {{auditor}}

**0:** Day 2 13:00

**1:** Purchasing and supplier control, counterfeit parts

**2:** Buyer

**3:** {{auditor}}

**0:** Day 2 15:30

**1:** Closing meeting, findings, action dates

**2:** Top management

**3:** {{auditor}}

**Signatures:**

- Prepared by
- Process owner
- Top management

**Notes:** Sample wording, not a certified procedure. Paraphrase and adapt to your own processes; do not copy clause text from the standard. Allocate audit time by risk and past performance, and confirm requirements with your registrar.

## Content

**Intro:** This pack gives you a working AS9100 document control procedure and the supporting artifacts auditors ask for: a process interaction table, a KPI list and an audit plan with time schedule. Fill in the fields, edit the rows, and export to Word or PDF.

**Sections:**

#### What the document control procedure must cover

**Body:** AS9100 expects documented information to be identified, reviewed, approved, available at points of use, protected and controlled for changes and retention. Aerospace adds specifics: controlling documents of external origin such as customer drawings and specifications, verifying revision status at contract acceptance, and keeping records for the period customers or regulators require. The sample procedure above covers each element in plain language that you can adapt.

**Bullets:**

- Unique identification, revision and approval on every document
- Current revision at point of use, obsolete copies removed or marked
- Customer and regulatory documents logged with revision check
- Records protected, retrievable and retained for a defined period

#### Process interactions and KPIs

**Body:** A process interaction table (often drawn as a turtle diagram or flowchart) shows inputs, outputs, owners and records for each process, which is the quickest way to prove you understand how the system flows. Pair each process with a measurable KPI. Aerospace customers care most about on-time delivery and quality escapes, so start there and add supplier performance, first pass yield and corrective action closure.

#### Building an audit plan that works

**Body:** An internal audit plan lists scope, criteria, method, date and time, auditee and auditor for each session. Schedule high-risk processes more often, such as special processes, and keep auditors independent of the area audited. Trace one real order end to end, because it exposes handoff gaps that process-by-process questions miss. Record evidence, not opinions, and agree finding due dates at the closing meeting.

**Cta:** Netray can connect a private on-prem AI layer to your ERP so on-time delivery, supplier and nonconformance KPIs are calculated from live data rather than assembled by hand.

**Faq:**

#### Is a documented document control procedure mandatory in AS9100?

**Answer:** AS9100 requires control of documented information, but it does not force a specific procedure format. Most registrars and customers expect a written procedure because it is the simplest way to prove the control exists and is followed.

#### What KPIs should an AS9100 company track?

**Answer:** At minimum track on-time delivery and product conformity, then add supplier performance, first pass yield, customer complaints and corrective action closure. Customers often provide their own scorecards, so align definitions with them.

#### How long is a typical AS9100 audit?

**Answer:** Registrars set audit days based on headcount, sites and complexity. A small shop may need two to four days for the initial audit, larger sites more. Internal audits are shorter and spread across the year according to risk.

#### Can I copy the standard's wording into my procedure?

**Answer:** No. The standard is copyrighted. Describe what your company does in your own words and reference the clause number. Auditors want to see your actual practice, not a repeat of the requirement.

## Search terms

as9100 document control procedure example, as9100 quality procedure examples, as9100 interaction of processes diagram, as9100 audit time table, example as9100 audit plan, measurement report according to as9100, as9100 kpis, as9100 audit process best practices

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json