Reporting

Weekly Project Status Report Template

A good status report takes two minutes to read and answers one question: is this project okay? Use this free template for a weekly update that sponsors actually read — or let Planquora draft it from your project record, separating fact from interpretation from forecast.

What it is

A weekly status report is a short, standardized update sent to stakeholders that communicates progress, health, and anything needing attention. Its job is not to list everything you did — it's to give a busy sponsor confidence and surface the few things they need to act on.

The best ones lead with an overall status (a RAG — Red / Amber / Green), then keep everything else scannable. If your report needs a meeting to explain it, it's too long.

When to use it

Weekly, on a predictable day, to the same distribution list.
As the written record behind a steering or client check-in.
Whenever status changes materially — don't wait for Friday to flag a project going Red.

The template

Header

Project: Name + one-line purpose
Reporting period: Week ending <date>
Prepared by: PM name
Overall status: 🟢 Green / 🟡 Amber / 🔴 Red — plus one sentence why

Body

Summary: 2–3 sentences: where the project stands this week
Accomplished this week: 3–5 bullets of completed, verifiable work
Planned next week: 3–5 bullets of what's targeted next
Schedule & budget: On track / at risk / off track — with the number, not a vibe
Top risks & issues: The 2–3 that matter, pulled from your RAID log
Decisions & help needed: Explicit asks with owners and dates — the part sponsors read first

Tips

Lead with the RAG status and the ask. Sponsors read top-down and often stop early.
Separate fact from forecast. "Shipped auth" and "expect to finish by Friday" are different claims — label them.
Keep it to one screen. Link out to detail rather than pasting it in.
Be honest about Amber and Red. A report that's always Green trains people to ignore it.

Browse all free templates or read the Help Center.