Templates

Weekly Status Report Template

A weekly status report takes 15 minutes to write. It takes your client 2 minutes to read.

For that 2-minute read, your client stays calm. They trust you. They're not calling asking "where are we?"

It's the best ROI activity in a project.

The Template

Send every Friday (or your project cadence).


PROJECT STATUS - [PROJECT NAME]

Week of [Date]

Overall status: ON TRACK (or AT RISK, or BLOCKED)

Completed This Week

  • Completed homepage design
  • Client feedback incorporated into product pages
  • Mobile optimization finished for first 5 pages
  • Got client approval on navigation structure

Keep it bulleted. Keep it short. 3-5 items.

In Progress

  • Building checkout page design
  • Creating design specs documentation
  • Designing mobile templates

Next Week

  • Client review of checkout page
  • Begin revision round based on feedback
  • Finalize design documentation

Blockers

None at this time.

(If there are blockers: What's blocking? When will it be resolved? What do you need from the client?)

Client Action Items

  • Provide copy for the pricing page (due: [Date])
  • Approve navigation structure (due: [Date])

Timeline Status

Original timeline: [Delivery date]

Current timeline: [Delivery date - same or updated]

On track? ✓

Key Metrics (if applicable)

  • Design approval rate: 90% (1 revision round needed)
  • Client response time: 24 hours (great!)
  • Scope changes: 0

Confidence Level

9/10 - We're on track. No major risks. Client is engaged and responsive.

(1-10 scale. 10 = will definitely ship on time and on budget. 1 = project is in trouble.)

Next Check-In

Next status: [Date]

Next meeting: [Date]


Customizations for Different Work

Design project:

  • Completed this week: Design work done
  • In progress: Ongoing design work
  • Next week: Design work planned
  • Add: Approval status, revision rounds needed

Development project:

  • Completed this week: Features built, bugs fixed
  • In progress: Current features
  • Next week: Next features
  • Add: Test coverage, deployment status

Strategy/Consulting:

  • Completed this week: Research done, analysis completed
  • In progress: Ongoing work
  • Next week: Next activities
  • Add: Key findings, recommendations status

Marketing project:

  • Completed this week: Campaigns launched, content created
  • In progress: Ongoing campaigns
  • Next week: Next activities
  • Add: Performance metrics, spending status

Variations

Short version (for smaller projects):

Completed this week: [3-5 items]

In progress: [Current work]

Next week: [Next work]

Blockers: [None or what's blocking]

Timeline: On track? ✓

That's it. Sent Friday afternoon. Client reads it Monday. Everyone's aligned.

Detailed version (for complex projects):

Add sections for:

  • Risk assessment
  • Budget status
  • Resource needs
  • Decisions needed from client
  • Schedule risks
  • Quality metrics

Timing

Send every Friday afternoon (2-3 PM).

This gives the client time to read before weekend. If there's a blocker, they reach out Friday or Monday.

Never send a status in a crisis. If you're blocked or in trouble, call the client. Don't email it.

Email is for "on track" updates. Calls are for problems.

The Red Flags in a Status Report

  • Status changes every week (sign of poor planning)
  • Lots of blockers (sign of poor process)
  • Timeline keeps slipping (sign of under-estimation)
  • Vague updates ("working on stuff") - be specific
  • No clarity on next steps

If you see these, address the underlying issue, not just the report.

Why This Works

Transparency: Client sees exactly what's happening.

Reduces calls: Client knows what's going on. They don't need to call asking.

Builds trust: Consistent communication builds confidence.

Paper trail: If there's a dispute later, you have documentation.

Accountability: You're committing to completion dates in writing.

Who Reads This

  • Client project manager
  • Client decision-maker (if involved)
  • Your team (optional - helps alignment)
  • Your account manager (if applicable)

Send to all stakeholders.

The Format

Email subject: "Project Status - [Project name] - [Date]"

Send as: Text in email (not attachment). Attachments get lost.

Or send as: Link to Google Doc (easier to update if needed).

Common Mistakes

Too detailed. Client doesn't need to know every task. 5-10 bullets max.

Too vague. "Making progress" isn't a status. "Completed homepage design" is.

No timeline section. Always mention the delivery date and if you're on track.

Blaming the client. Never say "client is slow to respond." Say "waiting on client feedback due [date]."

Making excuses. Focus on solutions, not problems.

FAQ

Should I send it every week even if nothing changed?

Yes. Status report shows continuity. If you're on track for two weeks in a row, client is even more confident.

What if the project is blocked?

Send the status. Explain the blocker. Explain what you're doing to unblock.

Should I email or post in Slack?

Email is formal and creates a record. Slack is fast.

Email for client status. Slack for internal updates.

What if there's bad news?

Include it in the status. Explain what happened.

Explain how you're fixing it. Then call the client.

Don't hide bad news in a status report. Get on the phone.

Ready to see all your tasks in one place?

Sync all your project management tools.

Start Free Trial