Rework: what it means
By Soumen Sarkar · October 2026
Rework is work done again because it was built on something wrong: a mistaken assumption, a clashing decision, or a plan that changed without anyone hearing.
Rework is the cost of finding out late. It counts the changes that have to be redone because what they relied on turned out to be different. It is one of the measures a team at agent pace watches, with waiting time and pick-up time.
Its usual sources:
- A wrong assumption found in review or in production instead of in the session.
- Two decisions that clash, each followed by different agents in the same area.
- Building around work in progress instead of on its plan, then merging two versions of the same thing.
- A plan that changed when the work landed, without the work built on it being told.
For example, two agents each add a "discount" field to orders on the same morning, one as a percentage and one as an amount in cents. Nobody notices until both are merged. Undoing one takes an afternoon. Caught when the second decision was recorded, it would have taken a minute.
Rework can't be driven to zero, and it shouldn't be: fixing forward means some fixes happen after the fact. The goal is to catch mistakes while they're small.
Campfyrr doesn't measure rework in hours. Its "What Campfyrr caught for your team this week" card on Activity counts the early catches that prevent it: clashes caught and wrong assumptions caught.
The principle behind this: Fix forward: We don't guard the gate. We correct the course.
Related: Correction · Landed · Waiting time
Questions that use it
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).