7.2.2 Review of Requirements Related to the Product
The organization shall review the requirements related to the product. This review shall be conducted prior to the organization's commitment to supply a product to the customer (e.g. submission of tenders, acceptance of contracts or order, acceptance of changes to contracts or orders) and shall ensure that;
a) product requirements are defined
b) contract or order requirements differing from those previously expressed are resolved, and
c) the organization has the ability to meet the defined requirements. Records of the results of the review and actions arising from the review shall be maintained (see 4.2.4)

OK - There is what TS says.
Our question: "Are product releases against Purchase Orders covered by this clause?"

Do we need to review and maintain records as stated above for each and every release against a Purchase Order?

Two sides:
1. This review was done during Inquiry Review and initial contract review prior to acceptance of the Purchase Order and releases are therefore covered.
2. How do we assure that nothing has changed from the initial review unless we verify the release against the contract (P.O.)

Thoughts? Ideas?

IMO 7.2.2 states contract review requirements prior to acceptance of a contract. If the contract is agreed and supplied under releases to the original purchase order, you should conduct normal contract review to ensure there are no changes to the original agreement. This can be as simple as reviewing whatever documents are provided with the order.

I think the 2 sides you posted are in fact two steps of normal contract review and both apply. As you say in 1, releases are therefore covered by the initial review but you point out the extension of that in 2 - ensuring there are no changes. In our business we compare all releases and POs against the original contract.

I think if you outline contract review in your procedures to include both new and releases, there would be no need for documentation past whatever you say you will do in the process. For example, if you say that all documentation supplied with release requests is reviewed against the original order prior to processing, then all orders processed are presumed to have been reviewed. There would be no need for additional documentation or records showing this was done.

I hope I understood your question.

Dave

I agree with your thoughts but I have one question.

"Records of the results of the review and actions arising from the review shall be maintained."

There would be no need for additional documentation or records showing this was done.

How do we reconcile the "requirement of records maintained" with your "no need ...or records showing this was done."

Again, IMO - the results of the review would either:

1) allow for release of parts without changes in which case there would be no other action to record (your processing document - work order - would serve as the records that no changes were found and the PO was processed under the agreed requirements)

2) identify a change in the original order which would prompt FULL contract review and documentation through another process (assuming you identified your action for this in the review procedure as suggested earlier).

The "records of the results and action" as required would either be the work order documenting "reviewed and no changes found" or the change form / contract review documenting "change found, reviewed and here's what happened".

When we identify a change, we put the parts/PO on hold and use the attached form to start the "change control" process.

Dave