ISO 9001 clause 8.2.3: review the commitment before accepting it

What clause 8.2.3 requires in practice

Clause 8.2.3 requires a review before the organisation commits to supplying products or services. The review must establish that the organisation has the ability to meet the requirements. It has two parts. Clause 8.2.3.1 sets out what the review covers and what must be settled. Clause 8.2.3.2 asks that documented information be available, as applicable, as evidence of the review results and of any new or changed requirements.

The review looks at five groups of requirements: what the customer has specified, including delivery and post-delivery activities; what the customer has not stated but which is needed for the known intended use; what the organisation specifies; applicable legislation and regulation; and any differences between the contract or order and what was said earlier. Those differences must be resolved. Where the customer gives no written statement of requirements, the organisation must confirm them before acceptance. A note allows a lighter approach where individual review is impractical, for example internet sales, with the review covering the information on the website or catalogue instead. The clause does not require a particular form or sign-off sequence.

Review more than price and delivery date

Customer-defined requirements may include delivery and post-delivery obligations. Known intended use can reveal necessary requirements not expressly stated by the customer. The organisation also considers its own requirements, applicable statutory and regulatory requirements, and differences between the proposed commitment and earlier information.

Bring appropriate technical and operational knowledge into the review. A salesperson may know the customer's commercial priorities while another function understands a significant capability limit. The process should connect those perspectives before the organisation commits, not leave delivery staff to discover the conflict afterward.

Why reviewing before commitment matters

The moment of acceptance is the last low-cost point to avoid a bad commitment. Once the business has agreed, any gap in capability, stock, skills or legal compliance becomes a delivery problem with a customer waiting. A real review gives the organisation the chance to clarify an ambiguous request, obtain resources, change the proposal or decline. This protects margins, because rework and penalties are avoided, and it protects the relationship by replacing a later apology with an earlier conversation. It also coordinates sales, technical and operations staff around a single understanding. In audits, a sampled order that shows a genuine review is strong evidence that the commercial process is under control.

How to implement clause 8.2.3

Make the review a short, real decision rather than a form to be completed. One way Sterling's teams do this is to define who must be consulted for each type of order and what they must confirm.

1. Define which orders or contracts need a full review and which can be covered by a review of the published offering.
2. Name the people whose knowledge is needed, such as technical, legal, operations or purchasing, according to the type of work.
3. Prepare prompts covering stated requirements, intended use, internal specifications, legal duties and delivery or after-sales activity.
4. Compare the order with earlier quotations or discussions and note any difference that needs resolving.
5. Confirm verbally agreed requirements with the customer before accepting them, and record the confirmed version.
6. Decide the outcome openly: accept, accept with conditions, renegotiate or decline.
7. Keep information on the result and any new or changed requirements, in proportion to the significance of the work.

Evidence an auditor expects for clause 8.2.3

The auditor samples accepted orders and traces how the commitment was made. Expect to see:

• records or system entries showing that a review occurred before acceptance, and who took part;
• evidence of how differences from earlier statements were resolved;
• confirmation of requirements where the customer gave none in writing;
• interviews with sales and delivery staff about how capability was checked;
• a customer-facing offering reviewed in place of individual orders, where that approach is used, with proof the published information is kept current.

Common nonconformities with clause 8.2.3

Weak review usually appears as acceptance that outpaces understanding.

• Orders were accepted and work began before the review took place, so the review became a retrospective approval.
• The review concentrated on price and delivery date and ignored legal or after-delivery requirements.
• An order differing from the quotation was processed without resolving the difference.
• Verbal customer requirements were never confirmed or recorded, and the delivery team learned of them only when the customer complained.
• A review record exists but nobody can show what it actually concluded or which requirements it considered, so it adds little confidence.

Illustrative software example: support after implementation

Illustrative construction example: an order differs from the quotation

A hypothetical contractor quotes for a defined work package. The customer's purchase order adds an acceptance condition and a different completion sequence. An administrative team prepares to accept the order because the total price matches the quotation.

The review process identifies the differences and routes them to suitable people. The contractor evaluates the effect on resources, provider arrangements and the customer commitment, then resolves the position before acceptance. The example shows why matching commercial totals is not enough. It does not determine the legal effect of any particular contract wording, which requires appropriate advice where needed.

Confirm requirements when they are not documented

Customers may communicate requirements verbally or through an informal exchange. The organisation must confirm customer requirements before acceptance where the customer has not provided a documented statement. The confirmation method should suit the transaction and preserve a clear understanding of the commitment.

The standard does not universally require the customer to sign a particular form. The organisation should choose an arrangement that avoids ambiguity and supports any applicable evidence requirements. A casual recollection after delivery is weaker than a clear confirmation made before the commitment.

Adapt review to the sales model

In some circumstances, such as internet sales, a separate formal review for each order is impractical. The source recognises review of relevant product or service information as an alternative approach. That does not remove the need to ensure that the resulting commitment can be met.

For a standard offering, review can address the information customers rely on and the capability behind it. Exceptions or unusual requirements may still need additional attention. Do not force every transaction through unnecessary paperwork, but do not let automation bypass a significant difference that the business knows about.

Preserve the decision and communicate its basis

Documented information is required as applicable for review results and new or changed requirements. Existing commercial or project systems can provide it when reliable and retrievable. The level of detail should support the relevant decision and the work that follows.

Common failures include approval after work has already started, review limited to one department and unresolved differences hidden in correspondence. Another is keeping a review record while operational teams use an earlier requirement. Connect the accepted basis with planning, design, purchasing and release as relevant.

Explore each numbered part