Work comes back for one of five reasons. The request was unclear. A fact was missing. The person did not check it before handing it in. The request changed. Or the person could not do it yet. Each one has a different fix. Find your cause before you fix anything.
The Friday that looks the same every week
You asked for a report on Monday. It came back Thursday. You opened it and your stomach dropped. It is not wrong, exactly. It is just not what you meant. So you write a note. The person fixes it Friday. You review it again Monday. One task took a week and two reviews.
Now multiply that by every task on your team. This is where the week goes.
The first thing most managers do is review harder. They read every line. That makes them slower, and it makes them the bottleneck. The better move is to find out why the work keeps coming back. There are only five reasons, and you can tell them apart.
Cause 1: The request was unclear
This is the biggest one. The person did exactly what they understood. They just understood less than you thought.
How to spot it: The work is good, but it is good at the wrong thing. Or the person asks "wait, who is this for?" after it is done.
The fix: Write the request with five parts. What should exist. Who it is for. What it must include. What it must not do. When it is due and who approves it. Our task brief checker shows you which part is missing.
Cause 2: A fact was missing
The person needed a number, a date, a name, or a file. They did not have it. So they guessed, or left a hole.
How to spot it: The fix is always a detail. "Add the start date." "Use the new price."
The fix: Attach the facts to the task. If the fact does not exist yet, say so in the brief, and say who will get it.
Cause 3: Nobody checked it before handing it in
The work was rushed. The person knew it was not quite ready. They sent it anyway, hoping you would catch what they missed. You did. Now it is your job.
How to spot it: Small, obvious misses. A broken link. A missing section that the request clearly asked for.
The fix: A check before the handoff, not after. A short pre-send checklist works. So does pasting the request and the work into Work Check and reading the result.
Cause 4: The request changed
You learned something new halfway through. The client changed their mind. Nobody told the person doing the work, or they were told in a hallway and forgot.
How to spot it: The work matches the old request perfectly.
The fix: When a request changes, change the brief, in writing, in the place the person works. Then tell them. A changed brief with no message is a trap.
Cause 5: The person could not do it yet
Sometimes the skill is not there yet. A new hire. A new kind of task. This is the least common cause, but it is the one managers reach for first.
How to spot it: The brief was clear, the facts were there, the person checked, and it still fell short. Only then is it a skill gap.
The fix: Teach, pair, or reassign. But check the other four causes first. Blaming skill when the real problem was the brief is unfair, and it does not stop the rework.
Find your cause in one week
Do this for five working days.
- Every time you send work back, write one line: what was wrong, and which of the five causes it was.
- On Friday, count.
- Fix the biggest cause first. Ignore the others for now.
Most teams find that causes 1 and 3 are 80% of the pile. Both can be fixed without anyone working harder.
A worked example
A six-person marketing team counted for one week. Fourteen things came back.
- Unclear request: 6
- Missing fact: 3
- Not checked: 4
- Request changed: 1
- Skill: 0
They did two things. Every task now starts with a five-line brief. And every person runs their work through a check before marking it done. Three weeks later, four things came back, not fourteen.
Where M-Tracker fits
M-Tracker is built around causes 1 and 3. Every task holds its brief, its files, and its links, so the request is clear and the facts are attached. When someone marks the task done, M-Tracker reads the work against that brief and tells them what is missing, in one plain paragraph, before the manager sees it. The person fixes it while it is fresh. The manager gets work that is right more often, and spends the saved time coaching instead of catching.
No screenshots. No tracking. Just the request, the work, and the gap between them.
Try M-Tracker free14-day trial. No credit card. No employee surveillance.
Questions people ask
Isn't some rework normal?
Yes. Creative work has rounds. The problem is rework that comes from a cause you could have removed for free.
What if the person gets defensive when I send work back?
Send back the gap, not a judgment. "The start date is missing" is easy to hear. "This is sloppy" is not. Our Performance review generator helps.
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