CE/UKCA mark documents, compiled.
Also called: Technical file · Conformity documentation · Declaration of Conformity · UKCA/CE marking
Compiling the technical file, test evidence and signed Declaration of Conformity that lets you apply the UKCA mark legitimately.
The mark is a claim; the technical file is the proof behind it. Hold drawings, the standards met, test reports, the risk assessment and a signed Declaration of Conformity. Then apply UKCA (CE for the EU). No file means no defensible claim, only a sticker.
What CE and UKCA documentation is
The UKCA mark (and the CE mark for the EU) is a self-declaration. By applying it you are stating, on your own authority, that the product meets the regulations that apply to it. Nobody hands you the mark; you apply it once you can stand behind the claim. The thing that lets you stand behind it is the technical file.
The technical file is the evidence pack: the design and drawings, the standards you decided apply, the test reports that show you meet them, a risk assessment, and the Declaration of Conformity you sign. For a heated, mains-or-low-voltage kitchen product that means electrical safety, electromagnetic compatibility (EMC), and food-contact compliance. The file does not get submitted anywhere by default. You keep it, and you produce it on demand if Trading Standards, a retailer, or a customer’s lawyer asks. That is the point: the mark is the public claim, the file is the private proof, and the two have to match.
Who signs, and what it commits you to
The Declaration of Conformity is signed by the manufacturer or their authorised representative. In a small DTC business that is usually the founder. The signature is not a formality. It is a legal statement that the named product, with its model and batch identifiers, conforms to the regulations listed on the declaration, and that the evidence exists to back it. Sign it without the file behind it and you have made a false declaration on a regulated product. That is the failure mode worth fearing, not the paperwork itself.
The conformity file, worked
The clearest way to see what the file holds is to lay it out. Here is the proofing box’s, the one we ran through to launch, so you can see the shape of a real file rather than a generic template.
Notice the mark is the last row, not the first. Everything above it is the reason the founder can sign their name to it. Get the order wrong and you are marking on hope.
- UKCA logo added because a competitor’s product has one.
- No test reports, no risk assessment, nothing on file.
- A declaration signed on trust, with no evidence behind it.
- Nothing to produce when a retailer’s compliance team asks.
- The applicable standards chosen and justified in writing.
- Dated test reports for safety, EMC and food contact.
- A risk assessment that names hazards and their mitigations.
- A signed Declaration produced on demand, in one email.
How it fits the bigger picture
CE/UKCA Mark Documents is the last activity of Stage 07 Engineer. It depends on the standards work, testing and risk assessment that came before it in Engineer, and it pulls them together into one defensible pack. With the file compiled and the mark applied legitimately, the product is clear to leave engineering and enter Stage 08 Develop, where the design is hardened for production and pre-production builds begin.
What it can do
It turns scattered engineering evidence into a single, defensible file, and it lets you apply the UKCA mark (and CE for the EU) as a claim you can actually stand behind. When a retailer like John Lewis or Lakeland asks for your compliance pack, you have one ready to send rather than a scramble.
What it can’t do
It can’t make an unsafe product safe. The file documents conformity; it does not create it. If the testing failed or the risk assessment found a hazard you have not designed out, the honest move is to fix the product, not to soften the wording. The mark is only as good as the evidence underneath it.
See the full 10-stage process →
Try it yourself
List the regulations that plausibly apply to your product. For a powered kitchen device that is usually electrical safety, EMC and food contact. Against each, name the standard, the test, and where the report lives. Anywhere you write “to be done”, you are not ready to mark. Draft the Declaration of Conformity last, and read it as if a Trading Standards officer were reading it back to you.
Not sure which standards apply to your idea yet? Start the Free Sprint → and map the regulated path before you build.
Your conformity checklist
Project notes: the file behind the mark
▸ From the notebook · optional reading
Compiling the proofing box’s technical file with Dan and Anna Hartley in Stockport, and the day a retailer asked to see it.
3 min read · click to open
By the time we reached marking, the hard work was already done. The BS EN 61010-type safety testing had passed, the EMC report was clean, and the food-contact compliance for the inner liner was signed off. Marking was meant to be the easy bit: pull it all into one folder and sign. It nearly wasn’t.
The drawer of evidence
Dan had the test reports, but they were scattered across three email threads and a lab portal. Anna had the risk assessment in a spreadsheet that had drifted out of step with the final design. The Manchester PCB house had revised the board twice since the EMC test, and nobody had checked whether the changes touched the tested configuration. I asked one question: “If John Lewis asked to see the file tomorrow, could you send it by lunch?” The answer was no.
What we actually did
We spent two days, not two hours. We reconciled the risk assessment against the shipped design, confirmed the PCB revisions were cosmetic and didn’t invalidate the EMC report (they didn’t, but we wrote down why), and built one indexed technical file: design and drawings, standards and justification, the three test reports, the risk assessment, and the Declaration of Conformity on top. Dan signed it. Then, and only then, the UKCA mark went onto the product and the box, with CE alongside it for the small EU run.
Three months later a retailer’s compliance team did ask. Dan forwarded the file inside the hour. That email is the entire reason the file exists. A mark is a promise you might have to keep at short notice, and the file is how you keep it. We pushed for the two days up front precisely so that afternoon was boring.
— Engineer stage, project notes, 2026
— Next stage → Stage 08 · Develo