IMO Charter Template

Somewhere in a SharePoint site you’ve never visited, there is a 30-page IMO charter that was written during the first week of an integration by someone who has since left the company. It has a version history with 14 entries. The last edit was four months ago. Nobody has opened it since.

I know this because I’ve written that document. Multiple times. For multiple clients. With increasing levels of formatting sophistication and decreasing levels of practical usefulness.

The problem with a 30-page charter is not that it contains bad information. It usually doesn’t. The problem is that a 30-page charter is a reference document, and reference documents are things people intend to read and never do. The charter’s job isn’t to be comprehensive. Its job is to be used. Those are different things.

After six integrations where the long charter collected dust and the one-page summary got taped to the wall of the war room (literally, in one case), I stopped writing the long version. Here’s the one-page charter I’ve used since, with commentary on why each section earns its space.

The One-Page IMO Charter

What follows is the actual template. Seven sections. Each one is a single paragraph or a short list. If a section takes more than three sentences to fill out, you’re either over-engineering the governance or under-simplifying the situation. Both are fixable.

Section 1: Why This IMO Exists

One sentence. What is the IMO here to accomplish? Not “manage the integration.” That’s a tautology. The answer should connect to deal value.

Example: “The IMO exists to coordinate the capture of $50M in labor synergies across 14 countries within 18 months of close, while maintaining business continuity and retaining critical talent.”

That sentence contains a dollar amount, a geography scope, a timeline, and two constraints. Anyone who reads it knows what success looks like and what failure would cost. Compare that to the typical charter opening: “The Integration Management Office (IMO) will serve as the central coordination body responsible for overseeing the integration of the two organizations, ensuring alignment across workstreams, and driving value realization in accordance with the strategic objectives outlined in the deal thesis.”

Same idea. One of them fits on a Post-it. The other one fits on a slide that nobody reads aloud because reading it aloud would take 30 seconds and everyone in the room would start checking their phones by second 12.

Section 2: What the IMO Owns (and What It Doesn’t)

Two lists. What the IMO is accountable for, and what it explicitly is not. The second list matters more than the first.

Owns:

• Integration plan and milestone tracking
• Cross-workstream dependency management
• Synergy tracking and reporting
• Escalation resolution
• Decision documentation

Does not own:

• Functional execution (that’s the workstream leads)
• Business-as-usual operations
• Budget authority beyond integration-specific spend
• Hiring and termination decisions

The “does not own” list prevents the IMO from becoming an empire. Integration offices have a gravitational pull. If you don’t define the boundary, every problem in the organization eventually gets routed to the IMO because nobody knows where else to send it. By month three your integration team is triaging IT help desk tickets and approving PTO requests.

(“But that would never happen at my company!” Sure. And the TSA will definitely be done in 12 months.)

Standing up an IMO? We’ve designed them for chemicals, pharma, carve-outs, and technology transformations. The structure changes every time. Let’s talk.

Section 3: Decision Rights

This is the section that separates charters that work from charters that decorate walls. Three tiers:

The Integration Lead decides: Resource allocation across workstreams. Meeting cadence. Workstream priorities when they conflict. Communication timing and content. Vendor and tool selection for integration-specific needs.

The Steering Committee decides: Changes to synergy targets. Timeline shifts of more than two weeks. Additions or removals of workstreams. Budget increases above a threshold you define (I’ve used $50K, $100K, and $500K depending on deal size).

The CEO/Sponsor decides: Changes to deal thesis. Public communications about the integration. Executive appointments in the combined organization.

The specificity matters. “The Integration Lead has decision-making authority” is meaningless. Decision-making authority over what? If the Integration Lead thinks they can reallocate headcount from the IT workstream to HR, and the CIO thinks otherwise, who wins? If the charter doesn’t answer that question before it comes up, the answer will be determined by whoever has the louder voice in the meeting. That’s not governance. That’s politics.

For a deeper look at why authority matters more than structure, the full IMO guide covers this in detail.

Section 4: The People

Names, not titles. This section has exactly three things:

1. Executive Sponsor: One person. Name. Not “the executive team” or “the steering committee.” One human being who will answer the phone when the Integration Lead calls with a problem at 7 PM on a Thursday.

2. Integration Lead: One person. Name. Full-time. Not “in addition to their current responsibilities.” If the Integration Lead has a day job, you don’t have an Integration Lead. You have someone who will be perpetually behind on two things instead of caught up on one.

3. Workstream Leads: Names and scope. Each workstream has one owner. If a workstream has two owners, it has zero owners. This is not a management platitude. I have watched it happen in real time, in multiple industries, with smart people who should have known better. Shared ownership is diffused accountability wearing a collaborative hat.

Section 5: Operating Rhythm

The calendar. Not a description of the calendar. The actual recurring meetings with frequency and purpose.

Meeting	Frequency	Purpose	Attendees
Steering Committee	Biweekly	Decisions, escalations, progress against milestones	Sponsor + C-suite + Integration Lead
Workstream Sync	Weekly	Cross-workstream dependencies and blockers	Integration Lead + all workstream leads
Daily Stand-up	Daily (first 90 days)	What’s stuck, what needs help today	Integration core team
Synergy Review	Monthly	Progress against targets, forecast updates	Integration Lead + Finance + workstream leads

Four meetings. That’s it. If your IMO has more than four recurring meetings, at least two of them are redundant. Meetings are not governance. Decisions are governance. Meetings are just the room where decisions are supposed to happen. The number of meetings an organization schedules is inversely correlated with the number of decisions it actually makes.

Section 6: Success Metrics

Three to five numbers. Not KPIs. Not a balanced scorecard. Numbers that tell you whether the integration is on track.

Example:

• Synergy captured vs. target (cumulative, monthly)
• Days to close for open decisions (target: <14 days)
• Workstream milestone completion rate (% on time)
• Attrition rate for critical-role employees
• TSA exit progress (if applicable)

The temptation is to measure everything. Resist it. Every metric you add dilutes the ones that matter. If you have 25 KPIs, you have zero KPIs, because nobody can hold 25 numbers in their head during a steering committee meeting. They’ll look at the one that’s green and ignore the three that are red. I’ve watched it happen. The executive brain can track about five numbers simultaneously. Design for that constraint.

Section 7: How This Ends

Every IMO should have an exit clause. What conditions need to be true for the IMO to wind down? This is the section that nobody writes, and it’s the reason IMOs either die too early (someone decides “we’re done” before the synergies are captured) or live too long (the integration team becomes a permanent fixture because nobody defined when their job was finished).

Example exit criteria:

• 90%+ of synergy target captured and verified by Finance
• All workstreams transitioned to BAU owners with documented handoffs
• No open P1 escalations for 30 consecutive days
• Steering Committee votes to dissolve (requires sponsor sign-off)

I’ll have more to say about this in an upcoming piece on when to wind down the IMO. For now: if your charter doesn’t define the end state, your IMO will end by attrition rather than by design. People will leave. Meetings will get cancelled. One day someone will ask “do we still have an IMO?” and nobody will know the answer.

How to Use This Template

Copy the seven sections. Fill them in with your specific context. The whole thing should fit on one page, maybe two if your workstream list is long. Print it. Put it where people can see it. Not in SharePoint.

The charter is a contract between the IMO and the organization. It says: here is what we will do, here is what we won’t do, here is who decides what, here is how you’ll know if we’re succeeding, and here is when we’ll stop. If you can’t fit that on one page, you haven’t made the hard choices yet.

The long version, with all the supporting detail about IMO structure, staffing, and operating rhythm, is still worth reading. But the long version is the textbook. The one-page charter is the exam. And in an integration, nobody has time to read the textbook during the test.

Download the editable IMO charter template with all seven sections pre-formatted and ready to fill in. Duplicate it to your workspace, replace the bracketed placeholders with your specifics, and print it. To see how it maps to the first 100 days of an actual integration, reach out.

Related Reading

• Integration Management Office (IMO): How to Set One Up That Works
• 3 IMOs, 3 Industries: What Changed Every Time
• 100-Day Plan for M&A Integration: Practical Roadmap from Day 0 to Day 100
• M&A Integration Checklist: What Gets Missed (Day 1 to 100)
• Why 70% of Transformations Fail (And How to Be in the 30%)