Standards & Consultancy

At Shufrans, we work according to international technical documentation standards such as S1000D, S2000M, ATA-iSpec 2200 and Shipdex, while having the flexibility to deal with your specific requirements.

Read more

Technical Writing

An important aspect of content development is technical writing. At Shufrans TechDocs, we focus on clarity in documentation. Therefore, we ensure that language is not an obstacle for users to read and understand the information to be conveyed.

Read more

Simplified Technical English

ASD-STE100 Simplified Technical English (STE) is an international writing standard that helps to make technical documentation less ambiguous, easier to understand and faster to translate.

Read more

Certified ASD-STE100 Training

We are the global leader in ASD-STE100 training and consultancy. Our certified Simplified Technical English training workshops are conducted by seasoned industry experts.

Read more

  • Shumin is personable and easy to work with, so it was great to work together on aviation management related events during her tenure. She is a good communicator, and a consultative manager who would often involve others in problem solving, team building, and focuses her time on more important activities while providing proper recognition, which I am appreciative of.
    Joyce Tay Senior Executive, Programme & Event Management at Civil Aviation Authority of Singapore
  • Rules about noun clusters (no more than 3 words, use of hypens and use of articles/demonstrative adjectives) and sentences (use of short sentences with a max. of 20 words without contractions and write only one instruction per sentence, but also use of vertical lists and connecting words) are definitely my favourite ones! The first session with you was interesting and carried out well! Overall, however, you did a very good job, rescheduling the assignment until we finished the TCTrainNet course, and I enjoyed attending your live meetings!
    Master's student, TCLoc Programme University of Strasbourg
  • Rule 1.3: Use approved words only with their approved meanings and rule 1.4: Use only the approved forms of verbs and adjectives are rules that left an impression on me. But it is difficult to have a favourite rule as you need something from all the rules we touched upon. The STE writing rules were presented well and I cannot think of any way to do this better. Overall, exercises were well balanced between how much each person had to do. More crucially is that people understand each question.
    Erik Madsen Head of Maintenance Support, Maersk Drilling
  • The training on Simplified Technical English is a completely unique experience received so far for me. I found it to be extremely helpful for documentation writers. Section 3 of the STE Specification which deals with verbs and section 4 on how to sentence construction in STE were useful from a personal perspective. The course exercises were interactive and had a practical side to them. They help us compare our current standard of writing to an improved version in STE. I highly recommend this training to my colleagues also in the other divisions and offices.
    Krishna Kishore Vedantam Product Design Specialist, Schindler
  • The introduction to ASD-STE100 has offered me some helpful insights into the theoretical background of this technical language standard. The STE rules are governed a logical flow of technical information. I would certainly recommend this course to writers who are interested in changing the way of technical writing with buy-in from the company. Overall, I have enjoyed Shumin's presentation!
    Markus Burri, Project Manager ZetaVision GmbH
  • Simplified Technical English is an important topic for our industry. I've enjoyed learning about all the rules of STE summarised into bite-sized information over the course of 2 training days. The quality of this training has been exceptional!
    Andreas Herter, Technical Trainer Schindler
  • Introduction to Simplified Technical English (STE) was comprehensive and gave me the full picture of this technical writing standard and its related implementation processes. Rule 6.6 is something that I appreciate very much as there is a prescribed limit for the length of every paragraph. This will make the reading process much easier and user-friendly. The exercises were challenging and do take some time to get used to. Nevertheless, this part of the training session is a 9/10 for me. Shumin's delivery of the training was very clear and succinct. Her knowledge of the STE language standard spans both breadth and depth!
    Mckeena Neo Technical Writing Team Leader, Thales Group (Previously, Gemalto)
  • The trainer was extremely knowledgeable and personable. She worked with us to resolve concerns and find creative solutions to challenging word choice suggestions. My preferred STE rules include: Limited accepted words in the vocabulary, limited length of sentences, and only using words for the approved meaning. A lot of writing, especially descriptive writing, can be verbose and cumbersome. It seems to me that sometimes engineers use fancy words to sound smarter or to show how complex or advanced the technology is, but that is not always helpful to the average user. As a user, I appreciate simple and clear instructions and explanations. I am hopeful that STE will let me write simply and clearly for our users. Thank you, Shumin! I really enjoyed the presentation and learning more about STE and how to use it.
    Mickie Newsome, Technical Communications Editor Komatsu
  • I have a great pleasure to work with Shumin Chen on a number of complex technical translation projects. She is very talented, efficient and dependable, making sure to meet and exceed the customer's expectations.
    Anouar Koutchoukali Owner, A Propos Vertaalbureau
  • 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

Shufrans TechDocs helps great companies like yours

client_logo_walloffame_bw