IATF 16949 documentation: what you need, what you do not, and how to keep it in step with the line

What documentation does IATF 16949 require?

IATF 16949 documentation is whatever proves that the automotive quality system is defined and running at your site. It builds on the documented information of ISO 9001:2015: the scope, the quality policy, the quality objectives and the information your processes need, plus the records that show conformity. IATF 16949 then adds its own clause on quality management system documentation (7.5.1.1), and the IATF's published FAQs confirm that this documentation must cover the requirements of all your direct customers, including Tier 1 buyers and manufacturers outside the IATF membership. On top of that, each customer's specific requirements can ask for their own documents, formats and retention rules.

In short: less text than most plants expect, and more evidence. A thin, accurate set of documents with a full trail of records behind it passes; a thick manual with gaps on the line does not.

The full list of requirements has its own guide, IATF 16949 requirements explained, and the customer layer is covered in Customer-specific requirements: managing CSRs in your QMS.

Documents and records in an automotive plant

The standard's umbrella term is documented information, and it covers two things that behave differently. A document tells people how the work is to be done: a process description, a control plan, a work instruction, a reaction plan. It changes with the process, and the superseded version leaves the point of use. A record shows what actually happened: a first-off check, a gauge study, a layout inspection result, an 8D report. It is never edited after the event, because an altered record stops being evidence. ISO 9001:2015 expresses the difference as documented information to be maintained (documents) and retained (records).

In a plant the two are tightly linked. The PFMEA identifies the risks, the control plan sets the checks that manage them, the work instruction tells the operator how to carry out those checks, and the check sheet records that it was done. Auditors follow that chain for a sampled part; where a link is out of date, a finding follows.

The documented information IATF 16949 names

The table lists the automotive items most plants must be able to show. It is not the complete standard; it is the part that turns into paper or data.

Daily work adds further records: set-up verification (8.5.1.3), maintenance (8.5.1.5), layout inspection (8.6.2), concessions (8.7.1.1), nonconforming product disposition (8.7.1.7), management review with cost of poor quality (9.3.2.1), and the APQP and PPAP files. The five core tools that generate most of these records are explained in The core tools: APQP, PPAP, FMEA, MSA and SPC explained.

What you do not need

Over-documentation usually grows from four habits.

A procedure for every clause

The standard names a handful of documented processes and leaves the rest to you. Write a procedure where the work is complex, rare, shared across shifts or where a slip reaches the customer. A procedure that restates the standard helps nobody on the line.

A copied manual or template pack

Documents written for another plant describe another plant. A borrowed process map or an invented approval step becomes a nonconformity against your own system.

Customer manuals pasted into your system

Customer requirements must be addressed, not reproduced. A register mapping each requirement to its process, owner and record is far easier to maintain.

Separate binders for the core tools

A PFMEA in one folder, a control plan in another and work instructions on a shared drive drift apart within months. Keep each part family's chain together.

A lean document set for a single plant

For a single-site supplier with a few customers, a workable set looks like this:

• The scope, the quality policy, the objectives with the customer targets they carry, and a process map with a named owner and performance measures for each process.
• A customer requirement register covering every direct customer, reviewed when a customer publishes a revision.
• Short process descriptions for the main processes, plus the documented processes the standard names, such as problem solving and the control of temporary process changes.
• For each part family: the PFMEA, the control plan, work instructions with reaction plans at the point of use, and the PPAP file.
• The competence matrix, the calibration and MSA records, the internal audit programme and reports, the scorecards and the management review record.

Retention periods belong in one place, set by the longest of your customers' rules and the legal requirements of the countries of manufacture and destination, and applied to paper and electronic records alike.

Keeping documents in step with the line

Document control in an automotive plant is really change control. When the process, a gauge or a reaction plan changed, were the PFMEA, control plan and work instruction revised together, did the next shift see the new version, and did the customer need to be told first?

Three disciplines keep the set accurate: link the documents so a change to one flags the others; keep the bypass list and concessions visible at the point of use with an end date; and feed lessons from complaints, field returns and 8D reports back into the FMEAs.

Effivity for IATF 16949: the guide shows how documents, records and the audit programme sit in one place, and IATF 16949 internal audit: system, process and product audits covers how the audit programme tests that the documents match practice.

IATF 16949 documentation: questions buyers ask