This appendix provides a working reference for the terminology and abbreviations used throughout the playbook. Integration performance tracking brings together concepts from strategy, finance, project management, operations, technology, human resources, and transaction execution. The same word can carry different meanings across those disciplines, so the definitions below reflect how terms are used specifically in an integration performance context rather than every possible technical or accounting interpretation.
The terminology also sits within a broader strategy consulting context. The purpose of the glossary is therefore practical consistency: executives, integration leaders, finance teams, workstream owners, and advisors should be able to use the same language when discussing targets, forecasts, value, milestones, risks, and corrective actions. Within post-merger integration, shared definitions are especially important because two legacy organizations may begin with different management conventions, source systems, and reporting standards.
A.1 Glossary of Integration Performance Tracking Terms
Actual: A result that has occurred and has been recorded using the agreed source and recognition rules. Actuals may include financial results, completed milestones, employee counts, customer outcomes, or other observed performance. Actual should be distinguished from forecast, estimate, commitment, and run-rate value.
Annualized benefit: The annual equivalent of a recurring benefit based on an agreed reference period or current level of implementation. Annualization should account for seasonality, volume changes, and temporary effects where relevant rather than mechanically multiplying a favorable short-period result.
Baseline: The approved starting point against which integration performance is measured. A baseline should specify the period, organizational perimeter, source, accounting or operating definition, and any normalization. Changing a baseline changes the interpretation of performance and should therefore be controlled.
Benefit: A positive economic or operational effect expected from an integration initiative. Benefits can include recurring cost reduction, incremental margin, working-capital release, capital expenditure avoidance, productivity, risk reduction, service improvement, or another measurable outcome linked to the transaction thesis.
Benefit owner: The individual accountable for delivering a defined benefit. The benefit owner may rely on other functions for implementation or validation, but should have sufficient authority to manage the initiative, forecast the outcome, and escalate constraints that threaten realization.
Benefits realization: The process of converting identified value opportunities into implemented and validated business results. It includes initiative definition, baseline confirmation, target setting, implementation, financial validation, forecasting, and monitoring until the expected benefit is embedded in normal business performance.
Business-as-usual: The normal operating environment and management processes that continue after integration-specific governance ends. A measure is ready for business-as-usual ownership when it has a permanent owner, reliable source, established target, and recurring review forum outside the temporary integration structure.
Cash impact: The timing and amount of cash inflow or outflow associated with an integration action. Cash impact may differ from accounting expense or benefit because of payment terms, accruals, capitalization, working-capital movements, tax effects, or other timing differences.
Committed cost: An approved or contractual expenditure that has not yet fully appeared in actuals but is sufficiently certain to be included in cost control. Examples include executed statements of work, purchase orders, approved severance, retention awards, and noncancelable termination charges.
Cost synergy: A recurring reduction in the steady-state cost base attributable to combining organizations or eliminating duplication. Typical sources include procurement, headcount, facilities, technology, logistics, professional services, and shared functions. Cost synergy should be reported net of recurring offsets where applicable.
Critical path: The sequence of dependent activities or milestones that determines the earliest achievable date for a major event. A delay on the critical path causes the event date to move unless the team changes sequencing, resources, scope, or another schedule assumption.
Cutover: The controlled transition from an existing system, process, platform, facility, or operating arrangement to a target state. Cutovers typically require explicit readiness criteria, detailed execution sequencing, go/no-go authority, contingency plans, and a stabilization period after the transition.
Data lineage: The traceable path showing where a reported metric originated, how it was transformed, and how it reached the final dashboard or report. Good lineage allows a reviewer to reproduce a number and understand any adjustments made between source and presentation.
Decision log: A controlled record of material choices requiring management or governance action. It normally captures the decision question, recommendation, alternatives, decision owner, required-by date, final decision, date made, and any resulting change to scope, timing, cost, or risk.
Definition of complete: The explicit criteria and evidence required before a milestone, deliverable, or action can be reported as complete. It replaces subjective judgments such as “substantially done” with a verifiable standard that may include approvals, test results, reconciliation, or acceptance.
Dependency: A relationship in which one activity, milestone, decision, resource, or deliverable relies on another. Dependencies should identify the providing party, receiving party, required deliverable, required-by date, acceptance criteria, and consequence if the prerequisite is late or incomplete.
Dis-synergy: A recurring negative economic effect created by the transaction or integration. Examples can include additional control roles, higher service costs, lost customer revenue, duplicated technology, or added compliance expense. Dis-synergies should be distinguished from temporary one-time integration costs.
EBITDA impact: The effect of an integration initiative on earnings before interest, taxes, depreciation, and amortization, measured using the organization’s approved management definition. EBITDA impact should distinguish realized recurring performance from identified opportunities, implementation actions, and nonrecurring integration costs.
Evidence: The source material supporting a performance claim. Evidence may include system records, signed contracts, finance reports, HR records, test results, approvals, customer data, or completed control documentation. Higher-consequence claims should generally require stronger or independent evidence.
Exception: A performance condition outside an agreed tolerance or requiring management attention. Exception reporting focuses executive attention on material deviations, deteriorating trends, unresolved dependencies, or decisions rather than presenting every underlying metric with equal prominence.
Forecast: The current evidence-based expectation for a future result, date, cost, or benefit. A forecast should change when new information changes the expected outcome, while the original target or baseline remains visible for performance comparison and accountability.
Forecast to complete: The expected additional cost or effort required to finish an initiative or workstream from the current reporting date. In financial tracking, it is combined with actuals to produce the estimate at completion.
Go/no-go decision: A formal decision on whether a planned event should proceed based on predefined readiness criteria and current risk. Go/no-go decisions are common for system cutovers, customer migrations, facility transitions, TSA exits, and other events with significant consequences if launched prematurely.
Green-amber-red status: A standardized performance classification indicating whether a commitment is on track, at meaningful risk, or forecast to miss or require escalation. The classification should be based on defined thresholds and evidence rather than individual workstream preference.
Initiative: A coherent body of work designed to produce a specific integration outcome or benefit. A well-defined initiative has an owner, baseline, target, actions, milestones, timing, dependencies, and evidence requirements that allow management to track delivery and value.
Integration cost: An expenditure directly attributable to executing the transaction or transitioning the combined organization to its target state. Integration costs are generally temporary and should be distinguished from recurring operating costs, recurring dis-synergies, capital expenditure, and ordinary business spending.
Integration Management Office: The temporary coordination structure that establishes integration governance, planning, reporting, dependency management, escalation, and executive routines. Effective integration office setup creates common standards while leaving business and functional leaders accountable for delivering their outcomes.
Integration performance tracking: The management discipline that measures whether integration actions are delivering the milestones, synergies, financial results, operating outcomes, and risk controls expected from the transaction. Integration performance tracking links the deal thesis to evidence, forecasts, reporting, escalation, and corrective action.
Issue: A problem or adverse condition that has already occurred and is affecting delivery or performance. An issue differs from a risk, which remains uncertain. Material issues should have an owner, assessed impact, containment action, resolution plan, and expected closure date.
Key performance indicator: A measure used to assess performance against an important outcome, target, or operating condition. Integration KPIs should be limited to indicators that meaningfully inform decisions, provide evidence of progress, or signal material deterioration.
Lagging indicator: A measure that confirms an outcome after it has occurred, such as realized savings, customer churn, actual integration cost, service performance, or completed migrations. Lagging indicators provide strong evidence but may surface problems too late for early intervention.
Leading indicator: A measure that provides early evidence about whether a future result is likely to occur. Examples include contract execution, test pass rates, critical-role appointments, customer-contact completion, or unresolved dependencies. Leading indicators should have a credible causal relationship to outcomes.
Materiality: The threshold at which a variance, risk, issue, cost, or decision becomes important enough to change management action or governance visibility. Materiality can reflect absolute value, percentage variance, customer impact, regulatory consequence, schedule criticality, or another relevant dimension.
Metric dictionary: The controlled reference defining each reported measure, including its name, business meaning, calculation, scope, baseline, target, source, reporting frequency, owner, validator, and status thresholds. It prevents different workstreams from using the same label for different calculations.
Milestone: A meaningful and verifiable point of achievement that changes readiness, value, risk, or operating state. A milestone should have an owner, due date, definition of complete, evidence requirement, and connection to a broader event or outcome.
Net value: The economic benefit remaining after relevant recurring offsets, one-time integration costs, implementation expenditure, or other agreed adjustments. Net value provides a more complete view of transaction economics than gross synergy alone.
One-time integration cost: A temporary cost required to execute the transaction or move to the target operating state and expected to cease after the transition. Examples include severance, migration support, temporary duplicate systems, advisors, rebranding, and certain facility exit costs.
Outcome: The observable business result the integration is intended to produce or protect. Outcomes can be financial, customer, employee, operational, technology, regulatory, or risk related and should sit above activities and milestones in the measurement hierarchy.
Performance bridge: A structured reconciliation explaining how performance moved from a baseline or target to actual or forecast results. Bridges can isolate synergies, business-as-usual changes, timing, scope, cost, dis-synergies, and other drivers so executives understand the cause of variance.
P&L impact: The effect of an integration action on the income statement. P&L impact should be distinguished from cash flow, run-rate value, and noncash accounting effects because the timing and recognition of each can differ materially.
Recovery plan: A defined set of interventions intended to restore an outcome, date, value, or acceptable level of risk after performance deteriorates. A credible recovery plan includes root cause, actions, owners, proof points, expected impact, and a contingency trigger.
Reforecast: The process of updating the expected future result based on current evidence while preserving the original target or approved baseline. Reforecasting makes emerging gaps visible and should not be confused with formally resetting the commitment.
Rebaseline: The formal approval of a new target, date, budget, or scope because underlying conditions have materially changed. Good rebaselining preserves the original commitment, records the rationale and approval, and distinguishes the new baseline from the current forecast.
Reconciliation: The process of comparing data, definitions, or reported results from different sources and resolving or explaining material differences. Integration reconciliation commonly spans finance, HR, technology, operations, workstream trackers, and parent-company systems.
Reporting cadence: The agreed frequency and schedule for updating, validating, reviewing, and escalating performance information. Integration cadences may be daily for critical events, weekly for active execution, monthly for financial realization, and exception-based for urgent matters.
Risk: An uncertain event or condition that could affect value, schedule, cost, customers, compliance, operating continuity, or another integration outcome. Risks should identify potential impact, likelihood or trigger, mitigation, owner, and the condition under which escalation occurs.
Run-rate benefit: The recurring benefit expected at the current implemented level, usually expressed as an annual rate. Run-rate value shows the steady-state economics of an action but should not be presented as though the same amount has already been realized in-period.
Schedule variance: The difference between an approved baseline date and the current forecast or actual completion date. Schedule variance should be interpreted together with criticality, available float, downstream dependencies, and business impact rather than treated as equally important across all activities.
Service continuity: The ability to maintain required customer, employee, supplier, regulatory, or operational services during integration. Continuity measures can include availability, delivery performance, response times, transaction success, incident severity, backlog, and other indicators appropriate to the operating environment.
Single source of truth: A governed arrangement in which there is one authoritative version of each decision-relevant fact, even when multiple source systems remain in use. It requires clear ownership, definitions, lineage, cut-off dates, and controlled transformations rather than one universal software platform.
Stabilization: The period after a migration, cutover, organizational change, or other major event during which performance is monitored until the new operating state is reliable. Stabilization criteria should be defined in advance and may include service, defect, customer, control, or productivity thresholds.
Steering committee: The executive governance forum responsible for resolving material cross-workstream issues, approving significant changes, allocating resources, making integration decisions, and holding leaders accountable for outcomes. Its agenda should emphasize exceptions and decisions rather than routine status narration.
Synergy: Incremental economic value made possible by the transaction that would not reasonably be expected from the businesses operating independently under the baseline case. Synergies can include recurring cost reduction, revenue or margin growth, working-capital improvement, or other quantified value.
Target: The approved performance level, value, date, or outcome against which delivery is assessed. Targets should remain stable unless formally rebaselined. The current forecast may differ from the target and should be shown separately to preserve accountability.
Transition Service Agreement: A temporary contractual arrangement under which a seller, former parent, or another party continues providing services during transition. TSA tracking should cover service performance, cost, replacement capability, exit milestones, dependencies, notice requirements, and any extension risk.
TSA exit: The controlled termination of a transition service after the receiving organization has established and validated the replacement capability. Exit should be based on operational readiness, not merely contractual date or technical availability, and may require business acceptance and contingency planning.
Value at risk: The amount of expected value exposed to an identified risk, delay, issue, or performance gap. It helps management prioritize attention by connecting execution problems to potential economic consequence rather than ranking every risk only by qualitative severity.
Value capture: The process of converting the transaction thesis into realized economic results. Value capture covers identification, initiative design, implementation, validation, forecasting, and embedding of benefits into budgets and normal performance management.
Value driver: The economic or strategic mechanism through which the transaction is expected to create value, such as procurement scale, customer cross-selling, footprint consolidation, technology rationalization, improved capacity utilization, working-capital efficiency, or access to a new capability.
Variance: The difference between actual or forecast performance and an approved baseline, target, or budget. Useful variance analysis explains the underlying driver, such as price, volume, scope, timing, foreign exchange, execution, or accounting treatment, rather than reporting the difference alone.
Workstream: A defined area of integration responsibility, usually organized around a function, business process, value driver, or major event. Typical workstreams include finance, HR, technology, commercial, operations, procurement, legal, communications, and synergy realization.
Workstream scorecard: A standardized summary showing a workstream’s outcomes, KPIs, critical milestones, financial commitments, risks, dependencies, decisions, status, and trend. The scorecard should provide decision-relevant exceptions while linking back to detailed controlled records.
Working-capital benefit: Cash value created through sustainable improvement in receivables, payables, inventory, or other operating balances. Working-capital benefits should be tracked separately from recurring P&L synergies because their accounting, timing, and sustainability characteristics differ.
A.2 Common Acronyms and Abbreviations
BAU: Business as Usual. The permanent operating environment and management process that remains after temporary integration governance and reporting are retired.
CapEx: Capital Expenditure. Spending capitalized on the balance sheet rather than expensed immediately. Integration technology, facility, and equipment investments may require separate CapEx tracking alongside operating expense and cash impact.
CRM: Customer Relationship Management. A system or process used to manage customer, account, opportunity, and commercial information. CRM migration and data quality are often central to commercial integration tracking.
EBIT: Earnings Before Interest and Taxes. An operating profitability measure that includes depreciation and amortization and may be used in financial bridges depending on company reporting conventions.
EBITDA: Earnings Before Interest, Taxes, Depreciation, and Amortization. A commonly used measure of operating performance and value creation, particularly in private equity and sponsor reporting.
EAC: Estimate at Completion. The current expected total cost when an initiative, project, or workstream is finished, typically calculated from actuals plus forecast remaining cost.
ERP: Enterprise Resource Planning. An integrated system supporting finance, procurement, supply chain, inventory, manufacturing, and other core processes. ERP migrations often create major integration milestones and dependencies.
ETC: Estimate to Complete. The forecast additional cost, effort, or resources required from the current point through completion. ETC is combined with actuals to support the EAC.
FTE: Full-Time Equivalent. A standardized unit representing employee capacity. FTE is used in workforce, productivity, shared-services, and organizational synergy analysis and should have a consistent inclusion definition.
FP&A: Financial Planning and Analysis. The finance function responsible for budgets, forecasts, performance analysis, and management reporting. FP&A commonly validates integration forecasts and helps embed benefits into business plans.
GL: General Ledger. The primary accounting record contains recognized financial transactions. GL actuals are normally the authoritative source for integration expense and financially realized benefits where the accounting structure permits identification.
HR: Human Resources. The function responsible for workforce, organization, talent, compensation, employee relations, and related processes. HR data are central to workforce actions, retention, and organization-integration tracking.
HRIS: Human Resources Information System. The system of record for employee and organizational data. HRIS data often support headcount baselines, workforce migration, role changes, and benefit validation.
IMO: Integration Management Office. The temporary governance and coordination structure responsible for integration planning, cross-workstream alignment, performance reporting, escalation, and executive routines.
IT: Information Technology. The function covering systems, infrastructure, applications, data, cybersecurity, support, and related capabilities. IT is often a major source of integration dependencies, costs, and cutover risk.
KPI: Key Performance Indicator. A measure used to evaluate progress or performance against an important target, outcome, or operating condition.
M&A: Mergers and Acquisitions. Transactions involving the acquisition, combination, or sale of businesses. Integration performance tracking begins after or around transaction close and connects execution to the M&A value thesis.
NWC: Net Working Capital. A measure generally derived from operating current assets and liabilities. Integration initiatives may target improvements in inventory, receivables, payables, and related cash conversion.
O2C: Order to Cash. The end-to-end process from customer order through fulfillment, billing, collection, and cash receipt. O2C performance is often important during customer, ERP, and shared-services migrations.
OpEx: Operating Expenditure. Costs recognized through normal operating expenses. Integration reporting should distinguish temporary integration OpEx from recurring operating costs and capitalized expenditure.
OTIF: On Time In Full. A service measure indicating whether orders are delivered by the committed date and in the complete quantity. OTIF can be a critical guardrail during supply-chain integration.
P&L: Profit and Loss statement. The income statement used to report revenue, costs, and earnings. Integration benefits and costs should be reconciled to P&L impact where financially measurable.
PE: Private Equity. Investment ownership in privately held companies. PE sponsors often require integration reporting focused on EBITDA, cash, value creation, timing, and management accountability.
PMO: Project Management Office. A structure that supports project governance, planning, milestones, risks, dependencies, reporting, and decision management. In integration contexts, PMO responsibilities may overlap with or sit within the IMO.
RACI: Responsible, Accountable, Consulted, Informed. A framework for clarifying roles in activities and decisions. It can be useful for defining workstream ownership, validation responsibilities, and governance interfaces.
RAG: Red-Amber-Green. A status convention used to indicate whether performance is on track, at risk, or materially off track. RAG definitions should be standardized and supported by evidence.
SG&A: Selling, General and Administrative expense. A broad operating-cost category where many corporate-function, technology, professional-services, and workforce synergies may be recognized.
SLA: Service Level Agreement. A documented standard for service performance between providers and recipients. SLAs are particularly important for TSAs, shared services, technology support, and joint-venture parent services.
SME: Subject Matter Expert. A person with specialized functional, technical, regulatory, or industry knowledge. SMEs may validate assumptions, define readiness criteria, or support resolution of complex integration issues.
SOP: Standard Operating Procedure. A documented method for performing a recurring process. New or revised SOPs may be required before operational migration or business-as-usual handoff is considered complete.
SOW: Statement of Work. A contractual document defining services, deliverables, timing, responsibilities, and commercial terms for an external provider. SOWs often form part of integration cost commitments.
TSA: Transition Service Agreement. A temporary service arrangement supporting operations while the receiving organization establishes replacement capabilities. TSA exit is often a major integration milestone and cost driver.
UAT: User Acceptance Testing. Testing performed to confirm that a system or process meets business requirements and is ready for operational use. UAT completion is frequently a critical cutover readiness gate.