# M&A Due Diligence to Integration: Preserve the Evidence Chain

**Category:** MA
**Author:** AI Assistant
**Published:** 2026-11-01
**Read Time:** 11 min read

## Summary
A diligence finding is only useful after completion if the team can still see its source, status, limits, decision and owner. Preserve that evidence chain as work moves across M&A, GRC, company secretarial and contracts.

## Full Content
M&A due diligence should hand over more than a list of conclusions. For each material finding, preserve the source, what was verified, what remains uncertain, the decision made, the affected entity or contract, the accountable owner and the next evidence required. That evidence chain lets the integration team act without turning assumptions into facts. It also connects M&A to GRC, company secretarial and contracts, so the deal record remains useful after the diligence workstream moves on.
![A diligence finding linked to source evidence, decision, owner and integration work](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793523824357/images/53f415243f20494d5af10c77bc1332fd8bb645d2878258bb41233f1e2e3e0a9b.jpeg)
## What the market scan covers, and what the hand-off must retain
For “M&A due diligence to post-merger integration”, the pages reviewed included [FTI Consulting on integrated due diligence](https://www.fticonsulting.com/uk/insights/articles/strategic-advantage-integrated-due-diligence-ma), [Deloitte's post-merger integration and separation service](https://www.deloitte.com/uk/en/services/consulting-financial/services/post-merger-integration-and-separation.html), [EY's integration programme steps](https://www.ey.com/en_uk/insights/mergers-acquisitions/nine-steps-to-setting-up-an-m-a-integration-program), [KPMG UK's payments-sector integration article](https://kpmg.com/uk/en/insights/finance/post-merger-or-acquisition-integration-in-payments.html), and [PwC UK's M&A trends page](https://www.pwc.co.uk/services/value-creation/insights/mergers-and-acquisitions-trends.html). The pages discuss connected diligence, integration governance, planning, workstreams and value tracking. They are advisory or vendor material, not statutory requirements.
The market coverage is right to emphasise that diligence must feed the integration plan. The missing operational question is often how much of the evidence survives the transfer. A slide can preserve the conclusion and lose the source, date, scope, confidence, reviewer or unresolved qualification. A task list can preserve an action and lose the original reason it exists. An AI-generated summary can sound settled even when the source was incomplete or contradictory.
The open position is an evidence-led bridge from diligence to action. It is not an argument for another generic integration dashboard. It is a practical design for carrying findings across M&A, GRC, company secretarial and contracts while distinguishing verified evidence from interpretation and decision.
## The diligence record must preserve five different things
A good hand-off separates the evidence, the finding, the assessment, the decision and the action. These are related, but they are not interchangeable.
1. \*\*Evidence:\*\* the source material reviewed, its origin and relevant date or version.
2. \*\*Finding:\*\* what the reviewer observed in that source, including limitations or missing context.
3. \*\*Assessment:\*\* how the buyer interpreted the issue under its own criteria and what uncertainty remains.
4. \*\*Decision:\*\* what the authorised decision-maker chose, why, and what alternatives were considered if relevant.
5. \*\*Action:\*\* what must happen next, who owns it, how progress will be checked and what completion evidence is required.
A diligence finding can be accurate and still incomplete. It may be based on a sample, an answer from management, a document version that later changed or a review limited by time and access. Preserve those limitations. Do not write “confirmed” when the available material only supports “reported by target” or “not independently verified”. Use the deal team's agreed status definitions and explain them.
The [Companies Act 2006 section 172](https://www.legislation.gov.uk/ukpga/2006/46/section/172) describes the duty of a director to act in the way the director considers, in good faith, most likely to promote the success of the company for the benefit of its members as a whole, having regard to listed matters. The article does not turn that provision into a transaction checklist or assert that every director has the same role at every stage of a deal. The practical point is narrower: preserve enough context for the people making decisions to understand what was known, what was assumed and what remains open.
![Verified findings, assumptions and open questions kept separate in the deal record](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793523824357/images/c9090a96651eadcd3eb2f3602d903c7dbe7da504182ea9ac4ac456632382815f.jpeg)
## A diligence-to-integration hand-off table
Use a hand-off table that is clear enough for a workstream owner to use and detailed enough for an executive or assurance reviewer to trace the reasoning. The fields below are a management framework, not a legal template.
| Field | Record before transfer | Review question after transfer |
| --- | --- | --- |
| Finding ID and topic | Stable reference and concise description | Can the receiving owner find the original item? |
| Source and scope | Document, interview, dataset or other source; version and date | Is this still the relevant source, and was its scope limited? |
| Evidence status | Verified, reported, inferred, disputed or unavailable, as defined by the deal team | Is the status still accurate, or has new evidence changed it? |
| Assessment | Issue, exposure, relevance and known uncertainty | Does the receiving function agree with the assessment? |
| Entity and agreement | Affected company, contract, service or business process where known | Is the right legal entity and contract in scope? |
| Decision | Approver, rationale, condition or escalation | Was the decision authorised and recorded? |
| Action | Owner, next step, dependency and due event | Is the action clear and feasible in the operating model? |
| Completion evidence | Evidence expected and reviewer who will accept it | Has the action been completed and checked, or merely marked done? |
### 1. Preserve the source, not just a summary
Link the finding to the document or record that supports it, subject to access rights and confidentiality controls. If a source cannot be transferred, record why, who can access it and how a receiving reviewer can obtain it. Keep a stable reference and version. If there are conflicting documents, identify the conflict rather than merging them into one unqualified statement.
This matters when a diligence file contains contracts, company records, policies, risk registers or data supplied by different parties. A source may be incomplete, outdated or subject to a specific review scope. The receiving team should not have to infer those limits from the wording of a summary.
### 2. Label confidence and uncertainty in plain language
The deal team should define a small set of evidence states and use them consistently. “Verified against a source” should mean something different from “asserted by management”, “inferred from available material” or “not reviewed”. If an issue remains open because information was unavailable, name the missing evidence and the person responsible for pursuing it.
Do not fabricate a numerical confidence score unless the organisation has a tested method and a reason to use it. A verbal label with a clear definition is often more honest than an arbitrary percentage. Avoid treating a model-generated confidence indicator as a diligence conclusion without a human review and source check.
### 3. Map the finding to the right entity and contract
A finding should identify the company, subsidiary, business unit, site or contract it concerns where that can be established. If scope is uncertain, preserve that uncertainty. The company-secretarial team can validate corporate structure and records. The contract owner can confirm whether a cited agreement is the executed version and which entity is party. GRC can assess whether the finding changes a risk, control or assurance plan.
The official [Companies House filing software page](https://www.gov.uk/software-company-changes) describes software that can be used to file specified company information, including incorporations, company changes and charges. It also sets out the need for a presenter account and company authentication code to use software for filings. It is a useful boundary source for a filing task, not proof that a diligence record or internal entity chart is complete.
### 4. Convert the finding into a decision, not just a task
An integration action needs a decision context. Is the team fixing a control, validating a source, seeking advice, changing a contract process, accepting a residual exposure or escalating to a board or committee? Identify who has authority for the decision and where the record of that decision belongs. If no decision has been made, label the action as pending rather than stating the issue is resolved.
### 5. Set completion evidence before assigning work
“Review supplier contracts” is too broad to verify. Define which agreements are in scope, what question the reviewer must answer, who accepts the answer and where the evidence will be stored. For a control, define the control owner, the evidence needed to show operation and who reviews it. For a corporate record, specify the authoritative source and how any filing outcome will be confirmed. The requirement will vary by finding; do not use one generic completion rule for every workstream.
### 6. Retain lineage through status changes
As integration proceeds, a finding may be reclassified, split into actions, accepted, superseded or closed. Keep the previous state and reason for the change visible. Link child actions to the originating finding. If a new source changes the conclusion, attach that source and identify who reviewed it. This allows the team to explain not only what it now believes, but how it got there.
## Connect M&A, GRC, company secretarial and contracts
M&A owns the deal context: diligence source, finding, assumption, decision and integration plan. GRC receives the relevant risk, control, compliance or remediation work and applies its own assessment process. Company secretarial provides the corporate context: affected entities, boards, records, authority and any filing task that must be handled by the responsible people. Contracts provides the executed agreement, obligations, owner and commercial follow-up.
Do not convert the four workstreams into one giant register. Each module should preserve the records it is responsible for and link related actions. The connection should make hand-offs visible, not erase professional boundaries. A deal-room note that flags a possible contract issue is not a legal interpretation. A company chart does not prove a filing was accepted. A GRC task does not establish that a control operated. A project milestone does not prove that an integration action achieved its intended outcome.
For companies within the relevant scope of the [UK Corporate Governance Code 2024](https://www.frc.org.uk/documents/6709/UK_Corporate_Governance_Code_2024_a2hmQmY.pdf), Provision 29 addresses the board's monitoring and review of risk management and internal controls, including a declaration about material controls. The Code states that the provision applies for financial years beginning on or after 1 January 2026. It does not create a civil penalty regime. An acquisition does not make the Code universally applicable to every company in the group. Check the Code's application to the particular company and reporting period.
![A deal finding flowing into entity, contract, GRC and integration workstreams](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793523824357/images/0b31c0eb55fdcbe3c97e78429519551f539f37dfa081ba36ace82b70e897e7f9.jpeg)
## A practical hand-off sequence
1. \*\*Freeze the review context.\*\* Record the diligence scope, source date and workstream that produced the finding. Note any access or sampling limitation.
2. \*\*Classify the evidence state.\*\* Separate verified source information from reported statements, interpretation, assumptions and unknowns.
3. \*\*Identify the affected record.\*\* Link the finding to the relevant company, agreement, control or operating process. If it is not known, assign an owner to establish it.
4. \*\*Make the decision explicit.\*\* Record what has been accepted, rejected, deferred or escalated, by whom and on what basis.
5. \*\*Create owned actions.\*\* Define the next step, accountable person, dependency and evidence required for completion.
6. \*\*Route to the correct module.\*\* Keep the deal context in M&A, control activity in GRC, corporate records in company secretarial and agreement detail in contracts.
7. \*\*Review after transfer.\*\* Ask the receiving owner to confirm that the source, status and scope are sufficient. Return unclear or unsupported items for correction rather than silently rewriting them.
8. \*\*Close with evidence.\*\* Keep completion evidence and reviewer acceptance linked to the original finding. If the issue is accepted or remains open, retain that status and its rationale.
This is not a universal transaction timetable. The order and legal requirements depend on the deal, sector, structure, jurisdiction and transaction documents. The framework is designed to reduce information loss during hand-off, not to replace transaction counsel, specialist diligence or board judgement.
## Where Simplif-i fits
Simplif-i's [M&A workspace](https://simplif-i.com/solutions/ma) describes organising targets, documents and findings, using AI-assisted analysis to support review, and planning integration milestones and synergies after completion. The page describes target checks against Companies House, deal-room documents and questions, findings and integration playbooks. It also says identified findings and suggested remediation should be assessed alongside the team's judgement. That is the right boundary: AI may support review, but a person must verify evidence and make the relevant decision.
The M&A page links its work to company-secretarial, supplier and GRC capabilities. Simplif-i's [GRC](https://simplif-i.com/solutions/grc), [company-secretarial](https://simplif-i.com/solutions/company-secretary) and [contracts](https://simplif-i.com/solutions/contracts) pages describe the adjacent workflows. A buyer should test whether the specific finding, source, status and action can be connected as required by its process. These product descriptions are not a guarantee that diligence is complete or that an integration outcome will be achieved.
## FAQs
### What should transfer from diligence into integration?
Transfer the source, finding, evidence status, scope, assessment, decision, affected entity or agreement, accountable owner, next action and completion evidence. If a field is not known, preserve that fact and assign an owner rather than guessing.
### Is an integration tracker the same as a diligence record?
No. A tracker normally shows work status. A diligence record preserves why an action exists, what evidence supports it and what limitations remain. Link them so the action does not lose its context.
### Should every diligence finding become a GRC risk?
No. GRC should assess relevant findings under the organisation's method. Some findings may become risks, controls, compliance actions or issues; others may require a contract review, corporate-record update or management decision. Do not force every observation into one category.
### How should a buyer handle an unverified statement?
Label it as reported or unverified according to the deal team's definitions. Identify the missing source, the limitation and who will resolve it. Do not rewrite an assertion as fact simply because it appears in a summary.
### Does Provision 29 apply to every acquired company?
No. Applicability depends on the company's position under the UK Corporate Governance Code and its reporting period. The official 2024 Code says Provision 29 applies for financial years beginning on or after 1 January 2026. It does not create a civil penalty regime.
## Sources
- [Companies Act 2006, section 172](https://www.legislation.gov.uk/ukpga/2006/46/section/172)
- [Financial Reporting Council, UK Corporate Governance Code 2024](https://www.frc.org.uk/documents/6709/UK_Corporate_Governance_Code_2024_a2hmQmY.pdf)
- [Companies House, Find software to register or file changes to a company](https://www.gov.uk/software-company-changes)
- [FTI Consulting, The Strategic Advantage of Integrated Due Diligence in M&A](https://www.fticonsulting.com/uk/insights/articles/strategic-advantage-integrated-due-diligence-ma)
- [Deloitte UK, Post Merger Integration and Separation](https://www.deloitte.com/uk/en/services/consulting-financial/services/post-merger-integration-and-separation.html)
- [EY UK, Nine Steps to Setting Up an M&A Integration Program](https://www.ey.com/en_uk/insights/mergers-acquisitions/nine-steps-to-setting-up-an-m-a-integration-program)
- [KPMG UK, Post-merger or acquisition integration in Payments](https://kpmg.com/uk/en/insights/finance/post-merger-or-acquisition-integration-in-payments.html)
- [PwC UK, M&A Trends: Mid-Year Outlook 2026](https://www.pwc.co.uk/services/value-creation/insights/mergers-and-acquisitions-trends.html)
- [Simplif-i, M&A](https://simplif-i.com/solutions/ma)
- [Simplif-i, GRC](https://simplif-i.com/solutions/grc)
- [Simplif-i, Company Secretarial](https://simplif-i.com/solutions/company-secretary)
- [Simplif-i, Contracts](https://simplif-i.com/solutions/contracts)


---
Source: https://simplif-i.com/api/blog/readable/ma/ma-diligence-evidence-chain-20261101
Web Version: https://simplif-i.com/blog/ma/ma-diligence-evidence-chain-20261101
© Simplif-i - Unified Business Management Platform