Skip to content
Discuss your project
Menu

Project controls

The Weekly Project Controls Report: Five Views That Support Decisions

Build a concise weekly report around milestone movement, readiness, production, resources and decisions, with a clear audit trail back to the programme.

Illustrative project controls office with abstract programme and progress charts.
AI-generated illustrative image; not a photograph of a Liongate project.

A weekly report can be accurate and still be difficult to act on. Pages of activity percentages, coloured indicators and charts do not necessarily tell a project director which decision is needed before Friday.

A useful data centre controls report connects the current forecast to the site position, then identifies the actions that could change the outcome. Five views can provide that structure without requiring every reader to navigate the full programme.

1. Milestone movement and its cause

Show the baseline date, previous forecast and current forecast for a small set of meaningful delivery milestones. Include the status date and the programme revision. A movement column makes deterioration or improvement visible; a short explanation makes it interpretable.

Distinguish verified progress from changes to assumptions, scope or calculation settings. “Forecast moved by four days” is incomplete without the reason. If the date is unchanged because available float absorbed a problem, make the reduced resilience visible rather than describing the milestone as unaffected.

2. Readiness for the next important workfronts

Report the unresolved conditions that could prevent upcoming work: information, access, materials, resources and required approvals. Link the exception to its activity or milestone and name an owner. Focus on conditions that need action during the reporting horizon.

A readiness percentage can supplement this view, but the remaining critical blocker matters more than an average. A workfront with nine of ten conditions closed may still be unable to start because the tenth condition is essential.

3. Planned output, achieved output and remaining work

Use physical quantities or agreed completion steps where appropriate. Explain the basis of measurement and keep the reporting periods consistent. Show whether the observed output supports the remaining duration, rather than presenting the cumulative percentage alone.

Illustrative example: the next four weeks require 200 units per week, while recent verified production averages 150 under comparable conditions. The report should identify what will change to support the higher forecast. Without a different workfront, method or resource position, the increase remains an assumption.

4. Resource demand against available capacity

Show upcoming labour or specialist peaks against confirmed availability. Separate general installation demand from scarce testing, witnessing or manufacturer resources where relevant. Check that the available workfronts can use the proposed deployment.

A resource shortage and an access shortage can produce the same low output, but require different responses. The report should help management distinguish them before asking for more labour.

5. Decisions needed, with dates and consequences

DecisionOwnerNeeded byProgramme consequence
Confirm the approved equipment release basis.Named design/procurement lead.Date linked to manufacture.Release remains conditional until resolved.
Agree an alternative workfront.Named delivery lead.Date linked to crew deployment.Planned output cannot be supported without available work.
Confirm specialist attendance.Named commissioning lead.Date linked to the booking window.Testing forecast remains subject to availability.

Replace generic requests such as “expedite design” with a defined decision and consequence. Keep the list short enough to discuss, while retaining the detailed registers behind it.

Keep the reporting process controlled

Use a common data cut-off and identify the source of each measure. Assign responsibility for collection and validation. Where two systems disagree, disclose and reconcile the difference rather than silently selecting the more favourable number.

Agree what colours mean. A green status should not mean simply that no one has raised a concern; it should follow defined criteria. Include uncertainty where it affects the interpretation, particularly for externally controlled dates.

The report should leave the meeting with decisions recorded, owners clear and the forecast understood. More charts can be added when they support those outcomes; they should not obscure them.

Continue reading

Put the next decision on a sound footing.

Our programme consultancy supports tender, construction and commissioning planning. For an existing programme, explore a schedule health check.

Explore all insights ↗

Bring clarity to your next project.

Tell us the project name, stage and support you need. We’ll discuss the right scope and next step.

Discuss your project ↗