How to Review Your Own Work With Claude
Most people who ask Claude to review their own work paste in a draft and ask some version of "does this look good?" The answer is almost always some version of yes, with a couple of minor tweaks. That's not because the draft is actually fine. It's because "does this look good" doesn't tell Claude what "good" means for this particular piece of writing, so it defaults to the same polite, surface-level pass it would give anything.
A review is only as useful as the specific thing you asked it to check.
The fix isn't a better version of "does this look good." It's naming the actual failure modes you're worried about, one at a time, and asking Claude to check for those specifically instead of the draft as a whole.
Why a generic request gets a generic answer
"Does this look good" has no wrong answer built into it. Claude can't fail that question, so it doesn't. Ask instead "does this opening line make a stranger want to keep reading" and there's now a real bar to clear, one Claude can actually say no to. The difference isn't politeness. It's that the second question has a concrete failure condition and the first one doesn't.
This matters most for your own work specifically, because you're the person least likely to catch your own blind spots. You already know what you meant, so a sentence that's actually unclear reads as clear to you, since your brain fills the gap automatically. A specific check forces Claude to evaluate the sentence as written, not as intended.
Tip
Ask Claude to review the draft as if it had never seen your intent, only the words on the page. That single instruction catches more real problems than ten rounds of "does this sound okay."
A short list of specific things worth checking
Rather than one broad review, run a draft through a small set of named checks. Each one catches a different kind of failure, and together they cover more ground than a single "review this" pass ever does.
Unsupported claims: any sentence that states a fact, a number, or a result without something backing it up in the draft itself
A weak opening: whether the first sentence would make someone with no context keep reading, or whether it buries the point
An inconsistent tone: a section that shifts from casual to formal, or from confident to hedging, without a reason
A missing counterargument: the obvious objection a skeptical reader would raise that the draft never addresses
Each of these is checkable. Claude can say yes or no to "is there an unsupported claim in paragraph two" in a way it can't say yes or no to "is this good." That's the whole shift.
Review this draft for three specific things: any sentence that states a number or result without support in the text, whether the opening two sentences would hook someone with zero context, and any place the tone shifts without a clear reason. Quote the exact sentence for each issue you find.
”Asking for the exact sentence, not just a general note, is what makes the review actionable. "The tone is inconsistent somewhere" tells you there's a problem without telling you where it is, which means you're back to rereading the whole thing yourself to find it.
Inside Claude Tutorial
This works on anything, not just prose.
Naming specific failure modes instead of asking for a general opinion is a habit that carries into reviewing spreadsheets, plans, and code just as well as writing. The app has a full lesson on it, with practice that transfers across all of them.
Reviewing for the reader, not for yourself
A second useful check is asking Claude to read the draft as a specific reader would, not as a neutral evaluator. "Would a customer who's never used our product understand this paragraph" surfaces different problems than "is this well written," because it forces the review to account for what that specific reader already knows and doesn't.
This works especially well when the actual reader knows less than you do about the subject. You wrote the draft with your own full context in your head, so a sentence that leans on an assumption you never stated reads as complete to you and confusing to them.
Read this explanation as someone who has never used our product before and has no background in the terms I've used. Flag any sentence that assumes knowledge they wouldn't have, and tell me what's missing for it to make sense to them.
”Knowing when Claude's review isn't enough
Claude's review is strong on structure, clarity, tone, and internal consistency, the kinds of problems visible from the text itself. It's weaker on anything that requires knowledge outside the draft: whether a number is actually correct, whether a claim about a competitor is current, whether a legal or medical detail is accurate. A review that comes back clean on those fronts means the draft is internally consistent, not that every fact in it is right.
Common mistake
Treating a clean review as proof the content is accurate. Claude can tell you a sentence is clear and well supported by the rest of the draft. It can't verify a fact against the real world unless you give it something to check that fact against.
If a draft leans on specific facts you haven't verified yourself, that's a separate check, not something a structural review covers.
Continue reading
- Brainstorming Better Ideas With Claude: narrowing a wide set of ideas down is its own kind of review, run earlier in the process instead of at the end.
- Knowing Where Claude's Answers Need a Second Check: what still needs an independent check even after a clean review.