If someone says “Please review this document,” ask whether they want you to read it, leave comments, suggest tracked changes or edit the text directly. Also confirm the part to review, the criterion and who has authority to approve the finished version. A clear reply is: “Would you like comments only, suggested changes you can accept, or direct editing?”
The word review communicates attention but does not always assign editing permission. One person may expect proofreading marks; another may expect a decision about factual accuracy; another may want a new final draft. The reader’s repair job is to turn an elastic request into an agreed work mode before making changes that somebody else might not have intended.
Why the verb review allows more than one workflow
Cambridge Dictionary’s entry for review includes reconsidering something to make changes or a decision, as well as assessing and discussing work. In ordinary collaboration, people use the same word for different stages: a quick look, a critical assessment, a set of comments, a proposed edit or a final approval.
Those stages are not interchangeable. Reading a proposal and saying “I have checked the figures” does not necessarily mean “I approve this plan.” A suggestion to shorten a paragraph is not automatically permission to overwrite the author’s original. Identifying the intended output is the first step of the conversation.
The mechanism is a task-scope ambiguity: the request specifies a general activity but leaves the permitted operation unsaid. You can repair it by offering a small menu of actions, asking for the success criterion, and repeating the chosen limit before working.
Did you know? Some editors literally separate viewing, reviewing and editing
Microsoft’s guidance for Word document modes distinguishes Viewing, Reviewing and Editing. Viewing is read-only; Reviewing can support comments and proposed revisions; Editing allows direct changes when permissions permit. This is a useful concrete example of a broader language distinction: being invited to look at a file is not the same as being authorised to alter it.
Software permission and social permission are also not identical. A link may technically allow editing even when the sender intended comments only. The sensible response is to check the request rather than treating a clickable Edit button as proof of intent.
The four-question review agreement
- Purpose: What is being checked—spelling, evidence, calculations, clarity, accessibility or readiness to publish?
- Mode: Should the reviewer only read, comment, make suggested changes, or edit directly?
- Scope: Which section or version is in scope, and what must remain unchanged?
- Decision: Who accepts the changes, and what counts as the review being completed?
A short version for ordinary chat is: “Is this feedback only, or may I edit? Which part matters most?” For a formal document, add, “I will return comments on sections two and three; no text will be changed until you approve.” You have now named an output that can be checked.
Worked dialogue 1: a pupil asks a classmate to review a composition
Fictional example. A pupil says, “Please review my story before I hand it in.” The classmate asks, “Do you want me to point out unclear parts, check punctuation or rewrite sentences?” The pupil answers, “Mark the places where you got confused. I want to improve the wording myself.” The classmate agrees: “I’ll add comments, not replace your sentences.”
The response respects authorship. It also makes the feedback useful: the reviewer identifies how the reader experienced the text without doing the pupil’s work. For school assessments, follow the actual academic-integrity and assistance rules; a private agreement cannot override those requirements.
Worked dialogue 2: a Science group prepares a presentation
Fictional example. One team member shares a slide deck and writes, “Can you review the results page?” Another replies, “Do you need a fact check against our measurements or design feedback? I don’t want to change the data labels without agreement.” The first person says, “Check whether every unit matches our table. Put corrections in comments.”
The second student does not invent new experimental results. The group can discuss whether a label is erroneous, but the evidence must come from the measured data, not from a desire for a tidy slide. This is why a precise review criterion can improve both language and subject learning.
If the group later wants a final edit, they can grant that separately: “Please apply the agreed unit corrections and show us the revised slide.” One successful review does not grant permanent authority to alter all future materials.
Worked dialogue 3: an adult team revises a public notice
Fictional example. A manager says, “Please review the notice today.” The colleague asks, “Should I comment on unclear wording, make tracked suggestions or replace the text directly?” The manager responds, “Make tracked suggestions on the first page, but do not change dates or approved prices. I’ll accept or reject the revisions.”
The colleague repeats the scope and returns suggested changes. This avoids a common failure: a well-meaning editor silently changes a substantive fact that another team is responsible for verifying. Tracked revisions and comments help preserve a visible decision trail, but the communication agreement comes first.
A review is not always an approval
A person can say, “I’ve reviewed the language” while still leaving the factual content unverified. A school peer can say, “I read the introduction,” without claiming to have evaluated the whole essay. A supervisor can say, “These comments are for revision, not final sign-off.” Each sentence marks what was actually accomplished.
Do not convert “no comments” into “approved” unless the agreed workflow says that silence has that meaning. When approval matters, ask directly: “Can you confirm whether this version is approved for distribution?” That is a different speech act from “Would you look at it?”
How to phrase the question without sounding territorial
Avoid, “You’re unclear,” or “You should have told me.” Instead describe the decision you need to make: “To avoid changing something you want to retain, should I comment or edit?” This gives the sender a practical reason for the question.
With friends: “Want suggestions or actual changes?” With a teacher: “Should I correct the language in comments or leave questions for the writer?” With a colleague: “Please confirm the review mode and who has final sign-off.” Register varies with setting; it does not change the need for consent and a clear output.
British Council TeachingEnglish’s discussion of register and appropriateness explains why phrasing should suit audience and context. A direct question can be polite when its purpose is helpful and its tone non-accusatory.
A quick reply template that avoids overcommitting
“Happy to review. I can [check one criterion] and return [comments or tracked suggestions] on [part or version]. I won’t edit the original unless you want me to. Who should approve the final changes?” Replace the bracketed words with the real scope. The goal is clarity, not a rigid formula that people must always recite.
If you are short of time, do not silently narrow the job and claim a full review. Say, “I can check the introduction for clarity today, but I can’t verify the references.” That sentence supplies an honest boundary and makes it easier for the owner to allocate the remaining work.
Misconceptions and risks
- “A reviewer has permission to rewrite.” Not unless permission and workflow support that.
- “Comments and edits are identical.” Comments raise issues without necessarily changing text; edits alter or propose to alter it.
- “Having file access proves approval.” Tool permissions and the sender’s intended task can differ.
- “No response means accepted.” Silence does not automatically supply the decision a project requires.
- “One version is enough.” Be sure the review applies to the intended file or version, especially where several drafts circulate.
Diagnostic questions before touching a shared file
Can you name the authorised mode in five words? Can you identify the section, version and criterion? Do you know whether the original should remain intact? Is there a named decision maker for accepting changes? If not, ask one precise question about the missing dimension instead of opening the file and guessing.
Version confusion is a separate problem, developed in eduKate’s guide to identifying a document version before reviewing. This lesson begins after the right document is found: it determines what kind of intervention has actually been requested.
Retrieval practice: choose the right reply
A friend says, “Review my poster,” but the title is incomplete and the layout is unfinished. Which reply is more accurate? “I’ll fix it” or “Would you like design comments, spelling checks or direct changes?” The second reply asks for the authorised task without inventing it.
Now try three brief cases. A teacher says, “Review your partner’s essay”; a Science group says, “Review these figures”; and a manager says, “Review the announcement.” Write one scope question and one permission question for each. Change the register but keep the distinction between examining and editing.
Answer check: acceptable responses might ask whether the teacher wants reader feedback rather than rewriting, whether the figures should be checked against source measurements, and whether the announcement requires tracked language suggestions or a final approval. The precise answer must come from the task owner.
Apply the method over the next week
Practise with one low-stakes document. First, ask for the review criterion. Second, clarify whether the owner wants comments or direct changes. Third, complete only the agreed portion. Fourth, return a concise note naming what you checked and what remains unchecked. Repeat the exercise with a different document and notice how the requested output changes.
Parents can teach the difference between helping a child improve a paragraph and rewriting it for them. Teachers can set peer-review roles explicitly, protecting the learner’s ownership of the final work. Students can practise giving evidence-based comments without taking over. Adult teams can agree change tracking and sign-off boundaries before multiple people edit a shared file.
Frequently asked questions
What if I already changed the file? Say what you changed, identify the original version and ask whether to retain or revert those changes. Do not hide an edit because it was made with good intentions.
Can I make corrections to obvious spelling errors? Only if direct editing fits the agreed review mode. Otherwise leave a comment or tracked suggestion so the author can decide.
Does “review and approve” mean the same thing as “review”? No. Approval adds a decision. Ask what counts as approval and who holds that authority.
What if several people are reviewing simultaneously? Agree which sections or categories each person handles and how their comments will be reconciled. Separate conflicting suggestions from approved final text.
The final habit
Treat “please review” as the beginning of a work agreement, not permission to do everything your editor can do. Name the criterion, the authorised action, the document scope and the person who decides. A short question before editing can save a long repair afterwards.