Controlled language methodologies already exist for some languages, particularly English (e.g. Simplified Technical English (STE)); there’s nothing to stop you adopting these, although it’s always possible to devise a set of company-internal rules according to your own requirements. The extent to which you can or must follow the rules when developing a controlled language is nowhere set in stone. If you use a Style Guide or have looked into this subject at some time in the past, then it is quite possible that you will have already come across one or more of the points mentioned above. In fact, every Style Guide that concerns itself with the definitions and restrictions governing the use of language will be mapping out a more or less precisely defined controlled language.
A Style Guide is also a way of making people aware of the parameters of the controlled language. To monitor adherence to these parameters, specialist software, known as Controlled Language Checkers, and modern component content management systems, such as our own SCHEMA ST4, also exist that provide authors with the relevant tools. An Authoring Memory function will suggest permitted sentences and formulations as the author types. Adherence to the permitted vocabulary, sentence length, sentence construction, etc., can, for example, be checked automatically and corrected as soon as any non-compliance is detected.