The 100-Day Manufacturing Integration Checklist

A manufacturing integration plan must protect production while the business changes. This post-merger integration checklist turns diligence findings into priorities for Day One and the first 100 days, with accountable roles, completion evidence and operating measures.
Use it to decide what must change now, what must wait and who owns the result.
How to use this checklist
Use this guide if you lead an acquisition, a PE portfolio integration or the operations of a manufacturer joining another business. Start before close, assign one accountable person to each action and review evidence weekly.
The dates are decision checkpoints, not deadlines for forcing every system or plant onto one model.
The executive sponsor approves scope and resolves cross-functional decisions. The integration lead coordinates workstreams; plant leaders protect daily operations.
Finance validates the value case. Quality, safety, supply chain, HR and IT own the controls in their areas.
For each action, record: named owner, target date, priority, dependency, status, evidence link and next decision. Use Not started, In progress, Blocked, Complete or Not applicable.
Mark an action Complete only after the responsible leader accepts its evidence. Explain why any action is Not applicable.
P0 means continuity, safety or a closing requirement. P1 means necessary integration control.
P2 means an improvement that can follow stabilization. Escalate unsafe conditions immediately under the site's safety procedures; do not wait for the weekly meeting.
Adapt targets to the business and obtain the relevant professional review for employment, contractual, environmental and regulatory decisions.
Before close, keep the businesses independent and use only information and planning activities cleared by the transaction's legal team. Do not change prices, allocate customers, direct the target's production or combine systems before the appropriate authorization.
Our post-merger integration work connects the deal thesis to the work on the plant floor. Begin with operational due diligence when the acquisition is still being evaluated.
Before close: what to lock down from diligence
Turn the deal thesis into a controlled handoff. Record the assumptions behind capacity, margin and synergies, identify the risks to continuity and name the people who can authorize decisions after close. Our guide to synergy tracking after an acquisition shows how to tie each synergy to an owner and a baseline.
Planning should expose unknowns rather than make the target appear more ready than the evidence supports.
If the deal has not closed yet, the manufacturing due diligence checklist lists the records to request and the red flags to test on the site visit. To see what an accounting review leaves out, compare operational due diligence and quality of earnings.
- Define the acquisition objectives and specify what must remain separate. Owner: sponsor; milestone: before close; priority: P1; evidence: approved integration scope; measure: unresolved scope decisions; dependency: deal thesis; risk: unnecessary integration.
- Translate each material diligence finding into a risk, action and accountable owner. Owner: integration lead; milestone: before close; priority: P1; evidence: diligence-to-action register; measure: high-risk findings without owners; dependency: permitted diligence access; risk: lost context at handoff.
- Establish decision rights and escalation limits for purchases, customers, staffing and capital. Owner: sponsor; milestone: before close; priority: P0; evidence: authority matrix ready for activation; measure: critical decisions without an approver; dependency: legal approval; risk: stalled decisions.
- Baseline delivery, backlog, demonstrated capacity, scrap, inventory and cash using agreed definitions. Owner: finance lead with plant leaders; milestone: before close; priority: P1; evidence: dated baseline and reconciliation notes; measure: missing baseline fields; dependency: reliable source data; risk: incomparable results.
- Validate each proposed synergy against a specific contract, process, site or role. Owner: finance lead; milestone: before close; priority: P1; evidence: assumption register with costs and timing; measure: unvalidated synergy value; dependency: lawful access; risk: double counting.
- Map critical suppliers, customer commitments, tooling, maintenance and single points of failure. Owner: operations lead; milestone: before close; priority: P0; evidence: continuity risk map; measure: critical exposures without contingencies; dependency: site review; risk: production interruption.
- Prepare shift-level communication and retention plans for critical skills. Owner: HR lead; milestone: before close; priority: P1; evidence: approved messages and coverage plan; measure: critical roles without backup; dependency: employment review; risk: knowledge loss.
- Rehearse the Day One plan, including access, payments, order release and rollback responsibilities. Owner: integration lead; milestone: before close; priority: P0; evidence: rehearsal log and open exceptions; measure: unresolved launch blockers; dependency: approved closing sequence; risk: an untested cutover.
Day One: the non-negotiables
Day One succeeds when people can work safely, customers receive the promised service and essential controls remain intact. Confirm readiness on every affected shift and site.
Avoid combining major production or systems changes with ownership transfer unless the change is essential, tested and explicitly authorized.
For the full list of checks by area, use the Day One readiness checklist for a manufacturing acquisition. If the deal combines sites, read how to integrate two manufacturing plants after an acquisition.
- Confirm safety responsibilities, emergency contacts and access to current work instructions. Owner: EHS lead; milestone: before each shift starts; priority: P0; evidence: signed readiness check; measure: unresolved critical hazards; dependency: site-level verification; risk: unsafe work.
- Verify customer orders, shipping documents and escalation contacts remain usable. Owner: commercial lead; milestone: first dispatch; priority: P0; evidence: order-to-shipment check; measure: missed committed shipments; dependency: order and logistics access; risk: lost service.
- Confirm payroll, benefits continuity and employee support contacts. Owner: HR lead; milestone: first payroll cutoff; priority: P0; evidence: payroll reconciliation and exception owner; measure: unresolved payroll exceptions; dependency: approved employment arrangements; risk: employee harm and distrust.
- Activate authorized user access and test essential business transactions. Owner: IT lead; milestone: start of business; priority: P0; evidence: access test and incident route; measure: critical transaction failures; dependency: approved identity and security plan; risk: blocked work or excess access.
- Verify purchasing authority, supplier payment routes and change-of-bank-detail controls. Owner: finance lead; milestone: first payment or purchase; priority: P0; evidence: approved controls and verification record; measure: blocked critical payments; dependency: validated bank and authority setup; risk: fraud or supply stoppage.
- Check quality release, traceability and customer approval requirements before shipping. Owner: quality lead; milestone: first shipment; priority: P0; evidence: release and traceability check; measure: unapproved releases; dependency: product and regulatory requirements; risk: nonconforming product.
- Deliver one consistent ownership message across sites and shifts. Owner: integration lead with HR; milestone: Day One; priority: P1; evidence: briefing log and question owner; measure: shifts not briefed; dependency: approved communication; risk: conflicting instructions.
- Open the issue log and assign decision owners, next actions and escalation times. Owner: integration lead; milestone: Day One close; priority: P0; evidence: triaged issue register; measure: critical issues without a next action; dependency: workstream contacts; risk: unresolved operational failures.
Days 1 to 30: stabilize
Establish a trustworthy picture of how the combined operation performs before accelerating change. Validate the baseline on the floor, resolve immediate risks and build a short workstream cadence.
Separate work that protects continuity from work that improves the business, so urgent delivery problems do not hide integration dependencies.
- Review delivery, safety, quality and cash exceptions in a short daily cadence. Owner: operations lead; milestone: first week; priority: P0; evidence: action log with closure evidence; measure: overdue critical exceptions; dependency: daily source data; risk: hidden deterioration.
- Reconcile plant reports with finance and agree one KPI dictionary. Owner: finance lead; milestone: Day 15; priority: P1; evidence: definitions, sources and sign-off; measure: unreconciled KPI differences; dependency: baseline access; risk: competing versions of performance.
- Validate bottlenecks using actual mix, run time, changeover and maintenance constraints. Owner: plant leader; milestone: Day 20; priority: P1; evidence: constraint study by product family; measure: demonstrated throughput and schedule attainment; dependency: observed operating conditions; risk: overstated capacity.
- Review quality-system differences and preserve controls needed for traceability and release. Owner: quality lead; milestone: Day 20; priority: P0; evidence: control-gap and change-control register; measure: overdue critical quality gaps; dependency: product requirements; risk: premature standardization.
- Confirm supply coverage and alternatives for critical materials and outside processes. Owner: supply chain lead; milestone: Day 15; priority: P0; evidence: supplier continuity plan; measure: uncovered critical-material days; dependency: demand and inventory data; risk: shortages.
- Interview key employees across shifts and assign backup coverage for critical work. Owner: HR lead with plant leaders; milestone: Day 30; priority: P1; evidence: skills and retention action plan; measure: critical tasks with one trained person; dependency: supervisor input; risk: key-person dependency.
- Rank initiatives by continuity risk, value, dependency and management capacity. Owner: integration lead; milestone: Day 30; priority: P1; evidence: approved sequence and deferred decisions; measure: active initiatives without capacity; dependency: workstream plans; risk: change overload.
- Revalidate the synergy register and distinguish potential, approved and realized benefits. Owner: finance lead; milestone: Day 30; priority: P1; evidence: reconciled benefit register; measure: benefits lacking a baseline or owner; dependency: contract and cost evidence; risk: reporting plans as savings.
Days 31 to 60: align
Choose common processes only after comparing their operating evidence and dependencies. Pilot important changes in a controlled area, agree acceptance criteria and preserve a fallback.
Aligning data and standard work can start now; a plant transfer or ERP replacement may need a much longer timetable.
- Compare plant roles using capability, quality, capacity, freight and customer requirements. Owner: operations lead; milestone: Day 45; priority: P1; evidence: footprint options and assumptions; measure: unresolved decision dependencies; dependency: demonstrated capacity; risk: moving work before readiness.
- Pilot selected standard work with employees from both businesses. Owner: plant leader; milestone: Day 45; priority: P1; evidence: approved trial and training records; measure: first-pass yield and cycle-time variation; dependency: quality change control; risk: copying the weaker process.
- Review duplicate supplier contracts and total landed cost before consolidation. Owner: procurement lead; milestone: Day 50; priority: P1; evidence: sourcing case with service and termination effects; measure: validated cost opportunity and supply risk; dependency: contract review; risk: savings offset by failures.
- Map item masters, routings, inventory records and finance codes before systems migration. Owner: IT lead with finance; milestone: Day 45; priority: P1; evidence: data mapping and reconciliation tests; measure: unresolved critical data defects; dependency: source-system access; risk: corrupted planning data.
- Define ERP and process cutover gates with testing, training and rollback owners. Owner: IT lead; milestone: Day 60; priority: P0 before any cutover; evidence: approved go/no-go criteria; measure: failed critical tests; dependency: reconciled data; risk: forced migration.
- Align maintenance priorities and critical spares with the production plan. Owner: maintenance lead; milestone: Day 50; priority: P1; evidence: risk-ranked maintenance backlog; measure: critical overdue work and unplanned downtime; dependency: asset condition; risk: deferred reliability losses.
- Compare recurring freight, utilities and other indirect-spend agreements without weakening service. Owner: procurement lead; milestone: Day 60; priority: P2; evidence: total-cost comparison; measure: finance-validated benefit net of costs; dependency: service and exit terms; risk: headline-only savings.
- Review cross-workstream dependencies and reauthorize dates when readiness changes. Owner: integration lead; milestone: weekly through Day 60; priority: P1; evidence: updated integrated plan; measure: overdue critical-path decisions; dependency: workstream evidence; risk: parallel plans that conflict.
For a focused review of recurring agreements, see our business cost reduction services. Keep contract savings separate from operational productivity and one-time cash releases.
Days 61 to 100: capture
Validate benefits against the approved baseline, test whether processes hold across shifts and transfer ownership into normal management. Day 100 is a review point rather than proof that every integration is finished.
Document remaining risks, future investment decisions and work that should continue after the integration team steps back.
- Reconcile claimed benefits to contracts, payroll or financial records and timing. Owner: finance lead; milestone: Day 90; priority: P1; evidence: benefit-to-record reconciliation; measure: realized recurring benefit net of implementation costs; dependency: consistent baseline; risk: double counting.
- Separate recurring savings, avoided costs, one-time cash and revenue assumptions. Owner: finance lead; milestone: Day 90; priority: P1; evidence: benefit category and approval for every claim; measure: unsupported benefit claims; dependency: agreed definitions; risk: inflated value reporting.
- Test new standard work across shifts, products and realistic demand conditions. Owner: plant leader; milestone: Day 90; priority: P1; evidence: sustained performance review; measure: schedule attainment, first-pass yield and scrap; dependency: trained teams; risk: a pilot mistaken for sustained performance.
- Verify customer service and quality have not deteriorated during change. Owner: commercial lead with quality; milestone: Day 90; priority: P0; evidence: complaints, returns and delivery review; measure: on-time delivery and customer escapes; dependency: comparable definitions; risk: value lost outside the cost model.
- Review employee feedback, leadership alignment and unresolved skills coverage. Owner: HR lead; milestone: Day 90; priority: P1; evidence: retention and capability review; measure: critical vacancies and single-person dependencies; dependency: shift-level feedback; risk: changes that cannot be maintained.
- Assign every open risk and deferred initiative to a permanent business owner. Owner: integration lead; milestone: Day 100; priority: P1; evidence: accepted residual-risk register; measure: unowned residual risks; dependency: management acceptance; risk: unfinished work disappearing.
- Approve the next operating roadmap with investment, dependencies and review dates. Owner: sponsor; milestone: Day 100; priority: P1; evidence: funded roadmap with decision gates; measure: approved initiatives with accountable owners; dependency: current performance; risk: an unfunded handoff.
- Hold the Day 100 review and transfer the management cadence, records and measures. Owner: sponsor; milestone: Day 100; priority: P1; evidence: signed handoff and next review date; measure: unaccepted handoff actions; dependency: permanent leadership; risk: gains fading after transition.
Measures to keep consistent
Track on-time delivery against the committed ship date, first-pass yield against the agreed good-unit definition, scrap against the same production basis, and throughput for a stated product mix and period. Use OEE only when availability, performance and quality are measured consistently.
Report safety concerns immediately as well as through the agreed management measures.
Keep a benefit register with baseline period, counterfactual assumptions, owner, category, implementation cost, realization date and supporting finance record. A negotiated price is not a realized saving until the benefit reaches actual spend.
A capacity improvement is not automatically revenue or cash.
Five integration mistakes to check for
Use these as review questions, not a diagnosis of your deal. Each mistake represents an avoidable planning gap: an unowned decision, an unsupported assumption or a change made before readiness.
Ask the responsible workstream to show the evidence behind its answer.
- Treating the diligence report as a finished integration plan. Convert each material finding into an owner, dependency and decision date.
- Moving production or systems before controls are ready. Require tested quality, capacity, customer approval and rollback gates.
- Counting the same benefit in several workstreams. Reconcile benefits once through finance and separate one-time effects.
- Losing the people who understand how the plant actually runs. Plan retention, backup coverage and documented standard work early.
- Declaring completion because the calendar reaches Day 100. Confirm stable performance and accepted ownership of remaining work.
Practical questions
Does every manufacturing integration need to finish in 100 days?
No. Use the first 100 days to establish control, validate priorities and demonstrate that the operating cadence works.
ERP migration, equipment transfers and footprint changes may extend beyond that point. Set their timetable from readiness, risk and approvals rather than a fixed calendar.
How do we decide what to integrate first?
Protect safety, quality, payroll, customer commitments and supply continuity first. Then rank changes by the value case, dependencies and the team's ability to absorb them.
A quick procurement saving should not undermine a critical supplier or trigger a production interruption.
Who should own the integration checklist?
Name one integration lead to coordinate it, with an executive sponsor who resolves cross-functional decisions. Each action also needs a named accountable workstream owner.
Plant leaders retain responsibility for daily operations; finance validates benefits and the evidence supporting performance claims.
What does it cost to hire integration support?
Scope depends on site count, systems, operating risks, workstreams and the capability of the internal team. Define the decisions and outcomes that need support before agreeing an engagement.
A discussion of the acquisition and its constraints helps establish the appropriate scope.
For the signs that outside help is needed, read when to hire a post-merger integration consultant. To set up the team that runs this plan, see the integration management office guide.
Use the checklist and Schedule a Call
Use the checklist in your next integration review, assign owners and bring the unresolved dependencies into one plan. If you need help turning diligence findings into action, Schedule a Call or call 717-707-7826, York.
Our Punta Gorda office is available at 813-303-0093.



