How to verify a project's real completion date

"When will the asset be finished" sounds like a simple question, but on troubled projects it has no answer. A schedule exists and it carries a date. The problem is that the date is usually not the result of a calculation — it is the input the schedule was fitted around.

Below are five checks an investor or executive can run without a planner's qualifications. They will not replace a full analysis, but they will show whether the stated date deserves confidence.

Check 1. Ask to see the critical path

The critical path is the chain of activities that determines the completion date. A delay to any activity on it moves the end of the project by the same amount; a delay elsewhere moves nothing until it consumes that activity's float.

The request is: "show me the critical path activities and explain why the completion date is what it is." If the answer is a list of milestones with no logic between them, a Gantt chart without relationships, or "that is what was agreed" — the critical path was never calculated and the date has no computational basis.

Check 2. Test schedule quality on three formal criteria

• Logic: every activity should have predecessors and successors. Dangling activities make critical path calculation impossible.
• Absence of hard date constraints: if half the activities carry fixed start or finish dates, the schedule is drawn rather than calculated.
• Realistic durations and resources: 400 m³ of concrete a day on one front with one crane is arithmetically unachievable, whatever the schedule says.

These three take about an hour to test and usually answer the question outright.

Check 3. Compare physical progress with budget expenditure

If 70% of budget is spent against 45% physical completion, the project does not have a schedule problem — it has a cost problem, and it has already happened. Divergence between the expenditure and physical progress curves is the fastest indicator that the completion forecast is understated.

The question that matters here is how physical progress is measured. If percentages are declared by eye by the performers, the figure is worthless. Reliable progress is calculated against rules of credit, where each work unit carries a weight and a completion criterion.

Check 4. Test the long-lead deliveries

On industrial and energy projects the start-up date is more often set by principal equipment delivery than by construction. Manufacturing and shipping cycles run from 6 to 18 months.

The check is straightforward: take the principal equipment list and compare actual order dates with the installation readiness dates in the schedule. If an item with a 12-month cycle was ordered five months before it is needed, no amount of construction acceleration will recover the start-up date.

Check 5. Look at the history of forecasts

Write down the completion dates stated over the last 6–12 months. If the date moves out by roughly a month every month, the project is in what project controls practice calls a running horizon: the slippage is not being recovered, it is being carried forward.

A project whose completion date moves a month every month is not behind schedule — it is unmanaged. In that situation the stated date is always optimistic.

What to do when the checks fail

If a schedule cannot pass these tests, repairing it iteratively is futile — it needs recalculation from actual status. Practically that means three steps: inventory of quantities actually executed, reconstruction of logic and a new baseline, then forecasting from it.

This work is done either inside a project audit — three to five weeks — or as part of establishing a project controls function where the project continues and needs ongoing control.