Your team's rework is almost always born in the request, long before delivery
Rework shows up at delivery, but it's born in a half-written request. See what a request needs to include and copy a ready-made template.

Knowing how to avoid rework starts before delivery, at the moment someone makes a request. The request arrives half-written, without saying what it's for or how it will be used, and the team doing the work fills in the gaps with its own guesses. When the guess misses, the task comes back.
This post shows where rework is born, what a request between teams needs to include and how to have the delivery checked against criteria agreed on before anyone starts.
Where rework really starts
Rework shows up at delivery, but it was almost always planted in the request. The scene is familiar in any company with more than one team.
Sales asks Marketing for "a company presentation for Thursday's meeting". Marketing makes twenty polished company slides.
On Wednesday, the explanation arrives: it was for a hospital, with pricing, in five slides. Everything starts over, and nobody got the execution wrong. The cost doesn't stop at the redone hours either: whatever was in Marketing's queue runs late too.
What's usually missing from an internal request:
- what it's for and who will use it;
- the format and the length;
- who decides whether it's good;
- when the person really needs it;
- what counts as done.
Sales and Marketing are the classic pair for this kind of mismatch, and it usually starts with requests that leave out the context.
Why requests arrive half-written
Whoever asks is in a hurry and knows the context by heart. For them, the obvious doesn't need writing down, and their obvious is rarely the same as the receiver's.
The channel makes it worse. The request goes down the hallway, by email with half the company copied or through the team's group chat, and every channel drops a piece. The person receiving it hardly ever asks, because asking feels like slowing things down. Hallway requests also vanish from the workload of whoever does them, as our post on invisible work shows.
The habit of giving every request an owner gets in the way too. The person assigned soaks up the gaps alone and delivers what they imagined, while the rest of the team never even sees the request. Our post on assigning an owner to every task shows why that leaves everyone less involved.
The definition of done nobody writes
Without a definition of done, each side imagines a different ending, and the request only finishes when both endings match. Until then, it goes back and forth.
Software teams gave this a name. The Scrum Guide calls it the Definition of Done: a formal description of when a delivery meets the agreed quality standard, and whatever doesn't meet it goes back to the queue.
Outside software, the idea fits in one sentence of the request, starting with "it's done when". In the Sales example, it would be something like: "it's done when I can present it in ten minutes to a hospital, with the new price list". For a request from HR to IT, it would be: "it's done when the new hire can log in on day one, with email and access to the team's folders".
How to avoid rework with a complete request
A short request template, the same for every team, solves a good part of the problem before anyone starts. It has six fields:
Request: what you need, in a few words
What it's for:
Who will use it:
Format and length:
Who decides if it's good:
It's done when:
I need it by:Click Copy list, paste into the team list's New item field and fill in the description. Reference files go attached to the request itself, not in a separate email.
The field that matters most is "It's done when". If whoever asks can't write that sentence, the request isn't ready to go out yet.
In Marketing, the request is often a campaign, and a fuller marketing brief template helps. The causes of marketing rework look a lot like those in any other team.
The incomplete request goes back before it becomes rework
With Connected lists, the request goes through triage before execution, and the delivery comes back to whoever asked to be checked. The path has three stops:
- Incoming requests. Someone on the team checks whether the request is complete. Missing the "it's done when"? They write down what's missing and talk to whoever asked, before anyone starts.
- In progress. Whoever will do it gives it a Pull, and everyone sees who has the request. A request with a cost can go through an approval first, with a check from whoever decides.
- Delivery to requester. Whoever asked checks it against the definition of done. It matches? They complete it. It doesn't? The request goes back to execution, with what's missing written down.
Each list gives the request a deadline when it arrives, and anything late turns red. The interdepartmental request workflow template has this path ready to import, and the Experto for departments page shows the other use cases.
So who answers for the request? Whoever picked it up. The list shows who has each request, and whoever asked follows along without asking in the group chat.
Requests between teams also show up when someone new arrives: HR needs the laptop, the access and the badge. The employee onboarding checklist already has those requests written out in full.
Frequently asked questions
What causes rework on a team?
Incomplete requests, a definition of done nobody agreed on and deliveries that aren't checked by whoever asked. All three share the same root: what each side expected wasn't written down.
What is a definition of done?
It's the sentence that says when the request is finished, written before anyone starts. It becomes the yardstick for checking the delivery and shortens the conversation about changes.
How do you avoid rework in requests between teams?
Use the same request template across every team, triage before execution and let the delivery go back to whoever asked to check it. That way the gap shows up at the start, when it costs one question.
Want to try it on your next request? Create your free account, free forever for up to 2 members, paste the template and see how to avoid rework in practice without chasing anyone.


