ISO 9001 clause 8.2.2: define an offering the business can deliver

What clause 8.2.2 requires in practice

Clause 8.2.2 applies when the organisation decides what requirements its products and services will meet before offering them to customers. It asks for two things. First, the requirements must be defined, and this includes both the applicable statutory and regulatory requirements and those the organisation itself considers necessary. Second, the organisation must be able to meet the claims it makes for what it offers.

The second point is easy to overlook. A brochure, a service description or a standard proposal makes statements, and the clause expects the business to be able to stand behind each one. That links marketing and sales to technical and operating reality. The requirement concerns the offering in general, which differs from the review of a specific order under 8.2.3. It does not prescribe a product specification template, a service catalogue or a particular approval route. The organisation chooses how to record the definition, provided it is clear enough for staff to deliver and for customers to understand what they are being offered. The output is an offering whose description, conditions and limits are consistent with real capability and applicable legal duties.

Define the offering sufficiently for its purpose

Clarify what will be provided and the important conditions or limits. A service description may need to distinguish available support from response or resolution commitments. A product description may need to make relevant characteristics and intended applications clear. The detail depends on the offering and the decisions customers must make.

Avoid terms that sound attractive but have no agreed meaning within the business. “Fully supported” or “suitable for all environments” may imply more than the organisation can demonstrate. If a claim depends on a particular configuration or use condition, relevant limitations should be understood and communicated appropriately.

Bring suitable knowledge into the requirement decision

Applicable statutory and regulatory requirements form part of the determination. Their relevance depends on the product, service, location and other circumstances. Use appropriate competence and access to reliable information; ISO 9001 certification does not itself establish that every legal requirement has been identified or met.

The organisation may also determine requirements necessary for its offering even where the customer has not asked for them explicitly. These can arise from the way the product or service must operate. Do not treat customer silence as evidence that no further requirement matters.

Why a defined, deliverable offering matters

An offering that sounds attractive but has no agreed meaning inside the business invites disputes. Sales promise a level of support that operations cannot staff, or a product description implies an application it was never tested for. Defining the offer carefully keeps promises accurate, allows teams to price and resource work properly, and reduces the number of exceptions that must be settled one order at a time. It also protects the business legally, because claims that cannot be met may breach consumer or contract rules. Customers benefit from clarity about what is and is not included. Auditors use this clause to test whether public statements and delivery capability are connected.

How to implement clause 8.2.2

Start with what you tell the market and test it against what you can deliver. One way Sterling's teams do this is to list every claim in the proposals and web pages and ask the delivery owner to confirm each.

1. List the products and services you offer, including standard packages and their options.
2. For each, write what is included, what is excluded and the important conditions or limits in plain language.
3. Identify the legal and regulatory requirements that apply to the offering, in the markets you serve.
4. Add the requirements the organisation itself considers necessary, such as internal quality or safety standards.
5. Ask the people who deliver the offering to confirm that every claim can be met with existing capability and resources.
6. Retire or reword claims that are vague, untested or unsupported, and keep descriptions consistent across channels.
7. Review the definitions when you add a new market, change the process or learn from complaints.

Evidence an auditor expects for 8.2.2

The auditor compares what the organisation says it offers with what it can show it delivers. Typical evidence includes:

• current descriptions of products and services, such as proposals, web content or catalogues;
• identification of applicable legal and regulatory requirements for the offering;
• interviews with sales and delivery staff about how a claim was confirmed as achievable;
• records of past orders showing that the stated characteristics were provided;
• records of a revision made after a claim proved unrealistic, showing how the wording was corrected across channels and who agreed it.

Common nonconformities with clause 8.2.2

The usual findings come from a gap between the offering as sold and the offering as delivered.

• A published claim cannot be supported by the organisation's actual capability.
• Relevant legal or regulatory requirements for the offering have not been identified.
• Service descriptions use terms that staff interpret differently, so customers receive varying levels of service.
• Different channels describe the same offering in conflicting ways.
• Nobody reviewed the offer definition after the process or market changed, so descriptions describe an older way of working that the delivery team has since replaced.

Illustrative manufacturing example: a performance description

Illustrative BPO example: a service package with unclear coverage

A hypothetical BPO provider offers “multilingual customer support” without defining which languages, service hours or types of enquiry the package covers. Different account managers interpret the phrase differently, and operations discovers commitments beyond its available capability.

The business defines the service requirements and the conditions under which the offering can be delivered. It connects the description with staffing, competence and escalation arrangements, then reviews the customer-facing information. The improvement is a clearer, achievable offering, not a promise that every future enquiry can be resolved without limitation.

Check the link between claims and capability

A claim may concern a feature, performance characteristic, service availability or other aspect of the offering. Determine how the organisation knows it can meet that claim. Evidence may involve appropriate technical evaluation, operating capability or experience relevant to the actual conditions.

Do not rely on a provider's general statement where the organisation's own combined product or service creates a different promise. If an external component supports the offering, understand the interface and limits. The organisation remains responsible for the claims it makes to its customer.

Keep determination connected with review and change

The requirements established here feed pre-commitment review. A particular customer's intended use or additional condition may require further examination. A standard offering is not a reason to ignore a known difference that affects suitability or capability.

When the offering changes, review the relevant information and operating implications. A new feature or service level may affect provider arrangements, competence or acceptance criteria. Common failures include vague claims, outdated descriptions and internal requirements known by specialists but absent from the information used by sales and operations.

Clause 8.2.2 does not prescribe one product-requirements document. Use information and controls proportionate to the offering, while meeting related documented-information requirements and preserving the basis for important decisions where needed.