A certificate of conformity is a live agreement with a certification body, and it applies to one precisely defined configuration of your product. The moment that configuration drifts — a substituted material, a revised PCB layout, a second-source supplier for a critical component — the certificate no longer describes what you are shipping. Across two decades in automotive and aerospace quality, I have seen almost nobody set out to break certification deliberately. It dies by a thousand small, reasonable-looking engineering decisions, each signed off locally without anyone asking the one question that matters: does the certification body know about this?

The failure is structural, not moral. Most engineering change processes were designed around function, cost and delivery, and certification consequences were left to memory. Memory is a poor compliance system. This article covers what the certificate actually covers, how notification obligations work, what follow-up inspectors really check, and what to do when you discover a breach after units have shipped.

What a Certificate Actually Covers

Read your certification documents and you will find a configuration control annex, a technical file index or a product description schedule. That annex is the legal heart of the certificate. It lists enclosure materials and their flammability ratings, creepage and clearance distances, the protective earth impedance path, the software version, rated inputs, and often the critical component list down to manufacturer and part number. The certificate is granted against that snapshot and nothing else.

This is where well-intentioned engineers go wrong. A change that is functionally equivalent — a polyester film capacitor from a different maker with the same capacitance, voltage rating and tolerance — can still fall outside the certified configuration. The certification body tested one specific part, from one specific factory, under one specific set of test conditions. Equivalence in the datasheet is not equivalence in the eyes of the scheme, and for good reason: subtle differences in failure behaviour, such as whether a capacitor fails open or short under overvoltage, directly affect safety outcomes.

Treat the certified configuration as a controlled baseline, on the same footing as a drawing under formal revision control. Any deviation from it is a change, regardless of how trivial it looks. If you cannot point to a line in the technical file that permits the substitution, you have an unauthorised deviation on your hands — whether or not anyone has noticed yet.

The certificate describes one configuration; the factory ships whatever the latest engineering change released. Keeping those two identical is the whole discipline.
The certificate describes one configuration; the factory ships whatever the latest engineering change released. Keeping those two identical is the whole discipline.

The Notification Obligation You Signed

Every product safety certification scheme I have worked under — EU directives with notified bodies, North American NRTL arrangements, sector schemes in vehicles and machinery — imposes a notification obligation on the certificate holder. You agreed, in writing, to inform the body of changes affecting conformity. Most schemes distinguish three tiers: changes requiring notification only, changes requiring engineering review, and changes requiring re-testing or re-certification. Classifying your change correctly is your responsibility, not the body's.

The practical mechanism is a change notification form submitted with revised drawings, a change description, and a rationale addressing which safety-relevant requirements could be affected. Be specific and be honest. A submission that says "minor PCB revision, no safety impact" when the revision moved a mains track closer to a SELV boundary will come back to bite you at the next follow-up inspection, because inspectors read diffs, not summaries. They will find the rerouted trace.

Build the notification trigger into the engineering change process itself. Before any ECO is released, a mandatory gate should ask: does this part number appear on the certified critical component list, or does this drawing appear in the technical file? If yes, the certification coordinator is a required approver with authority to hold release. Without that gate, notification depends on somebody remembering.

Certification gate in the change process

  1. 01ECO draftedChange description, affected part numbers and drawings listed.
  2. 02Certification screenCompare against critical component list and technical file index.
  3. 03ClassificationNotification only, engineering review, or re-test — decided by the coordinator, not the designer.
  4. 04Body submissionForm, drawings and safety rationale sent; release held until response.
  5. 05File updateApproved configuration recorded as the new baseline.
The check must run before the ECO is released, not after parts arrive at the line.

What the Follow-Up Inspector Actually Does

Twice a year or annually depending on the scheme, a representative of the certification body arrives to verify that what you build matches what was certified. This is not an audit of your quality system in general; it is a configuration comparison exercise. The inspector pulls production records, selects units currently being shipped, and checks them against the certified documentation: component ratings and manufacturers, marking and labelling, construction details, protective bonding, and the presence of critical components on the approved list.

Prepare by running your own dry run first. Sample finished goods from stock and the despatch area — not from the pilot line, which is often tidier than reality — and compare them against the technical file component by component. Check that the label matches the certificate number, model designations and warning markings exactly. I have seen entire follow-up visits derailed by a label artwork update that marketing approved without routing it through engineering, changing a model suffix or dropping a required symbol.

Expect the inspector to trace a specific serial number backwards through build records to its bill of materials, then forwards again to confirm the BOM was released before the unit was built. Date mismatches are a classic finding: production using a revised component before the change was notified or approved. Keep deviation permits and their expiry dates under control, because an open-ended deviation is treated as an unapproved permanent change. Close them or convert them into properly notified changes.

Inspectors read diffs, not summaries. They will find the rerouted trace, the swapped manufacturer, the missing symbol on the label.

The Quiet Killers: Substitutions That Void Compliance

Sub-tier supplier changes top the list of accidental decertification. Your certified component maker moves moulding or winding to a different factory, or quietly revises an internal design, and the part number stays the same. The certificate references the component manufacturer's own file number; if that listing has changed, your conformity is compromised through no visible action of your own. Critical component procurement needs flow-down clauses requiring notification of manufacturing site or design changes.

Software updates are the second killer, particularly where software implements safety functions, protective interlocks or EMC-relevant behaviour. A field update that changes relay drive timing or the filtering constants in a motor controller can shift EMC performance or disable a safeguard. Certified software versions belong under the same configuration control as hardware, and any release affecting safety-relevant behaviour needs assessment against certification requirements before deployment.

Material substitutions driven by purchasing, obsolescence or REACH-style restrictions come third. Flame-retardant grades of plastics are a frequent trap: switching to an equivalent polymer without the same flammability rating, or changing wall thicknesses during moulding optimisation, can invalidate enclosure compliance and electrical clearance simultaneously. Older stock built under the previous configuration is usually still shippable — but only if your records prove when the change took effect, unit by unit. Segregate and mark the changeover point physically and in the serial number record, because "we think the new material started around March" is not evidence.

Change that looks harmless vs change the scheme sees

What engineering sees

  • Same capacitance, voltage and tolerance
  • Same form factor and footprint
  • Second source already qualified for function
  • Purchasing saved 12%
  • No drawing change needed

What the scheme sees

  • Different manufacturer file number
  • Different failure mode under overvoltage
  • Outside the critical component list
  • Unnotified deviation since the ECO date
  • Finding at the next follow-up inspection
The datasheet lens and the certification lens produce opposite verdicts on the same substitution.

Field Modifications and Rework Still Touch Your Certificate

Compliance does not end at your despatch dock. Installers, service technicians and end users modify products, and in most schemes the certificate holder can be drawn into the consequences — particularly where modifications are foreseeable or where you supply spares and service instructions. A field service organisation fitting a higher-rated fuse, replacing a mains cord with a different type, or drilling ventilation openings in an enclosure has created a product you never certified. If that unit later causes harm, the investigation will ask what you did to make such modifications difficult and what your instructions warned against.

Manage this through spare parts control and service documentation. Sell fuses, cords and protective components only as matched kits with correct ratings and types, and make service manuals explicit: replacement parts must be of the specified type, and any other modification voids the certification. On complex products, consider keyed or coded connectors so incorrect substitutes cannot physically be fitted. Legitimate variants, such as a regional cord option, should themselves sit within the certified configuration or be separately notified.

Internally, guard against the workshop-modification habit. Rework operators bending a tab, adding a jumper wire or hand-soldering a component the automated line cannot place are all modifying the certified construction. Some of this is permitted if the technical file describes the rework method; undocumented rework found at inspection is a nonconformity, and if it touches a safety-relevant characteristic it can trigger a full re-evaluation. Document every permitted rework method in the file and train operators to escalate anything outside it.

Recovering Position When You Find a Breach

Suppose a dry run, an internal audit or a customer complaint reveals that a change went through unnotified six months ago and several thousand units have shipped. The worst response is silence: follow-up inspectors and market surveillance authorities both treat concealment far more severely than self-disclosure. Contact the certification body, describe the change factually with drawings and analysis, and agree the corrective route. In many cases, where you can demonstrate by analysis or targeted testing that the change does not affect the certified safety requirements, the body will accept it retrospectively with a file update and perhaps a sample evaluation.

Where the change does affect conformity, you are into product recall or field correction territory, and the rules of the applicable market surveillance regime apply — traceability of shipped serial numbers becomes the controlling capability. Root-causing why the notification gate failed comes next. In my experience the answer is almost always structural rather than personal: the ECO form had no certification field, the critical component list lived in a spreadsheet nobody owned, or the coordinator role was assigned to someone who left and was never replaced. Fix the structure, then retrain the people.

Maintaining certification through design change is ultimately a discipline of configuration honesty. The certificate describes one product; your factory builds another one every time an undocumented change slips through. Keep those two products identical on paper and in metal, and the certificate stays alive. Let them diverge quietly, and you will eventually learn about it in the most expensive way possible.