How to Ask a Coworker to Redo Work Without Friction

A colleague hands you work that is not right, and you need it done again. This is one of the most quietly loaded messages at work, because you are asking for extra effort on something they thought was finished, and how you ask determines whether they fix it willingly or get defensive and slow. Handle it badly and you get a grudging redo plus a colder working relationship. Handle it well and you get better work and a person who is easier to collaborate with next time.

The instinct under time pressure is either to soften it into vagueness (“maybe just a few tweaks?”) that does not communicate what is actually wrong, or to sharpen it into a critique of them rather than the work. Both make the redo harder. The better path is specific about the work and neutral about the person.

Separate The Work From The Worker

The single most important move is to talk about what the output needs, not about what the colleague did wrong. “This needs X” is a fixable instruction. “You forgot X” is an accusation that invites defense. Same fact, completely different reception.

Before:

This isn’t what I asked for at all. You missed most of the requirements and I need you to do it over.

After:

Thanks for this. A couple of things need to change before it is ready: the report needs the Q3 figures included, and the summary should lead with the recommendation rather than the background. Can you turn those around by Thursday?

The second version names exactly what needs to change and gives a clear deadline, without a word about the colleague’s competence. The redo is now a task with a spec, not a verdict on them. This is the reverse of a passive-aggressive email: the frustration is removed and only the actionable content remains.

Be Specific Enough That The Redo Is Right

A vague redo request produces a second wrong version, which is worse than the first because now everyone is frustrated. If the work missed the mark, say precisely how, so the next attempt hits it. “Make it better” is not instructions; “add the missing section, cut the last two paragraphs, and match the client’s formal tone” is.

Specificity is also a kindness. It tells the colleague you have actually read their work and thought about the fix, rather than tossing it back with a shrug. And it prevents the demoralizing loop of guessing, redoing, and guessing again. Specific, plain instructions are what make the redo land, which is the core idea behind the plain language guidelines.

Acknowledge The Effort, Briefly

A short genuine acknowledgment of the work already done (“thanks for pulling this together”) lowers the defensiveness before the ask. Not fake praise, which people see through, but a real recognition that they put in effort. Then move to the specific changes. If the work was seriously off and it keeps happening, that is a coaching conversation, not a redo email, and it belongs closer to an escalation raised without blame or a direct one-on-one.

A Wrivio Context for a redo request could say:

Rewrite this into a clear, neutral request to redo a piece of work. Keep every specific requirement and deadline exactly as written. Describe what the work needs, not what the person did wrong, list the exact changes, and include one brief genuine acknowledgment of the effort. Remove any language that criticizes the person rather than the output.

Press Ctrl+Shift+Space, paste your frustrated draft, and check the diff. Confirm the specific changes and deadline stayed intact and that it converted any “you failed to” into “this needs.”

Own Your Part If The Brief Was Unclear

Sometimes the work came back wrong because the original ask was vague, and pretending otherwise poisons the redo. If your brief was ambiguous, say so (“this is partly on me, I did not make the format clear”), which is the same honesty as correcting your own mistake. Owning your share makes the redo feel shared rather than punitive, and it makes the colleague far more willing to fix it.

Common Questions

How do I ask someone to redo work without offending them?

Talk about what the output needs, not what the person did wrong. “This needs the Q3 figures” is a fixable instruction; “you forgot the figures” is an accusation. List the exact changes, give a deadline, and add a brief genuine acknowledgment of the effort already made.

How specific should the redo request be?

Specific enough that the next version is right. Name exactly what to add, cut, or change, because a vague “make it better” produces another wrong draft and a frustrating loop. Detailed instructions also signal that you actually read their work rather than dismissing it.

Should I acknowledge the work they already did?

Yes, briefly and genuinely. A real recognition of the effort lowers defensiveness before you ask for changes. Avoid hollow praise, which people detect, but do not skip straight to criticism, which makes the redo feel like a rebuke.

What if the work is wrong because my instructions were unclear?

Say so. Owning that your brief was ambiguous makes the redo feel shared rather than punitive and makes the colleague much more willing to fix it. Pretending the fault is entirely theirs when it is not damages trust and the next round of work.

When is a redo request the wrong tool?

When the same problems recur repeatedly. A one-off redo is a normal task; a pattern of off-target work is a coaching conversation, not an email. Persistent issues belong in a direct one-on-one about expectations, not another round of specific change requests.

Download Wrivio for Windows to strip the frustration out of a redo request and keep just the clear, specific asks.