Integration Management Office for HVAC, Renewables and Electrical Contracting Acquisitions

Prepare, stabilise, integrate and hand over. The first 100 days can provide a useful planning horizon, but the scope, dependencies and business capacity determine the actual timetable.

Prepare

Agree objectives, responsibilities, information needs and Day 1 priorities. Output: an approved roadmap and readiness checklist.

Stabilise

Check continuity of live work, customer commitments, payroll, invoicing and access. Resolve urgent gaps before wider changes. Output: a prioritised issue log and confirmed owners.

Integrate

Implement agreed workflows, reporting and system changes in a controlled sequence. Test with the teams involved. Output: working processes, updated guidance and progress records.

Hand Over

Review completion against agreed criteria and transfer ongoing ownership to management. Output: a handover record, remaining actions and a review routine.

Integration should be sequenced around the business’s live commitments. Identify the routines that must continue, assign continuity owners and check dependencies before introducing changes.

• Live jobs and customers: maintain a clear view of schedules, outstanding work, variations and customer commitments.
• Teams and key people: clarify who leads, who communicates changes and where staff can raise concerns.
• Payroll, invoicing and cash: confirm owners, access and required records before changing systems or responsibilities.
• Controlled change: test new workflows, agree readiness criteria and plan a fallback where appropriate before switching over.

Full standardisation is not always the right first move. Agree what to integrate now, what to retain and what to review later.

The sponsor sets objectives and approves material decisions. Named workstream owners deliver actions. The IMO coordinates the plan, dependencies, reporting and escalation, with decision authority agreed at the start.

A clear management rhythm

Agree workstream check-ins, sponsor reviews and an escalation route proportionate to the deal. Use a single action and decision record so owners, deadlines and unresolved issues stay visible.

Measures tied to the integration objectives

Example measures include customer continuity, key staff retention, outstanding job records, reporting completeness, milestone progress and agreed benefits. Set baselines, definitions and targets for the engagement rather than assuming universal results.

Clear ownership after handover

Confirm which routines transfer to management, who maintains the playbook and how remaining actions are reviewed. Any ongoing support is agreed separately in the scope.

Illustrative scenario: a contracting group acquires a business using a different job system, with customer knowledge held by the owner and inconsistent handovers to invoicing. This illustrates the approach; it is not a client result.

Stabilise first.

Confirm responsibility for live jobs, customer relationships, payroll and invoicing. Maintain essential routines while recording gaps and agreeing priority decisions.

Align the work before switching systems.

Agree reporting definitions, completion records and handover responsibilities. Test shared reporting and selected workflows before deciding on migration or wider standardisation.

Transfer ongoing ownership.

Managers own the agreed processes, reporting and review routine. A living playbook captures the current way of working, while remaining integration actions have named owners and review dates.

Can you work with our existing management team and advisers?

Yes. Agree the sponsor, workstream owners and responsibilities alongside your team and relevant advisers. The IMO coordinates delivery; business decisions and specialist advice remain with the agreed owners.

Does everything need to be fully integrated?

No. Agree what should be shared, retained or reviewed later. The right level of integration depends on the acquisition objectives and operating needs.

Is systems migration included?

Only where explicitly scoped. Begin by mapping systems, data, access and dependencies, then agree decisions and technical delivery responsibilities with your IT owners and suppliers.

How are fees and timing agreed?

Review the deal stage, priorities and capacity before agreeing deliverables, fees and milestones. The first 100 days may frame the initial plan; the full timetable depends on scope and dependencies.

How is confidential information handled?

Agree confidentiality terms, approved sharing routes and appropriate access before exchanging sensitive information, including any pre-completion restrictions set with advisers.

What happens at handover?

Review agreed completion criteria, transfer routines to named management owners and record remaining actions. Any ongoing support is confirmed in the scope.