Voice Guide

Category: voice Sources: trace-summary-services-icp-competitors-background.md, live-service-sop-summaries.md, Glen tone direction (2026-08-04), founder-interview-glen-2026-08-11.md, founder-interview-glen-2026-08-11-part2.md, founder-brain-dump-ai-systems-reframe-2026-08-16.md, elon-musk-x-style-tone-voice-design-guide-2026-08-16.md, MASTER-BUSINESS-PLAN.md (Trace Launch project, fetched 2026-08-23 — the core tone statement and the extended banned-word list) Confidence: high Last Updated: 2026-08-23

Core Direction

Master plan statement (final): the tone is honest — straight to the point, plain, engineer-direct, with a hint of Glen's warmth. No corporate fluff, no rhymes, no aphorisms, no balanced-clause slogans. If a line sounds quotable, it is probably wrong.

Trace's voice, everywhere — client communication, service descriptions, SOPs, and every public page — is a capable, opinionated, high-agency person explaining something important directly to another intelligent person. Confident without arrogance, ambitious without empty hype, precise without being clinical, human without being sloppy. Inspired by the Musk/X communication approach (Tesla, SpaceX, xAI); see Website Redesign Direction for the fuller website-specific detail.

• Restrained, not decorated — no unnecessary decoration, no corporate fluff, no persuasion mechanics standing in for substance
• Product and mission primacy over persuasive rhetoric — the work and the method do the convincing
• Short, clear, declarative language — the simplest accurate words, said plainly
• Ambition grounded in demonstrated capability or first-principles logic — bold claims stay tied to the reasoning or evidence behind them
• Respect for the reader's intelligence and attention — no hand-holding, no padding, get to the point
• Calm competence with quiet intensity — confident and forward-looking without sounding breathless or salesy; serious without being self-important
• Personality added after content is secured, never before — the substance comes first; voice and creative texture layer on top of it, not in place of it

Tone

• Direct and precise — says what something is and what it is not, without hedging or overselling
• Technically confident — uses correct terminology naturally, not to impress
• Honest about boundaries — repeatedly clarifies what Trace does and does not control
• Practical over theoretical — focuses on what happens next, not abstract principles
• Calm authority — no hype, no inflated claims
• Operationally disciplined — scope, responsibility and unknowns are stated, not implied

This tone governs everywhere: direct client communication, service descriptions, SOPs, delivery documentation, and every public page. There is no separate persuasion-licensed register for public marketing copy — the same restraint and precision apply throughout.

Public Page Voice: Glen Talking

This governs every public page on tracetechnical.co.uk. The test: Glen talking, not a company writing. Plain, specific, occasionally dry, and willing to say what it cannot do.

1. Open on the visitor's own sentence, not the service name. The first thing on a page is what they would actually say out loud.

"The samples went in weeks ago and nobody can tell us where they are." "We cannot say which report belongs to which product any more." "Our new starter has never seen a technical file before."

2. Name consequences honestly, without inflating them. The quiet version is more believable than the dramatic one.

"The launch date moves, quietly. Nothing has failed. It is simply nobody's job to chase, so a week becomes a month and the season it was built for goes past." "It reads fine until a distributor reads it properly."

3. Refuse to invent numbers. Say so out loud rather than reaching for a statistic.

"I am not going to invent a figure for what a second test round or a missed season costs you. You already know it."

4. State boundaries as credibility, not disclaimer. The limit is the proof.

"I am not a test house and not a certification body, which is exactly why I can tell you what they are going to say before they say it." "If it turns out you do not need me, I will say so. It happens more than you would think."

5. First person, with credibility carried by story rather than claim.

"Hi, I am Glen. I am the one your team used to chase for test results, or certificates." "For most of my career I was on the other side of your emails, which means I have been the bottleneck."

6. Dry rather than jokey, and only in the margins. Never the main event.

"Do not get in touch if you genuinely enjoy: chasing a test house for an update you were promised last week... I do not mind any of it, which is either useful or a bit sad." "Better me, on a quiet Tuesday, than a distributor on a deadline." "This page does not exist. At least it is honest about it."

7. Lower the effort of getting in touch. Ask for less, and say so.

"Two or three sentences is plenty." "Send the product, not a tidy version of it." "Now the boring bit" — the label above the name and email fields, which come after the actual problem.

8. Never ask people to self-qualify. No "a strong fit when" lists. Each page states who it is for at the top ("For a product with a defined route that has stopped moving"), and the Services page says outright not to sit and work out which one applies.

Person: I, Trace, and we

"We" meaning the business is the single fastest way back into company-writing, and a one-person consultancy saying it invites the question of who else is there. The positioning depends on it being Glen. The footer strapline "You build protection. We clear the route." is the one sanctioned exception: a strapline may speak as the brand.

Communication Patterns

• Defines scope clearly: "Trace prepares and coordinates the route. It does not issue certificates or control the independent certification decision."
• States limitations honestly: "Route Finder is not a certificate, test result or guarantee of certification."
• Uses concrete deliverables over vague promises: "The client receives a clear, costed route and decision plan."
• Distinguishes between what is usable, what is missing and what creates risk
• Marks unknowns explicitly rather than smoothing over gaps: TBC convention
• Uses one consolidated request rather than drip-fed asks
• Records external decisions accurately — never strengthens their wording
• Prefers structured output: action plans, ordered priorities, defined responsibility

Signature Phrases

• "clear, costed route"
• "defined responsibility"
• "organised evidence"
• "practical help"
• "what is usable, what is missing, what creates the greatest risk"
• "a practical view of the range rather than another unprioritised spreadsheet"
• "fixed-fee" (recurring emphasis on cost certainty)
• "the connection between product, evidence, certification and claims"
• "TBC" — for anything unknown, unverified or low-confidence
• "separately scoped" / "separately quoted" — for work beyond the defined engagement
• "verified sources" — technical decisions backed by approved standards
• "do not discount; reduce scope if necessary"

Founder Lines and Analogies (First-Hand)

From the founder interview (2026-08-11). Glen's spoken register: blunt, plain, occasionally exasperated at the industry, always landing on a practical point. Echo the shape and directness of these rather than quoting verbatim, and anonymise any that name a real brand or body before public use.

• The buffer. Trace is the independent buffer in the middle, between the brand, the test house and the certification body, on the brand's side of the table. "I want to be that buffer in between, make people's lives easier."
• On the certifier's limits. "You cannot rely on a test house to spot it for you. It is not their responsibility, and I do not blame them." Independent checks exist precisely so testing and certification stay separate.
• The certificate as proof. For a startup, a certificate is the biggest flex there is: "we cared enough to spend the money before we even launched, here is the proof." The easiest marketing win a new brand has.
• The champion document. The technical file should be the brand's own champion document, one they built, own and understand, not a skeleton copied from a notified body. "If a standard asks you a question, how can you explain it if you don't even know what's in it?"
• Do it once. "Do it right the first time, pay someone to do it, and you reap the reward." Test and certification is expensive, and that is the point.
• On waste. The money spent redoing tests "may as well have just paid me." Repeat testing that was never needed is the most frustrating thing in the industry.
• On lead time. "Certification bodies owe you nothing. They do not owe you the privilege of skipping a queue because you didn't understand what a lead time is."
• On accountability. "Ignorance isn't a defence." One injured person in an untested product, and there is nothing to stand behind.
• On being modern. "We need to be fast, smart, and use technology where we can." Not an old-fashioned technical file drawn up the way it was forty years ago.
• Trust is the moat. "Trust is the one and only thing that's keeping us all in a job." What Glen wants a client to feel after any call is simply "I trust this guy." It cannot be faked: a consultant with no technical depth is found out.
• Cut the waffle. "We take a whole mess and streamline it." Trace knows exactly what it does, does not do every consultancy job under the sun, and does not need to shout about it. Simple and to the point.
• Independent by design. "I'm completely independent, my fees are fixed. I'm not paid more if there's a retest. I want it done efficiently and properly." A test house has a reason to want you to spend more. Trace does not.
• It's actually easy. The real myth is that certification is impossibly hard. "It's actually really easy when you know what you're doing," with the right documentation and methods. Glen has put certificates and testing through in a few weeks.
• What nobody tells you. Test houses and certification bodies are not a government service acting in your interest. They each have their own commercial intentions and ways of working. And assessor inconsistency is human variation, not proof you did something wrong.

Banned Phrases

These hold everywhere, including public marketing copy:

• "Guaranteed certification" or any language implying outcome certainty
• Hype words: "revolutionary", "game-changing", "world-class"
• Vague promises: "we'll take care of everything", "leave it to us"
• "Unlimited" (retainers are defined responsibility, not unlimited access)
• Rhymes, aphorisms, and balanced-clause slogans — if a line sounds quotable, it is probably wrong (master plan, final)
• Corporate-consultancy jargon: "seamless", "peace of mind", "end-to-end", "trusted partner", "hassle-free", "solutions", "leverage", "cutting-edge", and similar
• Strengthened external decisions (never overstate what a certification body said)
• "Gear" — use "apparel" (e.g. "motorcycle apparel", not "motorcycle gear")
• "Paperwork" — use "documentation"
• "Lab" — use "test house"
• Em dashes (—) — use a full stop, comma, colon, or parentheses instead
• "File" when referring generally to Trace's work or deliverables — use "documentation". Use "technical file" only when explicitly referring to the formal technical record for a product.
• "Protective products" — use "PPE products"
• Invented facts: fake statistics, fabricated scarcity/countdowns, false certification claims (see Ppe Claims And Product Information Risk)

Overselling is banned everywhere, including public copy — there is no persuasion-licensed exception. Direct client communication, service descriptions and delivery documentation, and every public page, all underclaim and over-clarify boundaries.

How Complex Ideas Are Explained

The pattern is: state what it is, then state what it is not, then describe the practical output. Complexity is resolved by specificity, not simplification.

Example: Route Finder is described by listing exactly what the client learns (9 specific items), then explicitly stating what it is not (not a certificate, test result or guarantee).

The SOPs follow the same pattern: purpose → what's included → what's excluded → delivery stages → output → stop conditions. Every service has explicit boundaries.

Systems / AI Language Rule

AI is a quiet capability, never a headline or a marketed feature (master plan, final). The live system is Trace Core — a deterministic product-and-evidence register, no AI in it yet. "Trace Brain" and "the Brand system" are dead names, never used. Do not describe Trace Core, or anything else, as AI-powered, trained, or a brain until it actually is one.

The longer-term "trained systems" / brain vocabulary in Systems And Ai Stance describes a future roadmap, not what exists today — do not use it in public copy, a quote, or a sales conversation while it remains unbuilt.

The test, for whenever AI is genuinely in use: could a reader interpret this as Trace throwing client files into a generalist AI tool, the way any generalist or con artist would? If yes, the wording has failed and must be rewritten.

Required framing once AI is live: "Systems accelerate expert judgement. They do not replace it." Every public mention states what the system drafts or surfaces, and states that Glen reviews it and owns the final output. Never describe a system deciding, issuing, or advising on its own. The public AI policy page (signed, three paragraphs, linked from footer/About/relevant services, never the homepage) carries the fuller promise: AI never decides compliance, never produces or alters evidence, and nothing reaches a client Glen has not thought through himself.

Related Articles

• Origin Story
• Values
• Primary Icp
• Content Strategy
• Delivery Methodology
• Systems And Ai Stance
• Website Redesign Direction
• Ppe Claims And Product Information Risk
• Banned Words