Functional Sample Acceptance Criteria: Exact Tests and Pass/Fail Limits to Require Before Production
A sample is not approved because it looks right on a desk. It is approved because it passes a defined test under defined conditions, with a record that another person can repeat.
Functional sample acceptance criteria are written requirements that define what will be tested, how it will be tested, what result passes, what evidence is required, and what happens after a failure. They turn the phrase “approved sample” into a release condition for production.
Write the test before you approve the sample. Functional sample acceptance criteria should exist before the supplier submits the approval unit.
Table of contents
- What are functional sample acceptance criteria?
- Why are sample tests more useful than a visual approval?
- What must every acceptance criterion include?
- Which functional test categories should you consider?
- How do you set a valid pass-fail limit?
- What evidence should the supplier submit?
- When should testing be in-factory or independent?
- What are the limits of sample acceptance criteria?
- Frequently asked questions
What are functional sample acceptance criteria?
Functional sample acceptance criteria are a test specification for a sample. They state the characteristic, test article and condition, method, equipment, sample selection, pass-fail limit, retest rule, evidence deliverable, and change trigger.
| Field | What to write |
|---|---|
| Characteristic | The function or failure mode being checked |
| Test article | Exact revision, material, configuration, and sample identity |
| Condition | Setup, environment, load, orientation, and preconditioning if relevant |
| Method | Named standard, approved procedure, or controlled work instruction |
| Equipment | Tool, fixture, software version, and required calibration status |
| Limit | The design or standard-derived pass-fail requirement |
| Evidence | Raw result, photos, video, measurement record, and tester identity |
| Change rule | What changes require the test to be repeated |
A functional sample acceptance criteria sheet is not a generic checklist. Functional sample acceptance criteria must reflect the approved product revision and its real use conditions. It is a product-specific agreement.
Why are sample tests more useful than a visual approval?
A visual check can identify obvious finish, labeling, or assembly issues. It often misses whether a product will carry a specified load, seal, cycle, fit, operate electrically, survive its intended handling, or remain consistent after a controlled change.
| Visual approval can show | Functional testing can show |
|---|---|
| Color, finish, and obvious damage | Whether the item meets a stated performance limit |
| Basic assembly state | Whether repeat use exposes a failure mode |
| Printed claims and included parts | Whether operation matches the approved configuration |
| A single attractive unit | Whether the result was measured with a defined method |
CPSC says testing requirements can vary by product, intended user, use pattern, and material composition.[^1] The result is that one universal drop height, load, cycle count, or electrical tolerance is not responsible guidance.
The limit must come from the product. Functional sample acceptance criteria should retain the documented source for every critical limit.
What must every acceptance criterion include?
Use one row for each critical functional requirement. Start with customer use and credible failure modes, then specify the exact test.
| Test row | Example structure |
|---|---|
| Requirement | Lid remains sealed during the defined use condition |
| Basis | Product design input, applicable standard, engineering analysis, or customer requirement |
| Method | Identified procedure with sequence, fixture, duration, and observation points |
| Limit | Stated leakage, force, measurement, operating, or condition limit from the approved basis |
| Sample selection | Defined sample identity and selection method |
| Evidence | Dated record, raw readings, images, and signature or accountable tester |
| Failure action | Hold sample, investigate cause, revise, retest, and document decision |
NIST defines measurement traceability as a documented, unbroken chain of calibrations to specified reference standards, with each step contributing to measurement uncertainty.[^2] A calibrated instrument does not automatically make a measurement fit for its purpose. The method and uncertainty must suit the acceptance limit.
Which functional test categories should you consider?
The categories below are prompts, not prescribed tests or thresholds. Functional sample acceptance criteria must be written by people who understand the product, risks, intended use, and applicable requirements.
| Category | What a criterion might define | Do not assume |
|---|---|---|
| Mechanical load | Load direction, duration, fixture, deformation or failure limit | The same load suits every size or use case |
| Cycle or life | Action, rate, count, checkpoints, and end condition | A generic cycle count proves durability |
| Leakage or sealing | Fluid, pressure or orientation, duration, acceptable result | A visual check proves a seal |
| Dimensional fit | Mating parts, gauge, datum, force, and fit result | Nominal dimensions guarantee assembly |
| Electrical operation | Input condition, output, protection response, and measurement method | A powered-on check proves safe operation |
| Packaging transit | Final product, pack-out, route condition, and damage limit | Empty-carton testing is enough |
| Software or firmware | Version, inputs, expected behavior, logs, and recovery condition | A demonstration covers edge cases |
For regulated products, the applicable rules or standards can determine testing. CPSC says a single children’s product can need multiple third-party tests, and not every laboratory is accredited for every applicable rule.[^1]
How do you set a valid pass-fail limit?
A functional sample acceptance criteria limit should be traceable to a real source: an applicable regulation or standard, approved customer requirement, engineering calculation, risk analysis, validated design input, or formal product requirement. Record the source beside the limit.
| Weak limit | Better limit |
|---|---|
| “Must be durable” | State the approved method, condition, endpoint, and source of the limit |
| “No leakage” | Define the test condition, observation method, and allowable result |
| “Works normally” | Define inputs, expected outputs, time, tolerance, and failure condition |
| “Pass drop test” | Identify the relevant test method or engineered condition and acceptance basis |
Do not copy a competitor’s stated test claim or a generic online number into an RFQ. If the basis is missing, mark the criterion open and obtain qualified engineering, lab, safety, or compliance input before production.
What evidence should the supplier submit?
The evidence should let the buyer determine what was tested, on which configuration, with what method and measurement system, and what happened.
| Evidence item | Why it matters |
|---|---|
| Sample identification and revision | Links the result to the actual approved configuration |
| Procedure and pass limit | Shows what the test was intended to prove |
| Equipment identity and calibration status | Supports the measurement claim |
| Raw readings and observations | Prevents a pass statement from hiding the data |
| Photos or video where useful | Shows setup, fixture, and visible condition |
| Test date and accountable tester | Creates a traceable record |
| Failure and retest record | Shows whether a problem was corrected or merely omitted |
Functional sample acceptance criteria should require a new review after a material, component, design, process, firmware, or pack-out change that could affect the tested result. CPSC says material changes can trigger retesting for rules affected by the change.[^1]
When should testing be in-factory or independent?
In-factory testing can be useful for process checks, controlled fixtures, early problem discovery, and production feedback. Independent or appropriately accredited testing may be needed where regulation, customer requirements, independence, specialized equipment, or a higher consequence calls for it.
| Test setting | Best use | Limitation |
|---|---|---|
| In-factory | Routine process control and rapid iteration | The buyer must still assess method, records, and conflict of interest |
| Independent laboratory | Specialized, regulated, customer-required, or disputed testing | Lab scope and method must fit the product requirement |
| Buyer witness or third-party inspection | Verification of selected setup and sample identity | A witness does not replace a valid test method |
CPSC says a reasonable testing program for certain general-use products should consider supplier relationships, materials, processes, and variability.[^3] Choose the setting based on the actual risk and requirement.
What are the limits of sample acceptance criteria?
Functional sample acceptance criteria cannot guarantee that every production unit will perform like a sample. They do not replace production controls, incoming checks, change control, inspection plans, required certification, or field feedback.
They also do not substitute for qualified advice on safety-sensitive, electrical, chemical, medical, children’s, structural, or regulated products. A sample can pass a poorly chosen test. That is why the test basis matters as much as the observed result.
Define, test, document, repeat. Functional sample acceptance criteria make that sequence reviewable before production begins.
Frequently asked questions
What are functional sample acceptance criteria?
Functional sample acceptance criteria are written, product-specific pass-fail tests that define the sample, method, equipment, limit, evidence, and action after failure before production is approved.
Should every sample have the same tests?
No. Tests depend on product function, materials, intended use, failure modes, applicable rules, and customer requirements. A cosmetic item and an electrical product require different functional evidence.
How do I choose a cycle-test count?
Use the count specified by an applicable standard, design requirement, engineering analysis, risk assessment, customer requirement, or validated product input. Do not invent a universal number of cycles.
Can a factory run its own functional tests?
Yes, in-factory tests can support process control and sample iteration. Define the method, equipment, evidence, and review process. Use independent or accredited testing when the requirement or risk calls for it.
What makes a pass-fail limit valid?
A valid limit has a documented source and a method capable of measuring it. The record should identify the product configuration, conditions, equipment, result, and acceptance basis.
Does a calibrated tool prove a test is valid?
No. NIST notes that traceability alone does not guarantee fitness for purpose. The method and measurement uncertainty must be suitable for the required limit.[^2]
What happens if a sample fails?
Hold approval, record the failure, determine the cause, revise the product or process as appropriate, and retest the affected criterion on the revised configuration. Keep the failed result in the project record.
When should a test be repeated?
Repeat it after a material, component, design, process, firmware, packaging, or supplier change that could affect the result. Define these triggers in the acceptance sheet.
Should functional tests be included in an RFQ?
Include the required evidence and the source of each criterion in the RFQ when the buyer needs suppliers to quote the right process, equipment, testing, or documentation. Final limits may need qualified review before release.
Can this replace regulatory testing?
No. Functional sample acceptance criteria are a commercial and engineering control. Product-specific legal or regulatory testing and certification can have separate requirements.[^1]
What should you release before production?
Finish functional sample acceptance criteria with an approved revision, test basis, controlled method, evidence package, failure rule, and change-trigger list. When those records exist, a sample approval says more than “looks good.” It says the critical function was defined and verified.
References
[^1]: U.S. Consumer Product Safety Commission, “Third Party Testing Guidance”
[^3]: U.S. Consumer Product Safety Commission, “General Use Products: Certification and Testing”