The site-specificity score: prove your documents aren't templates
Available on all plans
Open any generated document — the score pill sits under the action buttons and checks itself the first time you view it. It's the difference between paperwork that reads like a template and paperwork that reads like *your* job.
Read the score
Look at the pill: ✅ above 70, 💡 for 40–70, ⚠️ below 40.
Click it to expand the suggestions.
Each one quotes the wording it's about — "your document says 'appropriate PPE' — try specifying which PPE" — or names the missing detail to add.
Fix the wording or project detail, then click Re-check →.
The score updates live. Suggestions that point at project-level gaps (like the nearest hospital) are fixed on the Details tab, then regenerate.
Why it matters
An inspector's first suspicion of generated paperwork is that it's generic. A high specificity score — site address, named people, real hazards, concrete controls — is your evidence it isn't. Every check is also logged against the document version, so the score travels with the audit trail.
Frequently asked questions
What do the score bands mean?
Above 70: "Tailored to your site" — good, with optional tips. 40–70: suggestions to strengthen the document. Below 40: things to review — usually missing site details or vague phrases an inspector would query.
What kind of things get flagged?
Vague phrases like "appropriate PPE" (which PPE?), a missing site address or access details, no nearest-hospital information, weak or generic controls. Each suggestion says what to change in plain English.
How do I act on a suggestion?
Edit the wording it points at — in the document editor or the underlying project detail it names — then click "Re-check →" on the score panel to re-score. The suggestions are guidance to apply yourself, not automatic rewrites.
Related guides
Didn't answer it? Email [email protected] — we reply within 24 hours.