Status and reporting  ·  4 min read

Give people a four-box format: done, next, at risk, I need. Set one time it is due. Make the "done" box come from the task list, not from memory. Then read risks and asks first. You stop chasing because there is nothing to chase.

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.
Risks and asks first. Forty seconds to read, one clear thing to do.
1Status and reporting

The Friday message

"Hey, any updates on the launch?" You send it to six people. Three reply by Monday. One sends a paragraph you cannot use. One sends "all good." One forgets. You piece together a picture for your own manager from fragments.

You are not managing. You are collecting. And the people on the other end are not reporting. They are being interrupted.

2Status and reporting

Why updates are bad

Not because people are lazy. Because nobody told them what a good update looks like, and because writing one from memory on Friday is hard. What did I do this week? Everything blurs. So people write "worked on the launch" and move on.

Fix the format, fix the timing, and fix where the information comes from.

3Status and reporting

The four boxes

  1. Done this week. One line per item, with a link if there is one.
  2. Next week. One line per item.
  3. At risk or behind. What, why, and what they are doing about it. With a date.
  4. I need. A decision, an approval, a person, or nothing.

That is the whole format. The weekly status report builder turns the four boxes into a clean report to paste anywhere, with risks and asks at the top where you will see them.

4Status and reporting

One time, every week

Thursday at 4pm. Or Friday at 10am. Pick one and keep it. People plan around a fixed time. They cannot plan around "when you get a chance."

5Status and reporting

Read it in the right order

Risks first. Asks second. Then done and next. The first two tell you whether you need to act. The last two are proof.

If someone's risks box says "none" and their ask box says "nothing," that is a great update. It takes ten seconds to read. Say thank you.

6Status and reporting

Example update

Verification launch, week of June 1, Priya

Needs your help: Please ask product for the final screenshots. They block the FAQ page.

At risk: FAQ page. Screenshots are three days late. If they arrive by Tuesday, we hold the date. If not, it slips a week.

Done: Customer email drafted and approved. Pricing handout sent to sales. Help article updated.

Next: Send customer email Friday. Start FAQ page. Train support.

Forty seconds to read. One thing for the manager to do. Nothing to chase.

7Status and reporting

What to do when someone does not send one

Ask once, the same day. If it keeps happening, it is a conversation about the habit, not about this week. Most people stop missing it once they see that a good update takes two minutes and gets them what they need.

8Status and reporting

Where M-Tracker fits

In M-Tracker, the done list is already there because the tasks are. Each person's finished work, time, and goal links are visible to their manager without a Friday message. Daily accountability reports can go out by email on their own. People add the risks and the asks. The system fills in the rest. And when the work was marked done, it was already checked against its brief, so "done" means done.

Start free

How M-Tracker helps

Make the done box come from the work

This is the step that ends the chasing. If tasks live in a tool, the done list already exists. Nobody has to remember it. The person spends two minutes on risks and asks, and the done box fills itself.

Without this, the update depends on memory, and memory on Friday is bad.

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

How a task moves through M-Tracker: brief, work, review, improve, then the manager1BriefResult, audience,must include, due.Files and linksattached.2WorkThe person does itand attaches whatthey made.3ReviewM-Tracker comparesthe work with thebrief. One plainparagraph.4ImproveThey fix what ismissing while it isfresh.5ManagerSees work thatalready passed itsown test.No screenshots. No scores. The person sees the review first.

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