Picture a business with five sites. Maybe it's a building company with crews on three projects and a yard, or a manufacturer with two plants and a couple of distribution depots. Each site has a good supervisor. Each site does its inspections. And when someone at head office asks a simple question, like "did every site do its monthly inspection, and what did they find?", it takes a week of emails to answer.
One site sends a scanned PDF. Another sends a spreadsheet with its own column names. A third says the folder is on the site office computer and they'll get to it on Friday. The fourth uses a different checklist that's longer, which is great, except nobody can compare it with the others. The fifth didn't get the email.
None of these sites is doing anything wrong. The problem is that "one safety standard" usually only exists in a policy document. On the ground, every site has quietly built its own version.
What head office actually needs
It's tempting to think head office needs everything: every form, every photo, every signature, in real time. In practice, the people responsible for safety across several sites need answers to a handful of questions, and they need them without chasing anyone:
- Did it happen? Was each scheduled inspection done, at each site, when it should have been?
- What was found? Which items failed, and what did the inspector write about them?
- Is it the same everywhere? Is a "pass" at one site the same as a "pass" at another?
- What keeps coming back? Is the same fault turning up at the same site month after month, or at every site at once?
Notice what's not on that list. Head office doesn't need to edit a site's forms or rewrite its findings. It needs to see, compare and ask good questions. The site still owns the work.
Start with one checklist, not five
Consistency starts with the form itself. If every site inspects against its own list, you can't compare them, no matter how good each list is. Agree one core checklist that every site uses. Keep it short enough that people actually fill it, and specific enough that "OK" means the same thing everywhere.
Our Inspection Checklist template is a good starting point because it covers the basics most sites share: who inspected, when, whether PPE is available, whether fire extinguishers are in place, whether exit signs are visible, whether the spill kit is stocked, and notes for any fault found. Sites can add a few items of their own at the end, such as racking at a warehouse, scaffold at a construction site, or guarding at a manufacturing plant. The core stays the same.
A few rules make the shared checklist work:
- Same wording everywhere. "Fire extinguishers" means present, charged and accessible at every site, not just "there's one somewhere".
- Required fields for the things that matter. Inspector name and date shouldn't be optional. A record without them doesn't prove much.
- A note for every fault. A missing tick says something is wrong. A note says what, where, and what happens next.
- Photos where words fall short. A blocked exit or an empty spill kit is clearer in a photo than in a sentence.
Let sites run their own patch
The fastest way to kill a group-wide safety process is to make every site wait on head office. Site supervisors know their people, their hazards and their schedule. They should be able to share a fill link with their own crew, add the inspectors they need, and see their own results without asking permission.
It also matters that sites can't see each other's records. Branches and subsidiaries often have different clients, different contracts and different people. A site manager should be able to review their own team's findings honestly without worrying that another branch is reading over their shoulder. Keeping each site's data private makes people more willing to write down what they actually found.
Make the record land somewhere useful
Paper checklists and emailed spreadsheets fail for the same reason: the record ends up wherever the person who filled it happened to put it. When inspectors fill the checklist on a phone at the site, the record lands in one place straight away, with the date, the name, the ticks, the notes, the photos and the signature attached.
From there, each site's admin can open Reports, filter by form or date, and export a PDF for the site file or a CSV for a spreadsheet. If an auditor or client turns up asking for last quarter's inspections, the site can answer in minutes instead of digging through a drawer.
What to look for once the records are flowing
With one checklist and records that land in one place, head office can finally do the useful part. A monthly look across sites usually tells you more than any single inspection:
- Gaps. A site with no inspections for three weeks is a conversation worth having early.
- Repeat faults. The same spill kit flagged as empty four months running isn't an inspection problem. It's a restocking problem.
- Outliers. A site that never records a single fault might be the safest site you have. It might also be ticking boxes from the office.
- Group-wide patterns. If exit signage fails at three sites in the same month, it might be worth one central fix rather than three local ones.
The goal isn't to catch anyone out. It's to spot the things a single site can't see from where it stands.
Seeing every site without taking over
This is where most multi-site setups get stuck. Either head office gets a login to every site and ends up able to change things it shouldn't, or it gets nothing and goes back to chasing emails.
In FormSafely, each site, branch or subsidiary can run as its own organisation, with its own admins, forms, submissions and CRM records. We can then link those organisations under a parent. Head office admins get one read-only view of every sub-organisation's forms, submissions and customer records, labelled by site. Sites keep full control of their own work, and they still can't see each other. If that sounds like your setup, email hello@formsafely.com and we'll link your organisations.
Whichever tools you use, the order is the same: agree one checklist, let each site run it, and make sure the records land where the people responsible for every site can actually see them.