How do I write instructions that make it clear when a task is finished?
Quick answer
Describe what someone must produce or do, what observable conditions it must meet, and how completion will be confirmed. Keep the criteria limited to what matters for this task and audience. Replace “when it looks right” with checkable details, such as required sections, a named recipient, or a review step. If a condition is subjective, explain what evidence or decision will count as meeting it.
The question, the details, the next step.
How do I write instructions that make it clear when a task is finished? I often write things like “finish the draft when it looks right,” but people interpret that differently.
Describe a finish line someone can recognize, rather than a feeling they must guess. A useful instruction names the deliverable, the conditions it must meet, and—when needed—how completion is checked.
For example, “Finish the draft when it looks right” gives no shared test. A clearer version might be: “Send a draft with the three requested sections, add a heading to each section, and mark any unresolved questions in brackets.” The details here are illustrative; choose conditions that actually fit your task.
A good criterion is observable: another person could point to the result and say whether it is present. It should also be relevant. Listing every possible preference can make the task harder, not clearer.
What should I write down before I turn a vague instruction into criteria?
Start with four prompts. You do not need a long specification; a few well-chosen answers often make the endpoint clear.
- Deliverable: What should exist at the end—a draft, a decision, a set of notes, or something else?
- Required contents: What must be included, and what is explicitly out of scope?
- Observable conditions: What can the person or reviewer check in the result?
- Confirmation: Who, if anyone, needs to review or acknowledge it?
Separate must-haves from preferences. “Include the date and location” may be a must-have; “use a warm tone” may need an example or a short explanation if readers could interpret it differently. Don’t add a condition just because it sounds thorough. Include it only if it helps the recipient know what to do or helps the reviewer decide whether the task is complete.
Can you show how to handle something subjective, like “make it easy to understand,” without pretending there’s one objective answer?
Translate the intention into reasonable evidence, while acknowledging where judgment remains. For a short announcement, you might write: “Put the date, time, place, and action readers should take near the beginning. Use short paragraphs, then ask a reader unfamiliar with the event to flag any detail they cannot find.”
That instruction doesn’t claim that every reader will find the announcement easy. It gives the writer concrete choices and a check that can reveal confusion. If the intended audience is known, name it: “Ask someone who has not helped plan the event to check whether they can find the start time and location.” If no reviewer is available, specify the parts the writer should check themselves. Avoid using a review step as a promise that the work is perfect.
I need a small worksheet I can reuse. Could you include sentence patterns and a worked example?
Copy and complete this worksheet, removing any lines that do not apply:
Completion-criteria worksheet
- Task: [What is being done?]
- Deliverable: [What will exist when it is done?]
- Must include: [Required items or parts]
- Must meet: [Observable conditions]
- Check: [How will each condition be checked?]
- Finish point: [What action or acknowledgment marks completion?]
- Not included: [Important boundary, if needed]
Useful sentence patterns:
- “The task is complete when [deliverable] includes [required items].”
- “Before sending, check that [observable condition] and [observable condition].”
- “Mark [open question or missing item] as [label] rather than guessing.”
- “Completion is confirmed when [named review or handoff] has happened.”
Worked example, assuming the task is preparing a meeting agenda: “The agenda is ready to share when it lists the meeting date, start time, location, and each proposed topic; identifies the person leading each topic if known; and marks any unconfirmed item as ‘to confirm.’ Send it to [recipient] for review.” The bracket is a placeholder, not a real contact detail. If review is not part of the task, omit the final sentence.
A practical checklist
Name the deliverable so the recipient knows what to produce.
List only required contents and conditions that matter for this task.
Replace vague judgments with observable evidence or a stated review step.
Mark unknowns or unresolved items instead of asking someone to guess.
State who checks the result or what action marks completion, if applicable.
A few more useful answers
How many completion criteria should an instruction have?
Use enough to make the endpoint checkable, but no more than the task needs. A short task may need only a deliverable and a few must-haves; a more involved task may also need a review or handoff condition.
What if the result cannot be judged with a simple yes or no?
Describe the evidence, audience, or review process that will guide the judgment. Be honest that some preferences still require interpretation rather than presenting a subjective standard as an exact test.
Should finishing a draft mean it is approved?
Not unless approval is part of the task. Separate “ready to review” from “approved,” and state who makes the decision if approval is required.