How can I find claims in a draft that need support from the writer?
Quick answer
Read the draft one sentence at a time and mark statements that assert facts, causes, comparisons, or outcomes. Ask whether the nearby text supports each statement as written. If not, quote the exact wording, explain what is missing, and ask the writer to provide evidence, clarify the intended meaning, or narrow the claim. Do not supply a source or stronger assertion on the writer’s behalf.
The question, the details, the next step.
I need to review a draft and identify claims that need support from its writer. How do I do that without turning the review into a rewrite?
Treat the task as a focused claim audit, not a fact-check or line edit. Look for sentences that ask the reader to accept something as true: a number, a cause, a comparison, a prediction, or a statement about what people generally do. Then compare each claim with the explanation and evidence actually present in the draft.
Flag a statement when the draft does not show where it came from, how its terms are defined, or why the supporting details justify its scope. Your note should identify the wording and ask the author to resolve the gap. Possible resolutions include adding evidence, explaining the basis, narrowing the statement, or removing it.
What counts as a claim that sounds broader or more definite than the draft supports?
Watch for words that make a statement sound universal or settled: “all,” “never,” “proves,” “guarantees,” “the main reason,” or “will.” These words are not automatically wrong; they are useful prompts to check the scope. A sentence can also overreach without dramatic wording—for example, it may draw a general conclusion from one anecdote, or describe an outcome without showing how it was measured.
Compare the claim with the material around it. Does the draft give a source, example, method, or explanation that addresses this particular statement? Does that material support the same group, time period, and level of certainty? If the answer is unclear, flag the gap rather than deciding the claim is false.
Can you show me what a useful review note looks like?
Suppose the draft says, “The new sign-in process reduces missed appointments,” but the paragraph only describes how the sign-in process works. That description does not, on its own, show whether appointments are missed less often. A focused note might read:
“Claim to check: ‘The new sign-in process reduces missed appointments.’ I don’t see evidence of a change in missed appointments in this paragraph. Could you share the evidence or explain what comparison supports this? If the result is not established here, would you narrow or remove the outcome claim?”
This is a hypothetical example, not a finding about any real process. Notice that the note points to the exact claim, names the gap, and gives the writer options without inventing a statistic, source, or replacement conclusion.
How should I organize several flagged claims so the writer can respond efficiently?
Use a short list in the order the claims appear. For each item, include the exact phrase or a brief excerpt, the reason it needs attention, and one open question. Keep separate claims separate even if they appear in the same paragraph; a cause claim and a numerical claim may need different answers.
For example:
- Text: “[exact sentence or phrase]”
Why flagged: “The draft gives an example but does not show how far the conclusion extends.” Question: “What evidence supports this scope, or would you like to narrow the wording?”
Use neutral language such as “I don’t see support for this in the current draft” rather than “This is false.” Your review identifies what the draft leaves unresolved. The author must provide or verify any needed evidence; your note is not proof that the claim is accurate or inaccurate.
How can I make sure the review does not become a long list of vague doubts?
Apply the same test to every possible flag: Is there a specific statement? What, exactly, is missing from the draft’s explanation? Can I ask one answerable question that helps the writer decide what to do? If you cannot identify the statement or the gap, leave it out or make your concern more precise.
You do not need to flag every sentence that could use a citation. Prioritize claims whose scope, certainty, or reasoning seems important to the draft’s point. Keep the review limited to what you can observe in the text, and leave decisions about evidence and factual accuracy with the writer.
A practical checklist
Mark sentences that assert facts, causes, comparisons, predictions, or outcomes.
Check whether the nearby explanation supports the claim’s scope and certainty.
Quote the exact wording that needs the writer’s attention.
State the specific gap you can see in the current draft.
Ask whether the writer can provide evidence, clarify, narrow, or remove the claim.
Do not invent sources, facts, or replacement claims.
A few more useful answers
Should I call a flagged claim unsupported or false?
Say that you do not see support for it in the current draft. That describes the reviewable gap without claiming the statement is false.
Should every factual sentence receive a review note?
No. Focus on claims whose support, scope, or certainty is unclear or important to the draft’s point. Avoid notes that do not identify a specific gap.
What if the writer has evidence that is not in the draft?
Ask the writer to share or incorporate the relevant support. Your review can identify what the reader cannot see; it cannot establish evidence that the draft does not provide.