M&A Integration Checklist: What Acquirers Should Tackle First

Ask most acquirers what they have planned for integration and they will walk you through a list of workstreams. HR and payroll. Banking access and reconciliation. IT infrastructure. Legal and procurement structures. Client communication. The list is usually right. What is often missing are the two things every item on it depends on.

The first is a delegation of authority framework. The second is a deliberate approach to process alignment. Without these in place before the workstreams begin, integration efforts spend their early momentum solving problems that should not have existed.

The foundation layer: delegation of authority

The moment a deal closes, every authority structure in the acquired business is technically void. Sign-off levels, approval thresholds, procurement authority. All of it was defined within the context of a business that no longer exists in the same form. If the acquiring organisation has not replaced these explicitly, it has replaced them with ambiguity.

In one acquisition, this was not addressed at deal close. Nobody had established who could authorise what, at what value, across which functions. The old levels no longer applied. The new ones had not been communicated. Decisions either stalled or were made on assumptions that were no longer valid. Every workstream encountered the same wall, and it slowed things down at exactly the point where pace and clarity matter most.

The fix is structural and it needs to happen before day one: a clear delegation of authority framework, mapped across finance, HR, procurement, IT, and client-facing functions. It does not need to be permanent. It needs to be explicit, communicated, and in place.

The five workstreams that need to run in parallel

Once the authority foundation is in place, integration typically runs across five parallel tracks.

People and HR

Employment terms, PAYE and pension obligations, right to work checks, and the workforce communication that tells people what is changing, when, and what it means for them specifically. This track has a sequencing dependency: people communication cannot be credible until the strategic direction is clear, which means the authority and org chart questions need to come first.

Finance and banking

Signatory access, bank reconciliations, understanding the cash position, and unwinding any intercompany flows. This is often more time-sensitive than acquirers expect, particularly if there are payment runs, payroll dates, or supplier obligations that fall early in the integration window.

IT and systems

Infrastructure separation timeline, ERP access and migration, data ownership, and what stays shared in the interim and for how long. The timeline matters as much as the plan. Systems that stay connected beyond their intended period create compliance and operational risk. Systems separated too quickly create operational disruption.

Legal and procurement

Any shared entity or joint venture structures, supplier contracts that sit across both businesses, and the supply chain communication that follows. If the acquisition was a partial purchase rather than a full one, the legal separation of client and supplier relationships requires particular attention.

Client communication

Particularly if only part of the business was acquired, clients need clarity on who owns the relationship, what is changing, and what is not. The timing of this communication matters: it should follow the legal and authority questions, not precede them.

The process alignment trap

Alongside these workstreams, there is a parallel question that most integration checklists treat as an afterthought: how do you align the processes of two businesses that may have been doing the same things in very different ways?

The instinct is to standardise. Pick the better process and apply it across both. This is sometimes the right answer. It is often not.

In one integration, procurement operated in two distinct ways depending on what was being purchased. Consumables: off-the-shelf items bought on volume and price, where speed and simplicity were the operational priority. Specialist engineering purchases: items requiring quality verification, technical specification checks, and multiple approval stages, where rigour was the priority.

Merging the two into a single process did not produce a better system. It applied quality control overhead to consumable purchasing that did not need it, slowing down routine procurement and creating unnecessary cost. And it applied a consumable-speed approach to specialist engineering purchases that needed more rigour, introducing risk that had not existed before.

The right answer was intentional segmentation: a clear decision about which process applied to which category of purchase, and why. Not standardisation. Not the old way from either business. A deliberate design choice based on what each category of activity actually required.

This pattern appears across functions beyond procurement. Finance approval processes, HR onboarding, IT change management. The question is not "which way is better?" It is "what does this specific activity actually need?"

Setting the org chart timeline

One more thing that belongs in the first-90-days plan: the org chart timeline, communicated clearly and early.

People operating without a picture of where the structure is going make defensive decisions. They protect territory. They avoid committing to changes that might not survive the next restructure. They spend energy managing uncertainty rather than delivering.

The org chart does not need to be final. It needs to be directional. A clear statement of where you are headed, how long it will take to get there, and what the interim looks like gives people enough to work with. Silence on this question costs more than an imperfect answer.

How PeakRatio helps

PeakRatio works with acquirers on the integration architecture that determines whether the first 90 days create momentum or spend it resolving problems that should have been pre-empted. That includes the delegation of authority framework, the process alignment decisions, the sequencing of workstreams, and the communication plan that sits underneath all of it.

Integration planning is not a post-close activity. The foundation work needs to happen before the deal completes so that day one is productive rather than reactive.

If you are at this point and want to get the first 90 days right, reach out at PEAKRATIO or get in touch directly. This is precisely the kind of work PeakRatio was built for.