You send a draft with a note that says, 'Any feedback would be appreciated.' A week later, it comes back with corrected commas and a kind comment. You were hoping someone would tell you whether the argument made sense.
The reader may have done exactly what your request allowed. The handbook recommends telling colleagues what stage the work is at and which questions need their attention.
Tell the reader what kind of draft they're opening
An outline, an exploratory section, and a nearly final manuscript need different responses. State what's ready for review and what's still changing. Explain the intended audience or venue if that context matters.
You can also say what would be premature. For example: 'The structure is still open, so sentence editing isn't the priority yet.'
Ask about the decision you're trying to make
Choose one or two focused questions. Can the reader identify the contribution? Does the evidence support the interpretation? Is an important alternative explanation missing? Where does the reasoning become difficult to follow?
A request might sound like this:
'I'm revising the discussion before choosing an outlet. Would you read these four pages and tell me whether the main contribution is clear and whether the final claim goes beyond the evidence? If a short conversation is easier than written comments, that would help too.'
Adjust the scope and timing to what the person can reasonably offer. A meeting isn't automatically less work; ask what suits them.
Read comments for the problem underneath
A reader's suggested rewrite may point to confusion even if you don't adopt the exact wording. Ask what they understood at that point and what they expected next. Separate the underlying issue from one possible solution.
If feedback is unclear, follow up respectfully with a specific example. You don't have to choose between accepting everything and defending the entire draft.
Turn the response into a revision plan
Group comments into argument, evidence, structure, and presentation. Resolve the larger issues before polishing details. Keep track of decisions that need another discussion with collaborators.
Thank the reader and let them know how the conversation helped. Then return the favor when you have appropriate expertise and capacity.
Give conflicting comments a problem to solve
One reader wants more background; another wants a shorter opening. Before choosing a side, ask what each person couldn't understand. Perhaps the necessary context is buried in a long paragraph, so both comments point toward a more focused explanation rather than opposite revisions.
Return to the intended reader and the section's purpose. Which information must be present for the argument to make sense? Which detail belongs later or can be removed? You can use the feedback to diagnose the difficulty without accepting every proposed solution.
Keep a brief revision list that records the issue and your decision. If a concern remains unresolved, ask a focused follow-up instead of repeatedly rewriting the same passage. You still own the argument and the responsibility to support it. The reader's contribution is valuable because it shows where another person encountered the draft differently from the way you intended it to work.
Before sending your next draft, replace 'Any thoughts?' with the question you're actually trying to answer. Give the reader a manageable task, enough context, and a realistic date. You'll both have a clearer purpose.
Adapted from The New Faculty Handbook by Zafer Unal, pp. 95-96.
