To write a clear instruction, tell the reader what to do, what to do it to, and any condition or sequence that affects the result. “Send the file” may leave unanswered which file, where it should go, and when it is due. “Upload the signed form to the shared folder by 3 p.m. Friday” gives a concrete action and destination. W3C’s accessibility guidance calls for instructions that are clear and easy to understand, including explicit input requirements such as date formats. [1]
Put the action where readers can find it
Begin with the main verb when that fits the situation: “Choose a room,” “Enter the date,” or “Attach the receipt.” A direct verb shows the reader what to do. Avoid a long lead-in that delays the instruction, such as “In order to ensure that the materials are appropriately organized, it is requested that…”
Name the object as well as the action. “Review” is not complete if readers cannot tell what to review. “Review the three proposed titles” is specific. If an instruction has several steps, give each step its own numbered line so readers can follow the sequence and return to a particular point.
Supply the details people would otherwise guess
Include the information needed to complete the task: a destination, time, format, amount, or decision rule. Do not add detail merely to sound thorough; add it when a reader could reasonably make a different choice without it. “Name the file with your last name and the meeting date” is more usable than “Name the file correctly.”
For an invented example, imagine a volunteer checking out microphones for a reading. “Return the equipment promptly” leaves the deadline and place open. A usable instruction could say: “After the reading, return both microphones to the labeled case on the front desk before you leave.” It identifies the items, location, and timing in one sentence.
Separate steps from conditions
A sequence tells readers what comes first: “Sign the form, then upload it.” A condition tells them when an action applies: “If you need an interpreter, select ‘Request support’ before you submit the form.” Keep the condition close to the relevant action so readers do not miss which people or circumstances it covers.
Avoid burying a critical instruction inside a long sentence with several clauses. Purdue’s guidance on sentence clarity notes that interruptions between a subject and its main verb can make a sentence harder to follow. [2] Splitting a complex instruction into two short steps often makes the order easier to see.
Choose words and formats for the audience
Use terms the intended readers recognize, and define an unfamiliar term where it first appears. If a process uses an acronym, spell it out on first mention when readers may not know it. Plain-language guidance emphasizes writing for a specific audience, which means the clearest wording depends partly on what that audience already understands. [3]
Do not rely on color, position, or appearance alone to identify an item. Say “select the ‘Submit’ button” rather than “click the green one” if the button label is available. When a reader must enter a value, state the expected form: “Enter the date as month, day, and year, such as 04/18/2027.” W3C specifically recommends describing input requirements such as date formats. [1]
Run a practical test
Ask a person who has not seen your draft to follow it. Watch for pauses, questions, and choices you did not anticipate. If you cannot do that, read each step and imagine the reader’s next action: Is the object clear? Is the destination named? Does the sequence make sense? Could two reasonable readers produce different results?
For the microphone example, the test might reveal that the front desk closes before the reading ends. Revise the instruction to name an alternate handoff: “After the reading, return both microphones to the labeled case at the front desk. If the desk is closed, give the case to the event host.” The test improves the instruction by resolving a real decision point, not by adding decorative wording.
