Say it is off track in the first line. Then say by how much, why, what you are doing, and what you need. Five lines. People are not angry about delays. They are angry about delays they found out about late.
The report that hides the problem
"Good progress on the FAQ page this week. Content is drafted and we are finalizing a few remaining assets. On track for launch pending final inputs."
Read that again. "Pending final inputs" means the page is blocked. "On track" means it is not. The manager reads it, feels fine, and finds out a week later that the launch slipped.
Nobody lied. But the report was written to sound okay, not to be useful. That is the most common status report mistake, and it is the most expensive.
Why people hide it
Because saying "we are behind" feels like saying "I failed." It is not. Work goes off track for reasons. A report that names the reason early is the most professional thing you can send. A report that hides it is the thing that gets people in trouble.
The five lines
When something is off track, say:
- What is off track. Name the thing.
- By how much. Days, not feelings. "Three days late" or "will slip one week."
- Why. One sentence. Not blame. Cause.
- What you are doing. The action you have already taken.
- What you need. A decision, a person, an approval, or nothing.
Example, rewritten
At risk: FAQ page. It is three days behind. Product has not sent the final screenshots. I have asked twice and offered to take placeholder shots myself. If the screenshots arrive by Tuesday, we hold the June 3 date. If not, the page slips one week. I need: someone to tell product this is blocking the launch.
Six sentences. The manager knows exactly what is happening, what has been tried, what the deadline for a decision is, and what they personally need to do.
Put it at the top
Off-track items go first in the report, not buried under "done this week." If the manager reads only one line, it should be this one. The Status report generator puts risks and asks above everything else for this reason.
Give a date for the decision
"If X by Tuesday, then A. If not, then B." This turns a worry into a plan. It tells the reader when to act and what happens if nobody does. Most delays become crises because nobody knew when the last chance to fix them was.
What not to write
- "Facing some challenges." (Which? How big?)
- "Should be fine." (Based on what?)
- "Waiting on a few things." (Which things, from whom, since when?)
- "On track pending…" (If it is pending something, it is at risk. Say so.)
When it is really bad
Same five lines. More detail on what you are doing and what you need. Add one more: what you would do differently next time, if you already know. Owning the lesson early turns a bad week into trust.
Where M-Tracker fits
In M-Tracker, managers see work as it happens: tasks, time, and what is linked to which goal. A task that has not moved in a week is visible before Friday. Reports to clients and leadership can be built from that real picture, so "on track" means something. People write the risks and the asks. The facts come from the work.
Try M-Tracker free14-day trial. No credit card. No employee surveillance.
Work you can trust, without redoing it.
Your team gets feedback before work reaches you, or your client.
Copyright © 2020 – 2026 M-Tracker. All Rights Reserved. Privacy Policy
Trackbacks/Pingbacks