The Policy Framework Policy promotes the use of plain English and consistent writing styles.
Where possible, we comply with the Australian Government Style Manual and the content on this page provides relevant examples.
The latest version of the Macquarie Dictionary will advise the preferred spelling in policy documents.
The policy framework policy defines the types of text in the University’s policy suite and the kind of material they should contain. Policy developers must take care to place:
Policy developers need to understand the distinction between governance (rule/policy), management (procedure) and guidance (guidelines). Procedures can be approved more quickly than academic or governance policies, so placing process detail in procedures enables it more easily to be kept up to date.
Only rules, policies and procedures should state mandatory requirements.
The phrase ‘is/are responsible for’ suggests accountability but does not clearly require the subject of the sentence to do something. That phrase is more accurate when someone has overall responsibility for something, or when summarising (in a ‘responsibilities’ section at the start of a text) what a role is required to do by mandatory provisions elsewhere in the text.
Charles Sturt University rules, policies, procedures and guidelines must be written in plain English so that texts are shorter and easier to read.
To write and edit for plain English, apply the following principles:
Choose the shortest, simplest, least formal word that will convey the meaning, except when you need a different word to avoid repetition,
| Use: | Instead of: |
|---|---|
before | prior to |
but | however (when introducing a qualifying clause in a sentence) |
can or may | Is/are not |
change | amend or amendment |
exam | examination |
extra, more or further | additional |
must or will | is/are required to |
start or begin | commence or commencement |
use | utilise |
Some words are used habitually in university writing, although more precise words are available. Here are some examples
Other overused words to be cautious about using are: appropriate, collaborate, deliver/deliverable, determine, differentiate, engagement, highlight, important/importantly, innovative/innovation, leverage, nominate, outcome, outline (as a verb), pedagogy, significant/significantly, sustainable, synergies.
You’ll notice that these are mostly longer, more technical-sounding words so they also breach the rule of preferring short, simple words.
Always assume that at least some of the readers will be new to the University and unfamiliar with its technical language and abbreviations.
Where possible, paraphrase technical terms: e.g., ‘the student management system’ not ‘Banner’.
It’s often more concise, however, to use a technical term, initialism or acronym. In this case, you must explain it the first time you use it in a section of the text. (This is more reader-friendly than including the term, initialism or acronym in the glossary and expecting the reader to remember there is a glossary and look it up.)
So: ‘Banner (the student management system)’, and thereafter ‘Banner’. In later sections, if it’s possible that the reader will start reading at this point without having read the earlier section, again, ‘Banner (the student management system)’ the first time it’s mentioned in the section.
Use the same approach to introducing initialisms and acronyms in the text. These save space and time, but must be explained to the reader in each section where they are used.
It looks careless if you explain an initialism or acronym and then don’t use it: for example where the text ‘Division of Student Success (DSS)’ appears, and then ‘DSS’ isn’t used again. It also looks careless if you explain an acronym or initialism and then revert to using the term or name in full.
Use 'apply', not 'submit an application'.
Application’ is a noun based on the verb ‘apply’. The principle is to use the active verb, as it’s briefer, more direct and less formal.
Another example is: ‘a partnership agreement must include’, not ‘the expected inclusions of a partnership agreement are’.
Keep an eye out for these verbal noun phrases in your writing, and replace them with verbs.
Remove words that are unnecessary to the meaning. This may require some thought at times. For example:
Words like ‘actively’, ‘specific’, ‘appropriate’ are often added for the feeling they suggest, not because they contribute to the meaning. Strike them out.
Words like ‘important/importantly’ and ‘significant/significantly’ are often redundant. Everything in a policy or procedure is by definition important and significant – it doesn’t need saying.
University writing tends to do the opposite, preferring the passive voice, which makes it unnecessarily formal, ponderous and often obscure.
The active voice is present when the subject of a sentence or clause within a longer sentence performs the action: for example, ‘candidates must carry out work’.
The passive voice is present when the subject of a sentence or clause passively suffers an action: for example, ‘work shall be carried out’.
The passive voice often leaves open the question of who is performing the action, so the passive voice makes it harder for the reader to understand what is going on. It also uses more words and tends to make sentences more convoluted.
However, there can be good reasons for using a passive voice – just not as a default.
Good reasons for using the passive voice include:
Sentences should average 22 words. They can be longer than 22 words, but not often, and when they are, they should follow the other plain English rules. Here’s an example of a sentence that is too long and tangled, from an old policy:
This sentence needs to be rewritten and broken into several sentences:
Where long sentences contain a list of points, breaking them into subclauses can make them more readable. In the last example, the last part of the sentence could also have been rewritten as:
Sentences and longer texts should present information to the reader in the order that makes it easiest to understand. This will often be a chronological narrative: ‘first this happens, then that happens’ or ‘if this happens, then that happens’.
Here’s an example of a sentence that is hard to understand, from a policy text:
Placing this in chronological order makes it easier to read:
A policy or procedure about a specific activity should follow the ‘life cycle’ order of the activity, with sections for each stage of the activity. Typical life cycle stages are:
Organising the text in an intuitive life cycle order makes it easier for readers to find provisions within a long text.
Avoid using words or phrases that exclude one gender or a particular group, for example:
Australian style uses minimal capitalisation. This means capitals are only used where necessary for the meaning.
Headings and subheadings should be in sentence case: only the first letter is capitalised, and after that only words or phrases that need capitalisation under the rules below.
The title of a named individual should be capitalised: Professor Jill Smith, the Associate Dean (Academic). But generic titles (associate deans (academic), or ‘the associate dean (academic)’ where any one of these is meant) should not be capitalised.
Organisational unit titles should be capitalised when the full title of a specific unit is used: e.g., the Faculty of Science. But outside of these cases, organisational unit titles should be lower case (‘faculty’, ‘faculties’).
The full title of a specific award should be capitalised: e.g., Bachelor of Arts. But neither types of award nor disciplines should be capitalised: e.g., ‘diploma’, ‘higher degrees by research’, ‘doctor of philosophy’, ‘arts’, ‘business’.
Committee titles should be capitalised where there’s only one such committee: e.g., ‘Academic Senate’; but not where a number of the same committee are meant, or any one of a number of committees is meant: e.g., ‘faculty boards’, ‘the faculty board’.
Use title case for publications, for example policies and procedures.
Names of forms and websites should be lower case.
Policy style of the university policy library is to use numbered clauses and lettered subclauses (note this is different to the style of the university website). Unless subclauses are a full sentence in their own right, they should:
Avoid roundabout ways of saying things, for example:
In general it’s better to use a verb instead of a phrase with a noun based on a verb, for example:
Remove redundant words, for example:
In particular watch out for sonorous pairs of nouns where one of the two contributes nothing to the meaning, like the last example here.
Self-editing and team editing
Too often university writers think more about the content of texts than they do about the reader’s experience. Many university texts give the impression that the writer stopped typing, thought, ‘Good – that’s everything it needs to say,’ and gave little or no further thought as to whether it was well said – whether it would be easy for the reader to understand.
During and after drafting, rigorous self-editing is essential. In particular, look for places where the text breaches the plain English principles above, and correct this. But also consider the order of information in sections of the text – the reader’s journey through the text.
It’s not easy to see faults with our own work; asking a colleague to give it a rigorous review is a good double-check to ensure a high standard of readability – particularly if the colleague has also integrated the plain English principles into their practice.