# STE Review Checklist

Use this checklist as an operational review aid. It is not a replacement for the official
ASD-STE100 standard or dictionary. A search result identifies text to inspect; it does not prove
that the text violates a rule.

## Quick Check

Use this check for a general clarity rewrite:

- Compare the source and revision. Preserve facts, conditions, limits, units, exceptions,
  sequence, and responsibility.
- Confirm that code, identifiers, commands, paths, labels, quoted messages, and other protected
  literals did not change.
- Use explicit actors, referents, conditions, actions, and results.
- Put a prerequisite condition before the action that depends on it.
- Keep one independent action in each procedural sentence unless actions occur at the same time.
- Use one term for one concept and one wording for one repeated action.
- Separate observed facts, possible causes, and recovery actions.
- Report unresolved technical, lexical, safety, or regulatory questions.

## Full Check

Use this check for strict STE work, compliance reviews, safety text, high-risk content, or long
documents.

### 1. Meaning and Scope

- Make an inventory of actions, facts, conditions, negation, quantities, units, limits,
  exceptions, warnings, consequences, and cross-references.
- Confirm the scope of each modifier and logical connector.
- Confirm that the revision does not add a cause, risk level, requirement, or technical fact.

### 2. Vocabulary and Terminology

- Verify each general word against the official Issue 9 dictionary.
- Verify its approved meaning, part of speech, form, and use.
- Verify each technical noun and technical verb against the applicable category and project
  glossary.
- Record unverified terms instead of assuming that they are approved.
- Check abbreviations, spelling, and alternate names for the same concept.

### 3. Grammar and Sentences

- Check active voice, permitted verb forms, articles, complete constructions, and explicit
  referents.
- Inspect each `-ing` form, passive construction, modal verb, and multi-word verb in context.
- Split overloaded sentences and complex alternatives.
- Confirm that connecting words show the intended logical relation.

### 4. Procedures and Descriptions

- Classify each section as a procedure, description, safety instruction, or mixed content.
- For procedures, use imperative commands and put prerequisite conditions first.
- For descriptions, present information gradually and keep one topic in each paragraph.
- Put complex sequences and alternatives in vertical lists.

### 5. Length and Mechanics

- Apply the Issue 9 word-count method.
- Check the 20-word procedure limit and the 25-word description limit.
- Check the six-sentence description-paragraph limit.
- Inspect semicolons, parentheses, hyphens, and long multi-word nouns.

### 6. Safety

- Preserve the governing safety label and required wording.
- Start with the required command or condition.
- State only the known risk or possible result.
- Confirm that simplification did not weaken the safety intent.

### 7. Delivery

- Apply project, regulatory, and customer directives before general STE preferences.
- Use the correct verification status.
- List unresolved checks.
- Cite a rule number only after direct verification in an authoritative copy of Issue 9.

## Search Cues

Search for these features during a large review:

- Contractions such as `can't`, `don't`, `'re`, and `'ve`.
- Semicolons.
- `-ing` forms.
- Perfect or continuous auxiliary constructions.
- Forms of `be` followed by a past participle.
- Modal verbs such as `should`, `would`, `may`, `might`, and `could`.
- Vague referents such as `it`, `this`, `that`, `they`, and `which`.
- `and` or `then` between commands.
- Different nouns or verbs that might name the same concept or action.
- Sentences and description paragraphs above their applicable limits.

Inspect each match in context. Do not treat every `if`, `when`, `-ing` form, passive construction,
modal verb, or repeated connector as an automatic violation.