ASD-STE100 Simplified Technical English: Clearer AI Explanations Without Losing Meaning
By Gaurav Agarwal · Sources checked October 18, 2026
ASD-STE100 Simplified Technical English is a controlled language standard for technical documentation, with writing rules and a dictionary. Issue 9, dated January 2025, contains 53 writing rules in nine sections. You can request the official PDF free of charge. Its clarity principles can help with an AI explanation, but an informal rewrite is different from a checked STE document. Official overview, free-copy instructions.
The practical question is whether the reader can understand the same facts with less effort. A shorter answer that drops a condition, changes a technical term or removes an exception has failed that test.
This guide explains the distinction, then works through an original editing exercise you can apply to product explanations and documentation.
What ASD-STE100 Simplified Technical English actually means
STE is more specific than a request to “use simple words.” Its rules and dictionary control how language is used. The dictionary gives approved meanings and parts of speech; the rules also accommodate subject-specific technical nouns and verbs. A necessary technical term does not automatically need replacing with an everyday synonym. Source: the official STE FAQ.
The standard grew from work on aerospace maintenance documentation. Its official overview describes use beyond that original setting and identifies Issue 9, dated January 2025. Source: About STE.
For an everyday explanation, those origins offer a useful way to think: remove ambiguity without removing what the reader must know. For work that actually requires STE conformance, use the standard's rules, vocabulary and relevant terminology requirements. The name of the standard in a prompt is not a substitute for checking them.
| Your task | Useful approach | What still needs review |
|---|---|---|
| Make an explanation easier to read | Ask for shorter, clearer language while preserving source facts | Meaning, terminology and completeness |
| Produce documentation that must conform to STE | Work from the applicable standard and terminology | Rule-by-rule and vocabulary review by a competent reviewer |
| Publish a product explanation for buyers | Combine clear language with approved product evidence | Claims, scope, sources and editorial approval |
These are different deliverables. Decide which one you need before judging the output.
Four examples of what STE controls
The official FAQ gives these concrete distinctions:
| FAQ point | What it means for a writer |
|---|---|
| Choose an approved synonym | Use start instead of begin, commence, initiate or originate in the FAQ's example |
| Check the approved meaning and part of speech | The FAQ permits fall for movement under gravity, not as a substitute for decrease; familiar spelling alone does not settle usage |
| Put a necessary condition before the work step | If the reader must know a condition before acting, put it first; this is not a claim that every conditional clause must always lead |
| Use the stated language basis | Approved meanings and spelling use American English and Merriam-Webster's dictionary |
The standard also permits subject-specific technical nouns and verbs under its rules. A necessary component name does not become unsuitable merely because it is outside the core dictionary. These examples introduce the method; they do not replace the full standard.
Check the edition before using a rule list
Search results can mix editions and types of material. A dictionary page, training brochure and conference abstract may all be relevant, but they do not perform the same job as the applicable standard.
Here is a concrete source comparison from October 18, 2026:
| Material | Edition mentioned | How to use the result |
|---|---|---|
| Official ASD overview | Issue 9, January 2025 | Starting reference for identifying the issue |
| Shufrans training brochure, PDF page 25 | Calls Issue 7, January 2017, current | Recognize the older reference before using its rule guidance |
| tekom conference abstract | Offers information about Issue 8 | Treat the session abstract as an edition clue, not the latest standard |
The different issue numbers do not make every older explanation useless. They tell you to check which edition your work requires. Keep that edition, its dictionary and the project's terminology guidance together. Do not assemble a compliance claim from whichever rule summary and word list happen to be easiest to find.
Get the standard and choose the right training route
Use the official downloads page, then Fill in the request form, to request the free Issue 9 PDF. The current official form asks for an email address, name and surname, country, organization, field of activity and whether you are a new STE user, plus data-collection consent. Company website and news-update email fields are separate optional entries. Read the form's linked privacy policy before supplying your information.
Choose the next resource according to the work you actually need to do:
| Your need | Official route | Boundary to check |
|---|---|---|
| Read the applicable rules and dictionary | Request Issue 9 through the official form | A summary, older extract or course handout is not the standard |
| Learn to write or review STE documents | Use the accredited-trainer list and the training guidance | Check STEMG membership/partnership or UNINETTUNO certification, relevant industry experience and references |
| Become an STE trainer | Check the UNINETTUNO route described on the training page | The page says STEMG members/partners and UNINETTUNO-certified non-STEMG trainers cannot themselves certify other trainers |
| Use AI to assist a draft | Keep ASD-STE100 as the primary reference and retain human review | The downloads page identifies oversight, accountability, confidentiality and quality assurance as responsible-use concerns |
This separates getting the document, learning to apply it and qualifying to train others. A general technical-writing credential is not, by itself, evidence of STE accreditation. Check the current official list and the provider's scope before choosing a course.
Why “80 percent STE” cannot settle the question
An informal percentage does not say which rules were applied, which words were checked or which errors remain. It also gives no reason to assume that the omitted part is harmless. A missing condition can matter more than several tidy sentences.
The official downloads page describes a white paper about responsible AI use in STE environments, including human oversight, accountability, confidentiality and quality assurance. It identifies ASD-STE100 as the primary reference. Source: STE's AI white-paper description.
That gives you a better instruction for ordinary writing: state what must improve and what must remain unchanged. If you require formal conformance, say so and arrange the appropriate review. Do not relabel a general clarity edit as a certified result.
The training page tells writers they “must use only one reference: the ASD-STE100 document. There is no substitute for it.” Source: official training guidance.
A worked example: shorter, but still technically complete
Consider this fictional system description. Its retry threshold, error code and status name exist only for this exercise; they are not instructions for a real service.
Source passage
Following the occurrence of three unsuccessful connection attempts during a period of 60 seconds, automatic retries are discontinued by the client, with an E17 error being recorded, and although queued jobs remain in a pending state, a manual retry may be initiated by the operator only when the service status is Ready.
The sentence contains useful information. The problem is the effort needed to separate its conditions and actions.
An edit that loses meaning
If a connection fails, retry when the service is ready.
This version is easy to read and inadequate. It replaces a specific failure condition with any failed connection. It drops the client's automatic behavior, the error code and the queued jobs. It also makes the retry instruction sound more direct than the source's permission.
A clearer edit that preserves the stated facts
If three connection attempts fail within 60 seconds, the client stops automatic retries and records error E17. Queued jobs remain pending. The operator may retry manually only when the service status is Ready.
This is an editorial clarity example, not a claim that every word and construction has passed STE conformance review.
| Fact to retain | Present in the clear edit? | Why it matters |
|---|---|---|
| Three unsuccessful attempts | Yes | One failure is not the stated trigger |
| A 60-second period | Yes | The time condition remains part of the trigger |
| The client stops automatic retries | Yes | The actor and automatic behavior remain explicit |
| Error E17 is recorded | Yes | The identifier stays exact |
| Queued jobs stay pending | Yes | Their state has not silently changed |
| The operator may retry manually | Yes | Permission has not become a requirement |
| The service status must be Ready | Yes | The prerequisite and status label remain visible |
The comparison is more useful than asking whether the revised paragraph “sounds technical.” You can point to each retained fact and to the sentence that carries it.
Give the editing request explicit boundaries
For a normal product explanation, a request like the following makes the intended job clearer than an undefined compliance percentage:
Rewrite the passage for a technically interested reader who is new to this topic. Use clear technical English inspired by STE principles. Keep the original facts, conditions, numbers, units, identifiers and uncertainty. Use the same term for the same concept. Name the actor when the source identifies one. Separate actions from their prerequisites. Do not fill missing facts with guesses. After the rewrite, list any information you removed or could not interpret. Do not claim that the result conforms to ASD-STE100 without a separate conformance review.
This is a proposed editing request, not a report of a model test. Adjust it to the source and the reader. If you cannot identify the audience or the facts that must survive, resolve that before asking for a rewrite.
For the fictional retry example, the input should include the source passage and the seven retained facts in the table. The request then has a concrete boundary: improve expression without inventing a new retry policy.
Review the result in two passes
First, compare the meaning
Read the source beside the revision. Look for changes to:
- Conditions: Did “if three attempts fail” become “if an attempt fails”?
- Numbers and units: Did the time period survive with the same unit?
- Actors: Is it clear what the client does and what the operator may do?
- Permission and obligation: Did “may” become “must,” or the reverse?
- States and identifiers: Are Ready and E17 preserved accurately?
- Limits: Did the revision drop an exception or turn a possibility into a guarantee?
If a sentence has become clearer but one of these facts is missing, restore the fact before polishing further. Do not accept a rewrite simply because it is shorter than the source.
Then improve the language
Once the meaning is stable, split sentences that carry several separate ideas and remove phrases that contribute nothing. Google's technical-writing course recommends a single main idea per sentence and shows how embedded lists can become separate sentences or lists. Source: Short sentences.
Use active voice when it makes responsibility clearer. In the example, “the client stops automatic retries” identifies the actor more directly than “automatic retries are discontinued.” Google's course explains this actor-and-action distinction. Source: Active voice.
These are editing tools, not instructions to erase every qualifier or turn all prose into commands. The source's conditional meaning still governs the revision.
Preserve technical vocabulary when it earns its place
Replacing every unfamiliar word can make an explanation less precise. In the example, “queued jobs remain pending” carries a specific state. Replacing it with “the work is fine” would be easier vocabulary and worse information.
Keep a small terminology note for the passage: the term, its meaning in this source, and any exact label the reader must recognize. Define a necessary term at first use, then use it consistently rather than cycling through synonyms for variety.
For definitions, consult the authoritative documentation for the subject. Google's developer word-list guidance makes that distinction between editorial usage advice and technical definitions. Its word list is not the ASD-STE100 dictionary. Source: Google developer word list.
If the source itself uses a term inconsistently, identify the conflict instead of silently choosing a meaning. A polished contradiction is still a contradiction.
FAQs
What is ASD-STE100 Simplified Technical English?
It is a technical-documentation standard with specific writing and vocabulary rules, as explained above. A general request for plain language is a different editing brief.
Can I use its ideas for AI explanations outside aerospace?
You can use a clarity-focused editing approach for other technical explanations, and the official STE overview describes use beyond aerospace maintenance. Keep informal inspiration separate from a claim that the output conforms to the full standard.
Does asking for 80 percent compliance certify the result?
No. An informal percentage does not establish which requirements were checked or whether the text conforms. Use explicit editorial goals for a general rewrite and the applicable standard plus competent review when formal conformance is required.
Should I remove all technical terms?
Keep necessary terms and explain them for your reader. Do not replace a precise state, identifier or component name merely to use an easier word.
Can I trust an AI's statement that the rewrite is compliant?
Keep human oversight, accountability and quality assurance in the process, and ASD-STE100 as the primary reference. Those are the responsible-use topics identified on the official downloads page. An AI's assertion is not a record of the requirements your reviewer checked.
Where do I get the official standard and accredited training?
Request the free Issue 9 PDF through the official downloads page. Use its separate accredited-trainer list and training guidance to check a provider's qualifications and scope. A request for the document is not course enrollment.
For your next explanation, identify the facts that must remain true, revise the language, then compare the result with that list. If the sources disagree, resolve the conflict before treating the clearer version as usable instructions.
Idea credit: thevarunmayya's reel introduced the prompting topic. The source checks, fictional example, editing request and analysis here were developed separately.