Write Conditional Instructions Readers Can Follow

Write each conditional instruction around a decision readers can make from the information available at that point. State the condition, give the corresponding action, and explain where that path rejoins the main procedure. Test every path with a concrete example so skipped steps and missing inputs become visible before layout.

Locate decisions hidden inside ordinary prose

Practical instructions often contain branches without clearly presenting them as choices. A sentence such as “adjust the plan if necessary” asks readers to recognize an unspecified condition and invent the appropriate response. Search the draft for words such as “if,” “unless,” “otherwise,” and “as needed.” For each occurrence, identify the decision the reader is actually being asked to make.

Distinguish meaningful branches from optional commentary. A note about an alternative writing preference may not need a separate route through the procedure. A choice that changes required inputs or the next action does. Keep the main task in view while deciding how much structure to add. Overexplaining minor choices can make a straightforward procedure harder to follow, while hiding consequential ones creates uncertainty at exactly the wrong moment.

Give the reader an observable condition

A usable decision point tells readers what to examine. “If your plan is too ambitious” may be difficult to apply, while “if the activities require more time than the session allows” identifies a comparison. Define the relevant terms and inputs before asking for the decision. If judgment remains necessary, explain the factors that should guide it instead of presenting the condition as mechanically certain.

Consider a chapter about preparing a community workshop. Readers may need a shorter route when fewer preparation hours are available. The manuscript should establish what work must be completed and how the author expects readers to estimate it. Otherwise, a branch based on “limited time” gives no reliable way to choose a route. The decision needs enough context to be useful without pretending that every reader’s circumstances are identical.

Make each path complete enough to use

After the condition, state the action for that path. Check whether the action requires information introduced only on a different path. This is a common drafting error when a section evolves through revisions: one route says to use the completed comparison table, but readers following that route were never told to create it. Either supply the missing step or change the instruction to match their actual state.

Use distinct labels when several alternatives must be referenced later. Avoid relying entirely on visual position, such as “choose the option on the right,” because the arrangement may change in another format. A short descriptive label can remain understandable across layouts. Keep the wording consistent between the decision point, the action, and any diagram that illustrates the same procedure.

Explain where the routes rejoin

Readers need to know when a special path ends. After an alternative action, identify the next shared step or the condition that returns them to the main procedure. Without that instruction, they may perform both alternatives, skip the remainder, or repeat an earlier task. A clear return point can be as important as the initial choice, especially in a longer chapter.

Check that readers arrive at the return point with compatible outputs. If one route produces a detailed schedule and another produces only a priority list, the next step cannot simply say “use your schedule” for everyone. Explain how the outputs are used or add the necessary transition. This review tests the logic of the procedure rather than merely checking that every arrow or heading has a destination.

Walk through every route before exporting

Choose a concrete example for each branch and follow the instructions without filling gaps from your own knowledge. Record the starting inputs, decisions, actions, and final result. Ask a reviewer to try at least the routes most likely to confuse the intended audience. When a path fails, repair the prose and repeat that walkthrough, including the shared steps that come after it.

Finally, inspect the exported manuscript in its intended format. A decision label separated from its action by an awkward page break can undermine otherwise clear instructions. Check headings, references, diagrams, and reading order using the relevant formatting guidance. Preserve the walkthrough examples in your working notes so later edits can be tested against the same paths instead of relying on a general impression that the procedure still makes sense.