Services — Deep Dives
Category: offers
Sources: Services & Offers Notion hub — Route Finder, Certification Project, Range Review, Issue Support, Technical Ownership, Team Training deep-dive pages (fetched 2026-08-01), founder-interview-glen-2026-08-11.md, Glen live-editing session 2026-08-12 (motorcycle-deep-dive.html / ppe-document-workshop.html / ppe-foundation.html build), founder-brain-dump-ai-systems-reframe-2026-08-16.md, raw/ai-usage-notes-2026-08-18/ (00-Index, 01-Route-Finder, 02-Range-Review, 03-Certification, 04-Training, 05-Technical-Ownership), MASTER-BUSINESS-PLAN.md (Trace Launch project, fetched 2026-08-23 — current names, prices and service count)
Confidence: high
Last Updated: 2026-08-23
This article carries the narrative "why" behind each of Trace's eight services — why it exists, who it's really for, why the gap isn't already filled, the risk of not using it, and what happens next. For pricing tables, delivery scopes, and deliverable checklists, see Offer Architecture. This page is the working-specification layer underneath that architecture.
All eight services connect through one line: Trace helps a brand connect the exact product, the relevant evidence, the certificate and scope, the documentation and claims, the responsible person, the action required, and the next independent decision. See Ppe Buyer And Enforcement Context for why that connection matters commercially.
Every price on this page is public. Trace publishes prices on the ladder without exception — see the Publishing Rule in Offer Architecture.
On the "AI / Systems" note under each service below: these describe the systems vision — the deeper automation each service could eventually run on. None of it is built. The one live internal system is Trace Core, a deterministic product-and-evidence register with no AI in v1 (see Systems And Ai Stance). Do not read the AI/Systems notes below as a description of what a client experiences today, and never state or imply any of it is live in public copy, a quote, or a sales conversation.
Free Triage
Price: £0.
Positioning line: Fifteen minutes to find out if you're in the right place.
Why it exists: Pure pipeline entry for a visitor who is not yet sure they have a compliance question at all. Removes the cost of finding out.
Who it's really for: Anyone unsure whether their product counts as PPE, or whether Trace is the right kind of help.
What it entails: A literal 15-minute call, booked directly as a cal.com event — no form, no service page, no deliverable first. Purpose: qualification only. Is this PPE, is it in Trace's scope, and what is the right next step.
Boundaries: No written output, no technical opinion, no route mapping. That work starts at Route Finder or Range Review.
Best next service: Route Finder (a new or developing product) or Range Review (an existing range).
Second Opinion
Price: £395. The full £395 is credited against a Range Review booked within 60 days.
Positioning line: Someone else built the file. Find out if it holds up before you rely on it.
Why it exists: One service covering the situations that share the same underlying risk: relying on documentation nobody independent has read. That covers an independent review of the client's own product's technical file, vetting a supplier's or factory's evidence pack before the client relies on it commercially, and a pre-submission check for teams that build their own documentation and want it vetted at a lower cost than having Trace build the file.
Who it's really for: A brand about to rely on documentation nobody independent has checked — an inherited technical file, a supplier's or factory's evidence pack, or a file the team wrote itself and wants checked before a test house or certification body sees it.
Why the gap isn't already filled: A supplier or predecessor has every incentive to present their own evidence as complete, and a team that wrote its own file cannot read it the way an assessor will. Nobody currently checks it from the client's side before the client relies on it.
What it entails: A focused independent review of one product's file or evidence pack — technical file, factory- or supplier-submitted documents, labelling and markings, test reports and declarations — read with Glen's assessor experience. The written review names the issues and gaps before a test house or certification team receives the file, drawing on Trace's record of what individual certification bodies and test houses usually raise as findings or requirements. It ends in a written verdict plus a gap list. Not a full range audit — that is Range Review — not a certification decision, and never a guarantee of first-time acceptance.
Boundaries: Does not certify, does not issue a technical opinion carrying legal or certification liability, does not review more than the one product or pack specified, does not guarantee that testing or certification passes first time.
AI / Systems (vision — not built): The review runs on an assessment matrix covering the relevant parts of a file — evidence linkage, claims, labelling, declarations — and on an accumulated record of the usual findings and requirements of individual certification bodies and test houses, so each review starts from what the receiving body tends to raise. Glen reads every file with his assessor experience and signs off every verdict and gap list. Publicly this is presented only as Trace's experience and records — never named as a system, matrix, or AI.
Best next service: Range Review (the £395 credits in full within 60 days) if the same question applies across the wider range, or Certification Management if the file needs to be fixed and moved forward.
Route Finder
Price: £495. The full £495 is credited against Certification Management.
Positioning line: Know the route before you commit.
Why it exists: Route Finder is the first decision service for a brand bringing PPE to market. It exists to prevent a client committing money to testing, certification, documentation, or claims before the product route is sufficiently understood.
Who it's really for: PPE brands, founders, product-development teams, technical managers, quality teams, and compliance teams preparing to place PPE on the market — particularly motorcycle brands developing jackets, trousers, suits, gloves, footwear, or protectors. Not for businesses buying PPE for their workforce; Trace does not sell PPE.
Why the gap isn't already filled: Most providers become involved once a test house or certification body is already selected, or they give a general PPE-requirements briefing without mapping the route to the client's specific product, variants, claims, and evidence position. Route Finder sits earlier — an independent, product-specific decision service on the brand's side of the table.
Risk of not using it: Commissioning irrelevant or incomplete testing, building documentation against the wrong route, misjudging variant coverage, making unsupported claims, avoidable delays, or discovering late that the product can't progress as planned.
What it entails: A deliberately lightweight structured intake, completed by the client on a bespoke web page or hosted app: product type and category, target markets, claimed class or performance level (or an explicit statement that none is claimed), product images and/or a bill of materials, and any test reports, certificates, or impact-protector certificates already held. From that intake Route Finder delivers: confirmation of product family, variants, intended use, markets, claims, and current evidence; route and standards mapping with the logical test sequence (mechanical tests such as tear strength and seam strength first, abrasion and the remainder later, class determination early where no class is stated); a base price built from the standard test set and adjusted for the number of different constructions present and other variance factors, with colour/finish estimates where relevant; defined sample requirements; an initial risk matrix drawn from the test sequence, the claimed class or absence of one, and the evidence gaps; a review of uploaded evidence starting with the fastest-to-spot problems — report age, whether the laboratory sits on the accredited list, missing impact-protector certificates — with every gap logged into the report; lead-time estimates drawn from historical data for that product category; likely testing/certification/documentation/marking/IFU/claims requirements; key assumptions and open questions; product-family and variant boundaries; a practical next-step route map; and a pre-populated draft test-submission package in the submission-form variant the chosen test house requires, so handover into Certification Management, Range Review, Issue Response, or Embedded Support is clean and nothing is re-keyed.
AI / Systems (vision — not built): The Route Finder brain runs on every engagement — the intake-driven mapping, test sequencing, price and variance calculation, sample-requirement generation, evidence review, risk matrix, draft submission package, and certification hand-off are how the service is delivered, and there is no non-system version of it. Depth of evidence review scales with what the client uploads; the core route-mapping and pricing logic is always performed. Completed projects feed back anonymised, category-level patterns — actual prices, lead times, issues encountered, risks that materialised, construction-related variances — so future base prices, sequencing, risk matrices, and lead-time estimates get tighter; specific product detail, bills of materials, and one client's commercial pricing stay with that client. Glen reviews the mapped route, sequencing, and class and standard assumptions, adjusts pricing and risk weighting for commercial and client-specific factors, validates the evidence findings and missing-item list, decides which risk flags and lead-time estimates to temper or emphasise, and approves the route recommendation, sample requirements, and draft submission package before release.
Boundaries: The system does not set the final route recommendation or the commercial offer put to the client, judge whether a specific piece of existing evidence is acceptable for the intended certification path, fix the risk weighting or lead-time commitment given to the client, or interpret anything carrying certification or contractual liability. Whether to proceed with testing, and which test house is used, are human decisions.
Best next service: Certification Management (progressing a product) or Range Review (understanding an existing portfolio).
Certification Management
Price: £1,500. Repeat clients get a 10% discount on subsequent projects.
Positioning line: Move PPE certification forward.
Why it exists: Knowing the route isn't the same as having the time, structure, evidence, documentation, and follow-up capacity to move a project through testing and certification. Certification Management is the managed-delivery service for a product where the route is sufficiently understood.
Who it's really for: PPE brands, founders, product-development teams, technical/quality/compliance teams — particularly motorcycle apparel brands with a committed product but limited internal technical capacity. Not a PPE purchasing service.
Why the gap isn't already filled: Test houses and certification bodies perform their independent roles but don't act as the client's overall project coordinator. Generic consultants may advise on one element without owning the working rhythm across documentation, testing, certification, evidence, and actions.
Risk of not using it: Fragmented work, incomplete submissions, missed questions, repeated testing, unclear project ownership, slipping launch dates, or late evidence requests that could have been prepared earlier.
What it entails: Publicly, two entry points: full route coordination, or documentation-only support. (Testing-only and certification-only coordination exist as internal delivery scopes, offered case by case rather than presented as public choices — see Offer Architecture for current internal scope pricing.) Includes technical documentation build, test house liaison and test plan, and one round of corrections; test house fees and additional retest rounds are quoted separately, which keeps the fixed price honest instead of absorbing unpredictable third-party costs. Plus product-information/IFU/marking/evidence coordination, action and decision tracking, handover and maintenance requirements. Active projects get weekly status updates (position, completed actions, blockers, decisions needed, next steps) generated from the live project state rather than written up by hand, plus follow-up and chase communications to the test house or certification body driven off the same live data. The documentation set itself is generated bespoke for the exact notified body, test house, and — where known — individual assessor on that pathway: layout, content emphasis, supporting evidence, and document order are tuned to what that organisation actually wants and has accepted before, and known restrictions (for example a body that accepts only its own test reports) are flagged and checked against the submitted evidence before submission. Nothing starts from a blank template or a stock technical file. The finished file is the client's property — theirs to edit, archive, and reuse on future projects.
How Trace runs it (first-hand, 2026-08-11): Trace communicates directly with the client's factory under a mutual NDA, so the client does not have to relay everything and nothing discussed is ever shared. Submissions use Trace's own high-spec sample submission form, built from years on the receiving end of poor ones, so a motorcycle submission carries everything a test house needs in one pass (material names, protector names, article numbers, bill of materials) rather than coming back for missing detail. Trace is not loyal to one certification body and selects from the whole pool based on which fits the project, then absorbs the certifier's comments (some are normal on any submission) and replies until the file holds. The close is a thorough handover: responsibilities, final documents, and how to file the record so it stands up if anyone ever asks. The modular options (documentation-only, testing coordination, certification coordination) let a client who has done part of the route themselves bring Trace in for the rest, for example checking and vetting their self-organised testing before Trace builds the documentation and certification package.
AI / Systems (vision — not built): The Evidence & Documentation brain is used on every Certification Management project following the full route plus documentation model — generation, checking, learning, and the automated status and chase layers are core to the service, not an option. (The internal testing-only and certification-only variants use a narrower subset of the same capability.) It runs identity-matched gap analysis, flags aged or mismatched evidence, generates the instance-specific documentation set tuned to the chosen route, compares submitted evidence against known body and assessor expectations, and drives the live status and chase communications. Each comment cycle is ingested, so the next generation for that body or assessor class anticipates common comment themes and attracts fewer comments over time. What is retained for learning is body and assessor behaviour and documentation expectations — requirement patterns, comment themes, document-set preferences, restrictions — never one client's product IP pushed into another client's file. Glen reads every generated set in full, rejects, corrects, re-sequences, or rewrites anything that falls short, decides completeness and readiness, and signs the technical file. That signature is Glen stating he has checked and owns the content; it is never an AI signature or an automated approval stamp. The brain never invents test results or issues documents in Trace's name.
Boundaries: The system does not give final technical or commercial sign-off, decide whether a specific piece of evidence is acceptable in a specific instance, interpret ambiguous regulatory or assessor language carrying legal or certification risk, change the client's product claims or risk assessment without human review, or decide whether a certification body's comment is accepted or challenged.
Best next service: Embedded Support (ongoing maintenance) or Issue Response (if the project becomes urgent or hits a defined problem).
Range Review
Price: £150 per product, no setup fee, no minimum. Second Opinion's £395 credits in full against a Range Review booked within 60 days.
Positioning line: Know what to keep, fix, or remove.
Why it exists: To give a PPE brand a reliable view of what it has, what supports it, what's missing, and what should happen next across an existing or inherited product range. Not limited to new development — supports range maintenance, consolidation, retirement, relaunch, and certification-cycle prep.
Who it's really for: Established, live, inherited, or expanding PPE ranges — founders, product leaders, technical managers, quality/compliance teams, commercial leaders deciding what to keep, fix, update, consolidate, pause, or remove. Particularly relevant to motorcycle apparel brands with multiple products, models, variants, certificates, and technical files.
Why the gap isn't already filled: A normal document review confirms files exist, not whether the right evidence is connected to the right product, or whether the range still makes commercial and technical sense. Range Review combines portfolio triage, product-identity matching, evidence mapping, claims review, and forward planning in one exercise.
Risk of not using it: Continuing to invest in weak products, retaining unsupported claims, missing certificate/test-evidence renewal points, discovering too late that reports don't support a new application, or losing time maintaining products that should be consolidated or removed.
Product identity matching: Products are identified through name/model/style/SKU, brand and manufacturer, photographs/drawings/specifications, certificate number/type/annexes/scope, technical-file references, DoC product references, protection category/standards/claims, and known variants. Where documents can't prove two records relate to the same product, the item is marked uncertain and the client is asked to confirm — the review records confidence, it does not assume sameness from a name alone.
What it entails: Range Review is one public service, priced at £150 per product with no setup fee and no minimum: a structured current-state review covering identity, evidence presence, certificate/DoC status, IFU/marking, claims, gaps, decisions, and forward calendar. Test evidence older than five years is flagged as requiring replacement testing for any product needing a new certification application, unless the certification body confirms it can be accepted.
(Superseded 2026-08-24: this service previously had a £500 setup fee and a separate "Deep Product Review" tier at £350/product, offered only after the main review flagged a product. That structure is retired. Range Review is now one flat £150-per-product price.)
The review starts from a deliberate foundation step: the client's technical files, certificates, test reports, Declarations of Conformity, and related evidence are ported into a structured folder set, linked to specific live products, and cleaned. Nothing downstream is reliable without that linkage. The client also supplies the markets each product is sold into (CE, UKCA, or other), and may supply commercial context — relative volume, strategic importance, or sales ranking.
On that cleaned foundation the review delivers: orphan-product detection, flagging items that appear in the commercial range with no linked current certificate or technical file as high hidden risk; expiry interlinking that reads certificate and test-report dates and calculates the downstream consequence, so a certificate expiring in twelve months whose supporting test report has already lapsed is shown as retesting required at renewal, with the elevated risk and cost that carries; a prioritisation matrix ranking products into those that can safely remain, those needing immediate attention or further information, candidates for removal or major redesign on compliance grounds, and those that will generate the highest future cost; claim verification, checking claims made on certificates against the technical file and test reports and cross-checking those certified claims against current public and marketing statements where they can be reached; a recorded baseline of the public claims present at the time of review, so a later review can detect drift away from the certified claims; a standards-gap overlay identifying which referenced standards have been superseded or amended since the certificate was issued and which products may need gap testing or updated documentation at renewal; a multi-market consistency check where a product carries more than one mark, confirming evidence and claims stay coherent across them; horizon-scanning flags for products affected by known upcoming regulatory change; a renewal schedule for every retained product giving the target renewal date and a recommended start-of-submission window, typically six months ahead, so the notified body can meet its own timelines; an assessment of whether Declarations of Conformity and related documents are publicly accessible — visible, downloadable, correctly linked, or missing; a volume-weighted view of the prioritisation where commercial data has been supplied, so the order of attack reflects commercial reality; and, where requested or appropriate, a living digital inventory hand-back — a clean structured index of product to current certificate to key test reports to next action date that the client maintains as their own single source of truth.
AI / Systems (vision — not built): The Range Review brain is used on every Range Review; there is no non-system version of the service. It does conservative product-to-evidence linking, deliberately preferring to flag uncertainty over assuming a match, then runs the expiry interlinking, orphan detection, claim verification, standards-gap overlay, multi-market consistency checks, horizon-scanning flags, public-document checks, renewal scheduling, and prioritisation, and drafts the report. Depth of public-claim searching and volume weighting scale with the data and links the client makes available; the core documentation-driven analysis is always performed. Learning retains generalisable failure modes and structural patterns only — how documentation sets fail, common expiry interdependencies, frequent claim mismatches, observed standards drift, which prioritisation signals work — never one client's range, certificates, commercial context, or claims. Glen confirms or amends the linkages and the cleaned foundation, reviews every prioritisation decision and the risk and cost logic behind it, validates the claim, standards-gap, multi-market, orphan, and horizon flags, approves or revises the renewal schedule and recommended actions, decides which insight layers are emphasised or tempered for that client, and signs off the report — his signature stating he has examined the evidence and owns the recommendations.
Boundaries: The system does not make the final Keep / Fix / Pause / Remove or redesign decision, judge whether a claim discrepancy, standards gap, or multi-market inconsistency is commercially acceptable or must be corrected, set the commercial weighting of risk against business importance, decide whether an orphan product is removed or remediated, interpret anything carrying legal or certification liability, or sign off the report.
Best next service: Embedded Support (ongoing maintenance and responsibility), or the parked Compliance Control concept (see Offer Architecture / Proposed Services).
Issue Response
Price: triage first, then priced by severity level — Contained (L1, £495, 2 working days), Urgent (L2, £795, 1 working day), Critical (L3, £1,250, 4 hours). L1 and L2 are always billed outside Embedded Support retainers; a retainer never silently absorbs incident work.
Positioning line: Get PPE issues under control.
Why it exists: A live product problem often can't wait for a full Route Finder, Range Review, or retainer decision. Issue Response is the urgent-intervention service for a defined PPE compliance problem.
Who it's really for: PPE brands and the technical, quality, compliance, and commercial people responsible for products being placed on the market — especially motorcycle apparel brands, but can support other PPE categories where Trace has suitable capability and evidence. Typical triggers: a product about to ship, stuck in testing or certification, a marketplace challenge, a supplier-document problem, a product change, or a potential recall/regulatory response.
Why the gap isn't already filled: A test house or certification body answers questions within its own role but doesn't coordinate the client's full response across product identity, evidence, documentation, claims, actions, commercial pressure, and communication. Issue Response is a focused technical intervention, not open-ended hourly consultancy.
Risk of not using it: Shipping or continuing to sell a product with an unresolved concern, an incomplete response, a missed corrective action, a weak marketplace response, a delayed certification project, or unnecessary escalation.
What it entails: All issues arrive in writing — there is no phone route, by design: the issue has to be written down anyway, and written intake beats a frantic call. From the written intake, Trace defines the issue, product scope, evidence available, urgency, decision required, and immediate containment needs, then classifies it to a severity level. Common issue types the service covers: a failed or disputed test, a certification body raising unresolved questions, a marketplace or distributor challenge, a supplier-document or evidence problem, a product change of uncertain effect on an existing file, and a recall or regulatory response. Trace then provides a written position, action plan, evidence review, coordination, and next steps proportionate to the severity level. A recall or regulatory response includes defined technical support and coordination — it does not include legal advice, regulator representation, or an independent recall decision. The public page maps each severity level to common example issues so clients can self-classify before booking; L3 has an emergency booking route.
Boundaries: Exceptional entry route, not a guaranteed-resolution service. No legal advice; no control over regulator, marketplace, test-house, or certification-body decisions.
AI / Systems (vision — not built): The Issue Response brain drafts a conservative position paper, action list, and boundary language under time pressure. Glen reviews every draft for over-confidence, strengthens caveats in his own voice, and owns the position delivered. The brain speeds the first structured response; it does not speak for Trace without human sign-off.
Best next service: Certification Management, Range Review, or Embedded Support once the immediate problem is controlled.
Embedded Support
Price: From £750/month, built from the client's own selection against a fixed task menu. There is no entry-tier "Watch" plan.
Why it exists: For PPE brands that need continuing technical and compliance capability without immediately hiring a full-time internal specialist. A defined responsibility model, not a loose bank of consultancy hours.
Who it's really for: Established PPE brands with an active range, recurring product changes, ongoing evidence/certification responsibilities, or regular new products in development — especially motorcycle apparel brands needing a consistent technical point of ownership.
Why the gap isn't already filled: General consultancy retainers often sell access or hours without making the client's responsibilities clear. Embedded Support is structured around outputs, decision support, product volume, and ownership boundaries rather than time.
Risk of not using it: Compliance work stays reactive; knowledge is lost when staff or suppliers change; the business is too small for a full-time hire but too dependent on one internal person or too busy to maintain evidence, certification calendars, documentation, and external follow-up.
The task menu: every client configures their own package from the same fixed list of tasks, priced individually and summed against a £750/month floor.
| Task | What it covers | Price |
|---|---|---|
| Technical Q&A | Any team member can ask quick technical questions, at any time | Included, unlimited |
| Second Opinion | Review of documentation the client's team is preparing or has submitted, factory reports, certification body comments, test failures, and product development decisions. The existing Second Opinion service, now also available inside a retainer | Flat monthly fee |
| New documentation | Glen creates technical documentation for a product from scratch, using his standard process and templates. The client submits it themselves. The client picks how many sets a month | Per set, by band: Small £855, Medium £700, Large £600 |
| Organisation | Glen manages testing and certification submissions directly with test houses, certification bodies, and factories, including matters already in progress when the client joins. Weekly project status update | Flat monthly fee |
| Forward planning | A half-day planning session with Glen: new and existing products, timelines, costs, tests required, renewal schedules. Bookable once every 3 months while active | Flat monthly fee |
| Range Review | The client nominates products each month for a full Range Review: verdict, risk, and costed next actions per product | £150 per product |
Second Opinion, New documentation, and Organisation are each sized behind the scenes from one fact the client already knows: how many products the business handles a year. This never appears to the client as a formula. New documentation and Range Review are both priced directly instead: the client states a number, the price is that number times the per-unit rate (New documentation's rate varies by band, Range Review's does not).
What it entails: Set-up turns a scattered documentation state into a clean structured foundation, and the retainer keeps it current. Inputs are the client's existing product list, certificates, test reports, technical files, and any registers or folders they already hold; certificate scopes, expiry dates, and related metadata; mechanical and material test reports that may be reusable across products; the preferred reporting rhythm (weekly or monthly) and communication channels; optionally, volume or strategic ranking of products; and ongoing updates as new certificates, reports, and changes arrive. What is built and maintained: a living product register holding each product, its certificate scope, linked test reports, and current status; a real map and database of products against certificate expiry dates, generating a certificate calendar with configurable expiry alerts, typically at nine, six, and three months ahead, pushed into the client's preferred channel; documentation organised into a clean searchable structure; a cross-referencing system with a dedicated re-use register, linking mechanical and material test reports to every product for which they remain valid; a shared real-time task and status view, so completed work and open tasks are visible without waiting for the periodic report; the agreed weekly or monthly report covering tasks completed, tasks still open, and a soft utilisation insight showing capacity used against the agreed allowance, so both sides can see whether the level of support is right; a filtered vigilance digest of market-surveillance findings, recalls, and common failure modes relevant to the client's product categories and standards; a documentation-health overview rating the register as complete, partial, or critical gaps; a full change log and audit trail of every update to the register; and, when a certificate approaches expiry, a pre-populated Route Finder or Certification Management intake so the renewal project starts with clean data and nothing re-keyed. The client ends with a single, always-current source of truth for their products and certificates.
(Superseded 2026-08-24: this paragraph describes register and calendar features from the earlier Watch-tier model. The current commercial structure is the task menu above; this vision content is retained as a description of the underlying system, not as active pricing mechanics.)
Naming history: Technical Ownership → Compliance Continuity → Embedded Support. Embedded Support is the current, final name.
Boundaries: Does not replace the client's legal, regulatory, product, or commercial accountability. No certificates issued, no independent testing, no guaranteed certification or market access. Normally begins with a Range Review so the starting product, evidence, responsibility, and risk position are understood. The system does not decide whether a certificate or test report is still valid for a given product or market, interpret a market-surveillance finding or recall, change the client's product claims or risk position, settle the final content of formal reports or renewal recommendations leaving Trace, or decide whether the client should move to a larger or smaller configured package — that stays a human conversation. Issue Response L1/L2 always sits outside the retainer.
AI / Systems (vision — not built): The Embedded Support / Intelligence brain maintains the living product register, certificate calendar, documentation structure, cross-reference and re-use register, real-time task visibility, periodic reporting with the utilisation insight, vigilance digest, documentation-health overview, change log, and renewal hand-off, and drafts conservative impact assessments from calendar and standards-change signals. Depth of vigilance filtering and channel integration scale with the client's product set and preferred tools; the core register and calendar capability is always delivered. Learning retains anonymised category-level patterns only — how registers are structured, common cross-reference opportunities, typical expiry behaviours, frequent documentation gaps, which vigilance signals prove useful for a category — so each new engagement starts from a stronger template; the client's own register, certificates, and commercial data stay theirs. Glen approves the initial register structure, cross-reference rules, and calendar settings, reviews every impact rating and any vigilance or documentation-health flag needing professional interpretation, decides the content and emphasis of each report and what reaches the client, signs off formal outputs leaving Trace, and owns the ongoing technical position. The brain does not own the client relationship or final advice.
Training
Price: Half-day from £750, full day from £1,250, complete pathway 10% off. Prices are interim, flagged as such on-site, until a ground-up costing of the course content replaces them. (Session-level prices below — £750/£1,750/£1,500 — are the confirmed per-session figures behind that "from" range; the pathway price is £3,500, a £500 saving against booking separately.)
Positioning line: Build PPE capability.
Why it exists: Most PPE brands run on one person who can read a test report properly; when they are busy, on holiday or gone, decisions wait or get guessed, new starters learn by osmosis, the factory's reassurance goes unchallenged, and the same submission mistakes repeat because nobody can say why they were mistakes. Training exists so that judgement stops being a single point of failure. The aim is not to turn everyone into a certification assessor: it is to build people who recognise what good evidence looks like, ask better questions and know when to stop or escalate — capability that stays inside the brand and improves every product decision that follows. An interactive learning and decision experience, not a presentation-led compliance course — delivered through Trace's own app-based training platform, designed around Glen's real-world experience of recurring issues, evidence gaps, and workable decision pathways.
Who teaches it: Glen, from the side of the table that asks the difficult questions — experience across test-house testing, test-team leadership, documentation assessment, certificate issuance and commercial delivery. He has spoken at motorcycle PPE seminars and delivered bespoke training for industry-leading brands; their names remain private, the method does not. The public framing of the boundary: training does not replace independent testing, certification-body assessment, or the client's responsibility for its products and market decisions — it replaces the guesswork in between.
Who it's really for: PPE product-development teams, technical/quality/compliance teams, new starters, teams overly dependent on one specialist, brands wanting internal PPE champions. Motorcycle PPE Training is specifically for motorcycle protective-apparel brands — Trace should not present it as training across every PPE category.
Why the gap isn't already filled: Generic courses teach regulatory or technical requirements in a presentation or self-guided format. Trace's training is built from Glen's direct experience of recurring issues, weak evidence, test-house and certification-body questions, documentation failures, and workable decision pathways.
Three sessions (course structure and depth confirmed by Glen 2026-08-08, naming standardised 2026-08-12). Format for all three is individual or group, with Glen — never "one-to-one": the constant is that Glen personally delivers it, not headcount.
- PPE Foundation Training (£750) — half a day, delivered remote: for brand-new PPE businesses or anyone starting from zero. Organised around what's the client's to own and what genuinely isn't — what a certification body does, what the factory is responsible for, where responsibility sits regardless of who else touches the product. Terms and process only, not the documentation itself. Does not train specialists.
- PPE Document Workshop (£1,750) — full day, in person wherever possible: covers the client's whole documentation set, not just the technical file — the Declaration of Conformity, the IFU, the marking, and how they cross-reference each other and the product they belong to. Uses the client's own documentation as the base, then works through real scenarios, issues and roadblocks interactively, updating the set as each one resolves, so it becomes a real, championed, brand-owned record the team understands and can reproduce, not a document copied from a template. Also covers how the set should be stored for readability, and the update process for minor product modifications: what needs a full re-review versus what just needs the notified body told and the file updated on record. Reviews what the factory is actually supplying and whether it holds up as usable certification evidence; teaches how to read a test report for credibility, not just presence. Intended outcome, in Glen's own framing: a team of submission experts who own the documentation, can reproduce it for the next product, and can challenge a certification comment that is not warranted, because they know their own file inside and out. Raising the first-time submission acceptance rate is the underlying commercial driver — certification bodies cannot advise, and assessor responsiveness varies, so waiting on their explanation is not a plan.
- Motorcycle PPE Training (£1,500) — full day, in person wherever possible: built entirely from the client's own physical products, not a generic example. Motorcycle PPE has one governing standard per product type (garments: EN 17092, gloves: EN 13594, protectors: the EN 1621 series), so the real skill is not choosing between standards, it is knowing what is inside the one that applies: why each requirement exists, not only the mechanical tests, which ones are most often missed or done wrong, and which class or level actually applies and when (Glen, 2026-08-27; see Standards Coverage). Also covers what a previous test result can genuinely be reused for across variants or a product change, versus what actually forces a retest, a distinction Glen flags as one of the most commonly missed judgement calls in the industry. Participants read a real garment, glove or protector against its own bill of materials so every material, seam and component maps to the test it needs, alongside the common design flaws in a technical motorcycle garment, the typical fixes and the considerations that avoid them. Test-request building and test ordering run as one activity ("handling testing"): preparing a real test request from a selected product (material names, protector references, article numbers, test-house instructions) and deciding the order that keeps testing cost-effective, not just fast. Failure handling sits here too: a failed result is not automatically fatal, and the session works a task list to establish whether it is a genuine failure or whether another route avoids an unnecessary garment change. Also covers evidence review, reframed 2026-08-27 as reading and cross-referencing rather than just matching: interpreting a test report the way an assessor does, for what it actually proves rather than that it exists, cross-referencing it against the product, the materials and the other reports supporting it, and comparing it with factory evidence, including cases where a factory has reused a report and the product name does not match, what that does to certification, and how to route around it. Also covers when a factory's reassurance is not enough on its own and the team needs to push back rather than accept it. The intended outcome, in Glen's own framing (founder interview, 2026-08-11), is a team that operates as test-submission experts: the products understood inside out, why each component is tested, and the most effective test plan built before money is committed, so the client can handle the next submission themselves. Public copy for this session must stay strictly motorcycle-specific (standards by garment type, construction, evidence-to-product matching) — generic certification-process hurdles (factory documentation reliability, submission delays, notified-body review findings) belong on PPE Document Workshop instead, not here.
- Complete pathway (£3,500): saves £500 against booking separately.
How a client-specific session runs: Before — short product intake (types/families, claims, current standards/certificates, variants, known issues, questions); Trace maps the relevant standards pathway so the client isn't charged for irrelevant standards. During — one-to-one with Glen through five stages: product route, evidence review, decision pathways, client product application, practical action plan. Before also takes the client's own list of common or recurring issues where they supply one, plus product-level detail for their range, so scenarios walk through the client's actual physical products rather than generic examples and no time is spent on irrelevant material. After — short action summary covering routes discussed, relevant standards, key decisions, evidence/documentation gaps, questions needing external confirmation, and recommended next actions, plus two Q&A sessions of up to one hour each, bookable when needed after the main session at no additional charge, for the follow-up questions the session itself generates.
Interactive platform: The interactive platform is the delivery model, not an enhancement to it. Every Training delivery runs on it, together with the continuous learning loop from live projects — there is no non-interactive or purely static version of the service, and Trace does not sell Training without the platform ready. It carries scenario-based exercises, evidence/documentation activities, decisions and feedback, product/range context, practical pathways, progress tracking, facilitator review points, and reusable content structures. Participants engage with the scenarios, see the consequences of different choices, and take away concrete next steps. The session structure stays consistent across clients while the content inside it is filtered to the client's product set and stated issues.
Boundaries: Training does not replace independent testing, certification-body assessment, legal advice, or the client's responsibility for its products and market decisions. No identifiable client data, project detail, or source situation is ever exposed to another client — every scenario is reworked into fully anonymous form before it can be used. Scenarios are never theoretical or invented; only patterns that have actually occurred and been observed are eligible. The system does not decide the professional framing, the correct reading of a grey area, or the final teaching points, and it does not replace live delivery or the post-session Q&A with automated answers.
AI / Systems (vision — not built): The Training Scenario brain continuously ingests live project outcomes and interactions from across the full chain — factory production issues, certification-body, notified-body and test-house comments, buying and commercial decision points, documentation knock-backs, control failures, evidence gaps, common misunderstandings — filters them until the original source is untraceable, and converts them into structured scenarios mapped to the relevant product sets, so a motorcycle session draws only the patterns that apply to that category. It surfaces expert reasoning points, the wrong terminology people commonly use and precisely why it is wrong, the underlying principles behind the correct approach, and the practical next action when the situation recurs, and it prepares facilitator debrief notes. The scenario pool grows richer and more precise with every completed project, so preparation shortens while sessions stay grounded in current reality. Glen selects and frames which patterns become scenarios, checks the reasoning and the links back to Trace principles, approves the final scenario set for each delivery, decides how far a client's pre-submitted issues shape the mix, and delivers or oversees every session and Q&A. The brain accelerates scenario preparation; teaching and the relationship remain Glen's.