Wrivio
Get Wrivio
5 min readBy Wrivio Team

How to Write a Message Handing Back Work That Is Not Ready

A colleague or report handed you something that is not ready. The draft is thin, the analysis has gaps, the deliverable misses what you asked for. You have to send it back, and how you do that determines whether you get a better version next or a resentful one, plus a reputation as impossible to satisfy. Hand it back carelessly and you get defensiveness, a grudging patch, and a person who now dreads sending you anything.

The message that works is specific about what is missing, clear that it is going back, and careful to separate the work from the worth of the person who did it.

Be Specific About What “Not Ready” Means

“This isn’t quite there yet” is useless and slightly cruel, because it tells the person they failed without telling them how to succeed. The entire value of handing work back is the specificity of what needs to change. List the concrete gaps, in priority order, so the next version can actually close them.

Vague dissatisfaction forces guesswork, and guesswork produces a second draft that misses in new ways, which is how rewrite wars start. The specificity is the respect. This is the operational heart of how to give feedback on a colleague’s draft.

Separate The Work From The Person

Keep the message about the deliverable, not about their competence. “The analysis is missing the regional breakdown” is about the work. “You didn’t think this through” is about them. The first gets fixed; the second gets defended.

Before:

This isn’t what I was looking for at all. It feels rushed and incomplete and I expected more detail. Can you take another pass? It needs to be a lot better before we can use it.

After:

Thanks for getting this over. It’s close on structure, but three things need to land before we can send it: the regional breakdown is missing, the Q3 numbers do not match the dashboard, and the recommendation section stops short of an actual recommendation. If you can add those by Thursday, I think it is there. Happy to talk through the recommendation part if it would help.

The second version names three fixable things, keeps a reasonable tone, and offers help on the hardest part. It is a path forward, not a verdict. When the work needs more than a pass, the firmer version is in how to ask a coworker to redo work without friction.

Acknowledge What Works

Before the gaps, note what is actually fine. This is not flattery or a feedback sandwich; it is information. Telling someone the structure is right and the research is solid stops them from rebuilding the parts that already work, which a purely negative message often triggers. Praise the right things specifically and the revision stays targeted.

Make The Standard And The Deadline Clear

End with exactly what “ready” looks like and by when. Ambiguity about the bar is what produces endless rounds. If there are three must-fix items and two nice-to-haves, say which are which, so the person does not burn the deadline polishing the optional. For harder cases where the gap is about quality judgment, how to give critical feedback in writing goes deeper.

A Wrivio Context for handing work back could say:

Rewrite this as a constructive message handing back work that is not ready. Name the specific gaps in priority order, note what already works, keep it about the deliverable rather than the person, and state the deadline. Keep every name, figure, and date exactly as written. Do not add blame or vague dissatisfaction, and do not soften the gaps until they are unclear.

Press Ctrl+Shift+Space, paste your draft, and check the diff to confirm the gaps are specific and nothing reads as a personal judgment. The plain language guidelines reinforce that concrete, specific instructions get acted on while vague ones get guessed at.

Common Questions

How do I hand back work that is not good enough?

List the concrete gaps in priority order, note what already works so it does not get rebuilt, keep the message about the deliverable rather than the person, and state exactly what “ready” looks like and by when.

Why not just say it needs to be better?

Because vague dissatisfaction tells someone they failed without telling them how to succeed, which forces guesswork and produces a second draft that misses in new ways, the start of a rewrite war.

Should I mention what is good about it?

Yes, but as information rather than flattery: telling someone the structure and research are solid stops them from rebuilding the parts that already work, which a purely negative message often triggers.

How do I keep it from feeling like an attack?

Make the work the subject, not the person: “the analysis is missing the regional breakdown” gets fixed, while “you didn’t think this through” gets defended.

Download Wrivio for Windows to rewrite a frustrated rejection into specific, constructive feedback that gets the work fixed.