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.
Check a document before you create it
On the website, the last step of the RAMS, CPP, site induction and toolbox talk wizards checks your answers before you create the document. The panel is headed Suggestions to improve your document. Each suggestion names the wizard step it belongs to and has an Edit button that takes you back to that step. When the check finds nothing at all, the panel says Looks good -- no issues found. The Site Book app's wizards do not show this panel.
On every plan, the panel lists each required section you left empty. On Starter, suggestions about vague wording or a brief section are not listed: one locked line under the list counts them, for example "2 more suggestions: 1 section reads as generic, 1 looks brief". Pro and above list every suggestion with its Edit button.
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
Re-check did nothing and my score stayed the same. Why?
Our AI service has a daily usage limit. When it has been reached the check cannot run, and nothing is overwritten: the document keeps the score and suggestions it already had, and a document that has never been scored shows no score pill yet. Open the document and click Re-check → again later. The limit is a rolling daily one, so it frees up again as earlier use ages out.
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.
Who can run the score check on a team account?
On a Business or Site Control team an owner or admin runs and re-runs the check, including on a document for a job a colleague created: the score pill checks itself when they open the document, and Re-check → sits at the bottom of its expanded panel. A member only reads the score: the pill appears once an owner or admin has run the check, its panel lists the suggestions but has no Re-check → button, and a document nobody has scored yet shows a member no pill at all.
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
Not using The Site Book yet? Start your first job free.
Start free →Didn't answer it? Email [email protected] — we'll get back to you by email.