How to Ask for Feedback on Your Work in Writing

Most requests for feedback get a useless answer because they ask a useless question. “Let me know what you think” or “any thoughts?” hands the reviewer an open-ended job with no anchor, so they do the easy thing and say “looks good.” You get nothing you can act on, and you conclude the work was fine when nobody actually checked it.

Getting real feedback is a writing skill. It is about making the review small, specific, and safe to be honest in. Here is how.

Ask About Something Specific

The single biggest improvement is to name what you want feedback on. A reviewer faced with “thoughts on this whole document?” gives a shallow scan. A reviewer asked “is the argument in section 2 convincing, and is the tone right for a client?” gives you exactly that. You have turned an unbounded task into two answerable questions.

Specificity also tells the reviewer what stage the work is at. Asking about structure signals do not proofread yet; asking about wording signals the structure is settled. That saves them from giving you notes you cannot use. Clear, plain requests get clearer answers, which is the whole premise of the US federal plain language guidelines.

Make It Easy to Be Honest

People withhold critical feedback because being critical is socially expensive, especially to a peer or someone senior to them. You can lower that cost. Say explicitly that you want the problems, not reassurance: “I would rather hear what is weak now than after it ships.” Naming a specific worry of your own gives them permission to agree: “I think the opening is slow, does it lose you?”

This is the flip side of giving feedback well, which we covered in how to give critical feedback in writing. When you make honesty the easy and expected response, you get it.

Scope It and Set a Deadline

An open request with no deadline gets deprioritized, and a huge one gets declined. Bound both. Send the two sections you actually need eyes on, not the whole 40-page draft, and say when you need it by and how long it should take: “Fifteen minutes on these two pages by Thursday would really help.” A small, time-boxed ask gets done; a vague, unbounded one sits. This is the same courtesy as any well-framed request, including a reference ask, which we covered in how to ask for a professional reference.

Before and After

The difference is whether the reviewer knows what to do.

Before:

Hey, when you get a chance could you take a look at my proposal draft and let me know your thoughts? No rush, just want to make sure it’s good before I send it. Thanks!

After:

Could you look at two things in my proposal draft (attached, 3 pages)? First, is the pricing section clear, or does it raise questions I should preempt? Second, does the tone read as confident or pushy? I would genuinely rather hear the weak spots now. Fifteen minutes by Thursday would be a big help.

The second version gets you specific, honest, actionable notes; the first gets you “looks good.”

A Wrivio Context for a feedback request could say:

Rewrite this as a specific feedback request. Keep any deadline and detail exactly as written. Name exactly what I want feedback on, invite honest criticism explicitly, and bound the ask with a scope and time. Do not leave it as a vague “let me know your thoughts.”

Press Ctrl+Shift+Space, paste your draft, and check the diff. A rewrite that turns “thoughts?” into named questions with a deadline is doing its job; one that keeps the request open-ended has guaranteed you a shallow answer.

Common Questions

Why do I only get “looks good” when I ask for feedback?

Because an open-ended request like “any thoughts?” gives the reviewer no anchor, so they default to the easy, non-critical answer. Naming what you want feedback on gets you a real one.

How do I get honest criticism instead of reassurance?

Lower the social cost of being critical. Say explicitly you want the weak spots, and name a worry of your own to give the reviewer permission to agree with it.

How much should I send for review?

Only the part you actually need eyes on. A small, scoped ask gets done; a whole large draft gets deprioritized or a shallow scan. Send the two sections, not the forty pages.

Should I set a deadline for feedback?

Yes, a reasonable one, with a sense of how long it should take. “Fifteen minutes by Thursday” gets done; an open request with no deadline sits indefinitely.

Does asking about a specific section help the reviewer?

Yes. It tells them the stage the work is at, so they do not proofread when you need structural notes, and it turns an unbounded task into an answerable question.

Download Wrivio for Windows to turn a vague “let me know your thoughts” into a request that gets you feedback you can actually use.