Quality Agreement Template: Clauses to Settle Before the First Production Order
What the quality agreement template must settle
A quality agreement template is only useful if every clause it contains points at evidence. Use the clause structure below as the starting template, and treat each block quote as text to complete rather than as finished wording.
A quality agreement converts a general expectation of quality into written, checkable obligations. It should define what the supplier must deliver, how conformity will be demonstrated, what happens when it is not, and which records prove each step.
Settle these terms before the first production order because that order is where the obligations begin to carry financial consequences: materials are produced, goods are inspected, discrepancies require decisions, and records must exist. A clause that merely says “comply with all quality requirements” leaves every one of those decisions open.
Use one drafting rule throughout: every obligation should point to an evidence output—a signed document, controlled file, report, retained record or defined notice period. If a clause has no way to be checked, it is not yet an operational quality obligation.
1. Scope and definitions
Start by identifying exactly what the agreement covers.
Clause heading: Scope and definitions
This Quality Agreement applies to [products], [purchase orders], [manufacturing sites and processes] from [date]. “Specification”, “Non-conformance”, “Corrective Action”, “Reportable Event” and any notice period used in this agreement have the meanings stated in [schedule or section]. This agreement is incorporated into each covered Purchase Order. The order of precedence is [insert].
List the products, order references, sites, processes and specification documents within scope. Name the contacts authorised to approve changes, issue non-conformance decisions and receive notices. For every time-based notice, state the delivery method, recipient and point at which notice is received.
Evidence output: the signed agreement, a controlled document register showing the incorporated files, and a contact schedule with authorised recipients.
2. Specification and change control
Define how the supplier knows which requirements govern each order.
Clause heading: Specification and change control
The Supplier shall manufacture and supply only to the Specification revisions listed in Schedule [insert]. No change to a Specification, manufacturing site or controlled process shall take effect without the Buyer’s written approval. Each approval shall identify the changed item, the reason for the change, the effective revision and the records that must be updated.
Attach the governing drawings, specifications, bills of materials, test requirements and other controlled documents. Give every document a revision and approval status. Make the Purchase Order point to the agreed revision rather than repeating requirements incompletely.
Evidence output: the controlled specification index, revision history, written change approval and updated purchase-order reference.
3. Inspection and acceptance
State what will be inspected, where and how.
Clause heading: Inspection and acceptance
Inspection shall cover the characteristics, methods, sample size, defect tolerances and acceptance rule listed in the agreed Inspection Plan. Results shall be recorded for each inspected lot or other defined unit. Accepted, rejected or concessioned material shall receive a dated disposition record.
Complete every field rather than referring vaguely to “standard inspection”. Insert the sample size, defect tolerances and acceptance rule; if the parties use AQL, insert the agreed value. Also state whether inspection occurs before shipment, after receipt or at both points.
The inspection output should identify the item inspected, the requirement, the result, the evidence reference and the disposition. This makes a quote or production lot comparable against the same agreed requirements.
Evidence output: the approved Inspection Plan, inspection or test report, acceptance or rejection record and any signed concession.
4. Non-conformance and corrective action
Set out the route from a detected discrepancy to verified closure.
Clause heading: Non-conformance and corrective action
The Supplier shall notify the Buyer within [insert period] after identifying a Non-conformance, preserve the affected records and provide containment details. No affected material shall be used, shipped or otherwise dispositioned except under an authorisation recorded in the Non-conformance Report. Where corrective action is required, the Supplier shall provide the agreed corrective-action and effectiveness records before closure.
Define who may authorise rework, return, use-as-is or another disposition. Where root-cause analysis is required, state which occurrence triggers it. Keep the trigger, corrective-action deadline and closure criteria visible rather than embedding them in informal correspondence.
Evidence output: a numbered Non-conformance Report, containment record, authorised disposition, corrective-action report, effectiveness check and dated closure approval.
5. Records and retention
A records clause in the template must control the record, not merely mention record-keeping.
21 CFR 820.10 provides a relevant drafting reference because it addresses a documented quality management system covering records, identification and traceability, complaint files and regulatory reporting. The eCFR also identifies 21 CFR 820.35 as “Control of records”.
Clause heading: Records and retention
The Supplier shall keep the records listed in the Record Schedule complete, legible and retrievable. For each record, the schedule shall state its owner, file location, format, authorised access, retention period and the event from which retention runs. Records shall remain available for the agreed review period and shall be disposed of only under the agreed authorisation and disposition process.
Use these fields:
- Record: name the manufacturing, traceability, inspection, complaint, non-conformance, corrective-action or notification record.
- File: state where the record is retained and how it is linked to the relevant product or order.
- Access: identify who may retrieve or review it.
- Period: insert the retention period and its starting event.
- Change control: require the record schedule to follow approved document changes.
The retention period is for the parties to set; do not leave it implied or substitute an unsupported period. The signed Record Schedule is the evidence that the obligation is controlled.
Evidence output: the Record Schedule, file or log entry, access record and authorised disposition record.
6. Notification of adverse events
Draft the trigger, content, recipient and deadline separately.
Clause heading: Notification of adverse events
The Supplier shall notify the Buyer in writing within [insert contractual notice period] after any employee becomes aware of information that reasonably suggests that a Reportable Event has occurred. The notice shall contain [agreed product and event identifiers], a description of the known facts, the awareness date, the reporting contact and supporting records. Updates shall be provided within [insert period] until the final report is issued within [insert period].
Complete the report fields and preserve the Buyer’s acknowledgement. Do not use “notify if required by law” as a substitute for the contractual trigger.
21 CFR Part 803 supplies a precise regulatory reference where its requirements apply. Section 803.10(c) states:
“Any information, including professional, scientific, or medical facts, observations, or opinions, may reasonably suggest that a device has caused or may have caused or contributed to an MDR reportable event.”
It defines an MDR reportable event as:
“A death, a serious injury, or, if you are a manufacturer or importer, a malfunction that would be likely to cause or contribute to a death or serious injury if the malfunction were to recur.”
The trigger is therefore information that reasonably suggests the event may have occurred, not only a completed investigation.
Part 803 sets the regulatory reporting deadline at no later than 30 calendar days after the day the manufacturer becomes aware of a reportable event, with a 5-work-day period where reporting has been requested under § 803.53. That 5-work-day period applies only when it is requested; it is not a replacement period for every event.
Set your contractual initial-notice period separately. A supplier can usually report a suspected event to you faster than the regulatory deadline allows, and that earlier internal step is what lets you decide whether a report is required.
Evidence output: timestamped initial notice, completed adverse-event report, supporting file, transmission record and Buyer acknowledgement.
7. Escalation and termination
Define how unresolved quality issues move to a decision.
Clause heading: Escalation and termination
A Quality Escalation shall be issued when [insert agreed triggers] occur. The Supplier shall respond within [insert period], provide the specified corrective-action record and attend the review at [insert level]. If escalation does not resolve the issue, the parties shall follow the agreed termination or suspension procedure.
Complete the trigger, response period, decision authority, review route, cure period and termination conditions rather than leaving them to later negotiation.
Evidence output: escalation notice, response, meeting or review record, decision log and any termination notice.
Screening and due diligence are separate gates
Do not fold trade compliance into the quality clauses and treat signing as completion. The International Trade Administration’s Consolidated Screening List (CSL) identifies parties subject to United States Government restrictions on certain exports, reexports or transfers, and its due-diligence guidance says diligence continues as a company expands into new markets. Run both as their own transaction gate: record the search date, the results and the reviewer, and keep the file open after signature. The quality agreement neither replaces screening nor ends due diligence. Record the contract references and unresolved compliance questions in the RFQ checklist so they are settled before the order, not after it.
Walk-through to the first production order
Agree the documents in this order:
- Sign the scope and definitions.
- Freeze the specification revision index.
- Approve the Inspection Plan and acceptance record.
- Test the non-conformance and corrective-action route.
- Complete the Record Schedule.
- Define reportable events, contractual notice periods and the separate regulatory position.
- Agree escalation, suspension and termination rules.
- Complete and continue screening and due diligence.
- Issue the first production order incorporating the signed agreement, specification revisions, inspection plan, contact schedule and record index.
At that point, each obligation becomes auditable: the supplier produces against an identified revision, inspection creates a defined report, a discrepancy enters the non-conformance process, notices enter a traceable file, and every closure decision has retained evidence.
Source context
Each claim below is supported by the cited page. The workflow, headings and worked arithmetic above are Suppliers Help editorial guidance, not text from these sources. Sources checked 2026-10-02.
- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-820/subpart-B/section-820.10 — A device quality management system addresses documented controls including records, identification and traceability, complaint files and regulatory reporting.
- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-803 — A manufacturer becomes aware of a reportable event when an employee becomes aware of information that reasonably suggests a reportable event has occurred.
- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-803 — Individual adverse-event reports are due no later than 30 calendar days after the day the manufacturer becomes aware, and the 5-work-day period applies where § 803.53 requires it.