How to Choose a Sourcing Control Before Requesting a Supplier Quotation
Plan a distinct pre-RFQ verification task, define objective evidence and acceptance criteria, and record whether a supplier may enter the quotation pool.
A supplier’s claim should not enter a quotation decision as an untested assumption. Before requesting prices, define the claim that matters, select a proportionate way to verify it, and decide what evidence will be sufficient. This creates a clear gate between pre-sourcing research and commercial quotation work.
The objective is not to collect the largest possible document package. ISO guidance explains that documented information should support effective operation and that its amount, detail, and format can vary according to organizational circumstances. Evidence requests should therefore be driven by the sourcing decision rather than by document volume or appearance. See ISO 9001:2015 guidance on documented information.
The output of this activity is one completed verification record. It identifies the claim, scope, evidence, criteria, reviewer, finding, escalation path, and RFQ gate. Only suppliers that reach the defined gate should proceed to comparable quotation requests.
Decision to make before the RFQ
Use one decision sentence to keep the task bounded:
Before requesting a quotation, we need enough evidence to decide whether the supplier should enter the RFQ pool for this product and requirement set.
Define the uncertainty that prevents that decision. It might concern:
- Capability to perform a specified process.
- Control of externally provided work or materials.
- Availability of inspection, test, traceability, or release evidence.
- Whether product-specific CPSC manufacturing or product-safety obligations require further action.
- Whether a supplier’s described process is implemented, rather than merely documented.
Exclude price, payment terms, negotiation position, and contract-award questions. Those belong to later commercial work.
Define “sourcing control” for this task
A sourcing control is a planned method for checking a supplier-related claim before relying on that claim in an RFQ decision. A useful control answers one defined question, such as:
- Does relevant documented information exist?
- Is that information identifiable, current, in scope, and suitable for review?
- Does available evidence support the stated capability?
- Is an audit-style examination needed because files alone cannot establish implementation?
- Must product-specific CPSC questions be resolved before supplier comparison?
Document review, audit-style verification, and product-compliance research are different controls. Requesting a procedure can establish that information was supplied; it does not, by itself, establish that personnel consistently follow the procedure. Likewise, an applicability check identifies questions requiring resolution but is not automatically a complete legal or compliance conclusion.
Match the uncertainty to a control
| Uncertainty | Candidate sourcing control | What it can establish | What it cannot establish by itself |
|---|---|---|---|
| Whether defined information exists | Documented-information review | Presence, identity, scope, revision status, and relevance of supplied information | Consistent implementation in practice |
| Whether a described process is implemented | Audit-style verification against defined criteria | Evidence-based findings about activities in the agreed scope and period | Performance outside the reviewed scope or period |
| Whether product-safety obligations may affect sourcing | CPSC applicability and evidence check | Product-related questions that must be resolved before RFQ inclusion | A universal compliance conclusion without product-specific analysis |
| Whether several linked claims must be checked | Combined review with separate findings | A structured conclusion covering documents, activities, and product questions | Automatic certification, approval, or legal assurance |
Use an audit-style control when the task requires a planned, evidence-based examination rather than document collection alone. ISO 19011 addresses auditing principles, audit-programme management, audit conduct, and auditor competence; using these subjects to structure a review does not make the result a certification. See ISO 19011 — Guidelines for auditing management systems.
For consumer-product questions, research the relevant product through the CPSC Business & Manufacturing portal. Do not assume that one manufacturing, testing, certification, or reporting obligation applies identically to every product.
Build a distinct verification task
Write a one-question task statement
Use this structure:
Verify whether [specific claim] is supported by [defined evidence], against [stated criterion], for [product/process/site and period], before [RFQ decision].
A task statement should have a reviewable claim and a stopping point. Avoid broad instructions such as “audit the supplier,” “check quality,” or “confirm compliance.” They do not specify what must be demonstrated, which evidence is relevant, or when the review is complete.
Define the evidence before contacting the supplier
Request only information needed to support the stated decision. Distinguish between:
- Maintained information: Information used to describe, control, or operate a process.
- Retained evidence: Records showing that an activity occurred or that a result was achieved.
ISO’s documented-information guidance allows flexibility in the amount, format, and media used for documented information. Do not automatically demand a paper procedure when another identifiable and reviewable format could meet the information need. See the ISO documented-information guidance.
For each requested item, state whether it must show:
- Identity and subject.
- Relevant product, process, activity, or facility scope.
- Revision, issue date, or applicable period.
- Connection to the claim being assessed.
- Results, authorization, approval, release, or disposition where relevant.
- Consistency with other submitted evidence.
The existence of a file proves only that a file was made available. It does not automatically prove authenticity, practical implementation, or consistent performance.
Set objective acceptance criteria
Write the criteria before reviewing evidence. Define:
- Required content: What must be visible or demonstrable?
- Coverage: Which product, process, facility, activity, or period must be addressed?
- Currency: How will relevance to the planned sourcing decision be judged?
- Consistency: Which separate items must agree?
- Traceability: How must the evidence connect to the claim?
- Outcome rule: What causes pass, fail, conditional, or insufficient-evidence status?
Use insufficient evidence when the planned control cannot be completed. Do not convert missing, inaccessible, ambiguous, or inconclusive evidence into an assumption that the claim is true.
Assign a suitable reviewer and method
Identify the reviewer by role or required competence, not by an invented name. The reviewer must be able to understand the criterion, assess the evidence, identify gaps, and explain the finding.
For audit-style verification, define:
- Objective.
- Scope.
- Criteria.
- Evidence to examine.
- Review method.
- Finding categories.
- Reporting format.
- Escalation path.
Objectivity and reviewer competence are relevant subjects in ISO 19011. Product-specific legal or technical questions should be escalated when the sourcing team lacks the competence or authority to resolve them. Refer to ISO 19011 for its audit-guidance scope.
Separate verification from the quotation request
Send a bounded evidence request without asking for pricing. Tell the supplier:
- The claim being checked.
- The product, process, site, activity, and period in scope.
- The evidence requested.
- Any acceptable alternative formats.
- The applicable criteria.
- The possible outcome categories.
Complete and record the verification outcome before admitting the supplier to the RFQ stage. This separation prevents sales claims, pricing urgency, or negotiation activity from substituting for evidence.
Practical verification checklist
Complete every applicable row before requesting a quotation.
Task-planning and execution checklist
| Check | Verification question | Required entry or action | Complete |
|---|---|---|---|
| 1 | What sourcing decision will this task support? | Write one pre-RFQ decision sentence. | ☐ |
| 2 | What single claim is being verified? | Record a specific, testable claim. | ☐ |
| 3 | What is in scope? | Identify the product, process, activity, facility, and period where applicable. | ☐ |
| 4 | Is a CPSC applicability question present? | Record the product-safety question to research through the CPSC manufacturing resource. | ☐ |
| 5 | What criteria apply? | List the sourcing specification, documented requirement, audit criterion, or identified product requirement. | ☐ |
| 6 | What evidence would support the claim? | Specify maintained information, retained records, observable activity, or another defined evidence type. | ☐ |
| 7 | Is document review sufficient? | Mark yes only when existence, content, or consistency of documented information answers the decision question. | ☐ |
| 8 | Is implementation evidence necessary? | If yes, select an audit-style or combined control instead of relying only on submitted files. | ☐ |
| 9 | Is the control proportionate? | Confirm that the scope addresses the uncertainty without requesting unrelated documentation. | ☐ |
| 10 | Are acceptance criteria objective? | Define pass, fail, conditional, and insufficient-evidence conditions before review. | ☐ |
| 11 | Are evidence alternatives allowed? | State whether equivalent formats or media can satisfy the information need. | ☐ |
| 12 | Is reviewer competence defined? | Identify the knowledge, authority, or role needed to assess the evidence. | ☐ |
| 13 | Is objectivity addressed? | Base findings on criteria and evidence rather than sales statements. | ☐ |
| 14 | Is the supplier request bounded? | Remove pricing, negotiation, and unrelated qualification questions. | ☐ |
| 15 | Will the review be recorded? | Record evidence received, reviewer role, date, finding, gaps, and decision. | ☐ |
| 16 | Is there an escalation path? | Define what happens if applicability, authenticity, adequacy, or interpretation remains unresolved. | ☐ |
| 17 | Is the RFQ gate explicit? | Choose eligible, conditionally eligible, not eligible, or pending evidence. | ☐ |
| 18 | Has the outcome been completed before the RFQ? | Do not request a quotation until the gate decision is recorded. | ☐ |
Compact task record
| Field | Entry |
|---|---|
| Verification task ID | |
| Pre-RFQ decision | |
| Claim to verify | |
| Product/process scope | |
| Selected control | Document review / audit-style verification / CPSC applicability check / combined |
| Criteria | |
| Evidence requested | |
| Acceptable evidence alternatives | |
| Reviewer competence required | |
| Pass condition | |
| Fail condition | |
| Conditional condition | |
| Insufficient-evidence condition | |
| Evidence received | |
| Finding | |
| Open issue or escalation | |
| RFQ gate decision | Eligible / conditional / not eligible / pending |
| Decision record date |
Do not mark the record complete merely because evidence was received. Completion requires a documented finding, an outcome under the predetermined rules, and an explicit RFQ gate decision.
Image credit
Title: “a truck is parked in front of a bunch of shipping containers”
Photo: Bernd 📷 Dittrich
Source: Unsplash
License: Unsplash License
The image illustrates a sourcing and logistics setting. It is not evidence of supplier capability, process implementation, product compliance, or verification.
Sources
-
ISO 9001:2015 — Guidance on the requirements for documented information
Used for the distinction between documented information supporting process operation and retained evidence of results, and for flexibility in documentation format and extent. It does not prescribe a universal supplier document package. -
ISO 19011 — Guidelines for auditing management systems
Used when a sourcing control requires an audit-style approach, including consideration of auditing principles, programme management, audit conduct, and auditor competence. Applying the guidance does not constitute certification or supplier approval. -
U.S. Consumer Product Safety Commission — Business & Manufacturing
Used to identify product-safety and manufacturing questions that may require resolution before sourcing. Applicability must be assessed for the product concerned.
Scope and limits
This article covers planning one distinct sourcing-method verification task during pre-sourcing research. It supports selection among document review, audit-style verification, a CPSC applicability check, or a defined combination. It also provides a method for establishing evidence requirements, objective acceptance criteria, reviewer competence, recorded findings, and an RFQ admission gate.
It does not:
- Determine product-specific CPSC requirements.
- Provide legal advice or a compliance conclusion.
- Prescribe sample sizes, test methods, audit duration, or supplier-scoring weights.
- Require ISO certification or imply that a supplier is certified.
- Prove that submitted documents are authentic.
- Prove that documented practices are consistently implemented.
- Address price comparison, negotiation, contract award, or payment terms.
- Treat the selected image as sourcing evidence.
Final next move
Choose the highest-priority uncertainty that must be resolved before the RFQ. Complete one Compact task record, define the acceptance and outcome rules, and send only that bounded verification request to the prospective supplier. Record the RFQ gate decision before requesting a quotation.
Sourcing information earns its value when it is verified, compared and turned into a decision.