Guidance

Functional Standards writing style guide

Published 30 September 2024

1. Use plain English

You should write your standard using plain English and with the reader in mind.

Plain English is easier to understand and does not mean oversimplifying your text nor changing its meaning.

Keep your sentences short, with one idea per sentence. Leave out words you don바카라 사이트t need. Use lists when you can. Phrase your points positively where it makes sense.

Be careful with your punctuation; punctuation can completely change the meaning.

Reduce jargon where you can. Don바카라 사이트t define words that have an evident, plain English, meaning. Avoid acronyms.

Use the present tense; standards are not able to predict the future!

Notes and examples may be used for giving additional information intended to assist the reader.

No requirements, recommendations or permissions should be included in a note. Each clause needs to be numbered so it can be referred to accurately.

Each functional standard should be written:

- to contain mandatory (requirements) and/or advisory elements (recommendations)

- as outcome based, stating what is needed, rather than how activities are to be done.

- for long shelf life, and not contain elements which are likely to change, such as job titles

- to be agnostic to proprietary solutions and methods unless the government has adopted them

2. Use the resources

Use the template to ensure consistent 바카라 사이트look and feel바카라 사이트. The following sources should be used:

- The common glossary of definitions used in functional standards.

- Shorter Oxford English Dictionary for the meaning of words.

- 바카라 사이트 Digital Service Style Guide .

3. Be clear on the accountabilities

All accountabilities in a standard should state who the role is accountable to and what they are accountable for. For example: 바카라 사이트The project manager is accountable to the senior responsible owner for the day to day management of a project바카라 사이트바카라 사이트.

Some roles will be accountable to different people for different things 바카라 사이트 roles may not be shared.

4. Be precise in your writing

It should be clear, when reading a standard, which parts are mandatory (i.e. requirements), which are recommendations, which give 바카라 사이트permission바카라 사이트 and which denote a 바카라 사이트possibility and/ or capability바카라 사이트.

The context and preferred words to use are shown below.

Word Implications Notes
shall Requirements 바카라 사이트 content from which no deviation is permitted if compliance with the document is to be claimed. Do not use 바카라 사이트must바카라 사이트 as an alternative for 바카라 사이트shall바카라 사이트.Do not use 바카라 사이트may not바카라 사이트 instead of 바카라 사이트shall not바카라 사이트 to express a prohibition.
should Recommendations 바카라 사이트 content denoting a suggested possible choice or course of action deemed to be particularly suitable without necessarily mentioning or excluding others. 바카라 사이트shoulds바카라 사이트 are to be met on a comply or explain basis
may Permission 바카라 사이트 expression denoting approval, consent or opportunity to do something. Do not use 바카라 사이트possible바카라 사이트 or 바카라 사이트impossible바카라 사이트 in this context
might Possibility 바카라 사이트 expression denoting expected or conceivable outcome. Use in informative text only
can Possibility and capability 바카라 사이트 expression conveying expected or conceivable outcome and the ability to do or achieve a specified something. Use in informative text only
will Ambiguous term, do not use
must Do not use except in a legal context
is/are A description