A factory's brochure and its operation can be two different companies. The evaluation that matters compares documented capability with what the factory actually does — its quality systems, test equipment, production flow and documentation discipline. This guide explains how to check factory capability against claims, which quality systems are worth reviewing, what the test equipment and production flow should show, why documentation discipline is a signal, and which audit questions separate factories.
Key takeaways
- The evaluation compares claims with evidence: quality systems, test flow and documents.
- Documentation discipline predicts reorder reliability.
- The audit questions are the same for every candidate, so the comparison is fair.
Content updated: August 2026 — confirm current standards editions and model-specific details before ordering.
Scope note: This guide is industry information, not regulatory, legal or certification advice; the audit approach is general industry practice.
Factory Capability vs Factory Claims
Every factory has a brochure; the evaluation starts where the brochure ends. Capability is verified by asking what the factory can document: quality systems, test coverage, batch records and change control. Claims without documents are marketing, and the marketing does not survive a shipment mismatch.
The comparison table is simple: for each claim, ask for the evidence. "We test every unit" is a claim until the test records and the production flow confirm it; "we hold certificates" is a claim until the certificates name the exact configuration. The evaluation is a document review backed by a site visit.
The tone of the evaluation matters as much as its content. A factory that welcomes the questions and produces records on request is signaling confidence; one that deflects or promises documents "later" is signaling the opposite. The pre-order conversation predicts the post-order one.
The evaluation should also distinguish between capability that exists and capability that is exercised. A factory can own test equipment that is rarely used, or maintain a quality certificate for a line it does not actually follow. The audit verifies that the documented capability is the operating reality, and the batch records are the bridge between the two.
The scope of the evaluation follows the program. A stock purchase warrants a lighter check; a healthcare-adjacent OEM program warrants the full document review and a site visit. The depth is matched to the risk, and the risk is higher where the device and the documents matter more.
Quality Systems Worth Checking
The quality system is the factory's operating standard, and a few elements carry the most information:
| Element | What to check |
|---|---|
| Incoming inspection | Are components checked against BOM and specs? |
| Production flow | Are the test steps built into the line, not after it? |
| Aging and functional tests | Are units exercised before shipment? |
| Batch records | Does every batch carry traceable records? |
| Change control | Are changes documented and approved? |
The quality system is verified by asking how each element works and then looking at the records. A factory that can walk through the flow and produce records for a specific batch has a system; one that describes the flow but cannot show the records has a presentation.
The quality certification itself is a starting point, not a conclusion. The certificate says the system was assessed; the records say what the factory does. Both are reviewed, and the records carry more weight in a sourcing decision.
The quality system review also benefits from asking for the failure side of the story. How the factory handles a rejected batch, a field complaint or a change request reveals the system's real shape better than its success stories. The failure process is documented, tested and reviewed like any other process.
For a healthcare-adjacent program, the quality system is also the foundation of the document set. Certificates and reports are produced by the same discipline that runs incoming inspection and change control, and a factory that manages the system manages the documents. The two reviews are one review seen from two sides.
Test Equipment and Production Flow
The test equipment and the production flow show where testing happens and what it covers. The useful questions:
- Which tests run on every unit, and which run on samples?
- What does the aging test cover, and for how long?
- How are failures recorded, and how do they feed correction?
- What happens to a batch that fails?
The production flow should place testing inside the line rather than after it, because testing after assembly catches problems later and more expensively. The factory's published quality flow — incoming checks, functional testing and aging — is a starting point, and the site visit confirms it in practice.
The test equipment itself deserves a closer look. Equipment that is calibrated, dated and matched to the products being tested is evidence of a working system; equipment that is described but not shown is not. The audit asks which instruments run which tests, when they were calibrated and what the records show.
The production flow also tells the story of how changes are absorbed. A factory that tests a changed configuration as a new configuration, with new records, is running change control; one that lets the change slide through the existing records is not. The flow and the change process are reviewed together.
Documentation Discipline as a Signal
Documentation discipline is the strongest predictor of reorder reliability. A factory that maintains versioned certificates, batch records and change logs for every configuration is running a program; one that produces documents on request is running a scramble.
The checks are concrete: certificates name the exact configuration and standard edition; batch records connect the shipment to the design; change logs show what changed and who approved it. The absence of any of the three is a signal, and the signal is stronger than the brochure.
Documentation discipline also predicts how the factory handles a problem. A factory with a documented process can trace a field issue to a batch and a root cause; one without it treats every problem as a new investigation. The discipline is tested before the order, not after the problem.
The documentation review should sample actual records, not just ask for descriptions. Ask for a batch number from a recent shipment and follow it: the batch record, the inspection results and the certificate for that configuration. A factory that can produce the chain for a specific batch is running the discipline; one that cannot is running a presentation.
The discipline also extends to the supplier's own suppliers. Component-level traceability feeds the batch story, and the factory's ability to name its component sources and their records is part of the evaluation. The chain is only as strong as its weakest link, and the weakest link is often upstream.
Audit Questions That Separate Factories
The same questions run against every candidate:
- "Which standard edition does your certificate name, and does it match the configuration?"
- "Can you show the batch records for a specific shipment?"
- "What tests run on every unit, and what does the aging cover?"
- "How is a change documented, and who approves it?"
- "What happens when a batch fails inspection?"
The answers, with records, separate factories that run programs from factories that sell promises. A factory that answers all five with documents has earned the shortlist; one that answers with adjectives has not.
The audit questions should also be asked in writing, with the answers filed. A written Q&A with documents attached becomes the evaluation record that supports the sourcing decision, and it is the same record an auditor will want later. The questions are cheap; the record is the deliverable.
The evaluation closes with a decision, not a tour. The candidate either passes the evidence standard or it does not, and the decision is recorded with the supporting documents. A program that evaluates every candidate against the same standard, and records the result, has turned factory evaluation from a visit into a discipline.
Start with the WECENT site to review the company's manufacturing and quality positioning, then use the Factory page for the manufacturing and quality context and the Quality Control page for the production test flow and records. To run this evaluation against a candidate configuration, request the document set from WECENT's project engineering team — the review returns the certificates, test flow description and batch record approach for the program.
Frequently Asked Questions
What is the most reliable signal in a factory evaluation?
Documentation discipline. A factory that maintains versioned certificates, batch records and change logs for every configuration is running a program; one that produces documents on request is not.
Should I visit the factory before ordering?
For a healthcare-adjacent program, a site visit or a detailed remote audit is worth the investment. The production flow and the test equipment are verified in practice, not from the brochure.
Which quality system elements matter most?
Incoming inspection, production-flow testing, aging and functional tests, batch records and change control. The records behind each element carry more weight than the certification alone.
What happens if a batch fails inspection?
The factory's answer is the signal. A documented process quarantines the batch, finds the root cause and corrects it; an undocumented process improvises. Ask the question before the order.
How do I compare two factories fairly?
Run the same five questions and the same document requests against both, and compare the answers. The same standard for every candidate is what makes the comparison a decision.