How do I review a task guide without rewriting it from scratch?
Quick answer
Review the guide as a reader trying to complete the task, not as an editor looking for every sentence to improve. First check that readers know what they need and whether the task applies to them. Then follow the steps in order, flag missing choices or visual references, and check how readers know they are finished. Make targeted edits only where a gap blocks action or causes confusion.
The question, the details, the next step.
I have a task guide that feels a bit rough, but I don't want to rewrite the whole thing. How should I review it?
Do one practical pass before making style edits: pretend you are a reader who wants to complete the task. At each point, ask, “Could I act on this, using only what the guide gives me?” Mark places where the answer is no, then fix those specific gaps.
Keep the review to five checks:
- Prerequisites: what must the reader have, know, or decide first?
- Sequence: does each step follow from the previous one?
- Branches: what should the reader do when a condition or result differs?
- Visual references: do mentions of pictures, labels, or screens match what the reader can see?
- Completion: how can the reader tell the task is done?
You are reviewing usability, not trying to make every sentence sound different.
How do I check the prerequisites without adding a long introduction?
Look for anything the guide assumes the reader already has or knows. That could be an item, an account, a permission, a starting condition, or a term used later. Add only the prerequisite that affects whether the reader can begin; don't pad the opening with background that does not help them act.
For example, in a hypothetical guide for submitting a shared document, a useful opening might say: “Before you begin: have the final file ready and confirm you can access the shared folder.” Those details are placeholders for the actual task. If you do not know whether a prerequisite applies, flag it for the guide owner instead of presenting a guess as fact.
What is a quick way to test whether the steps are in the right order?
Read only the action steps, in order, and imagine doing each one. At every step, ask whether its needed information or result is already available. If step 3 asks the reader to choose an option that step 5 explains, the sequence may be wrong—or step 3 may need a short explanation.
Use a simple mark-up: write “blocked” beside a step if you cannot continue, “unclear” if you cannot tell what action it asks for, and “extra” if it does not help reach the stated result. Then revise the marked spots rather than replacing the whole sequence. A small reorder or one linking sentence may be enough.
And how do I handle choices or exceptions? I don't want to invent steps for cases I haven't checked.
Separate known branches from unanswered questions. When the guide already supports a choice, make the condition and next action easy to scan: “If [condition], do [action]. Otherwise, continue to [step].” If no approved action is provided for an exception, add an editorial note such as “[Confirm what readers should do if this condition occurs]” for the responsible person to resolve. Don't fill the gap with a plausible-sounding instruction.
For each branch, check that the reader can tell which situation applies and where to go next. Also check whether the branch returns to the main sequence. A choice that says what to do but not what comes afterward can leave the reader stranded.
The guide refers to a screenshot and says “when it looks right.” What should I check there?
Check whether the reference helps a reader find the right thing, not just whether an image exists. The text should identify what to look for, and any label or step number should match the visual. If the screenshot is missing, outdated, or hard to interpret, mark that specific problem for an update rather than guessing what it should show.
Replace vague completion language like “when it looks right” with an observable criterion if the guide owner can confirm one. For example, a placeholder might read: “You are finished when [the confirmed completion condition is visible].” That makes the missing detail explicit without pretending it has been verified.
Can you show me a compact review note I could use on an actual draft?
Use a note that points to the reader's obstacle and the smallest useful fix. For a hypothetical guide, it could look like this:
“Review focus: can a first-time reader complete the task?
- Before step 1: Confirm whether [required item or access] is needed; it is not stated.
- Step 2: The action refers to [term or control] before it is explained. Define it here or earlier.
- Choice after step 3: State what happens for [condition A] and [condition B]; the current text covers only one.
- Visual: Check that [image or label] matches the reference in step 4.
- Finish: Replace ‘when it looks right’ with [confirmed observable result].
- Keep: Steps 1 and 4 already read in a clear, usable order.”
The “Keep” line helps preserve material that works. Treat bracketed text as a prompt to verify, not as final instructions.
A practical checklist
Identify what the reader must have, know, or confirm before starting.
Follow every step in order and mark where progress is blocked or unclear.
Check that each stated condition has a clear next action and destination.
Match visual references, labels, and step numbers to the material readers will see.
Replace vague completion wording only with an observable condition the guide owner can confirm.
Record what already works so edits stay targeted.
A few more useful answers
Should I copyedit the guide during the same review?
First find gaps that stop readers from acting. Make wording edits where they resolve a specific confusion; save unrelated style preferences for a separate pass.
What if I cannot confirm whether a step or prerequisite is correct?
Mark the uncertainty as a question for the responsible guide owner. Do not turn an assumption into an instruction.
How can I tell whether a proposed edit is worth making?
Ask whether it helps readers start, choose the right path, perform a step, or recognize completion. If it does none of those, it may not belong in this review.