Skip to content
STE Guide

Free tool

Free ASD-STE100 Checker – Simplified Technical English Checker

Last reviewed: · Based on ASD-STE100 Issue 9

Check technical writing for common ASD-STE100 issues: sentence length, passive voice, complex words and phrases, and procedural writing problems. The check runs in your browser. Your text is not sent anywhere.
Text type

This checker is a writing aid. It finds common problems with simple rules. It does not do an official ASD-STE100 compliance check. For final decisions, use the current official ASD-STE100 specification.

What does the STE Checker check?

The checker looks for eight types of problems. Six are found automatically. Two need your own review, but the checker gives hints.

  • STE sets a maximum sentence length: 20 words for procedural sentences and 25 words for descriptive sentences. Long sentences are harder to read and easier to misunderstand. The checker counts the words in each sentence and flags the long ones.

  • Passive voice

    Automatic

    In a passive sentence, the reader does not always know who does the action. "The valve is opened" does not say who opens it. STE uses the active voice in procedures and, as much as possible, in descriptions. The checker finds common passive forms such as "is opened" or "has been removed".

  • Phrases such as "prior to", "in order to" or "utilize" make a text longer, but not clearer. The checker has a list of common complex phrases and shows a simpler alternative. The list is our own. It is not the official ASD-STE100 dictionary.

  • -ing forms

    Automatic

    STE limits the use of verbs that end in "-ing", because they can have more than one function in a sentence. "Commencing the test" is less clear than "Start the test". The checker flags -ing words that may be used as verbs. Some -ing words are part of technical names. Ignore those flags.

  • A noun cluster is a group of nouns in a row, such as "pump outlet pressure sensor cable". STE recommends no more than three words in a noun cluster. The checker flags groups that look too long.

  • Multiple instructions in one sentence

    Automatic (procedural mode)

    "Remove the cover and disconnect the cable" has two instructions. STE puts each instruction in its own sentence, unless the actions occur at the same time. This makes steps easier to follow and to check off.

  • An instruction starts with a command, such as "Remove", "Install" or "Do not". A condition can come first: "If the light comes on, stop the motor." The checker shows procedural sentences that do not start this way.

  • Words such as "should", "it is recommended" or "be careful" make instructions weak. Is the step necessary or not? STE prefers direct commands. Some of these words are in the complex-phrase list. Others you must find yourself.

How to use the ASD-STE100 Checker

  1. Paste your technical text. Use one procedure or one section at a time. Short inputs give clearer results.
  2. Select Procedural or Descriptive. Procedural text tells the reader what to do. Descriptive text gives information. The word limits are different.
  3. Click Check text.
  4. Review the detected issues. Each highlight has a short explanation. The score is only a guide.
  5. Rewrite the problem sentences. Make one change at a time and check again.
  6. Compare important decisions with the official specification. The checker cannot know your technical names, your company terms or the full STE dictionary.

ASD-STE100 Checker example

Before

Prior to commencing the inspection, ensure that the electrical power has been disconnected.

STE version

Disconnect the electrical power before you start the inspection.

What changed:

  • "Prior to" → "before". A simple word replaces a complex phrase.
  • "commencing" → "start". An -ing form becomes a simple verb.
  • "has been disconnected" → "Disconnect". The passive construction is removed.
  • The sentence is now a direct instruction. The reader knows what to do and when.

More examples

Before

The cover should be removed carefully by the technician, and then the cable can be disconnected.

STE version

Carefully remove the cover. Disconnect the cable.

Why it is clearer: Passive voice and "should" removed. Two instructions became two sentences.

Before

In order to obtain an accurate reading, it is recommended that the gauge be calibrated on a monthly basis.

STE version

Calibrate the gauge each month to get an accurate reading.

Why it is clearer: "In order to", "it is recommended that" and "on a monthly basis" removed. The sentence is now a command.

Before

Check the hydraulic pump outlet pressure sensor connector.

STE version

Check the connector on the pressure sensor at the outlet of the hydraulic pump.

Why it is clearer: A five-word noun cluster is broken up with prepositions. If the long name is the official name in your parts catalogue, keep it, but use it the same way each time.

See more than 20 before-and-after examples →

What the checker cannot do

The checker uses simple text rules. It does not understand meaning. It can miss problems, and it can flag text that is correct.

It does not know:

  • which words and meanings are approved in the official ASD-STE100 dictionary;
  • which technical names and technical verbs your company uses;
  • if your procedure is technically correct and in the right order.

A good score does not guarantee good documentation. See STE pros and cons.

Use the checker to find problems quickly. Then use the writing rules, the dictionary guide and the official specification to decide.

STE Checker FAQ

+Is this an official ASD-STE100 checker?

No. This is an independent, free tool. It is not made or approved by ASD. It finds common STE problems with simple rules. The official specification is the only authority.

+Is my text stored or sent anywhere?

No. The check runs in your browser. Your text is not sent to a server and is not saved.

+Why does the score not reach 100 for my correct text?

The checker uses patterns, not meaning. Technical names, -ing words in part names and long official part names can cause false flags. Review each flag and ignore the ones that do not apply.

+What is the difference between procedural and descriptive mode?

Procedural text tells the reader what to do. The limit is 20 words per sentence, and the checker also looks at instruction structure. Descriptive text gives information. The limit is 25 words per sentence.

+Can I use the checker for software documentation?

Yes. STE started in aerospace maintenance, but the same principles work for user guides, release notes and UI help texts.

Writing Rules →

The eight ASD-STE100 rule categories, in our own words.

ASD-STE100 Examples →

Before-and-after rewrites for procedures and descriptions.

ASD-STE100 Dictionary →

How approved words, meanings and parts of speech work.

ASD STE 100 PDF →

Where to get the official Issue 9 specification.

Check your technical text with the free STE Checker.

Open the STE Checker