---
type: Skill
title: Controlled Technical Writing
description: Use when creating or revising operational prose, including specifications, plans, tasks, ledgers, runbooks, technical documentation, reports, handoffs, instructions, and system explanations.
tags: [architectonic, core-skill, writing, technical-communication, simplified-technical-english]
source_status: adapted
source_name: ASD-STE100 Simplified Technical English, Issue 9
source_url: https://www.asd-ste100.org/assets/files/ASD-STE100_ISSUE9.pdf
source_license: Reference-only; ASD copyright
risk_level: low
requires_review: false
status: reviewed
---

# Controlled Technical Writing

## Trigger

Use when creating or revising operational prose.

## Inputs

The source text, intended audience, project glossary, authority context, and
applicable language doctrine.

## Procedure

1. Preserve the exact meaning, authority, safety conditions, uncertainty,
   identifiers, paths, commands, units, and interface names.
2. Identify the approved term for each concept. Use that term consistently.
3. Replace unnecessary jargon and vague words with short, familiar words.
4. Use the active voice. Use the imperative form for instructions.
5. Put one instruction or requirement in each sentence.
6. Put each condition before the instruction or result that depends on it.
7. Use `must` for requirements, `must not` for prohibitions, `should` for
   recommendations, `may` for permission, and `can` for capability.
8. Keep procedural sentences to 20 words and descriptive sentences to 25 words
   when the limit preserves meaning.
9. Split paragraphs by topic. Use lists for sequences and alternatives.
10. Move actions, requirements, limits, and warnings out of notes.
11. Review the result against the project glossary and the official ASD-STE100
    dictionary when it is available.

## Exceptions

Preserve required forms for code, identifiers, quoted sources, legal or
standards-mandated text, approved technical terms, brand names, and explicit
creative or marketing voice. Add a plain-language explanation when exact text can
confuse the reader.

## Verification

- One term identifies each concept.
- Each requirement and instruction has one interpretation.
- Actors, conditions, units, authority, uncertainty, and expected results remain
  explicit.
- Sentence length and voice follow the language doctrine or have a documented
  reason to differ.
- No formal ASD-STE100 compliance claim appears without a full dictionary check
  and qualified review.

## Failure Modes

- Simplifying text until it becomes false or incomplete.
- Replacing exact technical terms with vague common words.
- Using different terms for the same item.
- Hiding actions or limits in notes.
- Treating a style review as formal ASD-STE100 certification.