Forum Discussion: What are the Requirements for Products and Services in ISO 9001?

• This discussion revolves around a member’s struggle with clauses 8.2.2 and 8.2.3 of a quality management standard following a major issue raised by an auditor regarding what are the Requirements for Products and Services in ISO 9001?.
• Forum contributors discussed how internal processes, like the sales department coordinating with the transport department to confirm delivery times or checking stock levels to meet customer demands, ensure these requirements are met.
• A particular forum member, facing an auditor’s critique for “No Objective evidence of contract review,” shared their plan to develop a simple contract review procedure.

The discussion in the Elsmar Cove Quality Forum revolves around a member’s struggle with clauses 8.2.2 and 8.2.3 of a quality management standard following a major issue raised by an auditor. The primary concern was the need for more objective evidence of contract review within the organization. Participants in the forum shared insights and suggestions on addressing this issue, emphasizing the importance of demonstrating that the organization actively reviews quote requests or purchase orders before committing to supply. It was highlighted that a checklist is not necessary for this process. Still, the organization’s quality management system (QMS) should specify customer requirements before approval, such as delivery dates, quantities, product names/parts, price, and relevant documentation.

Forum contributors discussed how internal processes, like the sales department coordinating with the transport department to confirm delivery times or checking stock levels to meet customer demands, ensure these requirements are met. The discussion underscored the significance of recording these activities correctly to demonstrate compliance with the standard. The retention periods for documented information, as referred to in clause 8.2.3.2, were also examined, with the key phrase “As Applicable” indicating some flexibility in how organizations maintain records.

A particular forum member, facing an auditor’s critique for “No Objective evidence of contract review,” shared their plan to develop a simple contract review procedure. This procedure would involve a designated person reviewing customer requirements (like price, lead time, product name, and description) to verify the organization’s ability to meet these requirements without additional demands. Issuing the order into their system was proposed as the record of the contract review, suggesting that the system’s functionality to hold orders until they are “issued” could serve as evidence of the review process. This pragmatic approach reflects the organization’s actual practices and aims to satisfy the auditor’s requirements by providing clear, objective evidence of contract reviews.

Read the full article