Rolling Out an EHS System to 50+ Sites: A Group Playbook

Choosing an EHS system for a group is the easy part. The hard part is getting fifty, eighty or two hundred sites, in several countries and languages, to stop using their own binders, spreadsheets and chat groups and to record their safety work in one place, the same way, every day. Rollouts rarely fail on technology. They fail when a site manager does not see why the change matters, when the night shift was never trained, or when the old spreadsheet quietly stays in use next to the new system.

This guide is written for group and regional EHS directors, HR and operations leaders who own that rollout. It covers what ISO 45001 expects when you change how safety work is done, a pilot-then-waves plan, the people model that makes it stick, a readiness check for every site and how to measure adoption.

Why big rollouts stall

The same patterns show up again and again in multi-site programmes:

The change is announced, not explained. Sites hear that "head office has a new system" but not what problem it solves for them.
Every site wants its own version. Local forms, categories and risk matrices are copied into the system, and group data still does not add up.
Training reaches the office, not the floor. Supervisors and workers on rotating shifts, and contractors, are missed.
Two systems run in parallel. The old register is kept "just in case", so nobody fully trusts either.
Nobody owns adoption after go-live. The project team moves on and usage slowly drops.

None of these is a software problem. Each one is a change-management problem, which is why it pays to plan the rollout as carefully as the selection. If you are still choosing a system, start with our enterprise EHS software RFP checklist.

What ISO 45001 expects when you change the system

A new EHS platform changes how hazards are reported, how incidents are investigated and how actions are tracked. For sites certified to ISO 45001, that is not just an IT project. Three parts of the standard are directly relevant:

Consultation and participation (clause 5.4). The standard asks organizations to consult non-managerial workers on matters such as implementing, monitoring and evaluating the management system, and to let them participate in hazard identification, incident investigation and deciding corrective actions. A rollout that changes those processes is a natural topic for safety committees and worker representatives, before go-live, not after.
Competence and awareness (clauses 7.2 and 7.3). Workers must be competent to identify hazards and aware of how to report them. If the reporting channel changes, the training and awareness records must change with it.
Management of change (clause 8.1.3). Changes to work organization, processes and working conditions are to be planned and reviewed so that new hazards are not introduced. Treat the switch from paper to a digital system as a planned change: what happens to reports raised during cut-over, who covers sites without connectivity, and how you check afterwards that nothing was lost.

HSE GB's guidance Managing for health and safety (HSG65) frames the whole system as Plan, Do, Check, Act. The rollout plan below follows the same loop: plan with the sites, roll out in controlled waves, check adoption and data quality, then adjust before the next wave. For the clause-by-clause view, see our ISO 45001 software page.

Pilot first, then roll out in waves

A "big bang" go-live across fifty sites leaves no room to learn. A wave plan does:

Phase	Scope	Goal	Exit criteria
0. Design	Group EHS, IT, data protection, two or three site representatives	Agree the hierarchy, common forms, categories, risk matrix and KPIs	Definitions signed off; site list and owners per site
1. Pilot	One country or business unit, two to five sites of different types	Prove the standard works on real shifts	Agreed measures met (see below); issues logged and fixed
2. Wave 1	Sites closest to the pilot in language, process and culture	Repeat the pilot playbook with local champions	Readiness check passed before go-live; adoption measures met for a set period
3. Further waves	Remaining countries, grouped by region or business	Scale with less central effort each time	Same as wave 1; old registers formally closed
4. Run	All sites	Keep the standard and improve it	Adoption reviewed in management review; change requests through one owner

Two rules keep waves on track. First, the standard is set once, at group level: sites can add local scenarios or checklists, but categories, severity scales and KPI definitions stay common. Our playbook on standardizing HSE reporting across countries explains how to agree that dictionary. Second, a wave does not start until the previous one meets its exit criteria. A late wave costs weeks; a failed wave costs trust.

The people model: sponsors, champions and the floor

Change-management models such as Prosci's ADKAR describe the sequence each person goes through: awareness of why the change is needed, desire to take part, knowledge of how to change, ability to do it in daily work, and reinforcement so it lasts. In a multi-site EHS rollout that translates into clear roles:

Executive sponsor. A COO, regional head or group EHS director who explains why the group is changing, attends wave kick-offs and asks about adoption in operational reviews.
Site lead. Usually the site manager, accountable for go-live and for closing the old registers.
Site champions. One or two trusted people per site, ideally including a supervisor from the floor, trained first and given time to help colleagues. Champions from the pilot help train the next wave.
Safety committee and worker representatives. Consulted on the new reporting process and asked for feedback after the first weeks, in line with clause 5.4. In Bangladesh, factory safety committees are a natural forum; see our guide to safety committees in Bangladesh.
Contractors. Included in the plan from the start, with a simple way to report hazards and near misses. Our contractor safety guide covers the wider controls.

Training should be short and role-based: a worker needs to report a hazard with a photo in under a minute; a supervisor needs to review and assign; an investigator needs the full workflow. Train every shift, in the languages people use, and record it like any other competence.

A readiness check for every site

Before each site goes live, the site lead and the central team confirm the basics. A site that cannot answer "yes" to most of these is not ready, and that is fine: it moves to the next wave.

Site, departments and areas set up in the hierarchy, with the right people in each scope.
Users created for every role, including shift supervisors and contractor coordinators.
Open incidents, actions and inspections from the old system listed, with a decision on what is migrated.
Training delivered on every shift; champions named and available.
Phones or shared devices available where reporting happens; a fallback for areas with poor connectivity.
A cut-over date after which the old forms are withdrawn and archived.
Safety committee or worker representatives briefed and consulted.

Data and migration: what to bring across

Migrating every historical record is rarely worth the effort. A practical rule is to bring across what people still act on, and to archive the rest so it can still be found:

Migrate: open corrective actions, open investigations, current risk assessments, training records with expiry dates, equipment and inspection schedules.
Summarize: historical incident counts and hours worked needed for trend KPIs, so year-on-year comparisons still work.
Archive: closed paper records, kept according to your retention rules and local law.

Personal data in incident and health records needs the same care during migration as in daily use. Agree with your data protection officer who may see what, and check your vendor contract; our guides on role-based access in EHS software and the data processing agreement with an EHS vendor cover both.

Measuring adoption, not just go-live

A site that "went live" but records nothing has not adopted the system. Track a small set of adoption measures per site and per wave, and agree them before the pilot:

Active users by role, compared with the number expected.
Reports per month (hazards, near misses, incidents), compared with the site's history. Expect near-miss and hazard reporting to rise when reporting gets easier; that is usually a sign of better visibility, not a worse site. Our guide to leading and lagging safety KPIs explains how to read those numbers.
Time to close actions and the share of overdue actions.
Inspections completed against plan.
Old-register use: are paper forms still being filled in after cut-over?

Review these in the same meeting as safety performance. When adoption is discussed next to incident data, sites treat it as part of running the business, which is the reinforcement step most rollouts forget.

Rollout checklist

#	Item	Done
1	Executive sponsor named; reason for the change written in one paragraph that sites understand	☐
2	Group hierarchy, forms, categories, risk matrix and KPI definitions agreed once	☐
3	Rollout treated as a planned change (ISO 45001 clause 8.1.3), with cut-over risks reviewed	☐
4	Workers and representatives consulted on the new reporting process (clause 5.4)	☐
5	Pilot sites chosen to cover different site types; success measures agreed in advance	☐
6	Waves planned; each starts only when the previous meets its exit criteria	☐
7	Champions named at every site; role-based training on every shift and in local languages	☐
8	Migration rule agreed: open items migrated, history summarized, closed paper archived	☐
9	Data protection officer involved on access scope and the vendor contract	☐
10	Adoption measures reviewed per site, next to safety performance, after go-live	☐

Where AccelSafety fits

AccelSafety, our enterprise HSE software, is designed for this kind of rollout. Every site sits in one organizational hierarchy, from group to region, country, cluster and site, so a new wave joins the same structure and its results compare from day one. Access is scoped to each user's part of the hierarchy and enforced on the server, while approvals, reviews and configuration stay with the roles you choose, which keeps the group standard in one place. Workers and supervisors report from their phones with photos; incidents and investigation, hazards and near misses, risk assessment, actions and CAPA, audits and inspections, training and competence, contractors and visitors run the same way at every site, with work grouped by ISO 45001 clause. Group dashboards for lost days, near misses, hazard reports, recordable injuries and training manhours drill back to the auditable records behind them. Moving from paper? Our paper to digital HSE plan covers the first site. Book a free demo to plan a pilot with a structure like yours.

General information, not legal advice. Check the current text of ISO 45001 and local law for your sites.

Rolling out an EHS system to 50+ sites: change management that sticks