
Sourcing Assumption Verification Checklist
Turn an early sourcing assumption into a bounded verification task with clear criteria, evidence, methods, decision rules and records.
Convert an early sourcing assumption into a verification task by rewriting it as a testable statement with defined criteria, evidence, method, scope, owner and decision rule. The result should show whether the assumption is supported, contradicted or not verified. This conclusion determines whether the assumption is reliable enough for pre-sourcing planning. It does not approve a supplier, certify a management system, establish product compliance or replace legal and regulatory review.
Define the assumption before selecting a method
Working definitions
- Early sourcing assumption: A provisional statement used to shape a sourcing plan before sufficient evidence has been collected.
- Verification criterion: An observable condition that must be met for the assumption to be treated as supported.
- Evidence: Relevant, traceable information that can be reviewed against a criterion.
- Verification task: A bounded activity stating what will be checked, how it will be checked and how the result will affect the sourcing decision.
- Documented information: Information controlled and maintained or retained as evidence.
The ISO guidance on documented information under ISO 9001:2015 explains that documented information can exist in different media. It also states that organizations determine the documented information needed to support effective processes and provide evidence that planned results were achieved. These principles can help structure a verification record, but they do not establish that a particular supplier conforms to ISO 9001.
Rewrite broad assumptions as testable statements
Use this sequence:
- State the planning decision affected by the assumption.
- Remove vague terms such as “reliable,” “adequate,” “compliant” and “high quality” unless measurable criteria define them.
- Identify the exact condition that can be checked.
- Set the applicable boundary, such as a product, process, location, document set, period or sourcing stage.
- Specify what evidence would support or contradict the statement.
Example transformation
- Broad assumption: “The required manufacturing controls should be available.”
- Testable statement: “For the process included in this pre-sourcing review, the requested documented information identifies the control, responsible role and retained record used to show that the process was carried out as planned.”
- Supporting evidence: A current controlled document identifies the control and responsible role, while a relevant retained record shows the defined output.
- Contradictory evidence: A reliable record shows that the named control is absent or materially different from the stated control.
- Decision boundary: The task verifies the availability and content of the requested information. It does not prove that every activity was performed consistently or that the supplier meets all applicable requirements.
A task should test one bounded assumption. If a statement combines document availability, operational performance, regulatory compliance and supplier capability, separate it into distinct tasks with their own criteria and conclusions.
Build a distinct verification task
Required task elements
Include the following fields in each task:
- Decision: The pre-sourcing choice that will use the result.
- Assumption: The provisional statement being tested.
- Criterion: The condition that must be true.
- Evidence request: The exact record, document, field, page or observation needed.
- Source: The person, organization, system or official page providing the evidence.
- Method: Document review, structured inquiry, direct observation, process walkthrough, audit-style review or authoritative-source check.
- Scope: The included process, site, product category, record period or requirement.
- Exclusions: Matters the task will not establish.
- Reviewer: The person responsible for interpreting the evidence.
- Timing: The date by which evidence must be provided and how current it must be.
- Decision rule: Supported, contradicted or not verified.
- Record: Where the task, evidence references, source dates, review date and conclusion will be retained.
Use explicit decision rules
Apply the rule defined before evidence collection:
- Supported: The specified evidence is available, relevant to the defined scope and meets every stated criterion.
- Contradicted: Reliable evidence conflicts with one or more criteria.
- Not verified: Evidence is missing, inaccessible, stale, outside scope or too ambiguous to support a conclusion.
Do not convert not verified into false without contradictory evidence. If only part of an assumption has been checked, identify the supported portion and leave the remainder not verified.
For example, a current procedure may support the statement that a control is documented. It does not, by itself, verify that personnel follow the procedure consistently. That second claim may require sampled records, observation or a walkthrough.
Apply audit discipline without overstating the result
ISO 19011:2018 provides guidance on audit principles, audit-program management, conducting management-system audits and auditor competence. Its concepts can improve a sourcing verification task:
- Define the scope and criteria before collecting evidence.
- Select methods suited to the verification objective.
- Record the evidence sources and the basis for the conclusion.
- Consider reviewer competence and impartiality.
- Document sampling, access and time limitations.
- Retain enough information for another reviewer to reconstruct the decision.
Label the work accurately as a verification task unless it is formally planned and conducted as an audit. An audit-style review is not certification, and ISO 19011 does not itself establish conformity.
Match the method to the evidence needed
| Verification method | Best used when | Evidence produced | Main limitation |
|---|---|---|---|
| Document review | The assumption concerns whether specified information, controls or records exist | Copies, extracts, identifiers, revision dates and review notes | A document can show what is defined or recorded, but not by itself that practice is consistent |
| Structured inquiry | A process, responsibility or document needs clarification | Dated questions, attributed answers and follow-up requests | Answers remain representations until corroborated |
| Process walkthrough | The task concerns how stated steps connect in practice | Walkthrough notes, referenced records and the observed process sequence | The result covers only the observed scope and time |
| Direct observation | The criterion concerns an observable activity or condition | Dated observation notes tied to the criterion | A snapshot cannot establish performance outside the observation window |
| Audit-style review | Several criteria, evidence sources or process interactions require systematic evaluation | Defined scope, criteria, evidence trail, findings and conclusion | It requires planning and suitable reviewer competence and must not be described as certification |
| Authoritative-source check | The assumption concerns whether official guidance is relevant to the sourcing task | Page title, issuing body, URL, source date, access date and applicability note | Guidance-page relevance does not establish product or supplier compliance |
Choose the least extensive method capable of testing the criterion. A document review may be sufficient to verify that specified information exists. A claim about implementation may require corroborating records, observation or an audit-style review.
Use CPSC material only when relevant
For a consumer-product question within the remit of the U.S. Consumer Product Safety Commission, use the CPSC Business & Manufacturing page as an official starting point.
Turn the source check into a bounded task:
- Identify the specific CPSC page or tool reviewed.
- Record why it may apply to the product category or sourcing question.
- Retain the page title, issuing body, URL and access date.
- Record any displayed publication or update date.
- Identify unresolved questions about product-specific applicability.
- Define the next review needed if legal or regulatory interpretation remains open.
Visiting a CPSC guidance page does not prove compliance, testing completion, certification or supplier approval. It shows only that the identified official material was reviewed for the stated question.
Practical verification checklist
| Check | Required entry or action | Completion test |
|---|---|---|
| 1. Name the decision | State the pre-sourcing choice affected by the assumption | A reviewer can identify what will change based on the result |
| 2. Write one assumption | Use one bounded, declarative statement | The task does not combine unrelated claims |
| 3. Remove vague language | Replace subjective terms with observable conditions | Every material term has a criterion |
| 4. Define the scope | Identify the process, product category, location, period or document set | Included and excluded areas are clear |
| 5. Set verification criteria | List every condition that must be met | Each criterion can be answered from evidence |
| 6. Identify authoritative inputs | Name the official document, guidance page or other permitted source | The source title and issuing body are recorded |
| 7. Request exact evidence | Specify records, fields, dates, revisions or observations | The request is more precise than “send documentation” |
| 8. Select the method | Choose document review, inquiry, observation, walkthrough, authoritative-source check or audit-style review | The method can test the stated criterion |
| 9. Assign a competent reviewer | Match reviewer knowledge to the evidence and decision | Responsibility and competence limitations are recorded |
| 10. Set freshness requirements | Define how current the evidence and URLs must be | Stale evidence can be identified consistently |
| 11. Record source details | Capture the title, identifier, revision or edition, source date, URL and access date | Another reviewer can locate the same source |
| 12. Corroborate where needed | Use another evidence type when one source cannot establish the criterion | Unsupported representations are not treated as verified facts |
| 13. Document sampling | State which records or observations were reviewed and why | The conclusion does not imply full-population coverage |
| 14. Apply the decision rule | Mark supported, contradicted or not verified | The result follows the predefined criteria |
| 15. Record exceptions | List missing, inaccessible, ambiguous or out-of-scope evidence | Uncertainty remains visible |
| 16. State the sourcing action | Continue research, revise the assumption, change the method or defer the decision | The result leads to a specific next step |
| 17. Retain the verification record | Store the task, evidence references, conclusion and review date | The decision can be reconstructed later |
| 18. Schedule rechecking | Set a trigger for changed requirements, updated guidance or expired evidence | Time-sensitive claims are not reused indefinitely |
Compact task worksheet
- Decision to be informed:
- Assumption to verify:
- Verification criterion or criteria:
- Included scope:
- Excluded scope:
- Evidence required:
- Evidence source:
- Verification method:
- Reviewer and relevant competence:
- Freshness requirement:
- Result: Supported / Contradicted / Not verified
- Evidence and source dates:
- Sampling or access limitations:
- Limitations or exceptions:
- Resulting sourcing action:
- Recheck trigger or date:
Sources
-
ISO guidance on documented information under ISO 9001:2015
- Scope used: The role, form and extent of documented information, including information maintained to support processes and retained as evidence.
- Date handling: The source concerns ISO 9001:2015. Confirm and record the PDF’s publication or revision metadata and access date before publication or reuse.
- Use limitation: The guidance supports documentation principles. It does not establish that a particular organization conforms to ISO 9001.
-
ISO 19011 guidelines for auditing management systems
- Edition reflected: ISO 19011:2018.
- Scope used: Audit principles, audit-program management, conducting audits and auditor competence.
- Use limitation: Audit guidance does not provide certification or establish conformity by itself.
-
U.S. Consumer Product Safety Commission business and manufacturing guidance
- Scope used: Official starting point for CPSC business and manufacturing information when relevant to a consumer-product verification question.
- Date handling: Record any displayed update date and the final access date before publication or reuse.
- Use limitation: The page does not by itself resolve product-specific applicability or prove compliance.
Scope and limits
- This framework supports a distinct pre-sourcing research verification task.
- It does not establish supplier capability, approve a supplier, validate production output or support general product-quality claims.
- It does not establish legal or regulatory applicability, testing completion, certification or compliance.
- ISO documentation and auditing guidance can structure the task, but neither source proves conformity for a specific organization.
- CPSC material should be used only within its subject-matter scope and should not be generalized to products or jurisdictions it does not cover.
- Every conclusion applies only to the defined criteria, sample, period and access provided.
- Before publication or reuse, recheck time-sensitive facts and URLs, retain source and access dates, and leave every unsupported point marked not verified.
Sourcing information earns its value when it is verified, compared and turned into a decision.