Start Here

Two terms,
in plain English.

Compliance runs on acronyms, and these are the two this page is about. If you already work with them daily, skip the next thirty seconds.

TCF
Technical Compliance File
Available now

The dossier that proves your product meets the rules: product details, risk assessment, test reports, labelling and the Declaration of Conformity you sign. You need it before the product goes on sale, and you have to keep it for ten years after the last unit ships in case an authority asks. Without one you can't legally CE mark a product, and that's how shipments end up held at customs or pulled from shelves. Putting the file together is most of the work in getting a product to market, and it's what this platform is built to do.

DPP
Digital Product Passport
In development

A scannable digital record attached to a product covering its identity, materials, compliance data and what to do with it at end of life. The EU is phasing it in category by category under ESPR. Most of what goes into a passport comes from the technical file you already hold, which is why the two belong in one place. Our passport support is still being built, and there's a section further down explaining exactly where it stands.

The i-Comply Web App

An internal tool,
opened up.

Most compliance software is written by people who have never had to assemble a technical file under deadline. This one was built by the team that does it every week.

  • A structured, step-by-step technical file builder
  • One place for product data, test reports and declarations
  • A file for every product, in one account
  • Kept for the full ten-year retention period
Talk to us about access
Inside The File

Six sections,
in the order they're worked.

A technical file isn't one document. It's a dossier that a market surveillance authority can ask for at any point in the ten years after your last unit ships. The builder holds each part in its place, so you always know what the file should contain.

01
Product identification

Model numbers, variants, photographs, technical drawings and the bill of materials, plus the manufacturer, importer and any authorised representative. Everything else in the file hangs off this, because it's what ties the paperwork to one specific product.

02
Risk assessment

The hazards your product presents, how likely and how severe each one is, and what you did to control them. The app records how you got there, not just the conclusion, which is usually what an assessor wants to see.

03
Test reports and lab data

Reports filed against the harmonised standards they relate to, so the link between evidence and requirement is written down rather than carried in someone's head. Upload what you already hold, and we can coordinate testing for anything still outstanding.

04
Labelling and instructions

CE marking placement, warnings, age grading, pictograms and the user instructions, with the language versions each destination market expects. Labelling is one of the most common reasons a shipment gets stopped at the border.

05
Declaration of Conformity

Drafted from what's already in the file, listing every directive and standard applied. It carries your company's name and it's legally binding, so it's the last thing you write rather than the first.

06
Retention and retrieval

The file has to stay available for ten years after the last unit is placed on the market. That's long after the product is discontinued and the people who worked on it have moved on. It stays in the platform for the whole period, with its version history, and can be exported the day somebody asks for it.

The app gives the file its shape. You still bring the judgement.

This is a structured workspace, not an auditor. It won't tell you a section is thin and it won't declare a file finished. On a real project the information often isn't there yet, and an app that called your file incomplete on that basis would be wrong often enough that you'd stop reading it. What it does is hold the structure and show you what you've entered. You decide when a section is done, on the evidence you have. If you'd rather not make that call alone, our team will go through the file with you.

What It Does

What the app does
today.

A structured builder

A step-by-step workspace that holds every part of the file in its place, so you're not rebuilding the structure from scratch for each new product.

Storage that outlasts the project

Documentation in one secure place for the full ten-year retention period, instead of scattered across inboxes and the drive of whoever handled it at the time.

Every product, one account

A file per product or product line, all in the same place. Your second product starts from a structure you already know instead of a blank page.

A record of what changed

Versions are kept as the file develops. When a product is revised two years later, you can still see which report belonged to which specification.

Export the whole file

When an authority or a buyer asks, the file comes out as a package, rather than as a week of reconstruction from six folders and three people's inboxes.

Written by the people who use it

Every decision in the app came out of a real file our team had to get right on a deadline. That's what shaped the order things sit in and the questions it asks you.

In Development

The passport half
is being built now.

We're not going to tell you the Digital Product Passport is finished, because it isn't. The standards behind it are still being published, category by category, and the detail changes with each delegated act. We're building against them as they arrive, rather than shipping something now that has to be rebuilt in a year.

  • The file is the input A passport is assembled from information a technical file already holds: product identity, materials, conformity evidence. Building the file properly today is the work either way.
  • No second data-entry exercise The point of building both halves in one platform is that you enter your product once. When the passport requirement reaches your category, the data is already here.
  • We'll tell you where your category stands Obligations arrive on different timelines depending on what you make. That's a specific answer about your products, not something to read off a general page.
Ask about your category →
Drawing in progress
Two Ways To Work

Build it yourself,
or have us build it.

Self-serve
You build it

We set up your account and walk you through it, then you work the file at your own pace in the same structure our specialists use. This suits you if you have someone in-house who knows your products and needs somewhere organised to put the work.

Done-for-you
We build it with you

Our team prepares the file inside the same platform and does the chasing with your factories and the labs. At the end of it you have a market-ready file and the account it lives in, rather than a PDF and an invoice.

Questions

What clients ask first.

Will it tell me whether my technical file is complete?
No. The platform doesn't audit your file or flag sections as missing. On real projects the information often isn't there yet: a report is still at the lab, or a supplier hasn't come back. Treating that as a fault would put a warning on nearly every open file, which helps nobody. It holds the structure and shows you what you've entered. Whether the evidence is sufficient is your judgement to make, and it's the one our team can make with you.
Is the Digital Product Passport available today?
Not yet. It's in active development. DPP requirements are being introduced by product category and the specifications are still being published, so we're building the passport side as those arrive rather than guessing ahead of them. The technical file builder is available now, and the file you put together in it is the groundwork the passport draws on.
When will a passport be mandatory for my products?
It depends on the category and where you sell. The EU is phasing the requirement in group by group under ESPR, with the specifics set by delegated acts that are still being issued. Anyone who gives you one confident date covering all products is guessing. Tell us what you make and we'll tell you where your category currently stands.
Can I bring an existing technical file into the platform?
Yes. Most clients arrive with documentation spread across email threads, shared drives and supplier portals. You upload what you hold into the sections it belongs to and carry on from there rather than starting again. If parts of it need drafting or testing, our team can take those on.
Who can see my data?
You see your own files and only your own. i-Comply can see them as well, which is what lets our specialists pick a file up when you need us on it. Nobody else has access. No other client can see your products, and your bill of materials, supplier terms and costings go no further than the file they sit in.
What happens if an authority audits us?
You export the file and respond. Because it was all captured in a structured form as you went, there's no scramble to work out which test report belongs to which model, or which version of the instructions shipped. If the request gets technical, our team can respond alongside you.

See it properly.

Book a walkthrough and we'll show you the builder against one of your own products instead of a demo file.

Request a Demo →