Compliance & ContractsFree checklistPDF, Excel, Word exportAerospace

AS9100 Contract Review Checklist for Clause 8.2.3

AS9100D clause 8.2.3 requires you to review the requirements for products and services before you commit to supply them, and to keep documented evidence of that review. This checklist turns the clause into a form an estimator or contracts person can complete for each quote, PO or amendment.

0%

0 of 33 items complete

16 critical items still open - these are the highest-risk gaps.

Download checklist:

1. Customer requirements and documents

2. Technical, process and special requirements

3. Capability, capacity and schedule

4. Risk, regulatory and contractual terms

5. Acceptance, communication and records

Every critical item must be answered yes before the order is accepted. Open non-critical items need an owner and a due date. Keep the completed checklist with the order record as evidence for clause 8.2.3.2.

Order review inside your ERP

Want the review to block sales order release until it is complete? We can show how that is configured in your ERP.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Run it twice: once at quote stage to decide if you can bid, and again when the PO arrives to confirm that the order still matches what you quoted. Tick items as you verify them and attach the completed form to the order. The five groups follow the logic of the clause: understand what the customer wants, confirm technical and special requirements, prove you have the capability and capacity, assess risk and contract terms, then accept and communicate. Do not tick an item because it is probably fine. A blank line with a name and a date is better evidence than a ticked box nobody can explain.

What clause 8.2.3 actually asks for

The clause expects the review to cover requirements specified by the customer including delivery and post-delivery activities, requirements not stated but necessary for the specified or intended use, requirements you specify, statutory and regulatory requirements, and differences between the order and what was previously quoted. You must also be able to meet the requirements you accept, and you must retain documented information on the results of the review and on any new requirements. This checklist does not reproduce the standard text; read the current standard for the exact wording and your customer's own supplier quality manual for added requirements.

  • Review before commitment, not after the order is released
  • Amendments trigger a new review of the changed items
  • Verbal orders need confirmation before acceptance
  • Risk and capacity are part of the review, not a separate exercise

Where reviews usually fail

Most audit findings against contract review are not about a missing form. They come from a drawing revision that changed between quote and order, a special process called out in a note nobody read, a flowdown clause that never reached the outside processor, or a delivery date accepted without checking the heat treat lead time. The critical items in this list target those failures. If your ERP supports it, store the review result as a status on the sales order and block release to the shop floor until it is approved.

  • Drawing revision differs from the quote
  • Special process approval not confirmed with the customer list
  • Export control status unchecked for foreign nationals on the shop floor
  • Flowdowns not passed to outside providers

Making the review evidence audit-ready

Auditors sample orders and ask to see the review. Make that easy: record the reviewer, the date, the revision of every document reviewed and the decision. Keep the checklist, the quote, the PO and any clarification emails together under the order number. When a customer changes a requirement, re-open the review rather than writing a note on the traveler. For repeat orders on unchanged parts, a short delta review confirming that nothing changed is acceptable if your procedure defines it.

Frequently Asked Questions

Do I need to do a contract review for every purchase order?

Yes, clause 8.2.3 applies to each order or contract, but the depth can scale. A repeat order for an unchanged part can use a documented delta review that confirms revision, quantity, price, date and flowdowns. New parts, new customers and changed requirements need the full review.

Who is allowed to sign the review?

Your procedure decides, but the signer must have the authority to commit the company and enough knowledge of operations, quality and contracts to judge capability. Many shops require two signatures for new parts: the estimator or contracts lead and a quality or operations representative.

How long must contract review records be kept?

AS9100D requires you to retain documented information, and aerospace customers commonly require retention of ten years or more, sometimes the life of the program. Check the PO and the customer quality manual, then use the longest period that applies to the order.

Does a verbal or email order count?

Where the customer does not give a documented statement of requirements, clause 8.2.3 expects you to confirm the requirements before acceptance. Send written confirmation of what you understood and keep the reply or the confirmation with the order record.

If order review lives in email and spreadsheets, we can wire it into your ERP so a sales order cannot release until the review is signed, with the flowdown package attached automatically.