[Home](/)/[Resources](/resources)/Complete CE documentation bundle Document guideDoC / Technical file / Risk assessment # Complete CE Documentation Bundle: What Inspectors Expect to See A CE documentation bundle is not a pile of paperwork. It is the evidence system behind your CE mark. When a distributor, importer, Notified Body, or market surveillance authority asks for proof, the bundle should tell one clear story: this product was assessed, the right rules were applied, and the declaration is supported. Copy Link[Share on WhatsApp](https://wa.me/?text=https%3A%2F%2Fkrono-labs.com%2Fguides%2Fcomplete-ce-documentation-bundle) [Generate CE documentation bundle](/platform/start)[Start your project first](/platform/start) Free · no account required Problem ## The problem is not missing a document. It is missing the connection between documents. Teams often create CE documents one at a time: a lab report from the test house, a Declaration of Conformity from a template, a manual from product marketing, a BOM from procurement, and a risk assessment when somebody asks for it. Each document may look reasonable alone. The problem appears when they are read together. One document names the product differently. Another cites an old standard. The user manual omits a warning that the risk assessment depends on. The DoC claims a directive that the technical file never explains. The test report covers a prototype with a different antenna. This is how a documentation bundle becomes hard to defend. A complete CE bundle solves that by making the relationship between documents explicit. It turns compliance from scattered artifacts into a reviewable file. Requirements ## What belongs in the complete CE documentation bundle ### EU Declaration of Conformity The signed legal declaration that identifies the manufacturer, product, applicable EU legislation, harmonised standards, and responsible signatory. It should be concise, accurate, and traceable to the technical file. ### CE technical documentation The evidence file explaining the product, design, conformity route, standards, test evidence, drawings, instructions, labels, risk controls, and quality or production controls. ### Risk assessment A structured analysis of hazards, foreseeable misuse, severity, probability, mitigations, residual risk, and verification evidence. It connects design decisions to safety claims. ### Test and supplier evidence Lab reports, internal verification records, RoHS declarations, component certificates, battery reports, radio module evidence, and any supporting documents that substantiate conformity. ### Labels and user instructions CE mark placement, product identifiers, importer details where needed, warnings, installation instructions, safe use instructions, disposal marks, and model traceability. ### Change control record A clear record of how hardware, firmware, component, supplier, label, packaging, and intended-use changes are reviewed after launch. Process ## How to assemble the bundle without creating contradictions 01 ### Start with the product identity Define the exact product, model, variant, accessories, firmware version, photos, intended use, and sales region. Inspectors cannot assess a bundle if it is unclear which product the evidence belongs to. 02 ### Build the legislation matrix List every applicable directive or regulation, why it applies, the conformity assessment route used, and the evidence that supports each requirement. This is the spine of the bundle. 03 ### Attach standards and evidence For each standard, include the exact reference and version, the directive it supports, and the test or design evidence tied to it. Avoid orphaned reports that do not explain what claim they support. 04 ### Write the risk assessment as a decision record The risk assessment should show how hazards were identified, reduced, and verified. It should not read like a generic safety essay pasted into the file at the end. 05 ### Prepare the DoC last The Declaration of Conformity should summarize the finished evidence set. If the DoC is drafted first, it often lists standards or directives the rest of the file does not properly support. 06 ### Review for consistency before signature Check model numbers, manufacturer details, addresses, standard versions, directive titles, dates, labels, firmware references, and product photos across the full bundle. Consistency is audit armor. Inspector lens ## The questions your bundle should be able to answer quickly 01 Does the bundle identify the manufacturer and exact product without ambiguity? 02 Does the DoC list the same product, directives, and standards as the technical file? 03 Are harmonised standards current, relevant, and mapped to the right legislation? 04 Do test reports describe the same configuration that is being sold? 05 Is the risk assessment specific enough to explain actual design controls? 06 Are labels, warnings, user instructions, and traceability information present? 07 Can the company explain what changed since testing and whether that change was reviewed? 08 Can the file be produced quickly if an EU market surveillance authority requests it? Structure ## The structure is the advantage The reason to generate a CE bundle in Krono is not to make documents look tidy. It is to force the documents to agree with each other, expose gaps before signature, and give the reviewer a structured path through the evidence. ### Coherent cross-references A bundle is stronger when the DoC, technical file, and risk assessment agree with each other. Krono generates documents from one product workflow so references stay aligned instead of being rewritten three different ways. ### Review-ready, not blind-signature ready The goal is not to replace expert judgement. The goal is to create a structured draft your team can verify against real evidence before signature, reducing blank-page work and missed sections. ### Built around evidence gaps Good documentation should reveal what is missing. If a standard, test report, warning, supplier declaration, or risk control is unsupported, the bundle should make that visible before a distributor or authority does. ## Learn this properly, not just for one product In-depth courses and books that teach the process — not a one-off answer you'll need to look up again next time. [Browse courses](/courses)[Free roadmap tool](/platform/start) [Prefer to read? Get the book](/books) ## Frequently asked questions ### What is included in a complete CE documentation bundle? A complete bundle usually includes the EU Declaration of Conformity, technical documentation, risk assessment, test reports, standards list, product description, drawings, labels, instructions, supplier declarations, and change-control records. ### Do I submit the CE technical file before selling? For most self-certified products, no. The manufacturer keeps the technical file and must provide it to market surveillance authorities on request. Some high-risk products require Notified Body involvement before placing on the market. ### Can I generate CE documents before testing is complete? You can draft the structure early, but final documents should be reviewed against actual evidence before signature. Drafting early is useful because it reveals missing test reports, standards, labels, and risk controls. [ Map your product, free Every standard, document, and test that applies — free, no account required. Start mapping](/platform/start) Related guides * [CE marking overviewCE marking is a manufacturer's declaration that a product meets all applicable EU requirements.](/guides/ce-marking) * [How to build a CE technical fileComplete guide to building a CE technical file: template structure, required sections, evidence organization, and review-ready …](/guides/how-to-build-ce-technical-file) * [How to create a Declaration of ConformityStep-by-step guide to creating a legally valid EU Declaration of Conformity: required elements, common mistakes, and an example…](/guides/how-to-create-declaration-of-conformity) * [Risk assessment for CEComplete guide to CE risk assessment for hardware products: hazard identification, risk evaluation, control implementation, and…](/guides/risk-assessment-for-ce) * [CE marking checklist for startupsA practical CE marking checklist for hardware startups: identify directives, plan testing, build the technical file, prepare th…](/guides/ce-marking-checklist-for-startups) Generated documents are drafts for review. Your team must verify evidence, confirm legal scope, and sign only when the file is accurate.