How to build a subsidiary governance framework that works in practice
A subsidiary governance framework should make responsibility, information and escalation predictable across the group — without pretending every jurisdiction or subsidiary can be governed identically.
Create a governance framework people can actually operate, not a policy document that sits in a folder.
Use this as an operating framework and adapt the legal requirements to each jurisdiction.
Key takeaways
- Standardize the operating model, not every local legal requirement.
- Define group-level minimum data, governance and evidence standards.
- Make ownership of each obligation explicit and preserve maker-checker review for higher-risk work.
- Design escalation around events and exceptions, not only periodic reports.
What should a subsidiary governance framework achieve?
The framework should give the parent organization confidence that each subsidiary is properly understood, governed and maintained. It should also give local teams enough clarity to know what they own and when group Legal or Corporate Secretariat needs to be involved.
A practical framework covers four questions: what information must be maintained, who is accountable, what recurring work must happen, and which events require escalation.
| Role | Typical responsibility |
|---|---|
| Group Legal / Corporate Secretariat | Group governance standard, entity master, board/governance oversight, material changes |
| Local entity owner | Local coordination, evidence collection, deadline execution, local adviser management |
| Tax / Finance | Tax registrations, fiscal year data, financial-reporting inputs, entity classification |
| Treasury | Banking relationships, mandates, signers and authority changes |
| Reviewer / approver | Independent review for higher-risk data changes or compliance completion |
The exact titles matter less than eliminating ambiguity. Every important obligation should have one accountable owner even if several functions contribute.
- Every active entity has a complete identity record and responsible owner.
- Direct ownership and key governance relationships are current and evidenced.
- Material corporate documents are linked to the relevant entity or transaction.
- Recurring statutory and internal obligations have an owner and due-date logic.
- High-risk changes are independently reviewed where required by policy.
- Critical exceptions are visible to group oversight without waiting for a monthly report.
Keep local variation without losing group control
A global framework fails when it assumes every jurisdiction has the same directors, filing cycle, registers, local-residency requirements or reporting thresholds. The answer is not to abandon standardization; it is to separate the global core from local attributes.
Keep a consistent entity identity, ownership and accountability model globally. Add jurisdiction-specific fields, obligations and evidence requirements as a controlled local layer.
Delegation of Authority matrices and reserved matters
Subsidiary governance is not only about who sits on the board. Legal Operations and Finance teams also need to know which decisions are reserved to the board, parent, shareholder or a delegated executive — and whether monetary or transaction thresholds apply.
| DoA attribute | Example | Control question |
|---|---|---|
| Reserved matter | Acquisition, guarantee, borrowing, dividend, material contract | Who must approve before the subsidiary acts? |
| Authority holder | Board, parent board, CFO, country manager | Is the person/committee current and authorized? |
| Threshold | Transaction value or risk class | Does the decision exceed delegated authority? |
| Effective period | From / to date | Was the authority valid when the decision was taken? |
| Evidence | DoA policy, board resolution, POA | Can the approval basis be demonstrated later? |
A director or executive change should trigger review of any DoA, reserved-matter, POA or signing-authority relationship attached to that person. For the people layer, see the Board & Director Management guide.
Governance should react to events
Periodic calendars are necessary, but many of the most important governance risks start with an event. A director resignation, ownership transfer, registered-office change or acquisition can trigger multiple downstream actions.
For example, a director resignation may require board action, statutory filings, register updates, review of bank mandates, POAs and signing authority, and updates to internal systems. The framework should define how those dependencies are identified and closed.
Subsidiary events can affect upstream group processes. Ownership changes, late statutory accounts, director changes or unresolved local filings may delay consolidated financial reporting, parent-company disclosures, audit sign-off, financing work or transaction readiness. The escalation model should identify which parent-level process needs to know about the event and who confirms closure.
Build oversight around exceptions, not data dumps
Group oversight should focus on what needs attention: overdue work, upcoming material deadlines, unverified changes, stale records and unresolved dependencies. Large monthly spreadsheets can hide the very exceptions governance teams need to see.
Keep operational detail available, but summarize governance health by exception, trend and accountability. The ability to drill from portfolio issue to entity, evidence and action is more useful than a static red/amber/green score alone.
Questions
What is subsidiary governance?
Subsidiary governance is the framework used by a parent organization to oversee legal entities it controls while respecting local legal requirements and subsidiary-board responsibilities.
Should every subsidiary follow the same governance process?
The group should use consistent minimum standards and controls, but local legal requirements and entity circumstances may require different workflows or evidence.
Who should own subsidiary governance?
Group Legal or Corporate Secretariat often coordinates the framework, but accountability is shared with local teams, Tax, Finance, Treasury and business owners.
What should be escalated to group level?
Typical examples include material ownership changes, director or officer changes, overdue statutory obligations, changes affecting control, significant disputes and unresolved data conflicts.
How often should a subsidiary governance framework be reviewed?
Review it periodically and when the organization changes materially, such as after acquisitions, entry into new jurisdictions, reorganizations or control failures.
Prepared by the EntityOS Editorial Team for operational education. Regulatory references are checked against primary sources where cited. Jurisdiction-specific legal, tax and regulatory decisions should be reviewed by qualified advisers.
This resource is general operational information, not legal, tax, accounting or regulatory advice. Requirements vary by jurisdiction and facts. Use qualified advisers for jurisdiction-specific decisions.