ISO 9001 clause 8.5.5: manage post-delivery activities

What clause 8.5.5 requires in practice

The customer relationship does not end at delivery. This clause expects the organisation to meet the requirements for post-delivery activities connected with its products and services. To decide how far those activities need to go, five considerations are weighed: statutory and regulatory requirements, undesired consequences that could follow from the products and services, their nature, use and expected lifetime, customer requirements, and customer feedback.

The note gives examples: actions under warranty, contractual obligations such as maintenance, and added services like recycling or final disposal.

The scope is therefore set by risk and commitment rather than by a fixed list. A software supplier may owe patching and support; an equipment maker may owe servicing and spare parts; a service firm may owe follow-up reviews. The organisation decides, with reasons, and then delivers.

Determine the activities that actually apply

Start with applicable statutory and regulatory requirements and the commitments accepted from the customer. Consider the nature of the product or service, its use and intended lifetime, and the possible unwanted consequences associated with it. Customer feedback also matters: a recurring problem after installation may reveal that the current handover or support arrangements are inadequate.

Relevant activities could include warranty work, contracted maintenance or agreed arrangements for recycling and disposal. These are possible applications, not a compulsory package for every organisation. A business should distinguish what it must provide from an optional paid service and from assistance it chooses to offer on a particular occasion.

Make the boundary understandable at contract review and handover. Identify support channels, covered deliverables, responsibilities and escalation routes where those details are relevant. A statement that support is available is not enough if the customer and operations team interpret the coverage differently. Check that external service providers can meet any obligations delegated to them.

Why post-delivery activities matter to the business

What happens after handover often decides whether a customer returns. Prompt, competent support turns a problem into evidence of reliability, while neglected warranty claims or missed maintenance damage trust quickly. Post-delivery work can also be a source of revenue and, through feedback, the best early warning of weaknesses in design or delivery. Failing to anticipate legal duties such as safe disposal or recall handling can bring serious liability. At audit, this clause shows whether the organisation looks beyond shipment and uses what it learns later in the life of its products and services.

How to implement clause 8.5.5

Identify what customers and the law expect after delivery, then build it into normal operations. Check what sales material and proposals promise after delivery, since these statements often create obligations that operations never hear about. Revisit the list when offerings change. Share the findings with management for planning.

1. List the post-delivery commitments in contracts, warranties, regulations and marketing statements for each offering.
2. Consider what could go wrong during use or at end of life, and decide which follow-up actions would reduce that risk.
3. Take account of how long the product or service is expected to remain in use, and what support that lifetime implies.
4. Assign owners and resources for each activity, including any outside providers who help deliver it.
5. Provide customers with a clear route to request support or report issues, and track responses.
6. Use customer feedback and service findings as inputs to improvement and, where relevant, to design review.

Evidence an auditor expects for clause 8.5.5

Auditors look for proof that post-delivery commitments are known and honoured, usually by sampling customers or service cases. Looking at cases from several customers shows whether support is consistent, not only available in principle.

• Records of warranty claims, maintenance visits, patches, returns or disposal arrangements handled for sampled customers.
• Evidence of how legal and contractual after-sales duties were identified.
• Customer feedback and how it fed into decisions on support scope.
• Interview with a service or account owner about how commitments are tracked.

Common nonconformities with clause 8.5.5

Findings usually show up where after-sales duties are assumed rather than managed. In each, the organisation behaves as though its responsibility ends at the point of handover.

• Contract or warranty obligations are not tracked, so some are missed or met late.
• No consideration was given to end-of-life or disposal duties that apply to the product.
• Customer feedback after delivery is collected but is not used to decide support activities.
• Support work is done by a provider with no defined requirements or monitoring.

Illustrative manufacturing example: a warranty repair

Illustrative software example: supported releases

A software company delivers a reporting application under an agreement that includes maintenance for specified supported versions. A customer reports that a recent data-format change prevents an agreed report from running. The provider checks which release is installed and whether the reported behaviour falls within the maintenance commitment before assigning the work.

After correcting and testing the affected function, the team communicates the deployment conditions and confirms that the customer can use the required report. A support record connects the issue, version, test and customer communication. Where an older version is outside the agreed support arrangement, the team explains the available route accurately instead of inventing a new entitlement or ignoring applicable obligations.

Connect support to the wider quality system

Post-delivery information is valuable before the next sale as well as after the last one. Service teams may identify ambiguous specifications, unreliable components or instructions that customers repeatedly misunderstand. Pass relevant findings into requirements review, design changes, supplier evaluation and corrective action. The response should match the issue rather than route every minor enquiry into a major investigation.

Practical evidence can include support terms, service schedules, returned-product records, customer notifications and confirmation that agreed work was completed. Clause 8.5.5 does not prescribe a named post-delivery register. Select records that demonstrate fulfilment and preserve information required elsewhere in the QMS or by applicable obligations.

Common weaknesses include sales teams promising support that operations cannot supply, expired contracts remaining indistinguishable from active commitments, and warranty repairs being closed without checking the result. Another is treating customer feedback as a complaints statistic while failing to adjust the activities that caused repeated difficulty. Review coverage when products, contracts or service arrangements change.