-
Notifications
You must be signed in to change notification settings - Fork 4
A to Z of style
This style guide covers style, spelling and grammar conventions for all content published on GOV.UK Notify, arranged alphabetically.
If there’s a point of style that is not covered here, check the GOV.UK style guide.
You can search the A to Z by:
- Pressing
Ctrl
+f
on your keyboard if you’re using a PC or⌘
+f
if you’re using a Mac. - Typing the word or search term that you’re looking for.
See the GOV.UK style guide for abbreviations and acronyms.
How a user signs in to Notify. An account is tied to an email address. An account is not the same thing as a service.
Use the active rather than passive voice. Try to communicate one idea per sentence. The average sentence length should be between 15 and 20 words. ‘You need to’ is usually more appropriate than ‘you must’.
Use address, not postal address. It’s ok to abbreviate email address to address if you’ve already made clear what you’re talking about.
See the GOV.UK style guide for Americanisms.
Use the -is rather than -iz spelling, unless the word appears in JSON code, where the spelling is important. See the REST API documentation for an example of this.
Use contractions like you’re and we’ll. Avoid should’ve, could’ve, would’ve, they can be hard to read. Do not use contractions like can’t and don’t, especially when giving instructions. Use cannot, instead of can’t.
See the GOV.UK style guide for contractions.
Dates should be written in the format Wednesday 30 June 2022. Do not add suffixes to dates (st, nd, rd, th). For date ranges, use ‘to’ instead of a dash or slash. For example, from Monday 7 to Wednesday 9 November.
Both are correct. We use dispatch for consistency.
Use ‘for example’ instead of eg. Do not use etc or ie. See the GOV.UK style guide for eg, etc and ie.
Email is one word. Use a lower case e unless it’s the first word in a new sentence. Never write email messages or e-mails.
Write email addresses in full, in lower case and as active links. Do not include any other words in the link text.
Emails, text messages and letters, always in that order.
See less or fewer.
Use GOV.UK Notify the first time you mention the product on a page. After that you can call it Notify.
The Notify website, not user interface or UI.
See the GOV.UK style guide for titles.
See the GOV.UK style guide for hyphenation.
Use less instead of fewer if it sounds more natural than ‘fewer’. For example, letters must be 10 pages or less.
Use messages if you’re not being specific about the channel.
See GOV.UK Notify
See the GOV.UK style guide for numbers.
Use phone number, mobile phone number or international phone number. There’s no need to write telephone in full.
All content on Notify should be written in plain English. Sometimes it won’t be obvious which plain English term to use. If you’re not sure, speak to a content designer. See Writing for GOV.UK for more information.
Use smart (curly) quotes. See the GOV.UK style guide for quotes and speech marks.
Use recipients rather than ‘your users’.
Use reply-to email address or reply-to address, not email reply-to address.
Users upload a spreadsheet, not a CSV or Excel file.
Text messages, never texts or SMS.
Use 9am, midday, 4:30pm. Do not use the 24h clock, or any other time format.
For time ranges, use ‘to’ instead of a dash or slash. For example, 9am to 10am. Between 9am and 10am is fine too.
For more information, see the GOV.UK style guide for times.
See GOV.UK Notify
Do not describe our users as ‘users’. Address them as ‘you’ where possible and call their colleagues ‘team members’.
When you’re talking about our users’ users (the people who receive messages), call them recipients.
No need to explain what this means unless it’s not Monday to Friday. For example, if it includes Saturdays or bank holidays.