Report header
- Project
- Reporting period
- Overall RAG
- Apply the objective rules below rather than a judgement call.
IT Project Status Report
Status reports stay green until the week they turn red, because amber invites scrutiny nobody wants. Defining RAG by objective criteria rather than by judgement is the only reliable fix.
What you get
- RAG definitions based on criteria, not on feel
- A decisions-needed section, which is what the report is actually for
- Milestone tracking with baseline versus forecast dates
- A risks and issues section that distinguishes the two
How to use this template
- 1
Define RAG objectively. Green: on baseline date and within budget. Amber: forecast slip under two weeks or budget variance under 10%, with a recovery plan. Red: beyond those, or needing a decision. Objective rules remove the social cost of amber.
- 2
Lead with decisions needed. Put it at the top. A status report that reports progress but buries the blocking decision has failed at its only real job.
- 3
Keep the baseline date visible. Show baseline alongside forecast. Reports that only show the current forecast hide cumulative slippage, because each individual slip looks small.
What's inside
Here's a preview. Unlock the free download to get all 4 sections (3 more below).
Related templates
More free templates IT teams use alongside this one.
IT Management & Finance
Get templateIT Project Charter
Projects fail on scope, and scope fails on what was never written down. The most valuable section of a charter is the out-of-scope list, because that is what gets argued about in month three.
IT Management & Finance
Get templateIT Roadmap Template
IT roadmaps become wish lists because they list initiatives without capacity. Showing what the team can actually deliver alongside what has been requested is what turns the roadmap into a prioritisation conversation.
IT Management & Finance
Get templateIT RACI Matrix
RACI matrices fail in one predictable way: multiple people marked accountable for the same activity, which means nobody is. One A per row is the rule that makes the whole exercise worthwhile.
Frequently asked questions
How should project RAG status be defined?
+
By objective criteria: green is on baseline date and within budget tolerance; amber is a forecast slip or budget variance within defined thresholds with a recovery plan; red is beyond those or blocked pending a decision. Judgement-based RAG stays green until it cannot.
What is the difference between a risk and an issue?
+
A risk may happen and has a likelihood; an issue has already happened and needs action now. Reporting them in one list obscures what requires immediate attention versus what needs monitoring.
What should go at the top of a status report?
+
Decisions needed, with options, a recommendation, the decision owner, and the date by which it is needed. Progress narrative matters far less than unblocking the thing that is currently stuck.