ESOS qualification operates at group level, which sounds like a straightforward rule until you’re actually the one responsible for making it work across a business with multiple subsidiaries, several site types, and possibly overlapping management structures inherited through past acquisitions. A single-site organisation has one building, one set of processes, and one team to coordinate.

A group has all of that multiplied across every qualifying entity, and the compliance failures that occur in group ESOS assessments are almost never about the technical audit work itself — they’re about coordination breaking down somewhere in the gaps between entities.

This matters because the qualification rule itself is unforgiving on this point: if a parent company meets the ESOS thresholds, every UK subsidiary and group member falls within scope, regardless of whether that specific subsidiary would have qualified on its own. A group can be technically compliant on paper while one forgotten subsidiary, acquired eighteen months before the deadline, was never actually included in the scoping exercise at all.

Where Group Coordination Typically Breaks Down

• Subsidiaries acquired or established after the initial scoping exercise was completed, where nobody circles back to confirm the new entity has been folded into the group’s ESOS coverage
• Sites operating under different management structures or reporting lines within the same group, where responsibility for providing data to the central assessment process is unclear or simply assumed to sit elsewhere
• Different site types across the group — offices, warehouses, manufacturing facilities — each requiring different data collection approaches, with no single person holding the full picture of what’s needed from each
• Historical group structures that have changed through mergers or restructuring, where the current entity map used for ESOS scoping no longer accurately reflects the group as it actually exists today
• Site-level teams who don’t understand why they’re being asked for energy data, and deprioritise the request accordingly against their own local operational pressures

Why This Is Different From a Single-Site Problem

A single-site organisation that starts its assessment late faces a resourcing and timeline problem — genuinely serious, but conceptually simple. A group facing the same lateness is usually also facing a coordination problem layered on top, because the late start often reflects the fact that scoping the full group in the first place took longer than expected, or revealed gaps in understanding of which entities were actually in scope.

Fixing a timeline problem is a matter of application and effort. Fixing a coordination problem requires someone with genuine visibility across the whole group structure, which is often precisely the visibility that was missing in the first place.

The Data Consolidation Challenge Specifically

Beyond scoping, group assessments face a distinct data challenge: consolidating twelve months of energy, process and transport data from multiple sites, often held in different formats, by different local teams, with varying levels of completeness.

A single missing site’s data doesn’t just create a gap — it can undermine the assessment’s ability to demonstrate the required 90 percent coverage threshold across the group as a whole, turning what looks like a minor administrative oversight into a genuine compliance risk for the entire organisation.

Who This Actually Hits Hardest

• Groups that have grown through acquisition, where newly acquired entities weren’t formally integrated into the group’s compliance processes at the point of acquisition
• Groups with decentralised management structures, where individual sites or subsidiaries operate with significant autonomy and limited central oversight
• Groups approaching ESOS for the first time without a clear, documented entity map showing exactly which companies and sites fall within the qualifying structure
• Groups relying on a single central compliance function with no dedicated liaison at each individual site to actually gather and validate local data

Signs Your Group Coordination Is at Risk

• Nobody can currently produce a definitive, up-to-date list of every entity and site within your group that falls under ESOS scope
• Your group has acquired, sold, or restructured any entities since your last ESOS assessment without a formal review of how that affects your current scope
• Different sites within your group are at noticeably different stages of readiness when it comes to providing energy data
• There’s no single named individual with overall accountability for group-wide ESOS coordination, as opposed to individual site-level compliance

Getting group ESOS compliance right starts with an accurate, current entity map — not the one drawn up several assessment cycles ago — followed by a coordination process that gives every site clear expectations and a genuine deadline, backed by someone centrally who has the authority and visibility to chase gaps before they become a late-stage crisis rather than a manageable, tracked task.

Get Your Group ESOS Compliance Properly Coordinated Ecotilities manages ESOS scoping and data coordination across every entity in your group, closing the gaps that cause multi-site compliance to break down. Visit ecotilities.co.uk/esos or call 0333 2244 050.

 

Questions Groups Ask

How do we confirm exactly which entities in our group are actually in scope?

This starts with a proper group structure review against the ESOS qualifying thresholds — a task worth doing formally rather than relying on an outdated assumption from a previous cycle.

What happens if we’ve missed a subsidiary in a previous assessment?

This needs addressing directly and as soon as it’s identified — the priority is bringing the missed entity into compliance now rather than treating the oversight as something to worry about only at the next cycle.

Does every site within the group need the same level of assessment?

Not necessarily — the 90 percent coverage threshold allows some flexibility, but this needs to be calculated properly across the group rather than assumed site by site.

How do we get site-level teams to actually prioritise data requests?

Clear communication about why the request matters, realistic deadlines, and visible senior sponsorship from group level all help — this is as much a coordination and communication challenge as a technical one.

Can one Lead Assessor cover a group with very different site types?

Often yes, provided they have the breadth of experience required, though some groups benefit from an assessor team with complementary sector expertise across different site types.

How far in advance should group-wide coordination realistically start?

Considerably earlier than a single-site assessment would require — the coordination overhead alone typically justifies starting well ahead of any single-site equivalent timeline.