Stop paying for the same control seven times
In most groups, every subsidiary builds its own compliance programme from scratch — the same policy written seven times, the same evidence collected seven times, the same audit run seven times. Govrly lets the group implement once and let entities inherit, while each keeps its own workspace and its own accountability.
This page describes how we approach this work and how Govrly supports it. Where regulatory requirements are mentioned, confirm what applies to your organisation against the source documents published by the relevant authority.
What is multi-entity compliance management?
From the compliance programmes we build and run in Saudi Arabia: multi-entity compliance management is running compliance across several legal entities that share ownership but not systems. The defining problem is duplication: entities within one group implement the same controls independently, write the same policies separately, and collect the same evidence in parallel — while the parent, which carries the consequence of any failure, has no consolidated view of what any of them actually achieved.
This is the opposite of the supervisory problem. A regulator reads entities it does not own and cannot do the work for. A group owns its entities and could do much of the work once — but almost never does, because each subsidiary has its own team, its own tooling, and its own interpretation of a shared requirement.
The cost is not only financial. A group with seven subsidiaries running seven programmes has seven different definitions of what "implemented" means, which makes group-level reporting an act of translation rather than aggregation.
Implement once at group, inherit at entity
A control implemented centrally — a group security policy, a shared identity platform, a corporate training programme — can serve every entity that relies on it, with each entity's own evidence layered on top.
Implemented once by the group. Approved centrally, versioned centrally, and inherited by every entity that depends on the shared service — instead of being rewritten seven times in seven formats.
Inherits the group control, adds its own maturity scoring and the entity-specific evidence its supervisor expects.
Inherits the same control, mapped to its own compliance level and licensee obligations.
Inherits it again, scored against implementation status rather than maturity.
Same control, carried into the Statement of Applicability as an Annex A entry with its justification.
Inheritance does not remove the entity's responsibility. Each entity confirms the control operates in its own environment and holds its own evidence — what it avoids is rebuilding the control from nothing.
Where groups lose money and visibility
Six patterns that we see in almost every group large enough to have a group compliance function.
- 01/06The same policy is written in every entity
Seven access control policies, seven approval cycles, seven review dates, seven slightly different positions on the same question — and no way to update them all when the group position changes.
- 02/06Shared services are evidenced separately
One group identity platform, one group SOC, one group HR system — and each entity independently collecting evidence about the same shared control from the same team.
- 03/06Entities answer to different regulators
A financial subsidiary carries SAMA CSF, a technology arm carries the CST CRF, a government-facing entity carries the NCA ECC. The underlying controls overlap heavily. The programmes rarely do.
- 04/06Acquisitions arrive with unmapped compliance debt
A newly acquired entity brings its own frameworks, its own evidence quality, and its own gaps. Establishing what it actually has usually takes longer than the deal did.
- 05/06Group reporting is translation, not aggregation
Each entity reports in its own format against its own definitions. Producing a board pack means someone reconciling incompatible numbers by hand every quarter.
- 06/06The parent finds out last
An entity-level gap becomes a group-level problem the moment it becomes an incident or a finding. Until then, the parent has visibility only into what entities chose to report.
How Govrly works for multi-entity groups
Group-level controls, policies, and evidence implemented once and inherited by the entities that rely on them — with each entity adding what is specific to its own environment.
Every subsidiary retains its own users, controls, risks, evidence, and audit records. Entities do not see one another. The group sees across them.
One entity scored on SAMA maturity levels, another on CST compliance levels, another on ECC implementation status — all drawing on the same underlying control and evidence records.
Map what the acquired entity already holds against the group control library, so the gap is visible in weeks rather than discovered at its next assessment.
Coverage, implementation status, open risks, and overdue actions aggregate automatically, because every entity is working against the same definitions.
Consolidated visibility does not move responsibility. Each entity remains accountable for its own implementation, evidence quality, and remediation.
What belongs at group, what belongs at entity
Getting this boundary right is most of the design work. Push too much down and you recreate the duplication; pull too much up and entities stop owning their own compliance.
There is no universally correct split — it depends on how centralised the group's operations genuinely are. What matters is that the boundary is decided deliberately and recorded, rather than emerging by default from whoever acted first.
| Item | Usually group | Usually entity |
|---|---|---|
| Policies and standards | Written and approved once | Local procedures where operations differ |
| Shared service controls | Implemented and evidenced centrally | Confirmation of reliance and local coverage |
| Framework scoping | Group control library and definitions | Which frameworks apply to this entity |
| Risk register | Group-level and aggregated risks | Entity-specific risks and treatment |
| Evidence | Shared-service artefacts | Entity operational artefacts |
| Regulatory submission | Method, template, and quality bar | The submission itself, to its own regulator |
| Accountability | Oversight and escalation | Implementation and remediation |
Built for groups with entities that operate independently
Groups carrying accountability for subsidiary compliance across sectors, each subsidiary with its own regulator and its own operating model.
Organisations spanning financial services, technology, energy, and industrial operations, where framework overlap is large but rarely exploited.
Parent organisations whose affiliates fall within the ECC's scope but maintain their own systems, teams, and interpretations.
Groups operating inside and outside the Kingdom, where Saudi obligations sit alongside GDPR, ISO, and local sector rules.
Teams we work with that regularly inherit compliance programmes they did not build and need to assess quickly against a known standard.
Where one central function serves many entities, and the evidence for that function is best produced once rather than requested repeatedly.
How a group rollout works
The technical work is smaller than the organisational work. Entities that have run their own programmes for years will not hand them over willingly, and shouldn't have to.
- 01/07Map the entity landscape first
Which entities, which frameworks each carries, which regulator each answers to, and which shared services each depends on. This is the artefact the whole rollout depends on.
- 02/07Decide the group–entity boundary explicitly
What is implemented once at group and what stays local. Record the reasoning, because it will be challenged.
- 03/07Build the group control library
One set of controls and definitions, mapped to every framework in use across the group. This is where the duplication actually gets removed.
- 04/07Start with the entity that gains most
Usually the smallest or the newest — the one with the least to defend and the most to inherit. Early value there makes the next conversation easier.
- 05/07Migrate shared-service evidence to group
Identity, logging, SOC, HR, and training artefacts produced once centrally rather than requested separately by each entity.
- 06/07Onboard in waves, not all at once
Group compliance capacity is the constraint, not the platform. Each wave teaches you what the next one needs.
- 07/07Move group reporting off spreadsheets last
Only once enough entities are in the model for the roll-up to be meaningful. Switching too early produces a partial view that undermines confidence in the whole programme.
Multi-entity groups — FAQs
Running compliance across several legal entities that share ownership but not systems. The defining problem is duplication: entities implement the same controls independently and collect the same evidence in parallel, while the parent, which carries the consequence of any failure, has no consolidated view of what each entity actually achieved.
Yes. Controls implemented at group level — a group policy, a shared identity platform, a corporate training programme — can be inherited by the entities that rely on them, with each entity adding the evidence specific to its own environment. This removes the most expensive form of duplication in a group compliance programme.
Yes. Every subsidiary retains its own users, controls, risks, evidence, and audit records in an isolated workspace. Entities cannot see one another's data. The group sees across them without collapsing that separation.
That is the normal case, and the platform is built for it. A financial subsidiary can be scored on SAMA CSF maturity levels, a technology arm on CST compliance levels, and a government-facing entity on NCA ECC implementation status — all drawing on the same underlying control and evidence records, with each framework keeping its own scoring method and reporting.
No. Each entity remains responsible for its own implementation, evidence quality, and remediation. Consolidated visibility gives the group an accurate view of posture and progress; it does not transfer the obligation.
By mapping what the acquired entity already holds against the group control library, so its position is visible against a known standard rather than described in its own terms. Existing evidence that meets the group bar carries over; the remainder becomes a scoped gap with owners and dates rather than an open question.
Policies, standards, shared-service controls, and the group control library usually sit at group. Local procedures, entity-specific risks, operational evidence, and the regulatory submission itself usually sit at the entity. The right split depends on how centralised the group's operations genuinely are, and is best decided deliberately rather than left to emerge by default.
A regulator reads entities it does not own and cannot do the work for — its need is comparability across organisations. A group owns its entities and can implement much of the work centrally — its opportunity is reuse. Both need consolidated visibility with entity isolation, but the value each derives from it is different.
Yes. A group holding company, a regional sub-holding, and an entity's own management can each hold a distinct view scoped to their own remit, alongside any external regulator with visibility into that entity.
It depends on the number of entities, the number of frameworks in use, and how centralised the group's operations already are — far more than on the platform itself. Most groups start with one or two entities, establish the shared control library, then onboard in waves rather than attempting the whole group at once.
Do the work once. Let every entity inherit it.
Shared controls at group, isolated workspaces at entity, and one roll-up that adds up without reconciliation.
