A project that’s behind schedule gets one of two responses, almost reflexively: replan it, or recover it. They are not the same move, and picking the wrong one is how a recoverable project gets replanned into a second failure, or a genuinely broken one gets a new schedule that repeats the old problem on a new calendar.
Replanning treats the plan as the problem
Replanning assumes the original approach was sound and the schedule was wrong — new dates, adjusted milestones, maybe more resources, same underlying plan. That’s the right call when the slippage traces to an estimation error or a scope addition that was never re-baselined. It’s the wrong call when the slippage is a symptom of something the schedule can’t fix.
Recovery starts with a diagnosis, not a new schedule
Project recovery starts from a different premise: something in how the work is being run is producing the delay, and a new schedule built on the same root cause will slip again. That means the first deliverable isn’t a revised plan — it’s a diagnosis of why the project is actually behind, distinct from the story being told about why it’s behind, which are frequently two different things.
The tell: ask what changed since the last approved baseline
One question separates the two cases reliably: what has actually changed since the plan was last credible. If the answer is scope, staffing, or dependencies outside the team’s control, a replan with an honest new baseline is legitimate. If the answer is “nothing changed, we’re just not hitting the dates we set,” the plan was never the constraint — and a new one won’t be either.
What a real diagnosis actually checks
A genuine recovery diagnosis looks at decision latency (how long does an open question sit before someone with authority answers it), where accountability actually sits versus where the org chart says it sits, whether status reporting reflects real state or a rolled-up optimistic average, and whether the team doing the work believes the current plan is achievable — a schedule the team has quietly stopped believing in is a leading indicator no burn-down chart shows.
Executive reporting is part of the diagnosis, not just the output
A recurring pattern in stalled projects: the executive reporting itself is optimistic by construction, because each layer rolls up a slightly rosier number than the layer below it reported. Six real questions belong in front of any executive on a project like this — what’s actually done, what’s genuinely at risk, what decision is being avoided, what would change the timeline, who owns the next milestone, and what happens if nothing changes — and a status deck that can’t answer them plainly is itself a recovery finding.
What recovery produces that a replan doesn’t
The output of a real recovery engagement is a plan too, eventually — but it’s a plan built on top of a named root cause, with the specific mechanism that caused the original slippage either removed or explicitly controlled for. A replan without that diagnosis is a bet that the same conditions won’t produce the same result twice. Sometimes that bet is fine. Often it isn’t, and the second slip is more expensive than the first because it’s cost credibility on top of schedule.
The practical takeaway
Before committing to a new date, answer the diagnostic question first: has anything actually changed, or is the plan just being asked to try again. TekFidelity’s Program & Project Leadership work treats project recovery as a distinct engagement from routine replanning, starting from that diagnosis rather than a revised Gantt chart.