Weekly Status Report Template: 3 Copy-Paste Formats With Examples

A good weekly status report fits on one screen and answers five questions: what you shipped, what is in progress, what is blocked, what comes next week and what you need from the reader. Below are three templates you can paste straight into an email, Slack post or shared doc: a 5-minute weekly update for an individual, a project status report for stakeholders with RAG (red, amber, green) status, and a team roll-up for managers. Each comes with a worked example that sets a useful version next to a vague one.

A weekly status report is a short written summary, sent on a fixed day, of what changed in your work since the last one and what the reader needs to know or decide. It is not a timesheet and not a list of everything you touched. Its job is to let someone who was not in the room understand where things stand in under two minutes, without asking for a meeting.

The templates are written for two readers. If you report to a manager, especially from home or on a hybrid schedule, the weekly update is how your work gets seen. If you manage people, it is how you get useful information without scheduling another status meeting.

Which weekly status report template do you need?

Pick the template by who reads it. The individual update goes to your manager. The project report goes to people who depend on a project but do not work on it every day. The roll-up is what a manager sends upward after reading the team's individual updates.

All three share the same rule: the first line tells the reader whether they need to do anything.

Template 1: The 5-minute weekly update for your manager

Most people need this one. It takes about five minutes to write if you keep a running list of what you finished during the week, and it gives your manager everything they would otherwise ask for in a one-on-one.

Copy the weekly update template

Subject: Weekly update, [your name], week of [date]

Headline: [One sentence: the most important thing that changed this week, or "On track, nothing needed from you."]

Shipped

• [Outcome you finished, with who it helps] ([link to the PR, doc, ticket or result])
• [Second outcome] ([link])

In progress

• [Piece of work], [how far along: e.g. "draft done, review Tuesday"], expected [date]

Blocked

• [What is stuck], waiting on [person or team] since [date]. [What would unblock it.]

Next week

• [Top priority for next week]
• [Second priority]

Asks

• [Decision, feedback or help you need from the reader], by [date]

How to fill in each section

Headline. Write it last. If your manager reads only one line, this is it. When nothing needs their attention, say so; that sentence is useful too.

Shipped. List finished work only, phrased as a result and linked to evidence. Three items is plenty. If you shipped nothing this week, say what you learned or decided instead (more on that below).

In progress. Give each item a state and a date. "Still working on the migration" is a status; "migration 70% done, cutover planned for Thursday" is a forecast your manager can plan around.

Blocked. Name what is stuck, who it is waiting on and since when. A blocker without an owner is a complaint. A blocker with an owner and a date is something your manager can fix.

Next week. Two or three priorities, in order. This is what next week's update will be measured against, so keep it honest.

Asks. The section people skip and should not. If you need a decision, write the options and the date you need it by. If you need nothing, delete the section rather than writing "none."

Worked example: vague update versus useful update

The same week, written two ways. The vague version is not wrong; it just gives the reader nothing to act on.

The numbers in the example are illustrative. In your own update, use the numbers you actually have, and link to where they come from.

Template 2: Project status report for stakeholders

A project status report answers a different question from a personal update: will this project land when and how we said, and what do you need to decide? Stakeholders read many of these, so the format puts the verdict first and the detail after it.

What RAG status means

RAG stands for red, amber and green; some US teams say red, yellow, green (RYG), and the meaning is the same. Agree on what each color means before the first report, or every project will be green until the week it turns red.

Report one overall status, and change it the week the facts change. Amber is a useful color: an early amber is easier to fix than a late red.

Copy the project status report template

Project: [Project name], status report for [date range]

Owner: [Name], [role]

Overall status: [Green / Amber / Red], [one sentence on why, e.g. "Amber: payment provider sandbox is two weeks late, launch date holds if access arrives by the 10th."]

Summary: [Two or three sentences: where the project stands against the plan, and what changed since the last report.]

Milestones

Completed this period

• [Outcome, with link to evidence]

Risks and issues

• [Risk], likelihood [low / medium / high], impact [what slips and by how much]. Mitigation: [what the team is doing]. Owner: [name].

Decisions needed

• [Decision], options: [A] or [B]. Recommendation: [A, because...]. Needed from [name] by [date].

Next period

• [Top two or three deliverables, with dates]

What a good project report looks like

A useful overall status line reads like this: "Amber: the data migration test found duplicate customer records. We can launch on the 18th with a manual clean-up, or on the 25th with an automated one. Decision needed from Sam by Friday." It names the problem, the options, the trade-off, the person and the date.

A vague one reads: "Amber: some data issues, team is investigating." The reader cannot tell whether to worry, wait or act.

Two habits keep project reports honest. Keep the milestone table stable from week to week, so readers can see dates move instead of quietly disappearing. And move a risk to the decisions section as soon as the team cannot resolve it alone.

Template 3: Team roll-up for managers

A team roll-up is what a manager sends upward after reading the team's weekly updates. It is not the individual updates pasted together. Your own manager wants three things from it: are we on track, where do I need to help, and who did good work.

Copy the team roll-up template

Subject: [Team name] weekly roll-up, week of [date]

Headline

• [Most important result or change this week]
• [Biggest risk, or "No new risks."]
• [What you need from the reader, or "Nothing needed."]

Results this week

• [Outcome], [who did it, by name] ([link])
• [Outcome], [name] ([link])

At risk

• [Goal or project], [why], [what the team is doing], [date of next check]

Decisions and asks upward

• [Decision or help you need], options and recommendation, by [date]

People

• [Recognition: a specific thing someone did and why it mattered]
• [Capacity: absences, hiring, anyone overloaded]

Next week's team priorities

1. [Priority one]
2. [Priority two]
3. [Priority three]

Worked example: vague roll-up versus useful roll-up

The same team week, written two ways. The names and numbers are illustrative.

How to write the roll-up in twenty minutes

Read the team's updates first, then write the headline before anything else. Group results by goal rather than by person, but name the people who did the work. A roll-up that says "the team shipped X" hides exactly the information that remote and hybrid staff most need passed upward. Copy blockers only if they need someone above you; resolve the rest yourself and leave them out.

If the team writes individual updates with Template 1, most of the roll-up writes itself: their "Shipped" sections become your results, their "Blocked" sections become your risks, and their "Asks" tell you what to escalate.

How do you write outcomes instead of activity?

An outcome says what changed and for whom. Activity says what you spent time on. Readers skim activity because every week looks the same; they remember outcomes because each one is different.

Use this pattern for each line: verb + what changed + for whom + evidence.

Three rules make the pattern work:

• Name the evidence. A link to the doc, PR, dashboard or ticket lets the reader check without asking. It also turns your updates into a dated record you can use at review time.
• Give unfinished work a state, not an effort. "Draft 1 done" is checkable; "worked hard on the draft" is not.
• When nothing shipped, report what you learned or decided. Research weeks, incident weeks and planning weeks still produce outcomes: a ruled-out option, a decision, a finding. "Tested two approaches to the import; the streaming one handles files over 1 GB, so we are going with it" is a strong update.

Writing it down also helps the writer. Teresa Amabile's diary study of 238 knowledge workers at seven companies, about 12,000 daily diary entries, found that making progress was the most prominent event on people's best workdays (Harvard Business School Working Knowledge, September 2011). A weekly list of finished outcomes makes that progress visible to you as well as your manager.

How often should you send a status report, and to whom?

Send the individual update weekly, on the same day, to your direct manager, and post it where your team can see it if your team works that way. Weekly is long enough for real outcomes and short enough that nothing goes stale. Google's internal Snippets, the best-known example of the practice, asked people every Monday what they did last week and planned to do next; we covered how Snippets worked and why they outlasted standups.

Friday versus Monday is a matter of taste. Friday updates capture the week while it is fresh; Monday updates double as a plan. Pick one and keep it, because a predictable day matters more than the day itself.

If you are on a remote trial, send updates more often at the start. The case you made when you asked, covered in our guide on how to convince your boss to let you work remotely, is won or lost on whether your manager can see the work during the trial. Weekly is enough once the arrangement is settled.

Keep every update in one running document or thread, newest first. Over a quarter it becomes a searchable record of what you delivered, which is exactly what you need for a performance review or a promotion case.

Why written status updates matter more when you work remotely

When you work from home, your manager cannot see you working, and what they cannot see they may undervalue. In SHRM's July 2021 survey of 817 US supervisors of remote workers, 67% said they regard remote staff as more easily replaceable than onsite workers, and 42% said they sometimes forget about remote workers when assigning tasks (SHRM, July 2021). Trust is not settled either: in May 2025, only 54% of managers of remote workers strongly agreed they trust their team to be productive when working remotely (Gallup, 2025).

A weekly update is the cheapest answer to both problems. It does not depend on who sits near the manager, and it gives a remote manager the evidence that presence used to supply. Our article on proximity bias and remote visibility covers the research behind that gap in more detail.

For managers, the same logic runs the other way. Asking for written updates gives remote, hybrid and office staff the same channel to show their work, which is fairer than judging by who you happened to see. It also makes async work hold together: when progress is visible in writing, people stop needing a meeting to find out what everyone else is doing.

How a weekly status report replaces status meetings

Status meetings use everyone's time to transfer information that reads faster than it is spoken. In Atlassian's survey of 5,000 knowledge workers, 70% said meetings are ineffective for status updates, and 78% said they are expected to attend so many meetings that it is hard to get work done (Atlassian, March 2024, vendor research). Microsoft's 2025 telemetry from Microsoft 365 found the top 20% of users interrupted by a meeting, email or chat roughly every two minutes during core hours, and 57% of meetings held as ad hoc calls with no calendar invite (Microsoft Work Trend Index, June 2025, vendor research).

Companies that cut meetings report benefits, though the evidence is self-reported. In a study of 76 companies with over 1,000 employees each that introduced one to five meeting-free days a week, employees reported less stress and more autonomy, with the authors reporting the best results at three meeting-free days (MIT Sloan Management Review, January 2022). Shopify removed every recurring meeting with three or more people from its calendars in January 2023 and asked staff to wait two weeks before adding any back (NPR via OPB, February 2023).

A four-week switch from status meeting to written updates

You do not need a company-wide purge to get most of the benefit. A four-week switch from a status meeting to written updates looks like this:

1. Weeks 1 and 2: run both. Everyone sends Template 1 the day before the meeting. In the meeting, skip the round of updates and discuss only the "Blocked" and "Asks" sections.
2. Week 3: shorten the meeting. Cut it to 15 minutes, for blockers and decisions only. Anyone with nothing in those sections can skip it.
3. Week 4: replace it. Cancel the recurring meeting. Keep a short slot that is booked only when someone flags a decision that needs a conversation.
4. Every week after: reply to the updates. A one-line reply to each update ("thanks, unblocked Priya on the tax question") tells people the updates are read. Written updates die when nobody responds to them.

Keep the meetings that do work that writing cannot: one-on-ones, decisions with real disagreement, planning and anything about how people are doing. The aim is to move status out of meetings, not to remove conversation.

Common weekly status report mistakes

• Listing every task. A report with fifteen items hides the three that matter. Cut to the outcomes your reader would ask about.
• Hiding bad news in the middle. If something slipped, say it in the headline. Bad news is easier to act on the week it happens than a month later.
• Green until it is red. A project that flips from green to red overnight has often been amber for weeks before anyone said so. Change the color when the facts change.
• No dates on blockers and asks. "Waiting on legal" can sit for a month. "Waiting on legal since the 14th, need an answer by the 28th" gets answered.
• Writing it from memory on Friday at 5 pm. You will forget half the week and over-report the last day. Keep a running "done" list as you go.
• Sending it to the wrong reader. Your manager wants your asks; a sponsor wants the project verdict; your team wants what affects them. Do not send one report to all three.

Making the weekly update take five minutes

The hard part of a weekly status report is not the template. It is remembering on Friday what you did on Tuesday. Three habits fix most of it: keep a running list of finished work during the week, write the update at the same time each week, and reuse last week's "Next week" section as this week's starting checklist.

Tools can do some of the remembering. Disclosure: DoneThat, which publishes this blog, makes an automatic work tracker. It reconstructs your workday from desktop activity and drafts summaries from it, so the weekly update starts from what you actually worked on rather than what you remember; you choose who sees each summary, and you edit before sending. A plain running doc does the same job if you keep it up.

Frequently Asked Questions

What should a weekly status report include?

A weekly status report should include what you finished (as outcomes with evidence), what is in progress with expected dates, what is blocked and who it is waiting on, your priorities for next week, and any decisions or help you need from the reader. Put a one-sentence headline at the top so a reader who stops after one line still knows whether to act.

How long should a weekly status report be?

An individual weekly update should be about 150 to 250 words, short enough to read in under two minutes. A project status report can run to one screen plus a milestone table. If yours is longer, cut activity and keep outcomes, blockers and decisions.

What is the difference between a status report and a status update?

The terms overlap. A status update usually means a short, informal note from one person, often weekly, to a manager or team. A status report usually means a more structured document about a project, with RAG status, milestones, risks and decisions, sent to stakeholders. Templates 1 and 2 above cover each.

How do I write a weekly report to my manager?

Use the five-section format: shipped, in progress, blocked, next week, asks. Write each finished item as an outcome with a link, give unfinished work a state and a date, and put anything you need from your manager in the asks section with a deadline. Send it on the same day each week, in the channel your manager already reads.

What does RAG status mean in a status report?

RAG stands for red, amber and green. Green means the project is on track; amber means it is at risk but the team has a plan; red means it will miss a commitment without a decision or outside help. Agree on the definitions with stakeholders before the first report, and give one sentence explaining the color every time.

Should I still send a status report if nothing changed?

Yes, but keep it to two or three lines: what you worked on, why nothing shipped and what you expect next week. A missing update reads as silence, which on a remote team is often read as a problem. A short "no change, on track for the 15th" takes a minute and answers the question before anyone asks it.

Pick one template and start this week

Choose the template that matches your reader, paste it into wherever your updates live and send the first one this week. The format matters less than the habit: the same day each week, outcomes instead of activity, blockers with owners and asks with dates. After a month, you will have a written record of your work, and your manager will have fewer reasons to schedule a meeting to ask for it.

For more on working visibly from home, browse the remote work articles.

Sources

• Amabile, T. and Kramer, S., via Nobel, C. (September 2011). How Small Wins Unleash Creativity. Harvard Business School Working Knowledge. Diary study of 238 employees at seven companies, about 12,000 diary entries.
• Atlassian (March 2024). Workplace Woes: Meetings. Vendor survey of 5,000 knowledge workers across four continents.
• Gallup (2025). Hybrid Work in Retreat? Barely. Gallup Panel web survey of 17,660 US adults, May 7 to 16, 2025.
• Hsu, A., NPR, republished by OPB (February 15, 2023). Shopify deleted 322,000 hours of meetings. Should the rest of us be jealous?
• Laker, B., Pereira, V., Budhwar, P. and Malik, A. (January 18, 2022). The Surprising Impact of Meeting-Free Days. MIT Sloan Management Review. Survey of 76 companies with more than 1,000 employees each.
• Microsoft (June 17, 2025). Breaking down the infinite workday. Work Trend Index special report; aggregated Microsoft 365 telemetry to February 2025, excluding education and EU tenants.
• SHRM (July 26, 2021). SHRM Research Reveals Negative Perceptions of Remote Work. Online survey of 817 US supervisors of remote workers, July 2021.

Written by Don, DoneThat's AI coach (LinkedIn) - so this article is AI-written. Every statistic is cited next to the claim and linked in the Sources list, and vendor research is labeled as such. Reviewed by Christoph Hartmann, founder of DoneThat. More about DoneThat; corrections and questions go to support.