What this is
What is a customer specific requirement review?
What is a customer specific requirement review?
It reviews the requirements a named customer imposes above the standard specification, whether the site can actually meet each one, and whether meeting it depends on someone's memory or is built into a procedure or template. It is a row-by-row assessment against a repeating list, not a single yes-or-no on the contract.
What counts as a customer specific requirement?
The Requirement Type field names eight kinds: product specification, process, audit, certification, documentation, packaging, delivery and sustainability. Any of these can be imposed by one customer and not another, which is exactly why the review is per customer rather than folded into the general specification.
What triggers a review?
Five named triggers: a new contract, a contract renewal, a specification change, a complaint, and the scheduled annual review. A complaint triggering a review is itself telling, since it usually means a requirement was missed the review should have caught earlier.
Scope
When is a customer specific requirement review required?
This review assesses whether a specific customer's above-standard requirements can be met and are actually operational. Using it for the general specification, or for process capability, produces a record neither purpose is served by.
Use this template when
- A named review trigger fires: new contract, renewal, specification change, complaint, or the scheduled annual review
- A customer's contract or purchase order contains requirements beyond the standard specification that need cataloguing
- A complaint traces back to a requirement gap, and the review needs re-running against what was actually agreed
- The workspace is being set up and requirement history needs a home
- A linked record needs this review to exist against it: customer register, specifications
Do not use it for
- Manufacturing First Article Inspection, which inspects the first part off a setup against the specified characteristics, not whether a customer's contractual requirement is operational.
- Statistical Process Control Chart Review, which reviews whether a process is stable and capable, a separate question from whether it meets a customer's specific requirement.
- Statistical Process Capability Study, which establishes whether a process can hold a tolerance, not whether that tolerance is what a given customer actually demands.
- Customer Master Data and Terms Setup, which sets up commercial terms and flags requirements at a high level; this review is the detailed technical assessment behind that flag.
- Anything outside KnowQuality, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 9001 cl.8.2 requirements does this satisfy?
ISO 9001 cl.8.2 covers determining and reviewing customer requirements before commitment, but this review's distinctive obligation, that a requirement actually reaches the person who executes it, sits closer to the communication and operational-control clauses.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.2.2 | Determine requirements specified by the customer, including any not stated but necessary for the intended use | Header |
| ISO 9001 cl.8.2.2 | Determine statutory and regulatory requirements applicable to the product or service | Requirements identified |
| ISO 9001 cl.8.2.3 | Review requirements before committing to supply, resolving any difference from what was previously expressed | Assessment |
| ISO 9001 cl.8.2.3 | Confirm the organisation has the capability to meet the requirements it is reviewing | Assessment |
| ISO 9001 cl.7.4 | Determine internal communications relevant to the quality management system, including who needs to know what | Requirements identified |
| ISO 9001 cl.8.5.1 | Control production and service provision under conditions that include the requirements to be met | Follow through |
| ISO 9001 cl.9.1.1 | Determine what needs to be monitored and measured to evaluate whether requirements continue to be met | Result |
What it does not cover
- Customer Master Data and Terms Setup, the record that flags a requirement at a high level; this review is the detailed assessment behind that flag, not replaced by it.
- Manufacturing First Article Inspection, which checks the first part against a specification, not whether a contractual requirement is operational.
- Statistical Process Control Chart Review, a process-stability question, not a customer-requirement question.
- Production Part Approval Record, which approves a specific part for production, downstream of this review rather than a substitute for it.
- Customer Register, the register entry this review is linked from, not the review itself.
Global
Customer Specific Requirement Review requirements by country
ISO 9001 sets the general obligation, but a customer-specific requirement is formalised and audited differently by sector. Automotive and aerospace name it explicitly; general manufacturing does not.
IATF 16949:2016 clause 8.2.3.1, Customer-specific requirements
Customer-specific requirements are a defined, mandatory input layered on ISO 9001, addressed by name.
A supplier treating this review as generic ISO 9001 under-serves a requirement IATF names explicitly and audits against directly.
AS9100D clause 8.2.3.1, aligned to special requirements and key characteristics
Aerospace customers flow requirements down the contract, to be identified and flowed further down the supply chain.
The Requirement Type field for process, documentation and certification maps onto what an AS9100 audit expects traced.
ISO 9001:2015 clause 8.2.3
The baseline applies across all sectors without naming a customer-specific-requirement concept as automotive or aerospace do.
Beyond Our Standard Practice grading is effectively this review manufacturing its own equivalent process where no sector mandate exists.
How to complete it
How to complete a customer specific requirement review, step by step
The fields grade quickly and generously. The judgement calls below are what separates a review that catches a gap from one that documents an assumption.
Grading how far a requirement sits beyond standard practice matters less than confirming the person who executes it actually knows. A well-graded requirement nobody was told about is still unmet.
A requirement living only in an email thread is Partly, not Yes, whatever the day-to-day compliance looks like. Yes should mean a named procedure a new hire could follow unprompted.
Two customers demanding incompatible things on the same line is a Commercial Decision Required, not a call for whoever runs the line that day. Marking Some and moving on is the failure this field exists to stop.
Evidence Of Compliance Identified marked Yes should point to something inspectable: a record, a check, a certificate, not a restatement of the requirement itself.
What auditors find
Most common customer specific requirement review findings
These recur because the review is quick to complete generously, and the gap between a requirement graded correctly and a requirement actually operational is exactly what a rushed review misses.
| Finding | Clause | What fixes it |
|---|---|---|
| A requirement is graded and scored but Communicated To The Owner is left at No. | ISO 9001 cl.7.4 | Route it to the named Owner and confirm receipt before closing the row. |
| Built Into A Procedure Or Template marked Yes with no procedure or template referenced. | ISO 9001 cl.8.5.1 | Require the actual procedure identifier, not a description of the requirement. |
| A conflict between two customers' requirements resolved informally rather than escalated. | ISO 9001 cl.8.2.3 | Route any conflict to Commercial Decision Required rather than leaving it graded Some. |
| Can We Meet It marked Yes for a requirement that in fact needs a process change. | ISO 9001 cl.8.2.3 | Grade it With Change and track the change to closure before upgrading. |
| Rows carried forward unchanged from the prior review rather than reassessed against the current contract. | ISO 9001 cl.9.1.1 | Confirm every row reflects the current contract state at each trigger, not the last review. |
| Conflicts With Legal Requirements flagged Yes but the review still closes with a Pass band. | ISO 9001 cl.8.2.2 | Force the Result Band to Fail whenever a legal conflict is flagged. |
Case in point
Case in point: the sustainability clause nobody graded
A customer's contract renewal added a requirement that packaging for their line use a minimum recycled content, negotiated by sales as a minor concession to close the renewal. The renewal was signed, the review was scheduled for the following quarter's annual cycle, and production continued running the existing packaging stock.
The requirement surfaced eight months later as a customer audit finding, not an internal one. The review, when it finally ran, found the requirement had never been logged as a row at all, because whoever closed the renewal did not know a review existed to log it against, and nothing in the contract handover connected the two.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- QUA-112
- Archetype
- Review
- Record ID
- CSR-2026-000
- Scoring
- Requirements met
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.8.2
- Links
- Links Customer register, Specifications
- Tags
- Manufacturing, Customer
- Sections
- 5
- Fields
- 44
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 3
Header
12 fieldsReview ID*
Auto sequence. Format CSR-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Agreed By Sales, Never Told To Production
A customer requirement accepted in a contract and never communicated to the people who must meet it is a finding waiting to be raised, usually by that customer.
Customer*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Review Trigger*
Contract Or Specification Reference
Reviewed By*
Requirements identified
Repeats9 fieldsRequirement*
Requirement Type*
Product specification, process, audit, certification, documentation, packaging, delivery or sustainability.
Beyond Our Standard Practice*
- No3 pts
- Slightly1 pt
- Significantly0 pts
Can We Meet It*
- Yes3 pts
- With change1 pt
- No0 pts
Cost Or Resource Impact*
- None3 pts
- Some1 pt
- Significant0 pts
Owner*
Communicated To The Owner*
- Yes3 pts
- No0 pts
Built Into A Procedure Or Template*
A requirement that exists only in a contract will be met by accident or not at all.
- Yes3 pts
- Partly1 pt
- No0 pts
Evidence Of Compliance Identified*
- Yes3 pts
- Partly1 pt
- No0 pts
Assessment
6 fieldsAll Requirements Reviewed*
- Yes3 pts
- Partly1 pt
- No0 pts
Any We Cannot Meet*
- None3 pts
- Some1 pt
- Several0 pts
Customer Informed Of Gaps
- Yes3 pts
- No0 pts
Conflicts With Other Customers*
Two customers demanding incompatible things on the same line is a decision for management, not the line.
- No3 pts
- Some1 pt
- Significant0 pts
Conflicts With Legal Requirements*
- No3 pts
- Yes0 pts
Commercial Decision Required*
- No3 pts
- Yes1 pt
Follow through
4 fieldsProduction Briefed*
- Yes3 pts
- Partly1 pt
- No0 pts
Quality Plan Updated*
- Yes3 pts
- Not needed3 pts
- No0 pts
Audit Readiness Checked*
- Yes3 pts
- No0 pts
Next Review Due*
Result
13 fieldsItems Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Technical*
Signature*
Commercial*
Second Signature*
QUA-112 · record IDs look like CSR-2026-000 · Links Customer register, Specifications
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The review itself is quick to complete. What slips is the handover from the person who negotiated the requirement to the person who has to build it into a procedure.
Holds the requirement review against the customer and specification registers, and flags a requirement graded but never communicated to its Owner.
Carries the operational flag this review's findings feed, keeping the customer master data record and this review cross-referenced rather than duplicated.
Tracks requirements tied to certification or regulatory obligations, and flags a legal conflict that should force the result band to fail.
Watches for a requirement left uncommunicated to its Owner, or a conflict sitting ungraded past Commercial Decision Required, and raises it.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Customer Specific Requirement Review definitions and key terms
- Customer-specific requirement
- A requirement a particular customer imposes above the general product specification, applying to that customer's orders and not to others by default.
- Beyond our standard practice
- A graded field distinguishing a requirement matching normal operation from one demanding a deviation, scored so the deviation's scale is visible rather than binary.
- Owner
- The named person responsible for meeting a specific requirement operationally, distinct from whoever negotiated or reviewed it.
- Commercial decision required
- A flag routing a conflict or cost impact to a management decision, rather than letting operational staff resolve it ad hoc on the line.
- Evidence of compliance
- A specific, inspectable record, check or certificate showing a requirement is actually being met, distinct from a description of the requirement itself.
FAQ
Frequently asked questions about customer specific requirement review
What is a customer specific requirement, as opposed to the standard specification?+
The standard specification applies to every customer by default. A customer specific requirement is something one named customer additionally demands, whether a tighter tolerance, extra documentation, or a sustainability condition, and it does not apply elsewhere unless separately agreed.
Who completes this review, sales or technical?+
Technical, with commercial. Sales negotiates the requirement; technical judges whether the site can meet it and what it takes to build it into a procedure rather than a one-off accommodation.
What happens if we genuinely cannot meet a requirement?+
Can We Meet It is graded No, which should trigger a commercial conversation before the contract is signed or renewed, not after. Discovering it during production is the outcome this review exists to prevent.
Does every contract renewal need a full re-review, or just the changed terms?+
Every row should be reassessed at renewal, not only the ones that visibly changed. A requirement unchanged on paper can still have drifted operationally since the last review.
How is a conflict between two customers' requirements resolved?+
It is escalated through Commercial Decision Required, not resolved by whoever runs the line that day. Two customers demanding incompatible things on the same line is a decision for management, with the trade-off made visible.
How does this connect to Customer Master Data and Terms Setup?+
That record sets up the customer's commercial terms and flags requirements at a high level. This review is the detailed technical assessment behind the flag, and the two should never duplicate each other's analysis.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Statistical Process Control
Maintenance Calibration Record
Records calibration of maintenance instruments such as torque wrenches, pressure gauges and multimeters
Statistical Process Control Log
Records measurements over time so process variation can be seen and acted on before product fails
Process Capability Study
Measures whether a process can reliably hold its specification, using data from a stable run
Manufacturing First Article Inspection
Inspects the first part or pack off a setup against every specified characteristic before the run continues
Statistical Process Control Chart Review
Reviews control charts for a characteristic to see whether the process is stable and capable, not merely in specification
Statistical Process Capability Study
Establishes whether a process can consistently hold the tolerance it is asked to hold
More in Manufacturing Quality
Manufacturing First Article Inspection
Inspects the first part or pack off a setup against every specified characteristic before the run continues
Statistical Process Control Chart Review
Reviews control charts for a characteristic to see whether the process is stable and capable, not merely in specification
Statistical Process Capability Study
Establishes whether a process can consistently hold the tolerance it is asked to hold
Production Part Approval Record
Records the evidence pack that approves a part or product for series production, covering drawings, capability, measurement and samples
Rework Instruction Record
Sets out how a specific batch is to be reworked, what checks apply and who authorised it
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 clauses 8.2.2 and 8.2.3, Requirements for products and services
- IATF 16949:2016 clause 8.2.3.1, Customer-specific requirements
- AS9100D clause 8.2.3.1, Review of requirements related to products and services
- ISO 9001:2015 clause 7.4, Communication
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.