Loss of control is a reporting symptom first
By the time a project is formally late, the underlying problem is usually old. What changed first was not the schedule but the quality of information reaching management: status became narrative, dates became approximate, and the answer to "where are we?" started depending on who was asked.
The following signs are worth treating as early indicators. Individually, each is survivable. Together, they describe a project that management no longer controls.
1. Status has to be assembled on request
If a status update requires several days of internal collection, there is no reporting cycle — there is a periodic reconstruction. Reliable projects issue the same concise status on a fixed date whether or not anyone asked for it.
2. Percentages replace evidence
"Ninety per cent complete" is not a measurement unless the remaining ten per cent is defined. Where progress is reported as a percentage without acceptance criteria, the reported figure tends to stall near completion for a long time.
3. Actions live in email
When commitments are tracked in correspondence rather than a register with owners and dates, follow-through depends on individual memory. Items do not get resolved; they get forgotten, which is harder to detect.
4. Risks are discussed but never closed
A risk register that only grows is a list, not a control. Functioning governance shows risks being mitigated, accepted or closed, with the decision and its owner recorded.
5. Decisions are revisited
Repeatedly reopening settled questions is a sign that decision rights are unclear. If it is not documented who decides what, every decision remains provisionally open, and the plan cannot stabilize.
6. Suppliers report to no one in particular
Where several suppliers or internal teams each report separately to different people, no one holds the dependencies between them. Delays then appear at integration points, late, and with no obvious owner.
7. The plan is no longer used
The clearest sign. When the plan has not been updated for weeks and meetings run from a slide deck instead, the project is being managed by discussion. Discussion does not surface dependencies until they bite.
What structured recovery involves
Recovery does not begin with a new plan. It begins with an honest assessment of the current position: what is genuinely complete and evidenced, what is contractually committed, which dependencies are real and which decisions are outstanding.
Only then is a baseline re-established — usually smaller and more sequenced than the original — with owners, dates and acceptance criteria. The registers are rebuilt, the escalation path is defined, and reporting starts immediately, even before the plan is finished. Management needs the cadence more urgently than it needs the detail.
- Assess the true current position, with evidence
- Re-establish a credible, sequenced baseline
- Rebuild action, risk, issue and decision registers
- Define decision rights and escalation
- Start a fixed reporting cycle immediately
The cost of waiting
Recovery is inexpensive early and expensive late. Intervening when reporting has degraded but commitments are intact usually costs weeks. Intervening after contractual milestones have been missed costs a renegotiation. The signs above are worth acting on precisely because none of them yet look like a crisis.
This article provides general project-delivery commentary and does not constitute legal, tax, financial or other regulated professional advice.