Glossary  ·  2 min read

Rework: definition, example and how to measure it

Rework is time spent redoing work that was already marked done. Definition, a worked cost example, the five common causes, and how to measure it on a team.

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.

Rework is doing work again because the first version was not right. It includes fixing mistakes, adding what was missing, and redoing work that misread the request. Measure it as hours spent redoing work ÷ total hours worked.

1Glossary

In plain words

A task is marked done. Then it comes back. The time spent the second time is rework. The person who reviews it spends time too, and the work arrives later than planned.

2Glossary

The five usual causes

  1. The brief was unclear. The person built the wrong thing well.
  2. "Done" was never agreed. The person thought it was finished. The reviewer did not.
  3. Missing information, like a number or a file that came late.
  4. Late feedback. The reviewer saw it at the end, when changes cost the most.
  5. Real mistakes, like wrong figures or broken links.

The first four are process problems, not people problems.

3Glossary

An example

A 10-person team spends 15% of its time on rework. At 40 hours a week and $40 an hour, that is 60 hours a week, or about $2,400 a week. Over a year, more than $120,000 of salary goes to doing things twice.

4Glossary

How to measure it

MeasureHow
Rework shareHours on redone work ÷ total hours
Revision roundsAverage returns per task
Cost of reworkRework hours × loaded hourly cost

If you do not track hours by task, start with revision rounds. Count how many times each task goes back.

How M-Tracker helps

Where M-Tracker fits

M-Tracker times each task and marks when work comes back for changes, so revision time shows up on its own line on each project. Each finished task also gets a first review against its brief, which catches many returns before they happen. No screenshots and no activity tracking.

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

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.

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