Template  ·  2 min read

Weekly status report template

A weekly status report template with risks and asks at the top: at risk, I need, done, next. Copy it, see a filled example, and stop writing reports from memory.

A status report in the order the reader needs: at risk, I need, done, nextAT RISKFAQ page, 3 days behind. If screenshots arrive by Tuesday we hold June3; if not, slips a week.I NEEDOne message from you to product, by Monday.DONECustomer email approved · handout sent · help article updatedNEXTSend email Friday · start FAQ · train supportA busy reader getsthis far.So the two things theymust act on go first.Done and next are proof,not news.

Four boxes, in the order your reader needs them. Risks and asks first, because those are what the reader has to act on. Done and next after, as proof. Forty seconds to read. Two minutes to write.

1Template

When to use it

Every week, same day, same time. For your manager, your team, or a client who wants a weekly picture.

2Template

The template

Copy this
[Project or team] · week of [date] · [your name]AT RISK OR BEHIND- [What]. [How far behind]. [Why, one sentence]. [What you are doing]. [If X by date, then A; if not, then B.](or: Nothing at risk.)I NEED- [One specific thing, from whom, by when](or: Nothing needed from you.)DONE THIS WEEK- [Item, with link]- [Item, with link]NEXT WEEK- [Item]- [Item]

Fill it in with the builder

3Template

A filled example

Copy this
Verification launch · week of June 1 · PriyaAT RISK OR BEHIND- FAQ page. Three days behind. Product's final screenshots are late.  I have asked twice and offered to take placeholder shots.  If they arrive by Tuesday, we hold June 3. If not, the page slips  one week; the rest of the launch does not.I NEED- One message from you to product asking them to prioritize  the screenshots, by Monday.DONE THIS WEEK- Customer email drafted and approved by Dana (link)- Pricing handout sent to sales (link)- Help article updated (link)NEXT WEEK- Send customer email Friday- Start FAQ page once screenshots arrive- Train support on the new step
4Template

Rules that make it work

  • Say "behind" when you are behind. Softening it costs more later.
  • Every risk has a date. "Late" is a feeling. "Three days, slips a week if not fixed by Tuesday" is a plan.
  • One ask, specific. "Please ask product" beats "would appreciate support."
  • Link the done items. A link is proof. A sentence is a claim.
  • If there are no risks and no asks, say so in one line. That is the best report there is.
How M-Tracker helps

Where M-Tracker fits

In M-Tracker, "done this week" comes from the task list, so you only write the risks and the asks. Managers already see tasks, hours, and goal links by person, so the report confirms a picture they can check. Daily accountability reports can go out by email automatically.

Start free

Try M-Tracker free14-day trial. No credit card. No employee surveillance.

A status report in the order the reader needs: at risk, I need, done, nextAT RISKFAQ page, 3 days behind. If screenshots arrive by Tuesday we hold June3; if not, slips a week.I NEEDOne message from you to product, by Monday.DONECustomer email approved · handout sent · help article updatedNEXTSend email Friday · start FAQ · train supportA busy reader getsthis far.So the two things theymust act on go first.Done and next are proof,not news.

Copyright © 2020 – 2026 M-Tracker. All Rights Reserved. Privacy Policy