Presentation Template for Project Status Updates

The project status update is one of the most common presentations in business -- and one of the most poorly executed. Most status decks either bury critical risks in walls of text, or present a falsely rosy picture until it's too late to course correct. Neither serves the stakeholders who depend on accurate information to make decisions.

A well-structured project status presentation does three things in under 10 minutes: tells stakeholders where things stand today, where things are headed, and what -- if anything -- they need to unblock. Everything else is noise.

What to Include in a Project Status Presentation

| Slide | Content | Notes | |-------|---------|-------| | 1. Title | Project name, reporting period, presenter, date | Weekly or sprint cadence | | 2. Executive Summary | 3-bullet summary: status, key accomplishment, top risk | For time-pressed stakeholders | | 3. Overall Status (RAG) | Red/Amber/Green for Schedule, Budget, Scope, Resources | Single-glance health check | | 4. Milestone Tracker | Planned vs. actual dates for each milestone | Use visual timeline | | 5. This Period: Completed | What was finished since the last update | Builds credibility | | 6. Next Period: Planned | What the team commits to completing | Accountability anchor | | 7. Risks and Issues | Active risks with severity, owner, and mitigation | Don't hide these | | 8. Budget Status | Spend to date vs. plan, forecast at completion | Finance-friendly format | | 9. Dependencies | What the team is waiting on from other teams | Escalation trigger | | 10. Decisions Needed | Specific asks from the audience with a deadline | Why you're in the room |

Understanding RAG Status Reporting

RAG (Red, Amber, Green) is the fastest way to communicate project health without narrative. Here's how to apply it consistently:

Green means everything is on track. No significant deviations from plan, no unmitigated risks that would affect delivery.

Amber means there is a risk or issue that requires monitoring. Without intervention, this could become a problem. Amber is not "fine" -- it's a warning that something needs attention within the current reporting period.

Red means a problem exists that will affect delivery, cost, or scope without immediate action. Red should never be a surprise to stakeholders -- if the project was Amber last week, explain what changed.

Use RAG separately for each dimension: Schedule, Budget, Scope, and Resources. A project can be Green on budget and Red on schedule. Separating these prevents stakeholders from averaging across dimensions and missing specific problems.

Common mistake: Keeping a project Amber for multiple consecutive periods without a mitigation plan. If you can't move Amber to Green within two reporting cycles, escalate or reforecast.

How to Use This Template in slide-deck.io

Step 1: Start a new presentation in slide-deck.io. Describe your project context: "Project status update for Q3 ERP migration, 8-person team, stakeholder audience is VP Ops and Finance." The AI will generate a structured status deck.

Step 2: Fill in your RAG indicators. The status slide generates with placeholder colors -- update each dimension to reflect the actual state of your project.

Step 3: Populate the milestone tracker. Add your planned dates and actual completion dates. The visual timeline updates automatically.

Step 4: Add your risks. Be direct. A risk slide that says "some resource constraints may exist" helps no one. Write "Senior backend engineer on PTO weeks 3-4, creating a 2-day delay risk on API integration milestone."

Step 5: End with decisions needed. Every status update should close with specific asks. If you need no decisions, say so -- but if you need something, make it explicit: who, what, and by when.

Project Status Presentation Tips

Write the executive summary first. If you can't summarize the project's status in three bullets, you don't have enough clarity to run the meeting. Writing the summary slide first forces that clarity.

Separate completed work from planned work. Many status updates describe what happened and what's next in the same slide. Stakeholders lose track of accountability when they can't distinguish what was committed vs. what was delivered.

Put risks in the presentation, not appendices. Risks buried at the end of a deck get skipped. If you're carrying a significant risk, it belongs in the first half of the presentation where it will be seen and discussed.

Report on actuals, not intentions. "We plan to complete X" is not a status update. Status means reporting on what actually happened, then committing to what comes next.

Keep budget slides simple. Finance stakeholders want spend-to-date, forecast-at-completion, and variance from plan. They don't need a breakdown by cost code unless you're in a formal budget review.

Frequently Asked Questions

Q: How often should I do project status presentations? Weekly for active projects with multiple stakeholders. Bi-weekly for steady-state projects or where the audience is small. At critical milestones regardless of cadence. Async status updates (written summaries) can supplement but rarely fully replace a live review for high-stakes projects.

Q: What's the right length for a project status deck? 10 slides or fewer for a weekly status update. Status meetings are not the place for comprehensive project documentation -- that belongs in your project management tool. The deck is a facilitation aid, not a substitute for your project plan.

Q: How do I present bad news in a status update? Directly and early. Put the risk or issue on the second or third slide. Stakeholders who discover bad news at the end of a meeting feel ambushed. Present the problem, your assessment of impact, and what you need from them. Most stakeholders respect honesty far more than they appreciate optimistic spin.

Q: Should I include team capacity or velocity data? Include it if it explains a change in trajectory. If your delivery pace slowed because two engineers were pulled onto a different project, show it. Context helps stakeholders make better decisions about resource allocation.

Q: What if stakeholders don't read the status deck before the meeting? Design for it. Slide 2 (Executive Summary) should be so clear that a stakeholder who skipped the prep email can orient themselves in 60 seconds. You cannot control whether people prep -- you can control whether your deck compensates for when they don't.

---

Create your project status presentation free at slide-deck.io -- no design skills required.