How I work
Compliance work,
done the modern way
Trace Core runs the same written checks on every service and learns from every submission. The work is faster and more precise, and I sign off everything that leaves Trace.
30 minutes. Free, with no obligation.
Trace Core
A system of written checks
Experience from inside the test house and the certification body, written down as checks that run the same way on every job.
-
The requirements
What each certification body asks for, by route and by product category.
-
The written checks
The same checks, in the same order, on every document set and every product page.
-
Reviewed feedback
Assessor comments from previous submissions, reviewed before any of them becomes a check.
How a document set is prepared
Four passes before
anything leaves Trace
Your product information and evidence go into Trace Core. The set is built and checked there, then it comes to me.
-
Pass 1 of 4 · Trace Core
Preparation pass
I take your product information and evidence into Trace Core, which builds the document set from it. Missing information becomes a question to resolve.
-
Pass 2 of 4 · Trace Core
Countersigner pass
Reads the set the way a certification body would: what supports each statement, what has been missed, and whether the documents agree.
-
Pass 3 of 4 · Trace Core
Signatory pass
Checks, as a certification body’s signatory would, that every open question and review comment has been addressed before the set reaches me.
-
Pass 4 of 4 · Glen signs off
Final release
I read the work, resolve the technical judgement calls and approve its release.
Why keep preparing documents by hand?
Every check in Trace Core is work I used to do by hand. Written down and run the same way every time, it is faster and it does not drift. My time goes on the judgement calls.
Based on my experience assessing and preparing technical files, I estimate this approach cuts document preparation time by 75% compared with preparing the documents manually. Assessing a file properly takes hours. Writing it properly takes longer. I still review the finished work.
I wrote the long version up: where a compliance team’s knowledge lives.
Adaptive learning
Each submission
informs the next
Assessor feedback is reviewed before it becomes a preparation check. Product-specific comments stay specific, and wider lessons are carried into future work where they apply.
-
What Trace Core keeps
Which body asked for what, and on which route. Which comments come back, and why. Each lesson records its source, the body or route it applies to, the date, the reviewer and its exceptions.
-
What it never keeps
Your product information, test reports, certificates and commercial details. They stay with your job and never enter shared learning.
The line
Will it ever sign off on its own? No.
Nothing inside Trace Core approves, decides or certifies anything. Trace Core prepares and checks. I make the technical judgement calls and I sign what leaves Trace. Missing evidence becomes a question to resolve, never a gap filled in.
Read the AI policyThe next step
Let’s look at
your product.
Tell me what you're working on. Two or three sentences is plenty.
30 minutes. Free, with no obligation.