Sign In Try Free
Workflow-specific products Content, decks, briefs, proposals, legal, and sales each have a clearer buying path.
Review before delivery Draft, edit, collaborate, approve, and export in the same workspace.
Security + procurement path Security policy, support, and Azure Marketplace buying are public.

Gixo Lumen · deck structure

Project Management Presentation

A status deck exists to get blockers unblocked. Lead with the honest status and what you need — the detail of what the team did is the least useful part for the people in the room.

AudienceSponsors and stakeholders
Typical length10–14 slides
Runs for20–30 minutes

Last reviewed: August 2026

The slide sequence

Each step names the Lumen slide layout to use, so you can build this deck by adding layouts to a blank deck in order. Manual building is free and unlimited, and it does not consume the AI meter.

  1. Status in one word

    On track, at risk, or off track. Stated before any detail.

    Title
  2. Where we are against plan

    Milestones done, in flight, and slipped.

    Roadmap
  3. What moved since last time

    Only what changed. Not a re-read of the plan.

    TitleContent
  4. Blockers

    What is stuck, who owns it, and what would unstick it.

    Table
  5. Decisions needed today

    The reason the meeting exists. Put it early, not last.

    Agenda
  6. Risks and how they have changed

    New, worsened, and closed since last time.

    Table
  7. Budget and resource position

    Spend against plan and any resourcing gap.

    Stats
  8. Scope changes

    What was added or removed, and who approved it.

    Comparison
  9. What happens next

    The next milestone with a date and an owner.

    Timeline
  10. Where the detail lives

    Tracker, board or doc. Keeps this deck short.

    Sources
Read the titles alone before you present. Written as statements rather than labels, the titles of this deck should tell the whole story on their own. If they read as a table of contents, the sequence is fine but the writing is not.

What makes this deck fail

  • Green status with a red blocker. Status inflation destroys the value of every future report.
  • Decisions on the last slide. They get squeezed by overrun; put them in the first half.
  • An activity log. Sponsors need exceptions and decisions, not everything the team did.
  • Blockers with no owner or ask. Naming a blocker without saying what would fix it changes nothing.
  • Rebuilding the deck each time. A fixed structure lets people find what they care about instantly.

Adapting the length

You haveKeepCut
10 minutesStatus, blockers, decisions, next milestoneBudget, scope detail
30 minutesThe full sequence as listedNothing
Written updateEverything, plus links to the trackerNothing

Frequently asked questions

What should a project status presentation include?

Status in one word, progress against plan, what changed, blockers with owners and asks, decisions needed, risks, and the next milestone with a date.

How often should project updates be presented?

Fortnightly for active delivery and monthly for steering groups. Consistency of structure matters more than frequency, because people learn where to look.

What is the most common mistake in status decks?

Reporting green while a real blocker is unresolved. Status inflation costs you credibility permanently and makes every later report harder to trust.

Should status decks include a detailed plan?

No. Link to the tracker and keep the deck to exceptions and decisions, or the meeting turns into a plan review rather than a decision forum.

Can I build a project status deck for free?

Yes. Building manually from a blank deck in Gixo Lumen is free and unlimited on every plan, with no export paywall.

Related deck structures

Build this deck without paying for it

Start from a blank deck, add these layouts, and export a real PPTX — manual decks are free and unlimited on every plan, with no export paywall. Use the AI path when you would rather hand over source material and edit the result.