Rework and work quality  ·  4 min read

Ask three questions. Could a stranger start the task from the brief alone? Were all the facts attached? Did the person check the work before handing it in? If any answer is no, it is not a skills problem yet. Fix that first.

Five causes of rework, counted over one week by a six-person teamWhere 14 pieces of returned work came from (one team, one week)Unclear request6Not checked before handoff4Missing fact3Request changed1Skill gap0Causes 1 and 3 are usually 70 to 80% of the pile, and both are fixed before the work starts, not after.
One team counted its returned work for a week. Most of it came from the request, not the person.
1Rework and work quality

Why this matters

When work comes back wrong twice, it is tempting to think: this person is not good at this. Sometimes that is true. More often, the person was set up to miss. The request was thin. A fact was missing. Nobody expected a check.

Getting this wrong is expensive in both directions. Call it a skills problem when it is a brief problem, and you send someone to training who did not need it, while the rework continues. Call it a brief problem when it is a skills problem, and you keep rewriting briefs for someone who needs coaching.

2Rework and work quality

The three-question test

Take the last piece of work that came back. Answer honestly.

1. Could a stranger start this task from the brief alone?

Read the request as if you had never heard of the project. Do you know what should exist when it is done? Who it is for? What it must include? What it must not do? When it is due?

If you had to fill in gaps from your own head, the person doing the work had to fill them too. They filled them differently. That is a brief problem.

Paste the request into the task brief checker if you want a second opinion.

2. Were all the facts in one place?

Did the person have the numbers, the dates, the files, the examples? Or were some in an old email, some in a chat, and one in your head?

If the fix you asked for was "use the new price" or "add the start date," ask where those facts were. If the answer is "I told them in the meeting," that is a brief problem.

3. Did the person check the work before handing it in?

Were the misses small and obvious? A link that did not work. A section the request plainly asked for. Those are signs that nobody ran a check.

That is a habit problem, which is closer to a brief problem than a skills problem. Habits can be built in a week with a pre-send checklist and a tool like Work Check.

3Rework and work quality

When it really is a skills problem

If all three answers are yes, and the work still fell short, then you are looking at a skills gap. Signs:

  • The brief was clear, and the person says they understood it, but the result is off in a way they cannot see.
  • The same kind of mistake shows up across different tasks and different briefs.
  • When you show the gap, it is a surprise to them, not a "oh, right, I forgot."

That is a coaching conversation, not a review note. Pair them with someone. Show examples of what good looks like. Give smaller pieces for a while.

4Rework and work quality

A worked example

Sam's reports came back three times in a month. His manager was about to book a writing course.

She ran the test on the last report.

  • Question 1: The brief said "write up the survey results for leadership." Nothing about length, what decision leadership needed to make, or which results mattered. No.
  • Question 2: The survey data was in a shared folder, but the two follow-up interviews were in the manager's notes. No.
  • Question 3: Sam had sent it at 5:58pm on the due date. Probably not.

Three nos. She rewrote the brief: "A one-page summary for the leadership meeting on the 14th. They need to decide whether to extend the pilot. Lead with the three findings that matter for that decision. Use the survey plus the two interviews, attached." Sam ran the draft through Work Check before sending.

The next report came back once, for one small fix. No course needed.

How M-Tracker helps

Where M-Tracker fits

M-Tracker makes the first two questions easy to answer yes to. The brief, files, and links live with the task. And it makes the third question automatic: when the task is marked done, M-Tracker checks the work against the brief and tells the person what is missing before you see it. If work still comes back after all that, you know you are looking at a real skills gap, and you can coach it with confidence.

Start free

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