Skip to content
Template Reporting Reporting Project Operations Project Management

Template

Weekly Project Report Template

A concise weekly reporting structure for status, progress, blockers, risks, next steps, and decisions needed. Designed to take 15 minutes to fill in and 3 minutes to read.

💡 Send this report at the same time each week. Consistency matters more than completeness — a short consistent update is more useful than an occasional comprehensive one.

A weekly project report exists for one reason: to prevent stakeholders from needing to ask “where are we?” The best reports are short, honest, and action-oriented.

This template takes around 15 minutes to fill in and should take under 3 minutes to read.


Weekly Project Report

Project: [Project name] Report date: [Date] Reporting period: [Monday–Friday dates] Prepared by: [Name]


Overall status

DimensionStatusNotes
Schedule🟢 On track / 🟡 At risk / 🔴 Delayed[brief context if not green]
Scope🟢 Stable / 🟡 Change requested / 🔴 Scope shifted
Resources🟢 OK / 🟡 Stretched / 🔴 Blocked
Budget🟢 On budget / 🟡 Approaching limit / 🔴 Over budget

One-line summary: [What is the most important thing to know about this project this week?]


Completed this week

[List what was finished, not what was worked on. Finished = done, reviewed, approved, or delivered.]

  • [Item]
  • [Item]

In progress

[What is actively being worked on. Include the expected completion date for each item.]

ItemOwnerExpected completion
[Task][Name][Date]
[Task][Name][Date]

⚠ Blockers and issues

[Anything that is actively preventing progress. Be specific about what is blocked, why, and what is needed to unblock it. If nothing is blocked, write "None."]

IssueImpactWho can unblock
[Issue][What it delays][Name/team]

Risks

[Things that could become blockers or affect delivery — but aren't yet. Flag early.]

RiskLikelihoodAction
[Risk]Low/Medium/High[Mitigation or owner]

Decisions needed

[Items that require a decision from stakeholders or leadership this week. Include the deadline for the decision and what happens if it isn't made.]

DecisionNeeded fromDeadlineImpact if delayed
[Decision][Name][Date][What gets delayed]

Next week plan

[What the team plans to complete next week. Keep this short — 3–5 items.]

  • [Item]
  • [Item]

Notes and context

[Optional: anything else stakeholders should know — context, upcoming milestones, team changes, or relevant news.]


Report cadence guidance: Send this on the same day each week — Friday afternoon or Monday morning are the most common choices. The goal is predictability, not perfection.

Related services

Need help implementing this?

Templates are a starting point. If you want a system built and handed off to your team, let's talk.