Simplified Technical English | Shufrans TechDocs Home // Simplified Technical English | Shufrans TechDocs

 

What is Simplified Technical English?

Formerly known as AECMA Simplified English, Simplified Technical English is an international standard (ASD-STE100 Simplified Technical English) that helps to make technical documentation easy to understand.

find out more

Writing in Simplified Technical English

Learn how Simplified Technical English significantly improves text readability and user-friendliness from our industry examples ranging from data protection solutions to consumer electronics. Alternatively, send us some of your documents to qualify for a one-time free STE compliance check.

find out more

Writing in ASD-STE100

ASD-STE100 shortens your product’s time to market by standardising content and improving the rate of content-re-use. Our industry writing samples from the Aerospace & Defence sector will demonstrate exactly how good ASD-STE100 writing should work for you! Alternatively, send us some of your documents to qualify for a one-time free STE compliance check.

find out more

STE training & consultancy

Shufrans TechDocs offers a range of customised ASD-STE100 training solutions and consultancy services that will help you expand your knowledge of Simplified Technical English (STE) writing. Our training workshops cover the fundamental principles of STE writing rules as well as the practical and accurate application of these rules.

find out more

 

Shufrans TechDocs helps great companies like yours

 

 

  • I had the pleasure of working alongside Shumin for several projects during her time at the Singapore Aviation Academy. She is what I would call a balanced manager - always keeping a cool head regardless of the obstacles we had faced as a division. Her outstanding abilities include bringing inspiration to her team and her effortless presentation skills.
    Nasuha Rahim Executive, Civil Aviation Authority of Singapore
  • I am giving this training a 10/10. There was a good introductory and explanation to describe the 2-day training seminar. Rule 1.1 0 lets me use words that are: approved in the dictionary / technical names / technical verbs and is one rule I like very much because of its flexibility. I think rule 1.1 is the most critical and important for STE dictionary. Sometimes I have to use non-approved words as an exception, but I will try to keep this rule 1.1 in my documents for good measure. Although some of the exercises were tricky, they remind me of each rule application at that time. So they were practical for my role as a technical writer. I want to recommend this course to current technical writers in Korea or engineers who are interested in writing their own documents effectively.  
    Seung Eun Lee, Technical Writer DB HiTek
  • My favorite STE writing rules: * Rule 1.9 and Rule 1.10 When you must select a technical name, use one which is short and easy to understand. Both rules ensure a better understanding of technical contents. * Rule 3.6 Do not use a past participle with a helping verb to make a complex verb. Past tenses may be adequate for marketing texts due to stylistic reasons, but not for technical contents, where precision and clarity play a major role. * Rule 5.1 Keep procedural sentences as short as possible. The description of procedures in technical manuals has to be as simple as possible to avoid confusing the reader.
    TCLoc Master's Student University of Strasbourg
  • Best STE rules for my learning are: - Use simple verb tenses - Put commands first in warnings and cautions - Use active voice - Do not use present participles or gerund.
    TCLoc Master's Student University of Strasbourg
  • Shumin gave us a an all-rounded presentation to Simplified Technical English. Personally, rule 1.3: To use only approved words with their approved meaning holds the key to successful controlled language implementation. Rules 3.4, 3.6, 4.1, 5.3, and 5.5 are also among my favourites. The approved verb TO MAKE SURE THAT can come in very handy for technical writers as well. The presentation of STE rules offers quite a detailed overview that includes not only language rules but good, old technical authoring principles in general. It has been very helpful for us to learn and understand the concept of STE. I have found Shumin to be very competent in STE and will defnitely recommend her course!
    Eric, Head of Corporate Technical Documentation (CTD) Schindler
  • Frans has rare skills in global demand - indeed when I met him he was spending much of his time crossing oceans to find creative foreign language solutions for his clients' advanced technical publications challenges. Frans has a special knack for understanding the Asian markets and his brilliant decision to develop business out of Singapore should serve him well regardless of the economic climate. I wish him all the best of success.
    Tim Gottschalk Consultant, Boeing
  • I find that STE rule 2.1 extremely useful in technical documentation to avoid ambiguity. Rule 3.6 is one of my favorites because you need to master well syntax and language to always avoid passive voice. It was a good excercise, thanks Shumin for this interesting and challenging topic!
    Master's student, TCLoc for Technical Communication & Localisation University of Strasbourg
  • As advisor to her ASD-STE100 Simplified Technical English on-the job-training, Shumin adopts a very structured approach to learning. She observes, absorbs and analyses to come up with relevant and insightful questions as well as ideas regarding the subject matter and improved ASD-STE100 training methods. Shumin is a very driven and highly intelligent professional who works very well either independently or as part of a team. She has strong analytical skills and expresses herself very well both verbally and in writing. Her sense of responsibility and passion about achieving the set objectives while meeting and exceeding clients' expectations is very inspiring and is a great asset to the company and its customers alike.
    Frans Wijma, PhD ILS expert, trainer & consultant, Shufra Ltd
  • I love how you can apply the concept of STE to many industries whether or not you choose to work as a technical writer. Shumin was very clear in her instructions and it's too bad I could never catch up on time to review her entire courses and pose questions "in real time". The rules concerning the technical verbs and names + the categories for the different exceptions makes STE a very flexible standard that responds to the needs of specific users.
    TCLoc Master in Technical Comunication & Localisation 2018 University of Strasbourg
  • Frans Wijma has done excellent work for The Boeing Company in providing translation, translation system design, custom translation processing software, translation tool training, and translation system troubleshooting and tuning. He is familiar with the data structures of technical publications and has the ability to create solutions for interfacing the customers data with translation aid systems. Top qualities: Great Results, Personable, Expert.
    Mike Case Boeing
  • I had the pleasure of working alongside Shumin for several projects during her time at the Singapore Aviation Academy. She is what I would call a balanced manager - always keeping a cool head regardless of the obstacles we had faced as a division. Her outstanding abilities include bringing inspiration to her team and her effortless presentation skills.
    Nasuha Rahim Executive, Civil Aviation Authority of Singapore
  • I am giving this training a 10/10. There was a good introductory and explanation to describe the 2-day training seminar. Rule 1.1 0 lets me use words that are: approved in the dictionary / technical names / technical verbs and is one rule I like very much because of its flexibility. I think rule 1.1 is the most critical and important for STE dictionary. Sometimes I have to use non-approved words as an exception, but I will try to keep this rule 1.1 in my documents for good measure. Although some of the exercises were tricky, they remind me of each rule application at that time. So they were practical for my role as a technical writer. I want to recommend this course to current technical writers in Korea or engineers who are interested in writing their own documents effectively.  
    Seung Eun Lee, Technical Writer DB HiTek