Discuss a project
A large construction site with tower cranes, seen from above

Service 01

Project status and performance review

A clear position before the next decision.

On large projects the reported position and the position on site drift apart. Schedule logic stops reflecting the work, progress is reported differently by each contractor, and forecasts are rolled forward instead of re-built. Decisions are then taken on figures nobody fully trusts.

The review establishes where the project stands against its approved baseline, which issues drive the dates and the cost, and what to do next. It is carried out with the project team and ends in a report the team can act on.

One evidenced position

Schedule, progress and cost tested against the records and the site, with facts and assumptions kept apart.

Issues ranked by impact

The delays, inconsistencies and control gaps that matter most for milestones and cost, in order.

Actions the team can take

Recommendations with owners, sequenced so the most important ones start first.

What the review covers

The schedule, the progress, the cost and the information behind them are tested against each other and against the site.

Schedule logic and critical path

Open ends, constraints and lags that hide the real critical path, and whether the remaining logic still reflects how the work will be built.

Progress against what is built

Reported progress compared with installed work and inspection records, package by package.

Cost and forecasts

Costs and forecasts to completion checked against the baseline, approved changes and verified progress.

Information flows

How information moves between teams and systems, and where integration would improve coordination and reporting.

Deliverable: a report at a stated data date with the findings, their impact on milestones and cost, the limitations of the evidence and the recommended actions, presented to the project team.

Sample report

Status review, main works

Illustrative example
Project status and performance reviewSR-0001 · Rev A

1. Summary

The project is behind its approved baseline. Verified progress is lower than reported progress, and handover is forecast four weeks late. Recovery has not yet been demonstrated. The next step is to validate the remaining logic and progress, then test recovery options against resources, access, cost and commissioning constraints.

Planned60%
Reported59%
Verified on site55%
Handover4 wk late
AreaPositionStatus
ScheduleCritical path hidden by open ends and constraints; handover forecast 4 weeks late.Action needed
ProgressReported 59% against 55% verified on site; two packages overstated.Action needed
CostForecast €48.4m against a €46.0m budget; MEP €1.4m over.Action needed
InformationSite progress reaches the schedule by manual update, about two weeks late.Monitor

Action needed: affects a key milestone or the forecast at completion. Monitor: affects reporting quality, not yet dates or cost. Planned progress comes from the baseline, reported progress from the contractors, verified progress from installed and inspected work.

Main works · data date week 32, month 8Page 1 of 4
Page 1 of 4
Illustrative data, not from a client project. The full report is presented to the project team.

What the review looks at first, by sector

The method is the same on every project. What the review looks at first depends on what drives the dates in each sector.

Nuclear energy

Hold points, inspection status and document readiness checked against the activities that depend on them.

Semiconductors

Base build, hook-up and tool move-in compared area by area, where one late area holds several work fronts.

Data centres

Long-lead equipment, energisation and commissioning dates tested against installation progress, hall by hall.

Civil and infrastructure

Measured quantities, interim payments and the schedule compared, so progress claimed and progress built agree.

How a review runs

  1. 01

    Records and access

    Schedule, baseline, progress, cost reports and forecasts are collected once confidentiality and access are agreed.

  2. 02

    Analysis

    Logic, critical path, progress, cost and information flows are tested against each other and against the site.

  3. 03

    Findings discussed

    Draft findings are reviewed with the project team before anything is issued, so the facts are confirmed.

  4. 04

    Report and presentation

    Findings, their impact on milestones and cost, and the recommended actions are set out and presented.

Questions about the review

How is the review carried out?

With the project team, not separately from it. Enncon reads the records with the planning, cost and site teams and walks the work. Draft findings are checked with the team for factual accuracy. The report distinguishes verified facts, assumptions, limitations and unresolved differences, and sets out the actions Enncon recommends.

What information is needed?

The current schedule and the approved baseline, normally as Primavera P6 files, progress records, cost reports and forecasts, and contractor schedules where they exist. Access to the site or to inspection records allows reported progress to be compared with what has been built. Confidentiality terms, access permissions and a secure transfer method are agreed before any data is shared. The review works from the client’s existing systems and files; no separate integration is needed.

How long does a review take?

Scope and duration are agreed in the proposal before the work starts. They depend mainly on the size of the schedule, the number of contractors and packages, and the quality of the records available.

What happens after the review?

The report stands on its own and belongs to the client. Where it shows that information needs to be connected or that controls need support during execution, the other services can follow, but each is ordered separately.

Discuss your project

Tell us what you are building and where you need support.

Get in touch