Minimal one-page project controls report graphic with cost, forecast, programme, risk, change, cash and decision panels

Most monthly reports are written to evidence that work was done, not to help anyone decide anything.

That is why directors receive a thick pack, skim the first page and then ask someone in the room what is actually happening.

A director who has to hunt for the position will stop reading the pack.

This post is about building reporting that gets used.

The principle is simple:

One page. One position. One set of decisions.

If your report cannot state the current position, the forecast and the decisions required, adding more pages will not fix it. You need better controls, clearer ownership and a reporting rhythm that produces information people can act on.

This is the final post in our project controls series. We have covered cost, schedule, risk, change, earned value and reporting. The common thread is control: getting to the truth early, then using it to make a better decision.

What directors need from a monthly report

A director normally needs three things:

  1. How is the job going?
  2. What will it finish at?
  3. What do I need to decide or authorise?

That means the report must show more than cost to date or progress achieved. It must connect the current position to the likely result.

The report should tell you:

  • whether the project remains commercially sound;
  • whether the forecast is moving;
  • whether the programme is still achievable;
  • where risk is being consumed;
  • what change remains unresolved;
  • whether cash is arriving when expected;
  • which decisions cannot wait until the next cycle.

Truth rather than presentation. A usable plan rather than a descriptive report.

The one-page report template

The following structure gives directors the position without forcing them through a forty-page pack.

The supporting detail can sit behind it. The first page should stand on its own.

Abstract one-page directors' report template showing seven controlled information panels

Section What it shows The decision it should prompt
Position summary Contract value, value certified to date, cost to date, forecast final cost, forecast margin and movement since the last period Is the commercial position acceptable, and what has changed?
Forecast and trend Current forecast outturn and the direction of travel over recent periods Is the forecast stabilising, improving or deteriorating?
Programme position Forecast completion, critical path status, float position and key dates at risk Do we need to change sequence, resources or priorities?
Risk and contingency Current exposure, contingency held and drawn, plus the largest live risks and their owners Which risks need intervention, funding or escalation?
Change position Approved and pending change, value awaiting agreement and approaching contractual deadlines Do we need to notify, price, agree or escalate anything now?
Cash position Value applied for, expected receipts against payment dates and overdue amounts What action is needed to protect cash flow?
Decisions required The specific decision, the person responsible and the date required Who must act, and by when?

1. Position summary

Start with the numbers that establish the baseline.

Show the contract value, value certified to date, cost to date, forecast final cost and forecast margin. Then show the movement since the last period.

The movement matters. A position that looks acceptable today may still be deteriorating.

Do not hide movement inside a narrative paragraph. Show what changed, why it changed and whether the change is temporary or likely to continue.

2. Forecast and trend

A single forecast number is not enough.

Show the current forecast outturn alongside the direction of travel over the last few reporting periods. The trend often tells directors more than the latest figure.

A forecast that moves gradually in the wrong direction needs action before the margin disappears. A forecast that improves because a cost has simply been pushed into a later period is not an improvement.

This is where cost control that sees movement early supports the report. The one-page summary should draw from the live cost baseline, commitments and cost-to-complete assessment. It should not be rebuilt from memory at month-end.

3. Programme position

Show the forecast completion date, critical path status, available float and any key date at risk.

A programme can appear broadly on track while float is being consumed. Once the float has gone, a small delay can affect completion.

Your report does not need to reproduce the full programme. It needs to tell directors whether the current plan remains credible and where intervention may be needed.

Our guide to schedule control for contractors explains why critical path, float and contemporary records matter. The board report should bring the consequence forward: what date is threatened, what is causing it and who owns the recovery action?

4. Risk and contingency

Show current exposure, contingency held, contingency drawn and the largest live risks.

Every significant risk needs an owner. It also needs an action and a review date.

A risk register that nobody reviews is not control. It is storage.

Keep the one-page view selective. Directors do not need every low-level risk. They need the risks that could change cost, time, cash or contractual position, together with the action required.

Read more about risk and contingency control.

5. Change position

Show approved change, pending change and value awaiting agreement.

Also identify anything approaching a contractual deadline. That may include a notice, quotation, assessment or response date.

Change that remains unrecorded or unvalued will eventually appear somewhere else: in the forecast, the cash position, the margin or the dispute file.

The report should make the pipeline visible early. Change and configuration control keeps the record aligned across packages, instructions and interfaces.

6. Cash position

Show value applied for, expected receipts against payment dates and overdue amounts.

Cash is not a finance-only issue. A contractor can report a healthy margin and still face pressure because applications are late, notices are weak or receipts do not arrive when expected.

Use the UK construction payment process guide to check the payment timetable, notices and supporting records.

The report should answer a direct question: what cash is expected, when is it expected and what is already late?

7. Decisions required

This is the section that turns reporting into control.

List the decision. Name the person who must make it. State the date by which it is needed.

For example:

  • approve a procurement route;
  • authorise additional resource;
  • agree a recovery approach;
  • approve a commercial settlement position;
  • instruct a notice or formal escalation;
  • release contingency for an agreed action.

Do not ask for a decision without a date. That creates a queue, not control.

Lagging information is not enough

Lagging information confirms what has already happened.

Examples include:

  • cost to date;
  • value certified;
  • work completed;
  • payment received;
  • milestones achieved.

Leading information tells you what is coming.

Examples include:

  • forecast movement;
  • commitments ahead of spend;
  • float being consumed;
  • risks not yet closed;
  • changes not yet valued;
  • upcoming payment or contractual deadlines.

Minimal graphic contrasting historical project data with forward forecast, float and risk indicators

You need both.

A report made only of lagging indicators is a history lesson. It may be accurate, but it will not help directors protect the result.

The purpose of leading information is not to predict perfectly. It is to create time for a decision while choices still exist.

The reporting rhythm matters

Recommend a monthly reporting cycle with a short weekly exception check.

The monthly report should have:

  • a fixed reporting date;
  • a named author;
  • a defined review process;
  • an agreed issue date;
  • a short commercial review meeting.

The fixed date matters because it makes periods comparable. If the report is produced whenever the information happens to be available, movement becomes harder to identify and accountability becomes weaker.

The weekly exception check should not recreate the monthly pack. It should flag only material movement in cost, programme, risk, change or cash.

Use the commercial review meeting to decide

The commercial review meeting should walk the one-page report from top to bottom.

It should confirm:

  • the current position;
  • the movement since the last period;
  • the reason for any adverse change;
  • the actions already taken;
  • the decisions required.

Record the decision, owner and due date before closing the meeting.

Do not hold a meeting that reviews the report without deciding anything. That is another form of reporting theatre.

Minimal dark project controls graphic showing one report connected to cost, programme, risk and cash decisions

Right-sized controls for smaller contractors

A contractor with turnover under a few million does not need a forty-page pack or a dedicated analyst.

It needs one controlled page, produced to a rhythm, that directors act on.

The system should be proportionate to the job. Do not build processes for projects many times larger than your own. Use standardised templates, clear ownership and one place where the current information lives.

The report is the output of control, not a parallel exercise.

If the team assembles the report from scratch every month, the controls are not working. The cost baseline, programme, risk register, change log and cash records should already exist. Reporting should bring them together.

When the news is bad

State it early.

State it plainly.

State the options.

A report that only ever shows improvement at month-end is not credible. A director who hears bad news late has already lost choices.

The correct response is not to disguise the position with more narrative. Explain:

  • what has changed;
  • what caused it;
  • what happens if nothing changes;
  • what options remain;
  • what decision is needed now.

Early rather than late. Truth rather than presentation.

Common reporting failures

Watch for these signs:

  • the report proves work was done but does not support a decision;
  • multiple versions circulate;
  • numbers cannot be reconciled to the accounts or programme;
  • the forecast only moves at year-end;
  • actions have no owners;
  • decisions are requested without a date;
  • a thirty-page pack has no useful summary;
  • the team reports to the client but not to its own board.

These are not formatting problems. They are control problems.

Frequently asked questions

What should a monthly report to directors include?

It should include the current commercial position, forecast and movement, programme status, live risks, change, cash and specific decisions required. Supporting detail can follow, but the first page must stand alone.

How long should a board report be?

For a project, the executive summary should fit on one controlled page. The wider pack can contain supporting cost, programme, risk, change and payment detail where required.

What is the difference between a lagging and a leading indicator?

A lagging indicator shows what has happened, such as cost to date or value certified. A leading indicator shows what is likely to happen, such as forecast movement, float consumption or unresolved change.

How often should I report?

Use a monthly reporting cycle with a fixed status date and a short weekly exception check. Increase the frequency when the project is under material commercial or programme pressure.

What do I do if the numbers are bad?

State the position early, identify the cause, set out the available options and assign the decision to a named person with a date. Do not wait for the next month-end if the position has already changed.

Close the loop with a Commercial Health Check

Good project controls do not create more paperwork for its own sake.

They give you a firmer grip on cost, programme, risk, change and cash. They show movement early. They tell directors where a decision is required.

BHD Commercial's team brings 25 years' experience across construction, defence and infrastructure. Our collective professional-membership background supports a practical approach to project controls for contractors across the UK.

We bring the commercial discipline of major infrastructure programmes to smaller firms, right-sized for the job. Our head office is at 66 Paul Street, London EC2A 4NA, with a regional office at 4-5 Victoria Square, Wolverhampton, WV1 1LD.

If your monthly pack is long, late or difficult to reconcile, request a free Commercial Health Check. A straight view of the reporting pack is often the quickest way to find where control is missing.