Project status and performance reviewSR-0001 · Rev A1. 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
| Area | Position | Status |
|---|
| Schedule | Critical path hidden by open ends and constraints; handover forecast 4 weeks late. | Action needed |
|---|
| Progress | Reported 59% against 55% verified on site; two packages overstated. | Action needed |
|---|
| Cost | Forecast €48.4m against a €46.0m budget; MEP €1.4m over. | Action needed |
|---|
| Information | Site 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.
Project status and performance reviewSR-0001 · Rev A2. Milestones
Baseline and forecast dates for the key milestones, with the variance in weeks.
| Milestone | Baseline | Forecast | Variance |
|---|
| Structure complete | M7 | M8 | 4 wk |
|---|
| Building weathertight | M10 | M11 | 4 wk |
|---|
| MEP installation complete | M10 | M12 | 6 wk |
|---|
| Energisation | M12 | M13 | 4 wk |
|---|
| Handover | M13 | M14 | 4 wk |
|---|
MEP installation is six weeks late. Hook-up and testing overlap it, which holds energisation and handover to four weeks.
Project status and performance reviewSR-0001 · Rev A3. Findings
Each finding is traced to the records it comes from and was checked with the project team for factual accuracy. Unresolved differences are recorded.
| Ref | Area | Finding | Status |
|---|
| F1 | Schedule logic | Open ends and hard constraints hide the real critical path through the mechanical packages. | Action needed |
|---|
| F2 | Progress | Reported progress on two contractor packages is ahead of installed and inspected work. | Action needed |
|---|
| F3 | Cost | MEP is forecast €1.4m over budget, and approved variations reach the forecast by hand. | Action needed |
|---|
| F4 | Information | Site progress reaches the schedule through a manual update, about two weeks late. | Monitor |
|---|
Project status and performance reviewSR-0001 · Rev A4. Recommended actions
Actions in order of priority, each linked to the finding it addresses.
| Ref | Action | Finding | Owner | Due |
|---|
| A1 | Repair the logic of the remaining works and re-run the critical path | F1 | Planning lead | Week 1 |
|---|
| A2 | Measure progress against installed and inspected quantities | F2 | Package managers | Week 2 |
|---|
| A3 | Link the variation register to the cost forecast | F3 | Cost manager | Week 3 |
|---|
| A4 | Collect site progress weekly, at the source | F4 | Site engineers | Week 4 |
|---|