Palletgrove Distribution WMS Rollout: Status Report 11
Project status report presentation example in 8 slides
A project status report presentation has to show, in the few minutes a leadership meeting gives it, whether the project is on schedule, budget and scope, what changed since the last report, and what the leaders need to do. Palletgrove Distribution, an invented wholesaler, reports week 22 of a 39 week warehouse system rollout: amber overall, one site two weeks late, and four asks.
Every slide, in order
The whole deck as it renders, one slide after another. Read it the way the audience would.
The structure
What each slide is doing, so you can reuse the order even with different content.
- Slide 1cover
- Names the project, the report number and the date, so fortnightly reports file in order.
- Slide 2metrics
- Schedule, budget and scope health in three numbers, the first thing the reader looks for.
- Slide 3timeline
- Milestones done and still to come on one road, so progress since the last report is visible.
- Slide 4comparison
- Open issues with owner and due date, so the meeting can check each one in a minute.
- Slide 5comparison
- What caused the south delay and what has been done about it, in one problem and one fix.
- Slide 6checklist
- The work planned for the next fortnight, so the next report can be checked against it.
- Slide 7metrics
- Budget detail behind the green status, so the number on slide two can be checked.
- Slide 8closing
- Closes with the asks of the leadership team, each specific enough to answer in the meeting.
Slide by slide
Slide one names the project, report 11 and the period. Slide two gives schedule, budget and scope health with a reason each. Slide three shows six milestones: three done, one late and two still to come. Slide four lists five open issues with effect, owner and due date, and notes two closed this period. Slide five explains why the south site moved. Slide six sets the next fortnight's five tasks. Slide seven breaks down the budget: $1.12M, $0.48M and $0.26M spent, with $18,000 drawn from a $150,000 contingency. Slide eight lists four asks of the leadership team.
How to adapt this deck
A software project should swap milestones for releases and add a slide of open defects by severity. A project reporting to a steering committee rather than an operations team should move the asks to slide two, since that group meets to decide, and fold the next fortnight into an appendix. If the project is green throughout, cut the deck to slides one, two, three and eight. If you need a written report rather than a deck, see the project status report template in the documents examples, and the guide on how to write a project status report.
What project reporting practice says
UK government major projects are rated with a Delivery Confidence Assessment, which the National Infrastructure and Service Transformation Authority's annual report defines as an assessment of the likelihood of a project delivering its objectives to time and cost, published as green, amber or red. The Association for Project Management describes governance as giving the sponsor and senior leaders sufficient reporting to stay informed of progress. This deck applies both at project scale: one rating per dimension, each backed by its numbers.
What makes this deck work
Each status has its reason
Slide two rates schedule amber, budget green and scope green, and gives the reason under each: the south site moves from 31 May to 14 June, $1.86M is spent of $3.40M at 56 percent of the time, and no change requests came in. A colour without a reason invites a debate; a reason ends one.
The one change gets its own slide
Slide five explains the only schedule change in one problem and one fix: scanners dropped in six aisles behind steel racking, so four access points go in by 28 May with a second rehearsal on 2 June. The leadership team sees the delay is understood before it is asked to approve the new date.
Next fortnight makes the next report checkable
Slide six lists five tasks for 15 to 28 May with an owner each, from the printer driver fix to mapping 18,000 bins at the west site. Report 12 can open by ticking them off, which is how fortnightly reporting builds trust over a nine month rollout.
Questions people ask
What goes in a project status report presentation?
Health for schedule, budget and scope with a reason for each, milestones done and remaining, open issues with owners, any change since the last report and why, the next period's tasks, budget detail and the asks. Eight slides is enough for a regular leadership slot.
Should a project status report be a deck or a document?
Use a deck when the report is presented in a meeting and a document when it is read on its own. Many teams send the written report beforehand and present a short deck. The deck should carry the decisions and the changes, not every detail in the report.
How often should a project status report be presented?
Fortnightly suits most projects of six months or more, and weekly suits the final weeks before a go live. Keep the same slide order every time and number the reports, so readers can compare report 11 with report 10 without hunting for the numbers.
How do I report a delay in a status presentation?
Give it its own slide: what happened, the evidence, the fix, the new date and the condition for keeping it. Show it as amber on the health slide with a one line reason. Leaders accept a late date far more easily when they can see the cause is understood.
What asks belong at the end of a status report?
Only things the audience can do: approve a date, release people, note a cost or escalate a blocker. Keep each to a few words with a deadline in the description. If an item does not need anyone in the room, it belongs in the next fortnight list instead.
Can I update the same deck for each fortnightly report?
Yes. Edit the numbers and save, and every save is kept as a version, so earlier reports can be previewed or restored from the version history. If you need report 11 and report 12 as separate files, export each one to PDF before you change it.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make one like thisOther presentation examples
Product roadmap presentation example: now, next, later
A product roadmap presentation has to prove that every item answers a problem customers actually have, that the near term is dated and the far term is honest about being uncertain, and that people know how to add to it. Crewlantern, an invented onboarding app for frontline employers, puts mobile onboarding first because 71 percent of new hires open it on a phone and only 48 percent of them finish.
Budget proposal presentation: where every dollar goes
A budget proposal presentation has to prove to finance that every dollar has a line, that the increase is traceable, and that the money will be controlled once it is approved. The marketing team at Marlowfen Homewares, an invented retailer, asks for $1.4M, up $220K on last year, and shows what the extra money is expected to return against holding the budget flat.
Steering committee presentation: status, budget, decisions
A steering committee presentation has to show the sponsor in minutes whether the project is on track for money and time, what has gone wrong, and which decisions only the committee can make. Cindermoor Mutual, an invented insurer, reports its CRM replacement at month 7 of 12: 62 percent of budget spent at 58 percent of the time, a $290K forecast overrun and three decisions for today.
Want the steps in the builder? Read Edit your deck with the AI assistant, then Export a presentation to PowerPoint or PDF. For everything this generator can do, see the presentation maker.
Sources
Written and checked by the OneCraft team. Last checked .