In short
Start with common definitions and a reporting process that each business can support. Standardise repeatable work where it genuinely fits, but retain entity-specific access, approvals and financial records. Measure improvement in each business before claiming a group-wide gain.
In this guide
Find the repeated work between businesses
A group can have capable local teams and still spend too much time assembling management information. Each business uses different status labels, cut-off times and spreadsheet definitions. Head office then repairs the differences before it can compare performance or decide where help is needed.
Map one recurring group process, such as a management pack, purchasing review or operational escalation. Separate the work each business genuinely needs from the work created by inconsistent reporting. Ask local managers which requests duplicate information they have already supplied.
Decide what must remain separate
Common ownership does not automatically permit unrestricted sharing or shared administration. Establish the legal entities, contractual restrictions, staff access, customer permissions and financial responsibilities involved. Some businesses may need separate environments even when leadership wants a consolidated report.
| Area | Potential common standard | Boundary to retain |
|---|---|---|
| Management reporting | Definitions and review timetable | Source ownership and authorised access |
| Purchasing | Request information and comparison method | Contracting entity and spending approval |
| Customer work | Service stages and escalation categories | Customer permissions and local commitments |
| People operations | Onboarding task pattern | Employer records, payroll authority and confidentiality |
Document both what can be reused and what cannot be combined. A shared template is different from a shared database. A reporting relationship is different from permission to act on behalf of another entity.
Build a management view that can be reconciled
Agree the meaning of each measure, its reporting period and the person who accepts it. A customer enquiry, an active job and an overdue obligation need consistent definitions before they appear alongside one another. Keep the local source reference so a movement can be investigated.
Show missing submissions and stale information explicitly. Do not make a business look up to date because the group dashboard refreshed successfully. Leadership should be able to distinguish an operating problem from a problem in the reporting process.
Automate a common pattern, not every local exception
A sensible first change could collect approved reporting inputs, check required fields and route exceptions to the correct business. Later work may join systems or prepare a consolidated pack. The integration should use scoped access and preserve the originating entity throughout.
AI can help draft commentary from accepted information or classify a request for review. It should not infer permission to combine customer or employee records. Where businesses must stay isolated, their AI retrieval, credentials and working context need the same separation.
How Advery would approach the review
Advery's management visibility work connected project and financial information with defined source ownership and review routines. A group review applies that delivery discipline while accounting for each business's operating model, access boundaries and reporting responsibilities.
We would start with one management decision, compare the local processes and agree a limited shared standard. The test would measure preparation effort, unresolved differences and time to an accepted decision. Expansion would depend on local fit, access approval and the cost of supporting the next business, not simply on copying the first implementation.
Sources and guidance
- Advery: Management visibility and operating controls
- AICD and UTS HTI: Director's Guide to AI Governance, June 2026 snapshot