Your Polish plant has an ERP launch date. What would justify going live?

A rugged tablet and a blank checklist on a steel table in front of a Polish plant with a lit loading bay, linked by a burgundy route to a group head office flying German, Swiss and French flags.

In brief

ERP go-live readiness depends on recorded evidence from the plant. ERP (enterprise resource planning) connects orders, purchasing, production, stock and finance. Go-live is the day the plant runs on it. A sponsor can approve the launch when every critical activity has a named owner and either proof or a tested fallback with an exit date. A timed rehearsal of the switch to the new system must also have run. Where evidence is missing, the sponsor can postpone, narrow the release or accept a recorded exposure, and each carries a cost.

Differentiating Target ERP Launch Dates from Operational Readiness Evidence

In a hypothetical plant, group leadership fixed the weekend for the switch to the new system (the cutover) months ago. The programme report now shows configuration complete and testing on track. The sponsor faces a practical question: does the approval cover a date, or a plant that can run? A date shows when the plan expects readiness. Evidence shows whether the plant has reached it. A green milestone confirms delivery of a work package. It does not confirm that orders, material and invoices flow through the plant.

Delays bring implementation-partner fees, retained contractors, and a difficult conversation with the group board. A premature launch brings costs the programme report does not show. Orders that cannot ship produce no invoice, so cash waits. A late or unreliable first period-end close from Poland leaves headquarters managing the plant on weaker facts than before launch. Customers who see missed deliveries escalate past the plant to group management. That weakens local authority when the plant needs it most.

Aligning Corporate Headquarters and Local Plant Readiness Assessment Perspectives

A steering group in Munich, Zurich or Paris reasonably reads programme health through milestones, partner reports and a group template. It carries the capital and answers to the owner. The sponsor is weighing group-wide consistency against a launch the plant can absorb. The Polish plant answers to customer delivery windows and shift schedules that do not move for a software date. A line manager who says a warehouse process does not work yet is giving operating information, not resistance.

Three cross-border questions need answers before the dated review. Who at group level approves a local deviation from the template, and by when? Which executive in the Polish entity carries the statutory consequence if invoicing or reporting fails after launch? Do the runbook (the cutover script) and work instructions work for Polish-speaking shift teams?

The plant's process owners complete one launch-decision record (set out below) for the sponsor. Where no internal owner has authority on both sides, an executive between headquarters and the plant can hold it. That readiness owner carries the sponsor's delegated authority into both organisations and reports the same facts in both directions.

Operational Key Performance Indicators and Risk Window Assessment Signals

The risk window opens when the first commitment that makes postponement expensive falls due. Examples include a stock build ahead of cutover, implementation-partner demobilisation, customer notices and a data freeze. Inside that window, an ERP readiness assessment starts with three observations from the plant.

The programme report is green, yet line managers cannot walk one customer order through the new system without help.
Key users plan to keep parallel paper records for the first weeks.
The cutover script covers data migration but not the manual steps for goods receipt and dispatch.

Each observation prompts a request for evidence and says nothing about the plant's people. The missing manual steps need writing before the rehearsal. Parallel records can stay for the first weeks when the record names their owner.

Validating Manufacturing ERP Readiness Through End-to-End Order Testing

To judge ERP go-live readiness, follow one customer order through the new system. Let the plant choose it for its exceptions, such as a partial shipment, an export document or a scrap booking.

The order enters the system.
The system checks and reserves raw material for the order.
The planner schedules machine capacity, and the warehouse issues material to the line.
The line records finished output and material used, including scrap.
The shipping team prepares transport and customs documents and dispatches the goods.
Finance issues a compliant invoice and posts the revenue.

An experienced plant director reads the steps by consequence. A fault in material issue (step 3) or dispatch (step 5) reaches the shift and the customer first. Each needs a fallback that the shift has rehearsed. A fault in stock records surfaces last and costs most to unwind, which is why owners prove them first. A run by the shift that will use the system outweighs a green run by the programme team.

An activity is critical if its failure would stop goods, corrupt stock records, hold an invoice or break statutory reporting. The readiness owner proposes the classification and the sponsor confirms it before the plant gathers evidence. Other activities can run on a named manual workaround for a stated period.

Microsoft's go-live checklist and its guidance on preparing to go live are specific to Dynamics 365. They remain a useful reference for what a programme should test.

Initial Steps for Establishing ERP Cutover Governance

First, the sponsor names the readiness owner, the group approver for template deviations and the date of the review. If the risk window has already opened, the review starts by listing which commitments exist and which the sponsor can still reverse. The sponsor also checks the cutover date against the financial close and planned shutdowns. Second, owners prove their own activities, starting with stock and ledger records, the evidence hardest to reconcile later. Third, a timed cutover rehearsal exercises each fallback.

The sponsor therefore decides twice. At the dated review, the question is whether the evidence so far justifies making the commitments that close options. After the rehearsal, the question is whether to proceed, narrow or postpone.

Executive Decision Pathways: Proceed, Postpone, or Scope-Narrowing Options

At the second decision, each option is conditional on the evidence.

Proceed when every critical activity has an owner and either proof or a tested fallback, and the timed rehearsal has run.
Postpone when a critical activity has neither proof nor a tested fallback, unless the group board accepts the exposure. Postpone too when the plant does not trust its stock records, or a statutory requirement fails specialist review. A postponement names the evidence that releases the next date and which commitments from the risk window it keeps or reopens.
Narrow the release when non-critical modules can wait. The reduced scope must keep a continuous order-to-invoice process with every required approval. A plant might start with stock, production recording and dispatch, and defer advanced scheduling. That trades speed for a second cutover later.

Managing Escalation Protocol, Rollback Criteria, and Post-Launch Operations

An activity with no named owner or no tested fallback goes to the sponsor. The sponsor agrees the last realistic rollback point, who may call it and what triggers the call. Until live transactions post in the new system, returning to the current one is a planning matter. Afterwards it means reconciling two sets of records.

In the first weeks the readiness owner gives the sponsor a short list at an agreed cadence. It covers held shipments, unissued invoices, stock variances and fallbacks past their exit date, each read against limits set in advance.

Governance and Roles in the Final ERP Go-No-Go Decision

In our view, the person who recommends the launch should not be the only one who answers for its date. The readiness owner, normally the ERP programme director, assembles the record with the plant's workstream leads and recommends. Because that role can answer for the launch date, the recommendation lists every open exposure beside the process owners' sign-offs. The implementation partner reports the delivery position and the cost of delay, and does not certify readiness. The executive sponsor (for example the group COO) hears both, with plant leadership. The sponsor makes the ERP go-no-go decision and carries the operating risk. The sponsor should record in advance who may refuse a launch and who may overrule the refusal.

Managing Process Owner Objections and Unresolved Exposures

Each process owner decides whether to sign off their own activity. The readiness owner proposes what counts as evidence, and the sponsor confirms it with the critical classification. If a process owner will not sign, the record shows the missing evidence, who can produce it and by when. Until then the activity does not count as ready.

The sponsor can accept documented exposure in non-critical activities, within the limits the board has delegated. Launching with an untested fallback in a critical activity goes to the group board. So does any postponement that exceeds the sponsor's budget authority or changes a customer commitment.

Role of Internal Leadership Versus Interim Programme Leadership in Cutover

An internal programme leader can carry the readiness role if they can assemble the evidence and resolve dependencies. An interim programme director becomes relevant when no internal owner combines authority with both headquarters and the plant, time to use it and independence from the launch date. An outsider needs time to learn the programme, so an early appointment preserves more options than a late one. A readiness review ends with a report to the sponsor. The interim director is accountable for giving every open exposure an owner and a date.

Under the sponsor's written delegation, the interim director coordinates process owners and central IT and keeps the cutover rehearsal open until each fallback has run. The interim director then brings the sponsor one recommendation with the open exposures attached.

A CE Interim Partner aligns the mandate with the sponsor and governs the assignment. If headquarters or the plant contests the evidence standard, the Partner sets out both positions for the sponsor to decide. The mandate ends with a handover of the record to the permanent owner.

Standardised ERP Launch-Decision Record and Checklist

The record below is an editorial aid, not a recognised certification. The readiness owner proposes critical status, the plant completes the exposure and fallback fields, and the sponsor completes the decision field. Each entry leaves those fields blank.

Customer order intake: Evidence to request: trial of orders the plant chooses for their exceptions. Accountable owner: Customer service and planning lead.
Opening stock and ledger balances: Evidence to request: physical count reconciled to migrated records. Accountable owner: Plant logistics manager.
Goods receipt and storage: Evidence to request: live trial of receipt and batch records. Accountable owner: Plant logistics manager.
Production recording and material use: Evidence to request: trial on an active line with the work instructions the shift will use, including scrap. Accountable owner: Plant operations director.
Dispatch and shipping documents: Evidence to request: documents checked with carriers on real shipments. Accountable owner: Supply chain and logistics lead.
Invoicing and statutory reporting: Evidence to request: invoices and period-end routine, reviewed by a local specialist. Accountable owner: Finance director, Poland.
Cutover rehearsal: Evidence to request: timed rehearsal with a fallback route. Accountable owner: ERP programme director.

Post-Decision Execution and Documentation Handover

Record the approved scope, the exposure accepted and by whom, the owner of each open item and the next review date. Respect each specialist sign-off and the actual contract arrangements. The record replaces neither.

Frequently Asked Questions About ERP Go-Live Readiness Assessment

Does a Planned Launch Date Confirm Operational Go-Live Readiness?

Not on its own. The date reflects planning assumptions and contract milestones. Readiness needs evidence that the plant can receive material, run production, ship goods and issue compliant invoices. Until that evidence exists, the date remains a target.

Are All Open Software Defects Considered Launch Blockers?

Not by itself. Severity matters more than count. A cosmetic fault can wait for post-launch support. A fault that stops goods, corrupts stock or breaks statutory reporting needs a fix or a tested fallback before release.

Who Recommends and Authorises the ERP Go-Live Release?

The readiness owner recommends on the recorded evidence. The executive sponsor authorises the release after hearing plant leadership. Decisions beyond the sponsor's delegated limits go to the group board.

Can a Scope-Narrowed ERP Rollout Be Executed Safely?

It can, when the reduced scope still supports a continuous order-to-invoice process. It also needs the required approvals, an owner for each workaround and a plan for the second cutover.

When no one owns the evidence of ERP go-live readiness, a sponsor can approve a launch on an incomplete picture. Where the sponsor cannot name that owner, an Interim Transformation and Programme Director can carry the launch-decision record until handover.

Related reading:

A launch the evidence does not support can leave held shipments, unissued invoices and an unreliable period-end close. CE Interim provides cross-border executive leadership: an already vetted, mandate-matched, NDA-bound executive, ready to start after the completed mandate brief.

To discuss an interim programme mandate and its handover, speak with a CE Interim Partner.