We train your team on your own reports. Send us one anonymised report before the first session and we open by drafting one in your house format, live, in front of your people. Your template, your language, your standards. Not a demo on a made-up example.
Three sessions, two hours each, spread across five weeks — with practice on live jobs in between. The spacing is deliberate. People only keep what they use, so between sessions your team works on real reports and brings the problems back.
Session one — from site notes to a first draft
We start with your own report. Voice memos, scribbled site notes, photos on a phone — and a structured first draft in your house format by the end of the session. Your team leaves able to do it themselves on the next job.
Session two — QA and the mistakes that reach the client
Using AI as a second reader. Catching the section carried over from a previous report, the photo from a different site, the wrong-project reference, the US spelling. We work on real drafts your team produced in the fortnight between sessions.
Session three — one house style, and where AI stops
Standardising output so the report reads the same whoever wrote it. Referencing the standards and regulations you work to, with citations you can check. And the boundary: judgement, rating, sign-off, liability and authority stay with your professional, every time.
What your firm keeps
The training ends. These don't.
- A prompt pack built around your report types, not generic examples
- A house-style guide your team writes to, and AI checks against
- A short written summary of what we found and what to do next
What we need from you
- One anonymised report before session one
- Your report template, if you use one
- Two hours per session from the people who actually write the reports
That's it. No IT project, no procurement, no new system to roll out.
Twelve months of follow-up, included
The training doesn't end when the third session does. You get four follow-up sessions, one every three months for a year — 30 minutes each, with the same people.
They exist because of what happens after training. New starters join. Someone hits a report type we didn't cover. A tool changes and the thing that worked in March stops working in June. A quarterly check-in catches all of that before it turns into the team quietly drifting back to old habits.
Each one is short and practical: what's working, what's slipped, what's new, and one thing to fix before the next call.
No extra cost. It's part of the programme.