warning · Section 4: Sentences
Rule 4.3: Use a vertical list for complex text
When a sentence would otherwise be long because it includes many items (such as parts, components, or documents) or many actions, present those items as a vertical list instead. Introduce the list with a colon, mark each item consistently (dash, bullet, letter, or number), start each item with an uppercase letter, and punctuate the items according to whether each is a full sentence.
This rule needs human judgement. A checker can flag candidates; it cannot decide.
What a checker looks for
Usually a deviation, and context can excuse it.
- Flag a long sentence that strings together multiple items or steps with commas/"and" where a vertical list would clearly be easier to read and understand — the standard sets no specific item-count threshold, so judge by length/complexity and readability rather than a fixed number of items.
- In an existing vertical list, flag a missing colon at the end of the introductory clause before the first item.
- Flag inconsistent capitalization, incorrect end punctuation (a comma or semicolon at the end of an item, a missing period on a full-sentence item, a period on a non-full-sentence item, or a missing period after the last item), or a list that mixes procedural (imperative) and descriptive items together.
- Flag a vertical list where an item does not connect clearly and correctly back to the introductory clause before the colon.
What this rule does not cover
- A list item that is not a full sentence correctly has no end-of-item period; only the final item in the list takes a period.
- A sub-list flattened into the main list at a single indentation level (rather than nested) is the compliant layout, not an error.
How to fix it
Convert the introductory clause to end in a colon, then list each item on its own line with a consistent marker, capitalized, each ending in a period only if it is a full sentence, with a period always after the final item.
Constraints on the fix
- Keep all items at a single list level — flatten any nested sub-list into a parenthetical or in-line note rather than nesting it (this is how the standard's own worked examples handle an item that itself has sub-items).
- Do not mix procedural and descriptive content within the same list.
Examples
Not STE: The wheel assembly comprises the tire, the tube, the spokes, the spoke fittings, the valve, and the hub.
STE: The wheel assembly has these parts: - The tire - The tube - The spokes - The spoke fittings - The valve - The hub.
Not STE: If the RAT is retracted, remove the tag, open the isolating valves and, ensuring that there is no possibility of fouling, slowly extend the RAT to its full stroke. Close the isolating valves; tag "DO NOT OPERATE." Release the DOWN pressure.
STE: If the Ram Air Turbine (RAT) is retracted: (a) Remove the tag. (b) Open the isolating valves. (c) Slowly and fully extend the RAT and make sure that it does not touch other parts. (d) Close the isolating valves. (e) Tag the isolating valves with "DO NOT OPERATE." (f) Release the DOWN pressure.
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.
- Testing AI systems
Sentence-length and structure rules are the part of the standard a script can check without a model. - LLM governance, operationally
Prompt, rule pack and model version are the assembly that determines the output. Governing the output means governing the assembly. - 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 4 - Sentences, page 1-4-4.
This page is commentary and does not reproduce the standard. About this rule pack.