Bespoke engagement
Technical File Build
I assemble the technical file an auditor can open.
Scoped per engagement
Evidence scattered across wikis, build logs and engineers’ heads does not survive contact with an audit. It has to live in one place, in a structure the auditor recognises, current for the release actually shipping.
Build is where that happens. I assemble the technical file to the CRA’s Annex VII structure, write the vulnerability-disclosure policy the PSTI regime expects, and — the part that outlasts me — wire the file into your release process so it updates when the firmware does, not when someone remembers.
What it covers
- CRA technical file, assembled to the Annex VII structure
- Vulnerability-disclosure policy, PSTI-ready
- Conformity documentation in one defensible pack
- Release-process wiring so evidence updates when firmware does
Worth scoping if
- A notified-body conversation or buyer audit has a date on it.
- The evidence mostly exists but lives in five systems and three heads.
- Nobody on the team owns “the file”, and everyone is hoping someone else does.
How it works
-
Scoping call
I map what exists, what Gather still needs to produce, and quote the assembly in writing.
-
Structure and drafting
The file skeleton goes up early so everyone can see where each artifact lands.
-
Review cycles
Your engineers correct the technical record; I keep the regulatory framing honest.
-
Handover and wiring
The finished file, plus the release-process hooks and checklists that keep it current after I leave.
Asked before scoping
-
Do you also fix the findings?
No — I do evidence, not remediation. Your team (or your contractor) makes the fixes; I make the fixes provable. That separation is deliberate: the party attesting to the file should not be marking its own homework.
-
Why is there no price on this page?
Scope varies too much for an honest rate card — it depends on how much evidence already exists and how many products share the file. You get a fixed written quote after a scoping call.
Scope the file
Bring whatever exists today — half-finished is normal. A scoping call sizes the rest.
Field notes
Join the list
One field — your work email. One email every two weeks.