Weekly Report Example You Can Copy This Week

A weekly report is the fastest way to keep your manager and your team aligned without booking another meeting. If you typed "weekly report example" into a search box, you most likely want something you can paste, fill in, and send today, not a long essay about reporting theory. This page gives you a working template, a fully filled-in real example, and the mistakes that make most weekly reports get skipped.

Before you copy the template below, read how to write a weekly report if you have never built one from scratch. That guide explains why each section exists; this page shows the finished product so you can move fast.

Why a concrete example matters

Most people do not struggle to open a document. They struggle to know what "good" looks like. A blank page invites a task list, a wall of text, or a vague summary nobody reads. An example gives you a shape to follow, so your first draft is already close to right.

Use the example as a mold, not a script. Your numbers, projects, and blockers will differ. The structure should stay the same: done, in progress, blocked, next. When the format is fixed, the only thing left each week is to drop in the facts.

What goes in a weekly report

A good weekly report answers four questions in under two minutes of reading:

1. What did I finish? List shipped work with concrete outcomes, not activity.
2. What is in progress? Show percentage complete and the next milestone date.
3. What is blocked? Name the blocker and the person who can clear it.
4. What is next? Preview the week ahead so nobody is surprised.

Skip the narrative. Your manager does not need to know how the sprint felt. They need status, risk, and the ask. A weekly report is a status instrument, not a journal.

Keep it scannable. Bullets beat paragraphs. Numbers beat adjectives. "Reduced load time from 4.2s to 1.1s" beats "made the site much faster." If a line carries no fact or decision, cut it.

Weekly report template

Copy this block and replace the brackets. It works for engineers, marketers, designers, and operations roles.

# Weekly Report — [Your Name] — Week of [Date]

## Done
- [Project/Task]: [outcome with a number]
- [Project/Task]: [outcome with a number]

## In Progress
- [Project/Task]: [X]% — next milestone [date]
- [Project/Task]: [X]% — waiting on [person/team]

## Blocked
- [Task]: blocked by [reason]. Need [specific action] from [owner] by [date].

## Next Week
- [Top priority 1]
- [Top priority 2]

This template is the companion to our full weekly report template guide. If you report on a whole team rather than yourself, the weekly status report format shows the extra lines you need for a group view.

Real weekly report example

Here is a filled-in report for a product engineer. Notice that every line carries a fact or a decision, and the blocked line names an owner and a date.

# Weekly Report — Dana Lee — Week of Oct 13

## Done
- Checkout redesign: shipped to 100% of users, cart abandonment down 8%.
- API rate limiter: deployed, p99 latency cut from 320ms to 90ms.
- Onboarding survey: 412 responses collected, report shared with growth.

## In Progress
- Search rebuild: 70% — index migration done, query tuning by Oct 17.
- Billing audit: 40% — reconciled 3 of 7 vendors, finance review Oct 16.

## Blocked
- SSO rollout: blocked by missing Okta license. Need procurement approval from Priya by Oct 15.

## Next Week
- Finish search query tuning and launch to 50% traffic.
- Close billing audit and present to leadership.
- Kick off Q4 roadmap draft with product.

That report took about ten minutes to write and gave the manager everything needed to defend the team in the leadership meeting. The blocked line is the most valuable one because it turns a silent risk into a tracked, owned action.

How to adapt the example to your role

• Sales: Replace "Done" with closed deals and pipeline moved. Put the blocked line on a stuck contract with the decision-maker named.
• Support: Report tickets resolved, CSAT, and the one systemic bug eating the queue.
• Design: Report shipped screens, research completed, and handoff status to engineering.
• Founder: Report revenue, key hires, and the single bottleneck holding the company back this week.

The sections never change. Only the content inside them does.

Common mistakes in weekly reports

Writing a task list instead of an outcome list. "Worked on dashboard" says nothing. "Dashboard live, 3 bugs fixed, 2 open" lets someone act. Lead with results, not effort.

Hiding blockers until Friday. A blocker raised on Monday is a problem with a solution. A blocker raised in the report after the deadline is an excuse. Put serious blockers first.

Mixing weekly and monthly detail. A weekly report is a short pulse. Save deep analysis for the monthly report. If your weekly note is longer than one screen, you are writing the wrong document.

No owner on the ask. "Need help with the API" is vague. "Need the staging key from Sam by Tue" gets the key. Every blocked line needs a name and a date.

Forgetting the skip-level reader. Your manager's manager may read this. Write so a smart stranger understands the status in 60 seconds. No inside jokes, no unexplained acronyms.

Sending it late. A Monday report informs the week. A Friday report only records it. Send before the first standup.

Start your report now

Pick this week's three biggest finishes, name one real blocker with an owner, and send the report before your Monday standup. If building it by hand feels slow, open Reportify to generate a clean weekly report from your tasks in a couple of minutes.