The go-live has been postponed. What now?

When a go-live date slips more than once, that is not a scheduling problem but a steering problem. The first right step is not a new plan but an honest assessment: where does the project actually stand, in scope, data, processes and ownership. That diagnosis takes days, not weeks. The date is only the point where causes become visible that arose weeks or months earlier: a scope that was never documented and agreed, data that was never cleaned up, open process questions, or nobody allowed to decide bindingly. Here is how to tell whether the date really was the problem: if the plan stays unchanged after the postponement and only the dates move back, the cause was never touched. A second postponement is then likely, and it costs more than the first, because trust inside the company drops with every round.

Why is the date only the symptom?

A postponed go-live is a symptom whose cause arose weeks or months earlier. In most cases the scope was not documented and agreed, the data was not cleansed, processes were open, or there was no one authorised to decide. The date is the first place where all of this becomes visible at once.

Here is how to tell whether the date is really the issue: if the plan stays unchanged after the postponement and only the dates move back, the cause was not addressed. A second postponement is then likely, and it costs more than the first, because trust inside the company drops with every round.

That is why the first right step is not a new plan but a sober assessment. It answers where the project actually stands in scope, data, processes and accountability. This diagnosis takes days, not weeks.

What does an honest assessment examine?

An honest assessment checks six things against the original requirements: scope and open items, the date and budget forecast based on actuals rather than assumptions, data quality per object, test coverage of the core processes with real data, the rehearsed cutover, and whether the committees have the information they need to decide.

Microsoft documents the technical prerequisites for going live in its own documentation. The technical part is rarely the bottleneck. What tips over is data quality and business sign-off, and both can only be tested with real data, not with test records.

Source: Microsoft Learn: Deployment of Dynamics 365 Business Central

Only after this assessment can a solid decision be made, and there are exactly three options: continue with corrected control, rebuild parts, or secure the foundation before any new date is set at all.

Why does senior experience decide at this point?

Senior experience decides here because the hard questions are not capacity questions. Someone must be able to say that a date cannot be held before it breaks. Someone must distinguish symptom from cause while everyone involved is under pressure. And someone must be able to stand behind a no-go decision when the alternative is a forced go-live with unclean data.

The practical difference shows at one point: a senior asks for the remaining effort on an actuals basis and for the decision latency of recent weeks. Both figures say more about the next date than any project plan, and both can be read from the existing minutes without extra effort.

Control stays on your side throughout this process. We bring the view from outside and the experience of how such situations develop. The decision on date and scope is made by your organisation, with solid figures instead of hope.