Reporting upward: what your own management needs to hear about the job each month
Your monthly internal report describes what happened on site. The director reads it, says thanks and moves on. The decision you needed about staffing is still buried near the end, with no date showing when delay will affect the job.
Write a two-page internal project report around the decisions your own management must make. Put the requests and their needed-by dates on the first page, then explain the forecast, schedule, cash, unresolved changes and risks that support those requests. Keep it short enough to read before the review meeting and link the detailed records. This is different from reporting to the owner: your company needs to understand its exposure, resources and choices.
Lead with the decision, then explain the position
- State the asks first. Name each decision, the person who can make it, your recommendation and the date needed. Include what happens if the decision is delayed. Separate a request for authority from a request for information or practical support.
- Explain the forecast movement. Compare the current completion forecast with the previous report and starting budget. Describe the causes, assumptions and unresolved amounts. Do not make management reconstruct the story by comparing two cost spreadsheets.
- Show the schedule position. Use the agreed baseline and current milestone forecast. Identify the controlling constraint and the choices still available. Distinguish a recovery idea from an agreed, resourced plan.
- Address cash and receivables. Use checked company figures with a clear cutoff. Identify collection or billing actions, their owners and material uncertainty. Keep forecast income separate from approved amounts and receipts.
- Choose the changes and risks worth escalation. Explain items beyond the project team’s authority or capacity, with options and impacts. Keep ordinary follow-up in its supporting list so it does not obscure the few decisions management must take.
- Close the response loop. Issue the short report before the internal review and record each resulting decision. Carry an unresolved request forward with its age and next step rather than rewriting it as fresh background every month.
Common mistakes
- Sending the owner-facing report unchanged to company management.
- Putting a recommendation in a risk paragraph without asking for a decision.
- Reporting a favourable forecast while omitting the unresolved assumption that supports it.
Checklist
The first page should answer
- What decision or help is needed?
- Who can provide it and by when?
- What has changed since the last report?
- What supports the recommendation?
- What will be recorded after the review?
Check your understanding
Management acknowledges the report but gives no answer to your request. Can you treat that as approval?
