Integration Management Office (IMO) Setup

Executive summary

An integration management office (IMO) is the small group that runs the integration as a program: one plan, one set of owners, one weekly rhythm, one view of risks, and one synergy pipeline. It does not do the functional work. Finance still integrates finance, and IT still integrates IT. The IMO makes sure the work is sequenced, owned, visible and reported in a single format.

You need an IMO when more than a handful of workstreams run at once, when two or more functional leaders depend on each other's output, or when a sponsor wants to know weekly whether the deal thesis is on track. You do not need a large one. For many mid-market deals the IMO is a lead and one or two analysts, with part-time workstream leads.

The first move is to write a one-page charter: scope, decision rights, workstreams, cadence and what the IMO does not own. Then build the single register of initiatives with an owner, a stage and a value for each. Everything else follows from that register.

When to use this

Use this guide when:

• You are closing an acquisition, merger or add-on and the plan has more than five workstreams.
• A 100-day plan exists but no one owns keeping it current.
• Synergies were in the investment case and nobody tracks their progress to realized EBITDA.
• Leadership meetings keep restating the same open issues.

Do not set up a heavy IMO for a small add-on where one integration lead and the CFO can run a weekly meeting. The test is whether coordination, not work, is the bottleneck. If a single person can hold the whole plan in a spreadsheet, a charter and a weekly call are enough.

Diagnostic questions

1. How many workstreams are running, and how many have a named owner and a written plan?
2. Which workstreams depend on another's output, and where is that dependency written down?
3. Who decides when two workstreams conflict, and how fast?
4. Is there a single list of synergy initiatives with an owner, a value, a timing and a stage?
5. How is the synergy value in the investment case traced to named initiatives?
6. What reporting do the sponsor, the board and the lender expect, and how often?
7. How many people are dedicated to integration full time, and how many are doing it alongside a day job?
8. What was promised to employees, customers and suppliers, and who tracks those commitments?
9. Which risks are known, who owns each, and when were they last reviewed?
10. What costs are expected to achieve the integration (one-time costs), and who approves spending against them?
11. Which workstreams touch the close, payroll, billing or customer service, where a mistake is externally visible?
12. What does the sponsor need to see in the first 30 days to believe the integration is in control?

If question 4 has no clear answer, the IMO's first job is to build that list. A synergy that has no owner is a forecast and not a plan.

The framework: five jobs of an IMO

A workable IMO does these five things and stops. The risk is that it grows into a second management layer that duplicates the functions. The charter should state what the IMO does not own: functional decisions, hiring decisions and customer commitments stay with the line.

Step-by-step process

1. Name the sponsor and the IMO lead. The sponsor is a senior executive with the authority to settle conflicts between workstreams. The lead runs the office day to day. Owner: CEO or deal sponsor. Output: names in the charter. Time-box: before close if possible.
2. Write the charter. Scope, objectives tied to the deal thesis, workstreams, decision rights, escalation path, cadence, and what is out of scope. Owner: IMO lead with sponsor. Output: one page, signed off by the sponsor.
3. Define workstreams and assign leads. Typical workstreams are finance, IT, HR and people, commercial, operations and supply chain, legal and compliance, and communications. Owner: sponsor. Output: a named lead per workstream with a time allocation.
4. Size the IMO to the load. Count workstreams, expected initiatives and reporting obligations, then staff for coordination, not for execution. Owner: IMO lead. Output: headcount and cost, approved by the sponsor.
5. Build the initiative register. Every initiative, including synergies, TSA exits, system moves and people actions, with owner, value, timing, dependencies and stage. Owner: IMO analyst. Output: the single register.
6. Define stage gates. For example: identified, validated, planned, executing, realized, with entry criteria for each. Owner: IMO lead with finance. Output: a gate definition table.
7. Set the cadence. Weekly workstream leads' meeting, weekly or biweekly sponsor check-in, monthly steering committee. Owner: IMO lead. Output: recurring calendar and fixed agendas.
8. Stand up the RAID log. Risks, assumptions, issues, dependencies, each with an owner and a date. Owner: IMO analyst. Output: a log reviewed weekly.
9. Set the reporting format. One status page per workstream plus a program summary. Owner: IMO lead. Output: template used by every workstream.
10. Link finance to the register. Initiative values are tied to the P&L line they will change, so realized savings can be measured. Owner: controller with IMO. Output: mapping from initiative to GL line.
11. Review the IMO itself at day 60. Is it reducing coordination cost, or adding meetings? Owner: sponsor. Output: decision to keep, shrink or end.
12. Plan the handover. As work becomes business as usual, move ownership of ongoing tracking to the finance and operating teams. Owner: IMO lead. Output: handover checklist.

Templates

IMO charter (one page)

Initiative register (copy into a spreadsheet)

Stage gate criteria

Weekly workstream leads' agenda

1. Milestones due and missed (10 min).
2. Dependencies between workstreams (10 min).
3. New risks and issues, owner and date (10 min).
4. Initiative gate changes (5 min).
5. Decisions needed from the sponsor (5 min).

Metrics and KPIs

Setting targets without invented benchmarks. Do not take a standard probability weight or IMO cost ratio from a general source. Set probability weights from your own history, such as the share of your past initiatives that moved from each stage to realized. If you have no history, start with weights the finance lead and sponsor agree and write them down as assumptions, then revise them after the first two quarters of data. Judge the IMO cost against the value it protects in your own investment case.

Common mistakes

1. Making the IMO a reporting office only. Symptom: beautiful status decks and no decisions. Give the IMO decision rights for sequencing and escalation.
2. Making the IMO do the work. Symptom: functions disengage and the office grows. Keep ownership with the functional leads.
3. No sponsor with authority. Symptom: conflicts between workstreams sit for weeks. Name one person who settles them.
4. A synergy list that is not tied to the P&L. Symptom: savings are announced but never visible in EBITDA. Map each initiative to a GL line and a baseline.
5. Too many meetings. Symptom: workstream leads dread the cadence. Fixed agendas, short meetings, decisions logged.
6. Different formats per workstream. Symptom: the sponsor cannot compare status. One template for all.
7. No end date. Symptom: the IMO becomes permanent overhead. Set a review date and a handover plan.
8. Ignoring people commitments. Symptom: promises to employees or customers are forgotten. Track them in the RAID log.

Worked example (Illustrative)

The numbers below are made up to show the method. They are not benchmarks.

A sponsor has a $3.0M run-rate synergy target in the investment case. The IMO is a lead at $15,000 per month, one analyst at $8,000 and a part-time project coordinator costing $7,000, totaling $30,000 per month, or $360,000 over 12 months. That is 12% of the $3.0M target. Whether 12% is acceptable is the sponsor's judgment, based on the size of the deal and how much of the work the functions can coordinate themselves.

The initiative register in month three:

The register shows $3.0M of identified value but only $1,665,000 when weighted by stage, which is 55.5% of the target. The probability weights here are assumptions agreed by the sponsor and the finance lead, not benchmarks.

What the operator does with this: the gap of $1,335,000 between target and weighted pipeline is a message for the steering committee. The SG&A overlap initiative carries $700,000 at only an identified stage, so the IMO asks the finance lead to validate it with baseline data within two weeks, which moves it or removes it. The weighted figure is reported next to the target each month, and realized run-rate is reported separately once it shows in the P&L. See the synergy tracking model for how realization is measured, and use the acquisition synergy calculator to test the value of each initiative.

AI prompt assistance

Use AI to draft and to organize. The IMO lead remains accountable for what goes to the sponsor.

1. Draft a charter from deal documents.

I will paste the deal thesis, the list of workstreams and the sponsor's expectations. Draft a one-page IMO charter with purpose, scope, decision rights, cadence, reporting and funding sections. Mark every statement that I did not supply as an assumption.

Check: the sponsor reviews every assumption and decision right before it is circulated.

2. Summarize workstream status.

Here are six workstream status updates (pasted). Produce a one-page program summary: milestones missed, top five risks, dependencies at risk, and decisions needed. Do not add information that is not in the updates.

Check: confirm each item against the source update and the RAID log.

3. Find gaps in the initiative register.

Here is the initiative register. List initiatives with no owner, no P&L line, no baseline, or a start date earlier than the dependency's completion. Return a table with the issue named for each row.

Check: spot-check five rows against the register before assigning follow-up work.

Implementation guide

Governance: the sponsor owns the target, the IMO lead owns the process, workstream leads own delivery, and the controller owns the measurement of realized value. Report to the steering committee monthly using the same template each time, and refer to the PMI playbook for the full timeline.

What to expect: the first two weeks are spent on the register and the charter, and most conflicts in month one come from dependencies that were not written down. The point where the IMO is working is when the sponsor can answer "what is late and why" without a meeting.

Downloadable assets

The charter, initiative register, gate criteria and weekly agenda above are designed to be copied into a spreadsheet or document.

Related resources

• Post-merger integration hub: all integration guides in one place.
• PMI playbook: Day 1 to Day 365: the full timeline the IMO runs.
• Synergy tracking: from model to realized EBITDA: measuring what the register promises.
• Day 1 readiness checklist: the first deliverable most IMOs own.
• 100-day plan template for private equity: the plan the register should feed.

Frequently asked questions

What is an integration management office?

An integration management office is a small team that coordinates a post-merger integration: it owns the integrated plan, the weekly cadence, the risk log and the synergy pipeline. Functional leaders still do the work. The IMO exists so that dependencies, decisions and reporting are handled in one place and in one format.

How big should an IMO be?

Size the IMO to the coordination load, not to the amount of integration work. Count workstreams, expected initiatives and reporting obligations, then staff the minimum that can keep a single plan and register current. For many mid-market deals that is a lead plus one or two analysts, with workstream leads part time.

Who should lead the IMO?

The IMO lead should be someone with credibility across functions, enough seniority to escalate, and time to run the process, often from finance, operations or a dedicated program role. The sponsor, a senior executive with authority to settle conflicts, is separate from the lead and owns the target.

How is an IMO different from a project management office?

An IMO is a project management office specialized for a deal: its plan is tied to the investment thesis, it tracks synergies to realized EBITDA, and it manages commitments to employees, customers and lenders. A general PMO tracks projects. The IMO also has a defined end, when ownership hands back to the business.

When should the IMO be disbanded?

The IMO should end when initiatives have moved to business-as-usual ownership and realized value is tracked by finance. Set a review date in the charter, often around day 60, and a handover plan. If the IMO has no decisions left to make, it has become overhead.

How this works in a System of Performance

An IMO lives on the quality of its register: initiatives, owners, stages and the P&L lines they will change. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. If you want to see how many of your initiatives have an owner and a P&L line today, bring it to us as a launch partner.