error · Section 5: Procedural writing
Rule 5.2: Write only one instruction per sentence unless actions are simultaneous
Write only one instruction in each sentence of a procedure, and clearly show the sequence of work steps, usually with numbers or letters. Write more than one instruction in a single sentence only when the actions occur at the same time; you may also write more than one sentence within a single work step when the actions are simultaneous or when a result or limit follows immediately after the action.
This rule needs human judgement. A checker can flag candidates; it cannot decide.
What a checker looks for
A clear deviation from the rule.
- Flag a sentence that contains two or more sequential, independent instructions joined by "and" or a comma where the actions do not occur at the same time — these should be separate numbered or lettered work steps instead.
- Flag a procedure split into two separate numbered steps when the two actions actually occur at the same time — these should be one sentence joined by "and".
- Sequence is usually, but not always, shown with numbers or letters — do not flag a compliant unnumbered sequence of steps solely for lacking numeric/letter labels; only flag when the missing sequence indicator actually leaves the order of steps ambiguous.
What this rule does not cover
- Two actions joined by "and" that genuinely happen at the same time (e.g. "Cut and remove the wire.") are compliant, not a violation.
- A second sentence within the same work step that states a result, limit, or an action occurring immediately after the first is compliant and should not be split into a new numbered step.
How to fix it
If the instructions are independent and sequential, split them into separate numbered or lettered work steps with one instruction each. If the actions occur at the same time, keep them as a single sentence joined by "and". If a sentence states a result or limit immediately following an action, keep it as an additional sentence within the same work step.
Constraints on the fix
- Do not split instructions for actions that must occur at the same time into separate numbered steps.
- Do not merge genuinely sequential, independent instructions into a single sentence.
Examples
Not STE: Set the TEST switch to the middle position and release the SHORT-CIRCUIT TEST switch.
STE: A. Set the TEST switch to the middle position. B. Release the SHORT-CIRCUIT TEST switch.
Not STE: Hold the panel in its open position. Then install the fastener.
STE: Hold the panel in its open position and install the fastener.
Related rules
Where this fits in AI governance
A rule a checker can test is a rule a model can be held to. The same discipline, on the governance side of this site.
- Improper output handling
A procedural instruction acted on without a check is the same failure whether the reader is a technician or a downstream system. - Human-in-the-loop review
Procedures are where a generated instruction should not reach a reader without a person having read it first. - Output validation guardrails
A controlled language is a checkable output constraint. This is the control that treats model output as something to be checked rather than trusted.
Source
ASD-STE100 Issue 9, Section 5 - Procedural writing, page 1-5-2.
This page is commentary and does not reproduce the standard. About this rule pack.