Weekly Status Report

Phase: Monitoring and controlling | Audience: Client-facing | Project: WEB-2026-01 Corporate Website Development

Understand it first

In simple words: The Weekly Status Report tells the client where the project stands: overall health (Red/Amber/Green), what was done, what is next, milestones, actions needed from them and top risks.

Think of it like: A school progress report: grades, what went well, what needs attention, and what parents should do.

When is it created?	Every Friday during the project
Who prepares it?	Project Manager
Who approves or uses it?	Sent to client sponsor and Delivery Head
What happens next?	Discussed in the weekly call

How it connects to other documents

Data comes from the Schedule, Risk Register and Issue Log.
Client actions come from Minutes of Meeting.
Schedule of reports is set by the Communication Plan.

The sample document

Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.

Issued by: [Your Company] Technologies Pvt. Ltd.

Purpose: Progress for the week ending 30 Oct 2026, sent to the client sponsor.

Item	Detail
Document no.	WEB-2026-01/WSR-04
Version	1.0
Date	30 Oct 2026
Owner	Project Manager
Audience	Client-facing
Phase	Monitoring and controlling

Item	Detail
Overall	Amber
Schedule	Amber
Scope	Green
Quality	Green
Work complete	36% (planned 37%)

1. Summary

Designs for all seven page types were approved on 30 Oct, on schedule. The project is marked Amber because content for the four services pages has not yet arrived; if it is not received by 6 Nov, content upload in week 7 and the go-live date will be at risk.

2. Completed this week

Round 2 design revisions delivered and approved.
Design sign-off form signed (milestone D2).
Staging environment and code repository set up.

3. Planned next week

Start theme development and CMS configuration.
Build the contact form on staging.
Assess change requests raised by your team.

4. Milestones

Milestone	Planned	Forecast	Status
Kickoff	5 Oct	5 Oct	Achieved
Sitemap approved	14 Oct	14 Oct	Achieved
Design sign-off	30 Oct	30 Oct	Achieved
Staging site ready	27 Nov	27 Nov	Amber
UAT sign-off	4 Dec	4 Dec	Green
Go-live	9 Dec	9 Dec	Green

5. Actions needed from you

Action

Owner

Due

Status

Content for four services pages

Marketing Executive

6 Nov

Overdue

Pay invoice INV-2026-118 (M2)

Finance

14 Nov

Due

6. Top risks

Risk

Impact

What we are doing

Late services content

Launch delay

Using placeholder text so development continues

New requests during build

Scope and cost growth

Routing through change requests

WEB-2026-01/WSR-04 · v1.0 · Client-facing. Bracketed items such as [Client Name] are placeholders.

Key takeaways

Be honest: Amber early is better than Red late.
Always list what you need from the client.
Keep it short enough to read in 2 minutes.

Common mistakes to avoid

Reporting everything Green until it is too late.
Only listing activities, not results.
Sharing internal cost details with the client.

Next lesson: 31. Budget Tracker (EVM)