What factory evaluation documents on site: part 4
Production records prove the factory is controlled; conformity files prove its goods may ship into the destination market. Substance test data, declarations of conformity, labeling evidence, and change-tracking logs form a second documentation layer that assessors examine with equal care. Too often this layer lives elsewhere, with agents or headquarters, while the site under assessment cannot present it. This final part of the on-site guide maps each conformity file, its required linkage to production, and the maintenance routine that keeps the set current. Market access is documented or it is assumed.
Key takeaways
- Substance-compliance files must pair test data with production linkage, since a passing report proves little until it is tied to current lots and batches under RoHS-type substance disciplines. [1]
- CE-related files need declarations plus supporting assessment evidence behind the mark, consistent with the conformity structure described in CE marking references. [2]
- Label evidence closes the chain at the carton: required marks, warnings, and traceability codes checked against specifications and approval records.
- Change tracking decides whether the file set stays current; a log naming the regulation, version, affected products, and dated actions demonstrates the routine.
- Local retrievability is the test for every file: delegated knowledge the site cannot present reads as absent knowledge on the day.
The earlier parts of this documentation series traced production records from receiving to packing and linked them to shipments. This final part addresses the files that sit alongside production: substance compliance, conformity documentation, labeling evidence, and the change-tracking routines that keep everything current. These files decide market access as directly as any measurement on the floor.
They are also the files most often left to agents, trading companies, or distant headquarters while the factory focuses on making goods. That division of labor is understandable and risky: when the assessor asks the factory about the conformity of its own output, somebody on site should be able to present the file and explain it. Delegated knowledge that cannot be retrieved locally reads as absent knowledge.
The sections below map each file type, the linkage each one needs to production, and the maintenance routine that keeps the set current across standard revisions and order changes.
Pair substance data with production linkage
Restricted-substance compliance turns on homogeneous-material test data: results for the specific materials in the specific product, against the limits in force. References on the RoHS directive describe how such limits apply to electrical and electronic equipment placed on the regulated market. [1] The factory's file should therefore hold the test reports with dates and scopes, the bill of materials identifying which tested materials go into which models, and the incoming-lot linkage showing current production uses those same materials.
The assessor tests this file the same way as production records: by sampling. A report number is picked, its scope compared against the models on the current lines, and its materials traced to incoming lots in stock. Suppliers whose documentation is arranged for review through UTS Inspection are advised to keep this chain filed per product family rather than scattered across years of correspondence. Where materials changed since the last test, the file should show the retest or the risk assessment that justified continuity.
Verify the file behind the marking
Product markings condense a conformity story into symbols and text on the goods and packaging. For European markets, the CE marking indicates the manufacturer's claim that applicable assessment procedures were completed and documented. References on CE marking explain that the mark rests on technical documentation and, where the directives require it, involvement of designated assessment bodies. [2] The on-site check therefore looks past the symbol to the file: the declaration of conformity, the supporting evidence, and the version alignment across all of them.
Three consistencies decide the verdict. First, the declaration, the test evidence, and the product scope must name the same models and directive versions. Second, the technical documentation must be retrievable at the site or through a defined responsible party, not merely asserted to exist elsewhere. Third, labeling on current output must match the file, including model designations, required warnings, and traceability codes. A mark without this backing is a liability printed on the product.
Conformity files and their linkage points
| File | Required content | Production linkage |
|---|---|---|
| Substance test reports | Dates, scopes, limits applied | Tested materials traced to current lots |
| Declaration of conformity | Models, directives, versions named | Declaration scope matches lines running |
| Technical documentation | Assessment evidence per directives | Retrievable through a defined party |
| Label approvals | Content, marks, warnings specified | Current labels match approved version |
| Change log | Regulation, version, actions dated | Past updates show routine working |
Check labels as the chain's last link
- Compare labels to specificationModel identity, required conformity marks, safety warnings, and traceability codes each have a specified form; verify all against the order and the file.
- Trace labels to approvalsPick one label version in use and request its approval record, confirming who approved the content and when.
- Check change propagationConfirm that specification changes propagate to labels, since labels are frequently the last item updated.
- Verify market variantsWhere multiple markets require different marks, confirm the correct variant is applied to each destination's goods.
Keep the set current across revisions
Assign ownership of regulatory monitoring
Files decay without an owner. The factory should name who tracks regulatory changes for each destination market, which sources they watch, and where updates are logged. The log entry for each change names the regulation, the version movement, the products affected, and the actions taken with dates. This routine is modest administrative work that prevents the most embarrassing visit outcome: a factory controlled against rules that changed two years ago.
Review on change, not only before visits
The durable habit is event-driven review: new product family, new material, new destination market, or published revision each triggers a file check before production starts. Visit-driven scrambles then disappear, because the file is maintained as part of engineering change rather than as audit theater. Buyers can encourage this by asking, at each order change, which conformity files were reviewed, turning maintenance into a commercial expectation rather than a periodic surprise.
Make every file locally retrievable
The closing test applies to the whole conformity layer: can the site under assessment present each file and explain it, within the visit, without phoning another company? Delegation to agents, headquarters, or consultants is legitimate only when retrieval works through a defined, demonstrated channel. Knowledge that exists somewhere but cannot be shown on the day cannot support a conformity verdict about the site's output.
Factories that pass this test share one trait: the conformity files live where production lives, maintained by people who use them when specifications change. That placement is itself evidence of a working system. The evaluation then records what the best visits always show, that documentation and production describe the same goods, and buyers can plan shipments on that basis with confidence.
Sources
- Wikipedia: Restriction of Hazardous Substances Directive —— Overview of the RoHS directive restricting hazardous substances in electrical and electronic equipment.
- Wikipedia: CE marking —— Overview of CE marking as conformity marking for products sold in the European Economic Area.
Frequently asked questions
What must a substance-compliance file contain on site?
The test reports with their dates, scopes, and the materials or models they cover, plus the record linking those reports to current incoming lots and production batches. A report alone proves a sample once passed; linkage proves the shipped goods are represented. Ask for both together or neither convinces.
What sits behind a CE mark the assessor can verify?
The declaration of conformity, the supporting assessment evidence, and the technical documentation behind them, all naming the same product scope and directive versions. The marking on the product is the claim; the file is the proof. References on CE marking describe this assessment-and-documentation structure.
How should label evidence be checked during the visit?
Compare the label content against the order specification and the applicable marking duties: model identity, required marks, warnings, and traceability codes. Then trace one label batch to its approval record to confirm controlled changes. Labels are often the last item updated after specification changes, which is why assessors check them.
What does a good regulatory-change log look like?
Entries should name the regulation, the version change, the products affected, and the actions taken with dates. A log with these four elements shows the factory tracks its obligations; a log of general intentions does not. The strongest evidence is a past update handled correctly, since it demonstrates the routine working.