Instructions become harder to follow when an object changes names halfway through the task. A reader opens a folder, adds a file to a collection, and then saves an item in a library. Are those three locations, or three names for the same location? The writer may know the answer, but the reader should not have to guess.
A focused terminology pass can find these problems without creating a large glossary or rewriting the whole help article. Follow the reader’s task from its first instruction to its final result. Check the names of objects, actions and states at every point where the reader must recognize them.
Start with the task, not a list of preferred words
Choose one procedure that a reader can complete from beginning to end. Open its current instructions alongside the interface, form or materials they describe. If you cannot inspect the actual process, mark the labels that require verification rather than treating an old screenshot or a colleague’s recollection as definitive.
Use a simple illustrative task for the first pass. Imagine a fictional document portal where a user creates a folder, uploads a file, saves a draft request and finally submits that request. These names and controls are invented for this example; they are not directions for a real product.
The editorial question is whether the instructions preserve those distinctions. “File” names the uploaded document. “Folder” names its location. “Request” names the item sent for review. Replacing all three with the friendly-sounding word “item” would make the language less precise, even if every sentence became shorter.
Trace each important object through the instructions
Underline the nouns that the reader must identify: folder, file, draft request and submitted request. Then search the document for possible alternatives such as collection, document, submission and entry. Do not change them immediately. First decide whether each alternative refers to the same thing or introduces a meaningful distinction.
Make a small working note for each object. Record the name used on screen, the wording used in the instructions, and the point where the object first appears. This note belongs to the current editing task. It does not need to become a permanent reference document unless the team has a separate reason to maintain one.
In the fictional portal, an instruction reading “Add the document to your collection” needs investigation if the screen shows a control called “Upload file” inside a folder. A closer match might be “Open the folder, then select Upload file.” The revision helps the reader connect the written action to something they can identify.
Repeat names when repetition carries useful meaning
Writers often vary words to avoid sounding repetitive. In a procedure, repeating a key noun can be the clearer choice. Google’s guidance on writing for a global audience recommends consistent terminology for the same concept. It also advises replacing unclear pronouns with the relevant noun when necessary.
Consider: “Open the request beside the uploaded file and rename it.” The pronoun could refer to the request or the file. If the task is to rename the request, say so: “Open the request beside the uploaded file and rename the request.” You may decide to split the instruction, but first remove the uncertainty about its object.
Repeat selectively. There is no need to insert “the request” into every clause when only one possible object is present. Concentrate on sentences that mention multiple objects, transitions between screens, and steps where selecting the wrong object would change the result.
Check nearby headings and recovery instructions during the same pass. A procedure might consistently say “request” while an error-recovery paragraph suddenly calls it an “application.” If both refer to the same object, align them. If an application is genuinely different, explain that relationship before asking the reader to find or change one.
Keep actions distinct when their outcomes differ
Consistency does not mean using one verb for every action. Save, submit, publish, send and upload can describe different operations. Verify what each control actually does before choosing a more familiar verb. A short instruction is not useful if it tells the reader that saving a draft also sends it to someone.
For the fictional portal, the draft might say: “Save the request when you are ready for the reviewer to receive it.” If saving only retains an editable draft, that sentence is wrong. The intended instruction would need the separate Submit request control, along with any prerequisite already explained in the procedure.
Read the verbs as a sequence without the surrounding prose: create, upload, save, submit. Ask what changes after each action and what remains unchanged. If two verbs mean the same operation in this particular system, choose one consistent description. If their effects differ, preserve both names and explain the difference where it affects the task.
Explain real changes of state instead of hiding them
An object may legitimately acquire a new name after an action. A draft becomes a submitted request. A temporary selection becomes a saved collection. Readers need to know when that transition occurs, especially if later instructions refer to the new name.
In the fictional example, a useful bridge could read: “After you submit the draft request, it appears under Submitted requests.” This sentence identifies the action, the earlier state and the later location. It is more informative than switching from “draft” to “submission” without explanation.
Also check whether a word describes a status or a requirement. “Optional attachment” and “pending attachment” do different jobs: one describes whether an attachment is needed, while the other may describe progress. The guide to making required and optional instructions clear covers the first distinction in more detail.
Handle a mismatch without inventing a new interface
Sometimes a product’s visible label is awkward or inconsistent. Instructions still need to help readers find the real control. Quote or clearly identify that label, then explain it in ordinary language if necessary. Do not silently replace a button’s name with your preferred wording and leave the reader searching for a control that does not exist.
If labels differ between versions or account types, verify which version the article covers. Describe only the differences you can confirm. A vague sentence such as “your screen may vary” does not resolve a specific mismatch, and a guessed alternative can send readers down the wrong path.
For a longer process, a small worked example can show how names persist across several stages. The approach in explaining a process with a worked example is useful when the transitions need more context than a single instruction can provide.
Finish with a recognition test
Ask a reviewer to follow the procedure using only the text and the actual interface. At each step, have them identify the object to act on and the control that performs the action. Record moments of hesitation as questions to investigate, rather than immediately assuming every hesitation proves a terminology problem.
Then check the revised nouns and verbs once more from beginning to end. Confirm that the last instruction names the result the opening promised. Start with one procedure, repair its mismatches, and retain the verified labels for its next update. The immediate goal is a task whose objects and actions stay recognizable all the way through.
Photo: Artboard Studio / Unsplash. Illustrative stock photograph.