Diego Torre

Former Notified Body evaluator turned independent consultant. I spent my career testing products, reviewing technical files and making certification decisions for electronics manufacturers. Now that experience works on your side.

The path

From the test lab to the certification decision

I studied physics and completed a master's degree in electronic technologies before entering this industry through the laboratory door: conducting tests on electronic products inside an ISO 17025 accredited laboratory. That is where you learn how products actually behave when they meet the standard for the first time, what breaks, what passes, and what the test report will say.

From there I moved into coordination: supervising test campaigns, developing new testing capabilities and acting as the technical interface between the laboratory and the manufacturer. That role included building the laboratory's UAS and drone testing service from scratch.

The next step was into the certification body itself, under ISO 17065. First as a technical evaluator, reviewing technical files, assessing product modifications, conducting factory audits, and supporting CE marking activities. Then as the director of the certification body, leading the team, managing the business, and representing the organisation in European Notified Body coordination groups and standardization technical committees.

Every one of those roles shaped how I think about compliance today. I did not study regulation from the outside and then offer advice. I was the person on the other side of the table: the one reviewing your technical file, running your tests, and deciding whether the evidence was sufficient.

Accredited Testing Laboratory

Test Engineer
Conducting tests on electronic products under ISO 17025.

Laboratory Coordination
Supervising test campaigns and developing technical capabilities.

UAS Testing
Building a drone testing service from the ground up.

Certification Body

Technical Evaluator
Reviewing technical files, product modifications, factory audits, and CE marking activities.

Certification Body Manager
Leading the team and managing certification operations.

Coordination and Standardisation
Participating in European coordination groups for Notified Bodies and technical standardisation committees.

Independent Consultancy

DUASCE
The experience gained now moves to the other side of the table: helping manufacturers prepare products and supporting evidence to demonstrate compliance.

Conformity assessment experience, working on your side

What makes this different

The difference between knowing the regulation and knowing the evaluation

Reading the directive tells you what the requirements are. Working inside the evaluation system tells you how those requirements are actually assessed: what gets questioned, what gets accepted, what triggers a deeper review. That second layer is where most compliance projects succeed or fail.

That is not a perspective you can acquire from training courses or from reading guidance documents. It comes from years of reviewing files, running tests, conducting audits, and making certification decisions.

Why DUASCE exists

The support that was missing

Inside the evaluation system, I saw the same pattern repeatedly. Manufacturers arrived at the laboratory or the Notified Body with products that were close to compliant but not quite there. Documentation gaps, missing test evidence, design choices that would force a failed campaign. Problems that could have been caught weeks earlier if someone with the right experience had reviewed the project before it reached the evaluation stage.

But a laboratory tests; it does not advise. A Notified Body evaluates; it cannot guide. And the consultancies that manufacturers hired to bridge that gap often lacked the inside perspective to anticipate what the evaluator would actually look for.

DUASCE exists to close that gap.

Three things you can expect

Direct access
One consultant, no intermediaries. You communicate directly with the person who has the evaluation experience and does the technical work. Questions get answered, not forwarded.

Technical honesty
If the product does not comply, you will hear it clearly and with the reasons behind it. If a proposed approach carries risk, I will say so.

Defined scope
Every engagement has a clear deliverable, a fixed or estimated cost, and a realistic timeline. No ambiguity about what is included and what is not.

I publish my professional code of ethics that governs every engagement: independence from laboratories and certification bodies, absolute confidentiality, honest technical assessments even when the conclusion is uncomfortable, and a formal complaint channel. It is available to anyone, client or not.

Now you know who you would be working with

If the approach sounds right for your needs, the next step is a call.
No cost, no commitment, real answers about what your product needs.