Building the Bottom-Up Synergy Capture Plan

6.1 Converting Opportunities into Initiative Charters

A synergy opportunity becomes executable when it is translated into a defined initiative. The initiative is the basic unit of the capture plan: a sufficiently specific management action with an identifiable economic result, accountable owner, implementation path, and method of validation. The objective is to create enough detail to manage delivery without turning the synergy program into a task-level project schedule containing thousands of minor activities.

A good initiative begins with an action-oriented statement. “Procurement synergy” is a value pool, not an initiative. “Consolidate North American packaging suppliers and harmonize carton specifications” describes an operating change. “Corporate overhead reduction” is similarly too broad, whereas “combine regional finance organizations under a single shared-services model” defines a management action that can be designed, approved, and implemented.

The initiative charter should explain the economic mechanism. Management should be able to see how the proposed action changes the baseline and produces the expected benefit. A sourcing initiative might reduce the price on $30 million of addressable spend by 6 percent, creating $1.8 million of annual savings. A workforce initiative might remove fifteen duplicated positions with $2.4 million of fully loaded recurring cost while adding three new roles costing $450,000, producing $1.95 million of net recurring benefit. Showing the mechanism makes assumptions challengeable and reduces the risk that targets become unsupported financial plugs.

Each material charter should contain several core elements:

• Initiative definition: A concise description of the operating change and the business rationale.
• Baseline and target: The relevant cost, revenue, headcount, spend, asset, or other denominator and the expected financial benefit.
• Scope: The entities, functions, geographies, customers, products, suppliers, sites, or systems affected.
• Implementation actions: The major steps required to move from current state to the intended outcome.
• Milestones: Events that demonstrate meaningful progress, including approvals, contractual actions, launches, migrations, exits, or other implementation points.
• Economics: Gross benefit, recurring offsets, cost to achieve, in-period impact, and expected full run rate.
• Dependencies and risks: Decisions, systems, resources, contracts, regulatory requirements, and related initiatives that affect delivery.
• Ownership and validation: The executive accountable for implementation and the finance representative responsible for validating financial treatment.

The appropriate level of granularity requires judgment. An initiative should generally correspond to a coherent action that one executive can own and management can review as a meaningful unit. A $50 million procurement target spread across twenty unrelated categories is probably too broad because different suppliers, contracts, and implementation paths are involved. Creating a separate initiative for every individual purchase order would be unnecessarily detailed. Category-level or sourcing-wave initiatives may provide the appropriate middle ground.

Charters should distinguish committed value from upside. If an initiative has a high-confidence core worth $5 million and another $3 million dependent on unresolved assumptions, management should preserve that distinction. Combining both into an $8 million commitment makes the target appear more certain than the evidence supports. Upside opportunities can remain associated with the initiative while further validation continues.

Implementation detail should match the maturity of the initiative. Early charters may contain ranges, provisional owners, and unresolved dependencies. As the initiative approaches approval and launch, these fields should become more precise. The charter is a living management document, not a one-time diligence output. Material changes to value, timing, scope, or cost should be recorded rather than silently overwritten.

Charters should also identify the evidence that will ultimately demonstrate realization. A headcount initiative may require confirmed employee exits and payroll evidence. A sourcing initiative may require executed supplier terms and invoice-level validation. A revenue initiative may rely on specified customers, transactions, or products. Defining the evidence before execution prevents later disagreement about whether an initiative has actually delivered its promised value.

In a joint venture, the charter should state whether the initiative is controlled by venture management, a shareholder, or a shared governance body. If capture requires a parent to provide access to customers, renegotiate an agreement, transfer employees, or make an asset available, that dependency should be explicit. The initiative should not be written as though the venture CEO can unilaterally deliver value that requires shareholder action.

6.2 Assigning Initiative Owners, Targets, Milestones, and Accountabilities

Synergy initiatives require individual accountability. Committees, workstreams, and functions can support delivery, but a target owned by “the integration team” or “procurement and operations” often becomes a target owned by nobody. Each material initiative should have one accountable executive who can explain the economics, obtain required decisions, mobilize resources, manage dependencies, and answer for variances.

The owner should be selected based on authority over the value mechanism rather than authorship of the analysis. A consultant may develop the business case, and the integration office may track implementation, but neither substitutes for an operating owner. A procurement executive may own a sourcing initiative; a business-unit leader may own a customer cross-sell initiative; the chief information officer may own application rationalization. Where several functions participate, one leader should remain accountable for the overall result.

Ownership should be accepted, not merely assigned in a spreadsheet. Before an initiative becomes a formal commitment, the owner should review its baseline, target, assumptions, required actions, timing, costs, risks, and dependencies. Disagreement is better resolved at this stage than after leadership has begun reporting the target. Acceptance does not mean the owner can unilaterally reduce an ambitious goal; it means that management has created an explicit conversation about what the initiative requires.

Targets should specify the financial measure being owned. An owner may be accountable for annual run-rate savings, in-year EBITDA impact, incremental contribution margin, working-capital release, or avoided capital expenditure. Those measures are not interchangeable. The charter should show the relevant target and, where necessary, the bridge to other measures used by senior leadership. This prevents an owner from reporting a full run-rate result when the steering committee expects current-year P&L impact.

Milestones convert a distant financial target into observable evidence of progress. Effective milestones represent outcomes or decisions that materially advance capture. Examples include approving a future-state organization, issuing a supplier request for proposal, signing a renegotiated contract, completing employee consultation, obtaining customer approval, migrating a defined user population, closing a facility, or retiring an application. Milestones such as “continue analysis” or “hold workshop” describe activity rather than progress and provide weak warning of eventual delivery risk.

The milestone sequence should expose the critical path. If a $10 million technology saving requires application migration before a vendor contract can be terminated, the plan should separately identify design approval, migration readiness, testing, user transition, system retirement, and contract exit. Management can then see slippage months before the financial target is missed. Without intermediate milestones, an initiative may appear on track until the scheduled realization date has already become impossible.

Accountability extends beyond the initiative owner. A practical role structure typically distinguishes several responsibilities:

• Executive owner: Accountable for the operating action and delivery of the target.
• Initiative lead: Manages day-to-day analysis, planning, coordination, and milestone execution where the executive owner delegates detailed work.
• Finance partner: Validates baseline, calculation, recognition rules, and realized financial impact.
• Dependency owners: Deliver specific prerequisites controlled by another function or organization.
• Integration office: Maintains standards, consolidates reporting, challenges progress, and escalates unresolved issues.

Accountability should not be confused with blame. Complex integrations generate new facts and legitimate changes in assumptions. Owners should be encouraged to surface problems early rather than protect a green status until recovery is impossible. Governance should distinguish controllable execution misses from evidence-based changes to value or timing. The purpose of ownership is to accelerate decisions and corrective action.

Targets may also require cascading. A functional leader could own a $20 million total target made up of six initiatives whose day-to-day leads sit in different businesses. The master register should preserve both levels without counting the aggregate target as additional value. Senior leadership needs a manageable view of accountability while implementation teams need enough specificity to execute.

Joint ventures require special clarity because economic accountability and governance authority can reside in different places. The venture chief procurement officer might own a target whose delivery depends on a shareholder granting access to a master supply agreement. The venture owner remains responsible for coordinating the initiative, but the shareholder dependency requires its own named owner and due date. Reserved matters should be reflected as formal approval milestones when board or shareholder consent is necessary.

6.3 Mapping Dependencies, Prerequisites, and Critical Decisions

Synergy initiatives rarely operate independently. Organizational reductions may depend on system migration. Facility closures may depend on transferring production. Procurement savings may require product specification changes. Revenue synergies may require new incentives, customer-data integration, regulatory approvals, or product availability. A bottom-up plan that records targets without these relationships will systematically overstate how quickly value can be realized.

A dependency exists when one initiative, decision, resource, or external event affects another initiative’s ability to proceed. Teams should identify dependencies while charters are being developed rather than discovering them only when execution stalls. The most important dependencies are those that can delay the critical path, change the value case, or require decisions from leaders outside the initiative owner’s authority.

Dependencies can be grouped into several practical categories. Decision dependencies require management approval, such as selecting a future system or deciding which facility will remain. Operational dependencies require another process or workstream to complete an action. Technology dependencies involve system availability, migration, interfaces, or data. Contractual dependencies involve supplier, customer, lease, licensing, or transaction agreements. People dependencies involve staffing, consultation, retention, or knowledge transfer. Regulatory dependencies require government, antitrust, industry, or other formal approvals.

Each material dependency should identify the providing party, receiving initiative, required output, required date, current status, and consequence of delay. Simply noting “dependent on IT” is insufficient. A useful statement might specify that the finance organization initiative cannot remove twelve legacy-system support roles until the ERP migration is completed and stabilized, with the technology workstream accountable for a September 30 migration date. That level of definition allows both parties and senior management to act.

Prerequisites should be distinguished from parallel work. Some actions genuinely prevent an initiative from starting; others can proceed concurrently. Over-sequencing can unnecessarily delay value. For example, a combined procurement team may begin supplier negotiations before every organizational decision is finalized, provided authority and confidentiality rules permit it. Conversely, terminating system support before business users have migrated creates unacceptable risk. Owners should ask what must be complete, what must merely be sufficiently advanced, and what can proceed in parallel.

Critical decisions deserve their own tracking discipline. Integrations often lose time not because analysis is incomplete, but because leaders postpone choices among competing options. Facility selection, organization structure, technology platform, brand architecture, supplier strategy, product rationalization, and customer ownership can each unlock multiple synergy initiatives. The capture plan should identify the decision owner, decision date, required analysis, alternatives, and economic consequences of delay.

Where possible, the team should quantify those consequences. If each month of delay in a facility decision shifts $500,000 of savings, leadership can compare the cost of waiting with the value of obtaining additional information. Decision economics helps move discussions from general urgency to specific trade-offs. They also reveal which issues deserve steering-committee attention and which can remain within functional governance.

Dependency mapping should look across the entire initiative portfolio rather than remain within individual workstreams. Technology may be the prerequisite for finance, HR, commercial, and supply-chain synergies simultaneously. A small delay in one migration can therefore threaten a disproportionate amount of value. Aggregating dependencies identifies these concentration risks and allows management to prioritize scarce resources accordingly.

Legal-close restrictions must also be reflected. Some pre-close planning can be detailed, but implementation may be prohibited until control legally transfers. The plan should identify which milestones can occur before close, which require clean-team arrangements, and which must wait. Treating close as a generic milestone without understanding specific legal constraints can either delay legitimate preparation or encourage inappropriate premature coordination.

In joint ventures, governance dependencies are often central to the critical path. Shareholder approvals, board reserved matters, intellectual-property licenses, supply agreements, secondment arrangements, customer-access rights, and parent service agreements may all determine whether value can be captured. These should appear alongside operational dependencies in the initiative plan. Governance is part of execution architecture, not a separate legal workstream detached from synergy delivery.

6.4 Avoiding Overlap and Double Counting Across Initiatives

As synergy planning becomes more detailed, the risk of double counting increases. Multiple teams may identify different actions affecting the same cost, customer, supplier, facility, employee, or system. Each initiative may be reasonable on its own while the combined portfolio claims more value than the economic baseline permits. Preventing overlap therefore requires both analytical controls and active cross-functional review.

Double counting commonly occurs when initiatives are organized by functional ownership rather than underlying value source. Procurement may claim savings from reducing a software vendor contract while technology claims the same contract as part of application rationalization. Real estate may claim all facility expenses from closing an office while HR claims occupancy allocations associated with eliminated positions. A commercial team may claim revenue from cross-selling a product while a product team separately includes the same customers in a portfolio-growth target.

The first control is a clear value-driver hierarchy. Every synergy should have one primary economic source. An initiative may produce several operational consequences, but the recurring benefit should be attributed once. If application retirement eliminates a software contract, management should decide whether the technology initiative or procurement initiative owns the savings. The other workstream may retain a supporting milestone without adding the same financial value to its target.

The second control is reconciliation to the addressable baseline. If two initiatives together claim $12 million of savings against a $10 million cost pool, analysts should be able to explain whether the initiatives affect different future costs or whether an overlap exists. Similar checks can be performed against supplier spend, headcount, facility cost, customer revenue, product margin, or capital plans. Baseline reconciliation places an objective boundary around aggregate claims.

Teams should distinguish sequential improvements from duplicate savings. Suppose a supplier category has $100 million of spend. Demand management reduces required volume by 10 percent, leaving $90 million. A sourcing initiative then lowers price by 5 percent. The savings are not $10 million plus $5 million calculated on the original baseline; the price saving applies to the remaining $90 million and equals $4.5 million. The combined benefit is $14.5 million. The order of operations matters whenever multiple levers affect the same baseline.

Headcount initiatives create another recurring challenge. A functional restructuring may remove employees while a process-automation initiative assumes labor savings from the same team. The automation case must be calculated against the future-state organization or clearly identify additional positions that can be removed beyond the organizational redesign. Otherwise two projects claim the same salaries.

Commercial initiatives require comparable controls. Cross-sell, pricing, channel expansion, retention, and product bundling can affect the same customers. The master plan should identify customer segments, products, or transactions associated with major revenue initiatives and establish the sequence of calculations. A customer’s incremental purchase should not be counted once as cross-sell and again as channel expansion simply because two teams contributed to the sale.

Overlap reviews should occur before targets are formally committed and again when material initiatives change. A monthly or milestone-based review can focus on new initiatives, scope changes, and value increases rather than rechecking every item. Finance and the integration office are well positioned to coordinate these reviews because they see the aggregate portfolio, but functional owners must provide the operational detail needed to resolve conflicts.

Teams should also guard against subtler forms of double counting across financial categories. A facility closure can produce recurring occupancy savings, a one-time property sale, and reduced future capital expenditure. All three can be legitimate, but they must remain separate economic effects. Working-capital release should not be added to EBITDA synergy, and avoided capital should not be presented as recurring operating savings. Clear classification allows leadership to understand total value without conflating different measures.

Joint ventures can create double counting between venture and shareholder business cases. A parent may record a benefit from selling services to the venture while the venture records the purchased service as part of its operating model. Likewise, a shareholder may claim avoided investment while the venture counts use of the contributed asset as an operating advantage. Management should show value at the level where it is economically created and separately bridge distributions or transfers to shareholders rather than summing internal flows as independent synergy.

6.5 Building and Maintaining the Master Synergy Initiative Register

The master synergy initiative register is the authoritative record of the capture portfolio. It consolidates initiatives across functions and translates individual charters into a management view of total value, timing, ownership, confidence, risk, and progress. The register should serve as the source for steering-committee reporting, finance reconciliation, implementation reviews, and changes to the synergy forecast. When several workstreams maintain competing spreadsheets, management quickly loses confidence in which number is current.

The register should use a unique identifier for every initiative and preserve that identifier throughout the integration. Titles and owners may change, initiatives may be split or combined, and financial values may be revised, but stable identifiers create traceability. If an initiative is retired, its history should remain visible rather than being deleted. Management should be able to reconstruct how the current forecast evolved from the original plan.

Core fields normally include initiative ID, title, description, function, business unit, geography, executive owner, initiative lead, baseline, gross benefit, recurring offsets, net benefit, cost to achieve, financial classification, confidence, implementation status, key milestones, expected run-rate date, in-period impact, dependencies, risks, finance validation status, and latest commentary. Revenue, working-capital, and capital initiatives may require additional fields reflecting their particular economics.

Status definitions should be standardized. A practical stage model might include identified, validated, approved, launched, implemented, and realized. Each stage should have an objective definition. “Validated,” for example, might require an agreed baseline, supported calculation, owner acceptance, and major dependencies identified. “Realized” should require evidence under finance-approved recognition rules. Without definitions, different workstreams will use status labels inconsistently and the consolidated dashboard will provide false precision.

The register should retain multiple financial views where management needs them. The original deal-case target should remain distinguishable from the current committed forecast. Upside should remain separate from committed value. Achieved run rate should be distinguishable from in-year P&L impact and realized cash. Cost to achieve should not be netted invisibly against recurring synergy. These distinctions allow leaders to answer different questions without maintaining separate uncontrolled models.

Change control is essential. Initiative values will change as post-close information improves, supplier negotiations occur, organizational designs are approved, and implementation challenges emerge. Material changes should record the previous value, revised value, reason, date, and approving authority. A reduction caused by corrected baseline data differs from a reduction caused by execution failure; both should be visible. Similarly, newly discovered opportunities should be added transparently rather than used silently to mask shortfalls elsewhere.

Ownership changes should receive similar discipline. Executives move, organization structures change, and integration responsibilities transition to the business. Every initiative should always have a current accountable owner. When responsibility transfers, the outgoing and incoming owners should review status, assumptions, open decisions, and upcoming milestones. Changing a name in the register without an explicit handoff creates accountability gaps precisely when implementation may already be under pressure.

The register should support exception-based management rather than become an administrative reporting exercise. Senior leaders rarely need to review every initiative in equal depth. The system should highlight material value at risk, missed milestones, unresolved dependencies, forecast changes, decisions approaching deadlines, and initiatives whose confidence is deteriorating. Smaller initiatives can remain visible in aggregate while management focuses discussion on the issues that could materially affect transaction value.

Data quality needs an owner. The integration office typically administers the register, but initiative owners remain responsible for the accuracy of operational information and finance remains responsible for financial validation. Updates should occur on an agreed cadence, with late or incomplete submissions visible. Automation can reduce manual effort, but a sophisticated platform cannot compensate for weak definitions or unchallenged owner forecasts.

As the integration matures, the register should connect with normal management systems. Approved synergies should flow into budgets, forecasts, workforce plans, procurement targets, commercial plans, and capital programs. Once an initiative has become part of ordinary business management and its economics are consistently visible in actual results, the special integration process can eventually close it. The objective is to institutionalize the benefit, not to track the initiative indefinitely.

Joint ventures should adapt the register to reflect shareholder responsibilities and governance rights. Fields may identify the venture owner, shareholder dependency owner, required board or shareholder approval, contractual instrument, and entity in which value is realized. This prevents the venture management team from being held solely accountable for actions outside its control while preserving visibility into the full business case.

A well-maintained master register creates a single chain of accountability from synergy hypothesis to realized financial result. Every material value commitment should be traceable to an initiative, owner, baseline, calculation, milestone path, dependency set, approval history, and validation method. That discipline gives executives a reliable view of whether the transaction’s value agenda is advancing and gives initiative owners a practical mechanism for turning analytical opportunities into operating results.