Plain language

Last changed: 02 February 2024

Plain language is about making information accessible. The intended audience should be able to easily find what they need, understand what they find, and use that information.

Why plain language?

Plain language means more efficient communication. Information adapted to the intended audience makes communication more efficient as it reduces the risk of misunderstandings and misinterpretations. 

It strengthens our brand. Accessible information increases the quality of communication, which in turn strengthens the SLU brand.

It is an obligation. According to the 2009 Language Act, the language of the public sector 'is to be cultivated, simple and comprehensible'.

How to write in plain language

Following the steps below will help you write a readable and usable text. Plan your text, structure it according to the readers' needs, use concise and correct language and remember to proof-read. If possible, also ask a colleague for feedback.

Plan

  1. Define your target audience and purpose. Who are you writing for and why? What do you want your readers to know or be able to do when they have read your text? Use one or two introductory sentences to explain this.

  2. Plan your content. Starting with headings and subheadings is often a good way to plan your text. Which information do you need to include? What is already known to the readers and can be left out? If some information is not relevant to all readers, you can indicate this by using an informative subheading.

Structure

  1. Structure your content in a way that makes sense to the reader. This usually means that the most important information comes first. How else will the readers be able to decide if they need to read the whole text or not? 

  2. Divide the text into logical units. One idea=one paragraph. Start with a topic sentence and expand this in the paragraph. 

  3. Be generous with subheadings, and make them informative. Creating 'signposts' for the reader makes navigating the text easier.

  4. Use lists for longer enumerations and for instructions.

  5. Do not fill your pages, but make sure to leave plenty of space on the page as this improves readability.

Write

  1. Keep it short, and cut any unnecessary words. Too much information can obscure the main message, and the value of a document does not increase the longer it gets.

  2. Vary sentence length. Too many very long, or very short, sentences will have a negative impact on the readability of a text. Varied sentence length makes for a more comfortable reading rhythm.

  3. Keep it simple. Use words that can be understood, avoid jargon and explain necessary specialist terms. 

  4. Help the reader follow your train of thought by using connectors such as 'but', 'however', 'so', 'because' to link your paragraphs.

  5. Avoid too many passives. Although there are times when the passive works fine, active voice often works better, and there are cases where the passive may confuse the reader because it is not clear who performs an action. Write 'X sent the document', not 'The document was sent by X'.

  6. Cut out excess nounsVerbs are more direct and less abstract. For example, write 'consider', not 'give consideration to'. Write 'evaluate', not 'carry out an evaluation of'.

  7. Avoid grammar mistakes. Grammar mistakes reduce readability and may make the reader doubt the content.

Check

  1. Always proofread your text. Running the grammar and spell checkers in Word does not count as proofreading. If several writers contribute to a text, it is vital to have one person read the whole text to guarantee consistency.

  2. Test your text. Ideally, ask someone from your target audience to read the text and give you feedback. If this is not possible, ask a colleague.

Checklist and other resources

Checklist for plain language

You may find the SLU checklist for plain language useful when you revise texts, your own or those written by colleagues.

Other useful resources

There is no shortage of websites dedicated to plain language - below is a suggestion for getting started.