Draft a product's technical file

The technical file for a product is drafted from its own record: the risk assessment and Annex I answers, the product's class and conformity route, its SBOM coverage, its listed security advisories, its reporting history and its modification decisions. What you wrote goes in as you wrote it; what Declara observed is labelled "Recorded by Declara"; anything missing stays a visible placeholder.

It is a draft. Signing a declaration of conformity is a legal act taken under your sole responsibility, after the conformity assessment it refers to has been carried out.

Before you start

• The Readiness Pack, or a plan that includes it. Without it the page says so and the record stays usable.
• The owner or an admin role.
• The more of the essential requirements record you have filled in, the fewer placeholders the draft has.

Steps

1. Open the product, then Essential requirements and risk assessment.
2. In Technical file, press Draft beside Technical documentation (Annex VII) or EU declaration of conformity (Annex V).
3. Press Download for the PDF.

Section 4 of the technical documentation, the determination of the support period, is written from the newest support period determination: the end date, the factors you answered and your reasoning. Where none is recorded, or the reasoning is missing for a period under five years, the section keeps a visible placeholder.

Drafting again makes a new version; the earlier ones stay readable as they were.

What you should see

Each document shows its version, when it was drafted, and how many fields are still to complete. Workspace-wide documents (the vulnerability handling process, the disclosure and SBOM policies) stay on Readiness.

Related

• Record the essential requirements and risk assessment
• Record a product's support period
• Shared responsibility