ISO 9001 clause 8.5.2: identify outputs and keep their status clear

What clause 8.5.2 requires in practice

This clause is about knowing what each output is and where it stands. The organisation uses suitable means of identification whenever that is needed to ensure conformity of products and services. It also identifies the status of outputs against monitoring and measurement requirements right through production and service provision, so that anyone can tell whether an item or piece of work is awaiting inspection, has passed, or has been rejected.

Where traceability is a requirement, whether set by a customer, a regulation or the organisation itself, the unique identification of outputs must be controlled. Documented information needed to make traceability possible must be available as evidence.

Identification can be a label, a job number, a ticket status, a file version or a batch code. The standard cares that it works for the purpose, not what form it takes.

Make identification suitable for the work

Determine when confusion between outputs could affect conformity. Similar-looking products, customer-specific service cases or different configurations may need clear identification. The appropriate method depends on the process and how people interact with the work.

The standard does not require every output to carry an individual serial number. A suitable identification method may use an order, batch, location or other approach where it meets the need. If unique traceability is required, the arrangement must support that more specific purpose.

Why identification and traceability matter to the business

If an item cannot be identified, it cannot be controlled. Mix-ups send untested or rejected output to customers, and when a problem is found later, poor traceability turns a targeted recall or correction into a costly blanket response. Clear status prevents wasted effort on work that has already been approved and protects against skipped checks. For regulated sectors and demanding customers, demonstrable traceability may be a condition of doing business at all. Auditors often pick a finished item or completed job and trace it backwards through its records, and a smooth trail is one of the most convincing signs of a controlled process.

How to implement clause 8.5.2

Decide where identification genuinely protects conformity, then keep it simple and consistent. Identification should help the people doing the work, so involve them in choosing it. Over-marking everything wastes effort, while under-marking invites confusion. Revisit the approach whenever products, layouts or customer demands change. Keep it practical and brief.

1. Review each delivery process for points where outputs could be confused, mixed or passed on in the wrong condition.
2. Choose an identification method suited to the output, such as labels, markings, reference numbers, system status fields or version control.
3. Define the status categories people use, for example waiting, accepted, rejected or on hold, and where status is displayed.
4. Establish which products, services or customers require traceability and how far back and forward it must reach.
5. Link identifiers to the records that explain materials, people, equipment and checks involved.
6. Test traceability by selecting a completed output and following it through, then correct any broken links.

Evidence an auditor expects for clause 8.5.2

The most persuasive evidence comes from an actual trace exercise performed during the audit. Auditors often ask staff to explain a label or status in their own words, since this shows whether the system works.

• Observation of identification and status marking on items, files or jobs in progress.
• A sample output traced through its records to materials, operators and checks.
• Records showing how nonconforming or on-hold items are kept distinct from accepted ones.
• Interview with a team leader on what happens when an identifier is lost or damaged.

Common nonconformities with clause 8.5.2

Auditors frequently report these weaknesses. All of them undermine the ability to say with confidence what an item is and whether it has passed its checks, which is the entire point of the clause.

• Items waiting for inspection sit alongside accepted ones with nothing to tell them apart.
• A customer requires traceability, yet records cannot connect a delivered item to its inputs.
• Identification is applied inconsistently, so two identical-looking outputs carry different markings.
• Status is updated after the work has moved on, so the record does not reflect reality.

Illustrative manufacturing example: similar items with different status

Illustrative BPO example: a traceable service decision

A hypothetical BPO contract requires the provider to trace a completed processing decision to the customer submission and its relevant review. The team uses unique case references, but copied files sometimes lose the connection with the originating submission.

The organisation controls the identification and maintains the necessary evidence so the required relationship can be followed. It tests retrieval of a completed case and checks whether the relevant submission, processing result and review remain connected. Traceability is required in this example by the service arrangement; ISO 9001 does not impose the same detailed case history on every unrelated service.

Keep monitoring and measurement status visible

People should be able to determine the output's relevant status throughout provision. “Work complete” may be misleading if a required acceptance check is still pending. The method should prevent an unresolved output being mistaken for one that has met the necessary conditions.

Consider changes of location, shift, system or ownership. Status can be lost during a handover even when each team maintains its own records. Review the interface and ensure the receiving process has the information needed to act correctly.

Determine what traceability must enable

Where traceability is a requirement, establish the relationship the organisation needs to follow. It may concern a product, batch, service transaction or other output, depending on the applicable requirement. The necessary documented information should support that purpose.

A unique number is not enough if it cannot be connected with the required evidence. Equally, retaining extensive records without a reliable relationship may make retrieval impossible. Test the arrangement against the actual traceability question the organisation is expected to answer.

Distinguish output traceability from measurement traceability

Clause 8.5.2 concerns outputs. Measurement traceability concerns the basis for confidence in measurement results. A process may need both, but a calibration certificate does not establish which product was measured, and a product identifier does not establish the measurement's reference basis.

Common failures include duplicated identifiers, labels detached from the output and status fields updated without the underlying check. Another is designing a traceability system around available software rather than the requirement it must satisfy. Understand the needed relationship first, then choose a proportionate implementation.

Read the parent production and service guide to connect identification with preservation, release and control of changes.