Define the writing assignment

Review questions

Define the writing assignment

Technical writing begins with the reader’s task rather than a general wish to improve copy. The writer turns a vague request into a brief naming reader, situation, action, source of truth, and acceptance check. Different applicant and reviewer permissions require distinct paths instead of one procedure for everyone. Each consequential claim is tied to a source passage and release: an old article does not establish new interface behavior, and an official source may prove a button exists without proving every role sees it. The writer then chooses an appropriate form: procedure for action, reference for values, explanation for reasons, and fault path for errors. In the integrated case, verified sections can proceed while a disputed timing promise remains held for its decision owner. A receipt must never be mistaken for final approval.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1The current-release screenshot says “We received your request,” while an older article says the appointment changes immediately. Which statement can the writer publish now?
  2. Question 2A submission worker cannot reopen a request, but a reviewer can. What should the writer change first in a page that mixes both paths?
  3. Question 3Release-6 specification allows a reviewer to download CSV when status is Complete; the draft says “Every user can always download CSV.” How should the claim change?
  4. Question 4A reader needs file-upload steps and definitions of four fields. Which structure best supports that task?