Progress Says 70%. Is the Remaining 30% the Hardest Part?
Percentage complete can create false confidence when the remaining scope contains more interfaces, testing, commissioning, approvals and specialist dependencies.
The short answer
Seventy percent complete does not necessarily mean seventy percent of the risk is behind the project.
The remaining work may contain more interfaces, specialist testing, access restrictions, client decisions, commissioning and closeout than the work already finished.
Percentage complete measures progress. It does not automatically measure difficulty.
Early progress can be physically easier than late progress
Many projects begin with large, repetitive activities.
Excavation. Structure. Major installation. Large workfronts.
These activities can generate visible progress quickly.
Later phases become more fragmented.
Rooms replace floors. Interfaces replace repetition. Finishes require protection. Systems need testing.
The work becomes less forgiving.
A project can therefore move quickly through the first 60 or 70 percent and then slow sharply.
The percentage has not lied. The assumption that the remaining percentage carries equal effort has.
Weighted progress can still hide execution difficulty
Projects often improve simple percentage reporting with weighted activities.
That is useful.
But weighting typically reflects budget, duration or quantity.
It may not reflect coordination difficulty.
A commissioning activity may have a modest weight while controlling handover.
A client approval may carry little weight while blocking a whole area.
A handful of defects may represent almost no progress percentage while consuming weeks of closeout attention.
This is why the programme-confidence view should look beyond earned progress and ask what risk is concentrated in the remaining scope.
The remaining work should be examined for interfaces
Interfaces create uncertainty.
Two trades must coordinate.
One system depends on another.
A client decision affects a specialist package.
An authority witness is required.
The more interfaces concentrated in the remaining work, the less useful a simple progress percentage becomes as a predictor of finish.
Management should ask whether the last part of the job contains more dependency than the first.
If it does, remaining durations may need more confidence review.
The project is not merely completing quantity.
It is completing integration.
Closeout work is often underrepresented in progress systems
Inspection.
Defect closure.
Testing.
As-builts.
O&M information.
Training.
Handover.
These activities can consume significant effort while contributing relatively little to visible installed progress.
A programme that focuses mainly on physical installation may therefore look almost complete while closeout risk remains high.
Physical completion and accepted completion can be very different states, especially once inspection, commissioning and closeout begin.
The finish forecast should recognise the second, not only the first.
Remaining duration should reflect what has been learned
As the project progresses, management has better evidence than it had at baseline.
Actual productivity is known.
Approval cycles are known.
Supplier reliability is known.
Commissioning readiness is becoming clearer.
Remaining durations should use that learning.
If the project continues carrying optimistic baseline durations despite repeated evidence of slower performance, the programme is not forecasting.
It is preserving an old assumption.
A credible schedule updates the future with what the project has learned from the past.
The last 10 percent often contains the least substitutable resources
Early in a project, one crew can sometimes be replaced by another.
Late in the job, specialist dependency increases.
Vendor engineers.
Commissioning specialists.
Authority inspectors.
Client witnesses.
System integrators.
These resources may be limited and harder to accelerate.
That makes the final part of the programme less flexible.
Management should understand where the remaining work depends on people or organisations that cannot simply be multiplied with more budget.
This is one reason late recovery plans can be much harder than early ones.
A healthy progress report should make remaining risk visible
The objective is not to make percentage-complete reporting more complicated than necessary.
The project still needs a simple view.
The improvement is to add a short narrative around the remaining work.
Which high-risk interfaces remain?
Which specialist dependencies remain?
Where is float thin?
Which approvals remain unresolved?
Which commissioning or handover conditions could move the finish?
This gives management a more realistic interpretation of the progress percentage.
Seventy percent complete can then mean exactly what it should: the project has earned seventy percent of defined progress, while the remaining thirty percent carries a particular risk profile.
The same logic applies to resource forecasts.
If the remaining work is more fragmented, specialist or interface-heavy, the project may need more supervision per unit of physical progress.
The final phase can therefore consume management effort faster than installed quantity suggests.
This is another reason progress percentage should not be used as a direct proxy for remaining cost or remaining complexity.
The project should forecast the remaining work as it actually exists, not as a scaled-down version of what has already been completed.
There is also a psychological effect to high percentage-complete numbers.
Once a project reaches 80 or 90 percent, stakeholders naturally expect the finish to be close.
That expectation can increase pressure on the project team to compress the remaining work.
The remaining work may be exactly the part least suitable for compression.
Commissioning sequences may depend on specialist availability.
Client witness dates may be fixed.
Defect closure may require access through finished areas.
Authority approvals may follow their own timing.
Management should therefore be careful not to turn a high completion percentage into an automatic acceleration demand.
The better question is what kind of work remains.
A project with ten percent of repetitive installation left is very different from one with ten percent of integration and handover work left.
The same percentage can carry very different uncertainty.
This is also why the remaining-cost forecast should not be calculated by simple proportion.
If supervision, specialist testing, temporary systems and closeout teams stay on the project until the very end, the last percentage points may carry high time-related cost.
A small amount of physical work can therefore support a large amount of remaining expenditure.
The programme and cost forecast should reflect the shape of the remaining work, not only its volume.
That becomes especially important for senior management because late optimism can damage both completion credibility and margin.
A realistic view of the remaining 30 percent may feel less comfortable than a simple progress chart.
It is far more useful.
The remaining-work view should also influence management cadence.
A project entering commissioning and closeout may need fewer broad production meetings and more focused interface, testing and handover reviews.
The percentage complete is rising, but the type of coordination is changing.
If the management structure does not change with the work, the project can keep using a production rhythm designed for installation while the real risks have moved into integration and acceptance.
That is another reason the final phase can feel unexpectedly difficult.
The work changed, but the management model did not.
The strongest progress review therefore combines percentage complete with a statement about the shape of the remaining work.
Is the remainder repetitive or highly interfaced?
Is specialist availability secure?
Are testing and authority dates confirmed?
Is closeout evidence keeping pace?
Those questions do not replace the headline percentage.
They make the percentage useful.
Management can then see not only how far the project has travelled, but how difficult the final distance is likely to be.
That perspective is especially valuable near handover, when visible construction slows but management effort, specialist dependency and commercial sensitivity often increase.
That is a more realistic basis for forecasting the final phase.
It also keeps the final completion forecast grounded in the actual shape of the work.
Where Epicor Saturn fits in progress confidence
Epicor provides the enterprise-grade ERP foundation for finance, approvals, purchasing and governance. Epicor Saturn adds the construction and engineering project context that connects progress with workfronts, programme, resources, cost and completion states.
That connection helps management interpret percentage complete through the real execution conditions behind the number.
For progress confidence, Epicor Saturn connects reported progress with remaining work, project resources and completion conditions while Epicor provides the enterprise-grade ERP foundation. Explore Epicor Saturn for construction and engineering.
Frequently asked questions
Is percentage complete a bad metric?
No. It is useful, but it should not be mistaken for a direct measure of remaining risk or difficulty.
Why can late-stage work take longer per percentage point?
Because interfaces, specialist dependencies, testing and closeout often increase near completion.
Should remaining durations be updated from actual performance?
Yes. Live evidence should inform the forecast where conditions are comparable.
Why can the final 10 percent be hard to accelerate?
Because it often depends on specialist, client or authority resources that are not easily multiplied.