# Governance After an Acquisition: Control the Policy Transition **Category:** MA **Author:** AI Assistant **Published:** 2026-11-15 **Read Time:** 10 min read ## Summary After an acquisition, do not copy policies wholesale or assume the target’s controls remain fit. Decide what to retain, bridge, replace or retire, with an owner, evidence test and cross-module record for each material policy change. ## Full Content Governance after an acquisition needs a deliberate policy transition, not a folder merge. For each material policy or control, decide whether to retain it, bridge it temporarily, replace it or retire it. Name the post-close owner, test the evidence, identify affected entities and contracts, and record the decision in the integration plan. Do not assume that a policy is effective because it is signed, or that a buyer’s policy is ready for immediate use across every acquired business. ![An acquisition transition map for inherited controls and policy owners](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1794733445591/images/6bcadadb8b447acd35f090b84d45d6e5389c3b532ddbdba31a4a414659af2eaa.jpeg) ## What the market scan covers, and what it leaves open For “governance after an acquisition” and “M&A due diligence to post-merger integration”, search results and AI-answer summaries cover diligence workstreams, transaction structuring, legal issues, transitional service arrangements, regulatory review and integration planning. Myerson’s UK diligence guide describes a broad review of a target’s assets, liabilities, risks and commercial position. Devonshires’ integration guide discusses post-close legal workstreams. The [CMA’s merger investigation guidance](https://www.gov.uk/government/publications/mergers-how-they-are-investigated/mergers-how-they-are-investigated) and the [FCA’s change-in-control guidance](https://www.fca.org.uk/firms/change-control) cover distinct regulatory contexts. Their scope matters: the FCA page is for acquiring or changing control in a firm it regulates; CMA merger review is not a substitute for contract or internal-control analysis. The open operational gap is the policy handover. Due diligence may identify policies and controls, and integration plans may list workstreams, but the buyer still needs a controlled decision on whether each inherited practice can continue, needs a temporary bridge, requires replacement or should end. The answer must be tied to actual evidence, the legal entity, affected contracts, risk ownership and the integration milestone. A title such as “policy harmonisation” is not a plan. Do not claim every acquisition has the same regulatory route or that the UK Corporate Governance Code applies to all acquired companies. The [FRC’s Code](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/uk-corporate-governance-code/) and [guidance](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/corporate-governance-code-guidance/) are relevant within their stated scope. Check the particular entities, listing status, regulated activities and transaction facts before applying any requirement. ## Why policy integration fails when it is treated as document transfer A policy is a formal statement. A control is an activity or mechanism that helps implement an expectation. Evidence shows what happened. These elements connect, but they are not interchangeable. A PDF signed by the target’s management does not demonstrate that its controls operate as designed, that the process is still appropriate after ownership changes, or that the acquiring group has adopted it. Nor is a buyer’s policy automatically workable in the target. The acquired business may use different systems, suppliers, legal entities, roles or local procedures. A policy can prescribe a control that the new operating team cannot perform yet. If the organisation retires the target’s process before the replacement is live, it may create a control gap. If it keeps both without a clear boundary, teams may follow different versions or assume the other side owns the decision. The integration team needs a transition record, not an abstract policy inventory. It should identify source, scope, status, owner, evidence, dependencies, decision and next review. The record should distinguish known facts from a target representation that has not been validated. Mark the uncertainty and assign a validation task rather than presenting an assumption as confirmed. ## A policy transition framework: retain, bridge, replace or retire Use this framework for each material policy or control identified in diligence. “Material” should be defined for the transaction and business context, not borrowed from an unrelated template. The framework is a governance tool, not legal advice on the applicability of a specific rule. 1. **Inventory the source.** Capture the policy or control, version, owner, legal entity, business activities, relevant systems, supporting procedures and evidence. Record where it came from and whether the source document is current. 2. **Validate the operating reality.** Interview the owner, inspect a representative record and test whether the described process operates. Note whether the target’s answer is an assertion, a document review or independently verified evidence. 3. **Map the exposure.** Connect the policy to the risk, obligation, contract, service and entity it supports. Identify dependencies such as a supplier, outsourced function, customer commitment or regulatory condition that could be affected by change. 4. **Choose a transition state.** Decide to retain, bridge, replace or retire. Explain why. If a temporary bridge is needed, state its limits, owner, duration or review trigger and the condition for moving to the next state. 5. **Assign ownership and authority.** Name the person responsible for implementing and operating the decision after close. Identify any required board, committee, risk or legal approval. Keep the decision owner separate from the task owner where the governance model calls for it. 6. **Set an evidence test.** Define what proves the selected state is in place. A replacement policy may need approved text, trained owners and an operating control test. A retained process may need a review that confirms the post-close context has not invalidated it. 7. **Track exceptions to closure.** Record unresolved gaps, accepted exposure, actions, due dates and escalation. Preserve the original diligence finding and decision history. Close only when the agreed evidence is reviewed or an authorised decision changes the plan. | Transition state | Use when | Minimum governance record | | --- | --- | --- | | Retain | Evidence supports continued use and the post-close context is compatible | Source version, scope, owner, validation result and next review | | Bridge | A temporary arrangement is needed while a replacement is designed or deployed | Boundary, temporary owner, duration or trigger, compensating action and exit condition | | Replace | The buyer or combined business adopts a different policy or control | Approval, effective date, affected entities, implementation owner, training and test evidence | | Retire | The process is no longer needed or is superseded | Rationale, approvals, records-retention decision, dependencies checked and closure evidence | ![A controlled hand-off from deal diligence into integration owners](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1794733445591/images/531d94c07bfb5e2f33a91e744a0b489fd09a54690407d34d7a9bef5f4d6b97aa.jpeg) ## Protect the distinction between deal preparation and post-close action Before completion, the team may identify a desired transition and prepare work. Whether it can implement that change before completion depends on the transaction, applicable requirements, agreements and advice. Do not treat an integration checklist as permission to act. The [CMA guidance](https://www.gov.uk/government/publications/mergers-how-they-are-investigated/mergers-how-they-are-investigated) describes the CMA’s merger investigation process and potential remedies. The [FCA change-in-control page](https://www.fca.org.uk/firms/change-control) concerns control changes involving firms the FCA regulates. Both are reasons to keep regulatory assessment distinct from internal integration planning, not a basis to generalise the same restriction or approval to every deal. For a policy transition, record the stage clearly: proposed, diligence-confirmed, approved for implementation, in progress, operating and verified, or retired. Put the relevant conditions and dates in the transaction plan. If a legal or regulatory question remains open, keep it assigned to an appropriately qualified reviewer. Do not bury it in a generic “integration dependency” status. ## Connect the transition to the company that must operate it The group structure tells the team which entities exist, but each policy may apply to different companies, people or processes. Map the transition to the affected entity and identify which board or delegated authority approves the change. Where the policy underpins a contract, link the agreement and obligations. If the policy covers a risk or control, update GRC only after the decision is authorised and the relevant scope is understood. This is also where the four-module connection becomes concrete: - **M&A** holds the diligence finding, transition state, integration milestone, dependencies and accountable workstream owner. - **Company secretarial** identifies the entity, governance route and relevant board or committee decision. - **Contracts** identifies counterparties, commitments and contract terms affected by the new policy or control. - **GRC** links the policy to risks, controls, evidence, exceptions and remediation. The integration record should be the index to the decision, not a replacement for each specialist record. A document is not automatically public to every team because it is cross-linked. Preserve privilege, deal confidentiality and appropriate role-based access. If an adviser’s view supports a transition decision, record the existence and permitted reference to that advice without exposing privileged material unnecessarily. ## Measure implementation by evidence, not completion colour An integration dashboard can say a policy workstream is green while the operating process is not ready. Define the completion test first. For a replacement policy, the test may include approved scope, communicated responsibilities, updated procedures, access or system changes and a sample of operation. For a retained control, the test may be a post-close review showing that roles, evidence sources and escalation routes still work. For a retired process, check that obligations and records have not been abandoned with it. A failed test should lead to an explicit decision. Can the business continue under a temporary bridge? Does the owner need to restrict a process? Is a board or risk committee decision required? What evidence would permit the team to move to the target state? These questions are more useful than a single “policy harmonisation complete” milestone. Keep the history. Preserve the diligence description, validation, decision, approval, implementation, test result and later review. If the organisation changes its mind, record why and who authorised the revised transition. This is not bureaucracy for its own sake. It lets the organisation distinguish an inherited representation from a verified operating control and explain why it selected a particular path. ![M&A findings linked to entity, contract and GRC records](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1794733445591/images/bfd575a0277b48cd23cd118aeebc0c4cd24bf71dd38c3a17f7b3aea43ce69c91.jpeg) ## Where Simplif-i fits Simplif-i’s [M&A workspace](https://simplif-i.com/solutions/ma) describes organising targets and deal documents, analysing contracts and governance information, recording findings and planning integration milestones. Its product page says AI surfaces possible findings but does not replace professional review. That is the right boundary for policy transition: use automation to organise and compare information, then have the responsible team validate the source, scope and operating reality. The workspace connects to [GRC](https://simplif-i.com/solutions/grc), [company secretarial](https://simplif-i.com/solutions/company-secretary) and [contracts](https://simplif-i.com/solutions/contracts) so the transition can be linked to risk, entity, approvals and obligations. Assess permissions, evidence export and the exact implementation workflow with your own deal team. Simplif-i can provide structure for diligence and follow-up; it does not make legal or regulatory decisions for the buyer. ## Frequently asked questions ### Should the acquirer replace all target policies immediately? No. Assess each policy and control in context. A process may be retained, bridged temporarily, replaced or retired, with an owner, rationale, evidence test and review condition. ### What is the difference between a policy and a control? A policy states expectations or direction. A control is an activity or mechanism intended to implement an expectation. Evidence is needed to assess whether the relevant process operated. ### Can a policy transition begin before completion? Preparation and implementation are different questions. Check the transaction terms, applicable regulatory context and legal advice before acting. A project plan alone is not authority to implement a change. ### How should a temporary bridge be recorded? State its scope, owner, constraints, review date or trigger, compensating actions and the condition for exit. Keep it visible until the replacement is operating or an authorised decision changes the plan. ### Which acquisition approvals should be checked? Assess the facts and relevant regimes. FCA change-in-control guidance concerns firms regulated by the FCA. CMA merger investigation guidance covers the CMA process. Do not treat either as a universal approval rule for every deal. ### How do the four modules support policy integration? M&A tracks findings and milestones; company secretarial connects the entity and governance decision; contracts identifies affected commitments; GRC records risks, controls, evidence and remediation. ## Sources - [Financial Reporting Council, UK Corporate Governance Code 2024](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/uk-corporate-governance-code/) - [Financial Reporting Council, Corporate Governance Code Guidance](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/corporate-governance-code-guidance/) - [Competition and Markets Authority, Mergers: how they are investigated](https://www.gov.uk/government/publications/mergers-how-they-are-investigated/mergers-how-they-are-investigated) - [Financial Conduct Authority, Change in control](https://www.fca.org.uk/firms/change-control) - [Myerson, M&A Due Diligence: Key Steps, Process and Risk Areas](https://www.myerson.co.uk/news-insights-and-events/m-and-a-due-diligence-key-steps-process-and-risk-areas-explained) - [Devonshires, Post-Merger Integration Legal Guide](https://insights.devonshires.com/post/102kgly/post-merger-integration-legal-guide-tsas-risk-employment-transfers-explained) - [Simplif-i, M&A Due Diligence and Integration](https://simplif-i.com/solutions/ma) --- Source: https://simplif-i.com/api/blog/readable/ma/ma-post-acquisition-policy-transition-20261115 Web Version: https://simplif-i.com/blog/ma/ma-post-acquisition-policy-transition-20261115 © Simplif-i - Unified Business Management Platform