Evidence management for importers

Turn scattered product records into oneconnected evidence file.

Connect product details, applicable requirements, testing, supplier records and decisions in one traceable Product File.

Explore guided demo Try the file sorter

EN71_test_report.pdf

BOM.xlsx

DoC

Supplier · email

Stacking tower “Lumi”

Children’s toy · ages 1–3 · Great BritainFILE-2026-0488

Inbox4

EN 71-1 · Mechanical & physical

Test report · laboratory

Strong

Product identity

Supplier specification

Needs review

EN 71-3 · Migration of certain elements

Test report · laboratory

Strong

EU Declaration of Conformity

Declaration record · CE route

Reviewed

Importer / product traceability

—

Missing

Product evidence

Supplier records

Open gaps

Decision history

Overview

Five building blocks of a reviewable evidence record.

Build one structured file

Keep product, supplier, market, requirements and evidence connected.

Missing

See what is missing

Expose missing, outdated or disconnected evidence immediately.

Collect from suppliers

Request specific records and keep every response attached to the requirement.

Decision

Recorded

Record the decision

Preserve who reviewed what, the outcome and the rationale.

Prepare for review

Create a structured evidence pack for review, handover or response.

Structure

One product.
One evidence record.

Bring product details, supplier records, applicable requirements, evidence and decisions into one Product File.

Everything connected

Records stay tied to the product and requirement they support.

One current view

Teams work from the same structured evidence record.

Built over time

The Product File retains its history as evidence, suppliers and decisions change.

Product File

Overview

Evidence

Requirements

Suppliers

Requests

Decisions

Activity

Stacking tower “Lumi”

FILE-2026-0488 · Children’s toy · ages 1–3 · Great Britain

In review

Supplier

Guangli Toys Co.

Target market

Great Britain

Requirements

AEN 71-1 · Mechanical & physicalStrong

BEU Declaration of ConformityReviewed

!Importer / product traceabilityMissing

Assessment

Not every document provides the same evidential support.

See which records provide independent support, which are declarations or contextual records, and where evidence is still missing.

Evidence assessment describes what a record supports. Review status shows what your team has concluded about that record.

Requirement

Evidence

Source

Assessment

Status

Mechanical & physical safety

EN 71-1 test report

Laboratory

AStrong

Reviewed

Declaration of Conformity

DoC

Manufacturer / importer record

BDeclaration

Review

Product identity

Supplier specification

Supplier

CSupporting

Review

Migration of certain elements

—

DGap

Action needed

Tracking label

Artwork

Importer

CSupporting

Review

Strong · independent test evidence

Declaration · traceable supporting basis

Supporting · contextual record

Gap · missing, stale or disconnected

See how a connected Product File comes together.

Explore a pre-filled Product File, review its evidence and follow the path from an open gap to a recorded decision.

Explore guided demo Try the file sorter

Gap detection

See the gaps before they become a problem.

dossierwerk separates document presence from actual evidence coverage.

A present document may still be insufficient.

Missing evidence stays visible.

Every open issue has an owner.

Requirement coverage

67%

8 of 12 evidence areas covered

Open items

EN 71-3 test report incomplete

→ Migration of certain elements

Importer / product traceability record missing

→ Product traceability

Declaration not linked to supporting evidence

→ Supporting basis

Collection

Turn an evidence gap into a precise supplier request.

Request specific records, assign due dates and keep the full exchange connected to the Product File.

Gap identified

A missing evidence item is selected.

Request prepared

Product, requirement and request context are pre-filled.

Supplier responds

The supplier opens a focused upload room.

Evidence reviewed

The submission returns to the same evidence area for review.

“Please provide the current laboratory report for product variant LUMI-04 covering the evidence area identified in this request.”

Suppliers see only their request Every submission traceable The full exchange stays with the Product File

Judgement

Store the reasoning, not only the result.

Record what was reviewed, the outcome, what remains unresolved and the rationale behind the decision.

Decision recorded FILE-2026-0488

Proceed with conditions

Decision owner

Jordan Lee · Compliance

Date

22 May 2026

Evidence considered

AEN 71-1 test report AEN 71-3 test report BEU Declaration of Conformity CSupplier specification

Rationale

Core test evidence reviewed. Importer / product traceability record remains an open pre-shipment condition.

Open condition

Importer / product traceability record must be reviewed before shipment.

Traceability

Reconstruct how the file reached its current state.

Uploads, requests, reviews, changes and decisions remain visible in one chronological activity history.

12 May

Supplier specification uploaded

14 May · Jordan Lee

EN 71-3 evidence assessed as incomplete

15 May

Additional report requested

19 May · Supplier portal

Laboratory report received

21 May

Evidence assessment updated

22 May · Jordan Lee

Product decision recorded

EN 71-3 · migration of certain elements

Current state

Decision recorded

22 May · Jordan Lee Product decision recorded

Change control

Reuse what still applies. Reassess what changed.

When a supplier, material, product variant or production detail changes, see which evidence still applies and which areas need another review.

Evidence area

New supplier

Material change

New product variant

Product identity

Review required

Reusable

Review required

Toy-safety testing

Review required

Retest review

Review required

Chemical testing

Review required

Retest review

Review required

Declaration of Conformity

Update required

New record required

Importer / product traceability

Update required

Reusable

Update required

Reusable

Update or retest required

Review required

New record required

dossierwerk structures evidence reuse and change review. It does not determine whether new testing, conformity assessment or updated documentation is legally required.

See how a connected Product File comes together.

Explore a pre-filled Product File, review its evidence and follow the path from an open gap to a recorded decision.

Explore guided demo Try the file sorter

Output

Share a reviewable file—not a folder of PDFs.

Assemble selected evidence, assessments, decisions and known limitations into an evidence pack for an authorised recipient.

Selection

Product identity

Evidence index

Decision records

Internal notes — excluded

Evidence pack

Product identity

Supplier details

Evidence index

Requirement coverage

Decision records

Known limitations

Activity history

Select what leaves the system

Keep internal deliberations private

Preserve context around every record

Process

One continuous evidence process.

1Collect

Bring records together.

2Structure

Connect evidence to product and requirement.

3Assess

Understand what each record supports.

4Resolve

Close evidence gaps.

5Decide

Record judgement and conditions.

6Share

Prepare the evidence pack.

7Maintain

Keep the Product File current.

Structure

Connect evidence to product and requirement.

Principles

Built for reviewable decisions — not document storage.

Evidence over document volume

More files do not automatically create a stronger evidence record.

Judgement over black-box scoring

The system structures the review; accountable decisions remain with your team.

History over snapshots

A reviewable Product File shows how evidence and decisions changed over time.

See how a connected Product File comes together.

Explore a pre-filled Product File, review its evidence and follow the path from an open gap to a recorded decision.

Explore guided demo Try the file sorter

Gap

Request

Evidence

Decision

Evidence pack

{{ c.hero_h1a }}{{ c.hero_h1hl }}{{ c.hero_h1c }}

{{ c.rail_h2 }}

{{ c.rail_c1_t }}

{{ c.rail_c2_t }}

{{ c.rail_c3_t }}

{{ c.rail_c4_t }}

{{ c.rail_c5_t }}

{{ c.oif_h2a }}{{ c.oif_h2b }}

{{ c.ev_h2 }}

{{ c.foot_h2 }}

{{ c.gap_h2 }}

{{ c.sr_h2 }}

{{ c.dr_h2 }}

{{ c.ec_h2 }}

{{ c.mr_h2 }}

{{ c.foot_h2 }}

{{ c.cs_h2 }}

{{ c.pb_h2 }}

{{ c.pp_intro }}

{{ c.pp_1t }}

{{ c.pp_2t }}

{{ c.pp_3t }}

{{ c.foot_h2 }}

Turn scattered product records into oneconnected evidence file.

Five building blocks of a reviewable evidence record.

Build one structured file

See what is missing

Collect from suppliers

Record the decision

Prepare for review

One product.One evidence record.

Not every document provides the same evidential support.

See how a connected Product File comes together.

See the gaps before they become a problem.

Turn an evidence gap into a precise supplier request.

Store the reasoning, not only the result.

Reconstruct how the file reached its current state.

Reuse what still applies. Reassess what changed.

See how a connected Product File comes together.

Share a reviewable file—not a folder of PDFs.

One continuous evidence process.

Built for reviewable decisions — not document storage.

Evidence over document volume

Judgement over black-box scoring

History over snapshots

See how a connected Product File comes together.

{{ c.oif_h2a }}
{{ c.oif_h2b }}

One product.
One evidence record.