Aidar Akmaev
Quick answer: a project status report presentation shows, on one slide or a short deck, whether a project will land on time, on budget and in scope, what changed since the last report, and what needs deciding. Rate each dimension red, amber or green against tolerances agreed in advance, then show milestones, top risks and the asks.
In short
- Weekly statusOne slide for the team, sponsor and PMO, to catch slippage early.
- Steering committee deckEight slides plus an appendix, monthly or at stage gates, built around decisions.
- RAG ruleAmber: within the agreed tolerance, with a recovery action. Red: a tolerance is forecast to break, so someone above the project manager must decide.
- Overall statusThe worst dimension, never an average.
- DataFacts from a Jira, MS Project or Excel export; the reasons from you.
Disclosure: NOXI publishes this guide. Everything outside the NOXI section works in PowerPoint, Google Slides or Keynote, and the routes compared near the end include ones that fit some teams better.
Status report or steering committee deck: which are you making?
A status report keeps people informed on a fixed rhythm. A steering committee deck gets decisions from the people who control budget, scope and dates. Same data, different job.
| Format | Audience | Cadence | Length | Its job |
|---|---|---|---|---|
| Weekly status | Team, sponsor, PMO | Weekly | 1 slide | Spot slippage early |
| Sponsor or PMO report | Sponsor, PMO | Fortnightly or monthly | 2–4 slides | Confirm status, raise risks |
| Steering committee deck | Sponsor, business owners, finance, suppliers | Monthly or at stage gates | 8 slides + appendix | Decisions, approvals |
| Exception report | Steering committee | When a tolerance is forecast to break | 2–3 slides | One decision, fast |
PRINCE2 calls the steering committee the project board: an executive who owns the business case, a senior user and a senior supplier [4]. The board delegates tolerances (permitted deviation on time, cost, scope, quality, benefits, risk and, since the 2023 edition, sustainability [3]) to the project manager, receives regular highlight reports, and steps in only when a tolerance is forecast to break, a principle called "manage by exception" [4][5].
You don't need PRINCE2 to borrow the idea: agree up front what the project manager may absorb and what goes to the committee. At team level, lighter works: Atlassian's weekly update play suggests a post at the end of each week with a tight headline and one to three sentences on wins, input needed and next focus [10]. If you are reporting a business unit's quarter rather than a project's health, see our QBR presentation guide instead.
The one-slide project status: anatomy
A one-slide status has six zones: a header with overall status, a headline, status by dimension, milestones, top risks and issues, and what you need. An executive who reads only this slide should know whether to worry and what to do.
| Zone | What goes in it | Rule |
|---|---|---|
| 1. Header | Project, reporting date, overall RAG, trend | Overall = worst dimension |
| 2. Headline | One-sentence verdict with the key number | States the change, not the topic |
| 3. Status by dimension | Schedule, cost, scope, risk, resources, benefits | Colour + word + one-line reason |
| 4. Milestones | Next 3–5: baseline, forecast, change | Forecast dates, not hopes |
| 5. Risks & issues | Top 3, each with owner and next step | The rest stays in the log |
| 6. Decisions & help | Each ask with owner and deadline | "None this week" is valid |
The headline does most of the work. "Project Falcon status update" says nothing. "Go-live holds at 12 May; supplier testing one week late, recovery plan agreed" gives the verdict, the problem and the fact that it is handled. Write it last, once the colours are settled. Our guide to consulting-style slides has more on action titles.
Use a fixed grid: dimension strip under the headline, milestones left, risks right, decisions along the bottom, in the same positions every week.
RAG rules: thresholds that end the colour debate
Set the thresholds with your sponsor before the first report and tie them to the tolerances the committee delegated to you. Then the colour is a calculation, not a negotiation: green within plan, amber within tolerance with a recovery action, red when a tolerance is forecast to break.
The definitions at the top of this guide follow the UK government's: its National Infrastructure and Service Transformation Authority (NISTA) rates major projects on the same three-point scale [1], and its assurance template describes red as delivery that appears unachievable, with the project possibly needing re-baselining [2].
| Dimension | Green | Amber | Red |
|---|---|---|---|
| Schedule (key milestones) | On baseline, or ≤ half the tolerance used | Over half the tolerance used; recovery plan in place | Forecast beyond tolerance |
| Cost (forecast at completion) | Within budget, or ≤ half the tolerance used | Over half the tolerance, still within it | Forecast beyond tolerance |
| Scope | No unapproved change to committed deliverables | Change requests pending that affect deliverables | A deliverable can't be met without a scope decision |
| Risks & issues | Every high risk has an owner and mitigation | High risk, mitigation under way | An issue already hits a tolerance, or no workable mitigation |
| Resources | Key roles filled as planned | Gap covered short term | Critical role or supplier missing beyond an agreed limit |
| Benefits | Business case holds | Benefit assumptions weakening | Business case no longer holds as approved |
These are starting points, not a standard: agree the "half the tolerance" line and the resource limit (two weeks, say) with your sponsor. With ±5% on cost, green runs to 2.5% over budget, amber from 2.5% to 5%, and red is anything forecast beyond 5%.
Six rules that keep RAG honest
- Rate the forecast, not the effort.A busy week is not green; what counts is whether the end date and cost still hold.
- Overall status is the worst dimension.Never average. If the sponsor overrides a rating, show the override and the reason.
- Every amber and red has a path to green.An action, an owner and the date the colour should change.
- Show the trend.An improving amber and a worsening amber are different conversations.
- Never let colour carry the meaning alone.About 1 in 12 men has a colour vision deficiency, most often red-green [9]. Print the word next to the colour.
- Treat red as a call for help, not a verdict.NISTA states that red does not mean a project will fail. At 31 March 2026, 58% of the 189 projects in the UK government's major projects portfolio were amber and 18% were red [1].
Who decides the colour? The project manager proposes it, the PMO checks it against the rules, the sponsor confirms it, and disagreements are written down. In the UK portfolio, senior responsible owners rate their projects every quarter, but where a project has had independent assurance in the past six months, NISTA publishes the independent rating instead [1].
Written rules matter because reports drift optimistic. A study in MIS Quarterly found that optimistic biasing degrades reporting quality, which is linked to project performance [6]. Three of its authors, writing with Mark Keil in MIT Sloan Management Review, describe how executives get blindsided when bad news is filtered on its way up [7].
If you use earned value, SPI (earned value ÷ planned value) and CPI (earned value ÷ actual cost) below 1.0 mean less work done than planned, or work that cost more than planned [8]. Mapping them to colours (say, red below 0.90) is a local convention, and the US GAO's cost guide says unfavourable indices should be investigated to find the cause [8].
The steering committee deck: eight slides
Eight slides, with the asks stated up front on slide 2. The committee has read the pre-read, so the meeting is for the two or three things only they can decide; everything else goes in the appendix.
| Slide | What goes on it | Question it answers |
|---|---|---|
| 1. Title & status | Project, period, overall RAG, trend, verdict | Should we worry? |
| 2. Summary & asks | Verdict, three reasons, decisions on the agenda | What do you need from us? |
| 3. Status by dimension | Six-dimension RAG with trend and reason | Where is the problem? |
| 4. Milestones | Baseline vs forecast, today line | Will we land on time? |
| 5. Budget | Approved, spent, forecast, variance vs tolerance | Will we land on budget? |
| 6. Top RAID items | Risks, issues, dependencies, changed assumptions | What could knock us off? |
| 7. Decisions needed | Options, recommendation, owner, deadline | What do we decide today? |
| 8. Next period | Work before next meeting, help needed | What happens next? |
Appendix (numbered A1, A2…): the full RAID log, change log, detailed plan, RAG rules and metric definitions. Run the meeting from slide 7. As a rule of thumb, send the deck two working days ahead and give decisions at least half of a 60-minute meeting. Open with last meeting's decision log: what was decided, by whom, and whether it happened. If the project also reports to the board, that is a shorter, more strategic deck; see our board meeting presentation guide.
The decisions-needed slide
Give each decision one row: the ask, the options and their effect on time, cost and scope, your recommendation, who decides and by when, and what happens if nobody decides. A well-framed decision takes minutes; a vague "for discussion" item eats the meeting.
| Column | Write | Avoid |
|---|---|---|
| Decision | "Approve $64K to hold 1 March go-live" | "Discuss data migration" |
| Options | A, B, C with time, cost, scope impact | One option dressed as a choice |
| Recommendation | Your pick and why, in one line | No view |
| Owner | One named role | "The committee" |
| Deadline | A date, and why that date | "ASAP" |
| If no decision | What slips, by how much | Leaving it blank |
Most options pull the same levers: money or people, the date, scope, or accepting the risk. If an option breaches a tolerance, say so: the committee is then also being asked to change the tolerance. Keep small asks (release a specialist, unblock a supplier) in a separate "help needed" line, and walk the sponsor through the slide beforehand. Nobody should hear a red for the first time in the room. When the cause is technical, such as a slow data migration, see how to explain a technical problem to executives as cause, impact and options.
Milestones and Gantt: show the slip, not just the bars
Show baseline and forecast for each key milestone, mark today, and keep the chart to the five to eight milestones the committee cares about. A Gantt with 80 tasks hides the one slip that matters.
- Baseline next to forecast: a pale bar and a solid one, or two markers, with the variance in working days.
- A today line, so late work is obvious.
- Dependencies only where they explain a slip, not the full network.
- A milestone trend chart for long projects: plot each milestone's forecast date at every reporting date. A line that climbs every month shows a pattern that no single snapshot reveals.
RAID: what goes on the slide and what stays in the log
Keep the full RAID log (risks, assumptions, issues, dependencies) in a spreadsheet or your project tool. The slide shows only the three to five items the committee must see, each with an owner and a next step.
| Type | What it is | Slide columns | On the slide when |
|---|---|---|---|
| Risk | May happen | Impact, likelihood, owner, mitigation | High impact, not mitigated |
| Assumption | Treated as true | Assumption, check by, date | Proved false or unchecked |
| Issue | Happening now | Impact, owner, action, due date | Hits a milestone or budget |
| Dependency | Needed from outside | From whom, needed by, status | Late or at risk |
Some teams read the A and D as actions and decisions; either works if the appendix says which. Decisions still get their own slide.
Worked example: an ERP rollout status (illustrative)
The setup. Phase 1 of Calloway's ERP rollout (finance and warehouse) has an approved budget of $2.40M with a ±5% cost tolerance and a 1 March 2027 go-live with a 10-working-day tolerance. Reporting date: 30 September 2026; the steering committee meets in mid-October.
Headline: "Go-live forecast slips 12 working days to 17 March; one decision today holds 1 March."
| Dimension | Status | Reason |
|---|---|---|
| Schedule | Red ↓ | Go-live forecast 17 March, 12 days late; tolerance is 10 |
| Cost | Amber → | Forecast $2.49M: +$90K (3.75%), within ±5% |
| Scope | Amber → | CR-07 (retailer EDI, +$38K) pending |
| Risks & issues | Amber ↓ | 7,380 of 41,000 customer records (18%) failed validation |
| Resources | Amber → | Warehouse lead at 50% during Nov–Dec peak |
| Benefits | Green → | Business case unchanged |
Overall: Red, worsening (amber last month). The 3.75% cost overrun uses 75% of the 5% tolerance, so cost is amber. The 12-day slip is beyond the 10-day tolerance, so schedule is red, and so is the overall status.
| Milestone | Baseline | Forecast | Change |
|---|---|---|---|
| Finance build complete | 18 Sep 2026 | 25 Sep (done) | +5 days |
| Mock migration 2 | 23 Oct 2026 | 13 Nov 2026 | +15 days |
| UAT sign-off | 5 Feb 2027 | 23 Feb 2027 | +12 days |
| Go-live | 1 Mar 2027 | 17 Mar 2027 | +12 days |
Changes are in working days; float absorbs three days of the migration slip.
Decision 1 (owner: sponsor, the CFO; by 16 October). Option A: add a second data-migration contractor for eight weeks at $64K. Go-live holds, but the forecast rises to $2.554M (+6.4%), beyond the cost tolerance, so the committee must also raise it to 7%. Option B: move go-live to 17 March at no extra cost, putting cutover in the last fortnight before the 31 March year-end close. Option C: move the warehouse slotting module to Phase 2, deferring its benefits. Recommendation: A, because cutover during year-end close is the bigger risk. The date leaves two weeks to onboard the contractor; with no decision, B happens by default.
Decision 2 (owner: COO; by 30 October). Defer CR-07 to Phase 2; adding it now costs $38K and about three weeks. Help needed: release the warehouse lead full time from 2 November to 18 December.
From a Jira, MS Project or Excel export to slides
Export the facts from your tool, write the reasons yourself, and let the slide software handle layout. Here is what each tool exports, per its vendor's documentation, checked on 2 October 2026.
| Tool | How to export | Watch for |
|---|---|---|
| Jira Cloud | List or search › More actions (•••) › Export › Export CSV [11] | Filter first; CSV export handles up to 10,000 work items [12] |
| Jira Plans | Share › Export › timeline image (.png) or data (.csv) [13] | Premium and Enterprise; exports only what is visible |
| MS Project desktop | File › Export › Save Project as File › Excel Workbook, then the Export Wizard [15] | Map baseline and forecast dates |
| Project for the web | ••• › Export to Excel [15] | Microsoft says it is becoming Planner |
| Excel tracker | Your own sheet | One row per item, one tab per table |
Prepare three tables and a page of notes: milestones (baseline, forecast, actual), budget (approved, spent, forecast at completion) and the top RAID items. The notes carry what no export contains: why each amber or red happened, the recovery actions, and the options for each decision. Drop columns you don't need, such as personal emails, and check your organisation's policy before uploading project data to any tool.
How to build it in NOXI
I describe the steps in NOXI because it lays out Gantt charts, timelines, scorecards and comparison tables from your own data and can design the deck in the style of your PMO template. Uploading files needs a free account.
Step 1 — Upload the export, your notes and a style reference
Upload the CSV or Excel export and your notes (NOXI also takes PDF, Word, PowerPoint, text and images) and it works from your files. With "Match reference", attach last month's deck or the PMO template (PowerPoint, PDF or even an image) as the reference: NOXI designs the new deck in that style, with its colours, typography and layouts.
Step 2 — Brief it and review the outline
Give the audience, the eight slides from this guide, your RAG rules and tolerances, and one rule: "use only the figures in my files". Review the outline first, then generate; slides are drawn on screen as they are built.
Step 3 — Edit by chat or on the slide
Ask in plain language: "make slide 4 a Gantt with baseline and forecast bars and a today line", "turn the Resources row amber and add the reason". Click any element and tell the AI what to change, or on desktop circle a cell and the AI follows your sketch. Table cells and chart numbers are editable directly.
Step 4 — Check every number and colour
Put the export next to the deck, tick off each figure and recompute each colour from your rules. The status is still yours to sign.
Step 5 — Share, present and export
Send a PDF as the pre-read and download an editable PowerPoint (.pptx) for the PMO pack, free and with no watermark. NOXI's own export engine writes real, editable text boxes, embeds the fonts and keeps the original image quality, so the file opens in PowerPoint with your typography. Or present full-screen from NOXI, share a view-only link, or invite workstream leads as editors to work on it together in real time.
The weekly refresh: generate next week's deck from the new export with last week's as the style reference, or paste the changed rows into the chat and ask the AI to update milestones and colours; version history keeps earlier versions. NOXI is free (1,000 credits a month; a full deck uses about 25), and your presentations, prompts and files are not used to train AI models. More on house styles in our guide to AI presentations in your own template.
Two prompts for the status slide
Use them in NOXI after uploading your files, or in any AI tool that has your data; replace the brackets. A wider library is in our presentation prompts guide.
Using only the attached [export] and [notes], build a one-slide status for [project] as of [date]: header with overall RAG and trend; a one-sentence headline with the key number; six dimensions (schedule, cost, scope, risks, resources, benefits), each with colour, word label and one-line reason; the next four milestones with baseline, forecast and change in working days; top three risks with owners; a decisions band at the bottom.
Rate each dimension: green if within plan or using no more than half the tolerance; amber if using more than half but still within it; red if forecast beyond tolerance. Tolerances: cost ±[5]%, go-live ±[10] working days. Overall = worst dimension. Show the calculation for each colour in the footnote.
Other ways to build the status deck
Pick by how often the deck repeats and who reads it. Linked Excel data in PowerPoint refreshes with right-click › Update Link [16], and Atlassian's free Jira Cloud for Excel add-in can refresh the workbook on a schedule [14]: hard to beat when charts must look identical every week, though the narrative stays manual. Jira Plans exports a timeline image with a legend for presentations [13]. Below committee level, a written weekly update is often enough [10]. Template galleries give layouts to fill; Beautiful.ai's 16-slide status template runs on its platform after a 14-day free trial, as of October 2026 [17]. NOXI fits when you want the whole deck designed from your exports and notes in your existing style. For general design rules, see our professional presentation design guide.
Frequently asked questions
- What should be included in a project status report presentation?
- An overall status with a trend, a one-sentence headline, a red-amber-green rating for schedule, cost, scope, risks, resources and benefits with a reason for each, the next milestones with baseline and forecast dates, the top risks and issues with owners, and the decisions or help you need.
- How do you decide if a project is red, amber or green?
- Agree tolerances with your sponsor first, for example ±5% on cost and ±10 working days on go-live. Green is within plan or using no more than half the tolerance; amber uses more than half but stays within it, with a recovery action; red is forecast beyond tolerance and needs a decision from above the project manager.
- What is the difference between a status report and a steering committee presentation?
- A status report keeps the team and sponsor informed on a fixed rhythm, often one slide a week. A steering committee presentation goes to the senior people who control budget, scope and dates, usually monthly or at stage gates, and is built around the decisions only they can make.
- How many slides should a steering committee presentation have?
- About eight in the main flow: title and status, summary and asks, status by dimension, milestones, budget, top RAID items, decisions needed and next period. The full RAID log, plan and RAG rules go in a numbered appendix.
- What is a RAID log in a status report?
- A RAID log records risks, assumptions, issues and dependencies; some teams use the A and D for actions and decisions. The full log lives in a spreadsheet or project tool, and the status slide shows only the three to five items the audience must act on.
- How often should you send a project status report?
- Weekly for the team and sponsor, fortnightly or monthly for the PMO, and monthly or at stage gates for the steering committee. If a tolerance is forecast to break between meetings, escalate straight away with a short exception report.
- Can AI create a project status report from Jira?
- Yes. Export your Jira work items to CSV, add notes on causes and decisions, and upload both to an AI presentation tool such as NOXI, which builds the status slide, milestones and RAID tables from your file. The AI cannot know why a date slipped, so write the reasons yourself and check every number.
Sources & methodology
The slide structures and RAG thresholds combine project-method terminology (PRINCE2, earned value) with common PMO practice; they are guidance, not a standard, and the threshold values are examples. Calloway Foods is fictional. Tool steps were checked on vendors' own pages on 2 October 2026 and change often.
- [1] Three-point delivery confidence scale; 31 March 2026 portfolio (189 projects: 15% green, 58% amber, 18% red); red not meaning failure; quarterly self-ratings and independent ratings after assurance — NISTA Major Projects Annual Report 2025–26, GOV.UK (13 July 2026).
- [2] Green, amber and red descriptions, Annex A of the Assurance of Action Plan template (v1.1, 2025) — GOV.UK, Assurance of action plan guidance and templates.
- [3] PRINCE2 Version 7 integrates sustainability into project performance — PeopleCert, PRINCE2 Project Management Foundation (Version 7).
- [4] Project board of executive, senior user and senior supplier; the executive owns the business case; the project manager works within tolerances set by the board — Knowledge Train, PRINCE2 roles and responsibilities (July 31, 2026).
- [5] Seven tolerance areas including sustainability (2023 edition), management by exception, highlight and exception reports (secondary summary) — Wikipedia, PRINCE2.
- [6] Optimistic biasing and reporting quality — Iacovou, Thompson and Smith, "Selective Status Reporting in Information Systems Projects", MIS Quarterly 33(4), 2009.
- [7] Why executives are blindsided by troubled projects — Keil, Smith, Iacovou and Thompson, "The Pitfalls of Project Status Reporting", MIT Sloan Management Review (March 2014).
- [8] CPI and SPI formulas, values below 1.0, investigating indices — US GAO, Cost Estimating and Assessment Guide (GAO-20-195G), Table 23.
- [9] About 1 in 12 men has a colour vision deficiency; red-green is the most common — National Eye Institute (updated November 5, 2025).
- [10] Weekly project updates: end of week, tight headline, one to three sentences — Atlassian Team Playbook.
- [11] Export CSV from a Jira Cloud list or search — Atlassian Support (updated February 20, 2026).
- [12] CSV export from the Issue Navigator supports up to 10,000 work items — Atlassian Support (updated July 3, 2026).
- [13] Jira Plans timeline image with legend, up to 500 items; CSV of visible data; Premium and Enterprise — Create a static image of your plan; Export your plan data as .csv.
- [14] Jira Cloud for Excel (official): free, by Atlassian, scheduled refresh — Atlassian Marketplace.
- [15] Export Wizard in Project desktop; Export to Excel in Project for the web, which is becoming Planner — Microsoft Support.
- [16] Linked Excel data in PowerPoint and Update Link — Microsoft Support.
- [17] Project status report template (16 slides), 14-day free trial — Beautiful.ai.
Build this month's steering committee deck in NOXI, free: upload your Jira or Excel export and your notes, use last month's deck as the style, and get the status slide, milestones, RAID and decisions slides ready to present or download as an editable PowerPoint.
