A to Z content style guide
Writing content for Transport for West Midlands
You should create all content with user-focused content design principles. This means content has an identified user need and is written in plain English.
Do not use marketing speak - users will be visiting your website to perform a task (for example, buy a train ticket or find out about Swift cards). Your content shouldn’t try to sell them anything - instead, tell them the information they need to know in the simplest way possible.
Research has shown that both high literacy and low literacy users prefer plain English because it takes less time to read. Users won’t be on your website for fun - so make the experience quick and easy.
To find out more about why plain language is important, read:
- advice about clear language from the Readability Guidelines project
- the plain English Campaign’s A to Z of alternative words - this helps you find a simple replacement for a complicated word
Read the GOV.UK introduction to content design to find out more about content design principles.
Design Team can help you to test your content with user research.
About the A-Z of style guide
This style guide will help you to use consistent words across Transport for West Midlands services.
If something is not covered by this style guide, check the GOV.UK style guide . You can also email Samresha Purewal if you think something is missing from this guidance.
Introducing Transport for West Midlands
If you’re talking about day-to-day services (bus, train or tram), you may need to make it clear that Transport for West Midlands does not run these.For example, you could say: "We don’t run the buses, trains or trams. We can point you in the right direction if you need help."
A to Z of style
Abbreviations and acronyms
The first time you use an abbreviation or acronym explain it in full on each page unless it's well known, like UK or BBC. Then refer to it by initials.
Do not use full stops in abbreviations: BBC, not B.B.C.
If you only use a term once, you don't need to include the abbreviation afterwards.
Use 'm' (for millions) and 'bn' (for billions) for sums of money and measurable quantities: £10bn; 1bn litres of water. However, spell out for people and countable nouns: 3 billion commuters; 10 billion tickets.
Use lower case for standard measurements: kg; km; lb; mph but use upper case for KB; GB; MB.
Exception: Spell out metres to prevent confusion with abbreviation for million.
- Do not include a space between the number and the unit: 20km; 50kph; 100KB
- Never add an 's' to measurements: 20km, not 20kms
Use lower case for ie and eg, but avoid using these terms altogether where possible. Use 'that is' or 'for example' instead.
Use the active voice, not the passive voice - it’s easier to read. For example:
We’re going to get the train tomorrow (active voice)
A train is going to be caught by us tomorrow (passive voice)
Use the contact details design pattern. This shows you how to format addresses.
Addressing the user
Address the user as 'you' wherever possible.
Do not hyphenate.
Do not use hyphens in ages unless to avoid confusion, although it's always best to write in a way that avoids ambiguity. For example, 'a class of 15 16-year-old students took the A level course' can be written as '15 students aged 16 took the A level course'.
Write ages like this: XX years old (for example, 66 years old).
Exception - use hyphens when talking about age groups:
- under-16s (n): under-16s
- under 16 (adj): If you are under 16
- over-60s (n): over-60s
- over 60 (adj): If you are over 60
American and UK English
Use UK English spelling and grammar. For example, use 'organise' not 'organize', 'modelling' not 'modeling', and 'fill in a form', not 'fill out a form'.
American proper nouns, like 4th Mechanized Brigade or World Health Organization, take American English spelling.
Use and rather than &, unless it's a department's logo image or a company's name as it appears on the Companies House register.
Not mobile app, iOS app, iPhone app or Android app.
Bacs (Bankers Automated Clearing System)
Use the acronym as it's more widely known than the full name. No need to include the full name in brackets.
Only use bold for instructions when you’re talking about an interactive service.
You can use bold to explain what field a user needs to fill in on a form, or what button they need to select. For example: "Select Continue."
Use bold sparingly - using too much will make it difficult for users to know which parts of your content they need to pay the most attention to.
Do not use bold in other situations, for example to emphasise text.
To emphasise words or phrases, you can:
- front-load sentences
- use headings
- use bullets
Only use upper case if you're talking about a specific bus station: Dudley Bus Station, Coventry Pool Bus Station.
Use lower case if you're talking about bus stations in general: You can find bike racks at our bus stations.
Lower case except in a name: Dudley Metropolitan Borough Council.
Bullet points and numbered steps
You can use bullet points to make text easier to read. Make sure that:
- you always use a lead-in line with a colon
- the bullets make sense running on from the lead-in line
- you use lower case at the start of the bullet
- you do not use more than one sentence per bullet point - use commas or dashes to expand on an item
- you do not put 'or' or 'and' after the bullets
- you do not make the whole bullet a link if it's a long phrase
- you do not put any punctuation at the end of a bullet
- there is no full stop after the last bullet point
Bullets should normally form a complete sentence following from the lead text. But it's sometimes necessary to add a short phrase to clarify whether all or some of the points apply. For example, 'You can only register a pension scheme that is (one of the following):'
The number and type of examples in a list may lead the user to believe the list is exhaustive. This can be dealt with by
- checking if there are other conditions (or if the list is actually complete)
- listing the conditions which apply to the most users and removing the rest
- consider broader terms in the list which capture more scenarios (and could make the list exhaustive)
Use numbered steps instead of bullet points to guide a user through a process. List the things the user needs to do in order. You do not need a lead-in line. Steps end in a full stop because each should be a complete sentence.
campaign/scheme names and brands
If you have a scheme or campaign brand, explain the brand. Don't expect users to understand what you mean. If you say ‘be aware and share’ or ‘get your roll and stroll on’ out of context, it’s not clear what that means.
Don’t capitalise slogans like ‘be aware and share’. If you’re talking about a specific brand or campaign, use capitals. For example, Workwise, PassProtect. Don’t tell people to ‘Be Aware and Share’, but do say ‘the Be Aware and Share’ campaign.
- 'get half-price travel when you start a new job with the Workwise scheme'
- 'find your nearest cycle route on the Starley cycle network'
- 'hire a bike with West Midlands Cycle Hire'
- 'If you join the PassProtect scheme, you will get a discount if you need to replace your child's school travel pass.'
cash fareDo not use - it's confusing. Say 'ticket bought on the bus, train or tram on the day' instead.
DO NOT USE BLOCK CAPITALS FOR LARGE AMOUNTS OF TEXT AS IT'S QUITE HARD TO READ.
Always use lower case, even in page titles. The exceptions to this are proper nouns.
Not "check box"
Do not hyphenate.
Don't use "click" when talking about user interfaces because not all users click. Use "select".
You can use "right-click" if the user needs to right-click to open up a list of options to progress through the user journey.
Treat as singular, except staff and police: the committee has but the staff are; the police want.
A pair and a couple are both plural.
Try to avoid. Use these instead:
- older person's free travel pass
- disabled person's travel pass
- 16-18 photocard
- under-16 photocard
- discounted travel pass
It’s okay to use concessionary if you’re talking about the English National Concessionary Travel Scheme.
Use the contact details design pattern.
You can use contractions to help make your text less formal.
Avoid negative contractions like can't and don't. Many users find them harder to read, or misread them as the opposite of what they say. Use cannot instead of can't; do not instead of don’t.
Avoid should've, could've, would've, they've too. These can also be hard to read.
Coronavirus is the virus which causes the illness COVID-19. Coronavirus is lower case.
Use lower case when writing about local councils in general. Use capitals for the official name of a local council, for example: Birmingham City Council.
Refer to 'customers' rather than 'passengers'.
- use upper case for months: January, February
- do not use a comma between the month and year: 4 June 2017
- when space is an issue - in tables or publication titles, for example - you can use truncated months: Jan, Feb
- use 'to' in date ranges - not hyphens, en rules or em dashes. For example: tax year 2011 to 2012
- Monday to Friday, 9am to 5pm (put different days on a new line, do not separate with a comma)
- 10 November to 21 December
- do not use quarter for dates, use the months: 'Jan to Mar 2013'
- when referring to today (as in a news article) include the date: 'The minister announced today (14 June 2012) that…'
Use 'to' instead of a dash or slash in date ranges. 'To' is quicker to read than a dash, and it's easier for screen readers.
Always explain what your date range represents, for example 'tax year 2013 to 2014' or 'September 2013 to July 2014'. Date ranges can be the academic year, calendar year or tax year. This is why date ranges must be very, very clear.
See times for more guidance on how to write times.
Direct Debit Instruction
Use this term when referring to disabled accessibility, as 'accessibility' has a wider meaning.
Not 'the disabled' or 'people with disabilities'.
Lower case even in a name, like Warwick district council.
eg, etc and ie
eg can sometimes be read aloud as 'egg' by screen reading software. Instead use 'for example' or 'such as' or 'like' or 'including' - whichever works best in the specific context.
etc can usually be avoided. Try using 'for example' or 'such as' or 'like' or 'including'. Never use etc at the end of a list starting with these words.
ie - used to clarify a sentence - is not always well understood. Try (re)writing sentences to avoid the need to use it. If that is not possible, use an alternative such as 'meaning' or 'that is'.
FAQs (frequently asked questions)
Do not use FAQs.
If you write content by starting with user needs, you will not need to use FAQs.
FAQs are discouraged because they:
- duplicate other content on the site
- cannot be front-loaded (putting the most important words people will search for), which makes usability difficult
- mean that content is not where people expect to find it; it needs to be in context
- can add to search results with duplicate, competing text
Use 'fine' instead of 'financial penalty'.
For example, "You'll pay a £50 fine."
Use "we'" and "us" when addressing the user where possible. For example, instead of "Transport for West Midlands has…" say "We have" - it’s more personal.
fire and rescue service
Focuses/focused/focusing. Not focusses/focussed/focussing.
Lower case unless it's a full title. For example: 'UK government', but 'Her Majesty's Government of the United Kingdom of Great Britain and Northern Ireland'.
- re- words starting with e, like re-evaluate
Do not hyphenate:
Do not use a hyphen unless it's confusing without it, for example, a little used-car is different from a little-used car. You can also refer to The Guardian style guide for advice on hyphenation.
Use 'to' for time and date ranges, not hyphens.
see eg, etc and ie
Do not use italics. They can be hard to read online.
Use upper case when referring to a specific role: Lord Mayor of Birmingham.
Use lower case if writing generally: service assistants, station managers.
Our travel tool that helps with live route-planning across our network
A stand-alone link to it should be action-led and first-person: 'Plan my journey'.
If giving instruction, it can be second-person (to avoid mixing perspectives): 'Plan your journey'.
If listing tools, we can use the product name: 'Journey Planner'.
Front-load your link text with the relevant terms and make them active and specific. Do not use ‘click here’. Use text that describes the link instead.
Lists should be bulleted to make them easier to read. See bullets and steps.
Very long lists can be written as a paragraph with a lead-in sentence if it looks better: 'The following countries are in the EU: Spain, France, Italy...'
See sign in or log in.
Use lower case for standard measurements: kg; km; mph; kph but use upper case for KB; GB; MB.
Spell out metres to prevent confusion with abbreviation for million.
Do not include a space between the number and the unit: 20km; 50mph; 100KB.
Never add an 's' to measurements: 20km, not 20kms.
Only use when talking about the company that runs the tram - West Midlands Metro. To talk about the tram as a mode of transport, use tram, not Metro.
Use the £ symbol: £75.
Do not use decimals unless pence are included: £75.50 but not £75.00.
Do not use '£0.xx million' for amounts less than £1 million.
Write out pence in full: calls will cost 4 pence per minute from a landline.
Currencies are lower case.
Use when talking about network bus tickets - always use a lower case ‘n’, upper case ‘B’.
Use when talking about network tickets for the bus, train and tram - always use a lower case ‘n’, followed by an upper case ‘N’.
Use when talking about network train tickets - always use a lower case ‘n’, upper case ‘T’.
Use 'one' unless you're talking about a step, a point in a list or another situation where using the numeral makes more sense: 'in point 1 of the design instructions', for example. Or this:
You'll be shown 14 clips that feature everyday road scenes.
There will be:
- developing hazard in 13 clips
- developing hazards in the other clip
Write all other numbers in numerals (including 2 to 9) except where it's part of a common expression like 'one or two of them' where numerals would look strange.
If a number starts a sentence, write it out in full (Thirty-four, for example) except where it starts a title or subheading.
For numerals over 999 - insert a comma for clarity: 9,000
Spell out common fractions like two-thirds.
Use a % sign for percentages: 50%.
Use a 0 where there's no digit before the decimal point.
Use '500 to 900' and not '500-900' (except in tables and for the 16-18 photocard).
Use MB for anything over 1MB: 4MB not 4096KB.
Use KB for anything under 1MB: 569KB not 0.55MB.
Keep it as accurate as possible and up to 2 decimal places: 4.03MB.
Addresses: use 'to' in address ranges: 49 to 53 Cherry Street.
Spell out first to ninth. After that use 10th, 11th and so on.
In tables, use numerals throughout.
see operator names.
Use lower case and include a hyphen.
Refer to older people rather than elderly people.
One word. Do not use 'on-line' or 'on line'.
Do not abbreviate the name. For example, do not use ‘WM Metro’, ‘NX West Midlands’ or ‘West Mids Railway’.
You can use an acronym for timetables and passenger information. For example, ‘West Midlands Metro (WMM)’, ‘National Express West Midlands (NXWM)’ or ‘West Midlands Railway (WMR)’.
Do not use the NXWM acronym without explaining it first. It is not a well known acronym.
Do not use slashes instead of "or". For example, do not say "Do this 3/4 times".
Verb: I would like to opt in
Adjective: an opt-in clause
A ticket that’s printed on paper, not on a Swift card.
Refer to 'customers' rather than 'passengers'.
pay as you go
Do not hyphenate and always use lower case.
pay as you go credit
Use to describe Swift cards with a stored cash value
Note: Do not use 'pay as you go travel value (cash)' or 'pay as you go cash value'.
Lower case plain and upper case English unless in a title: the Plain English Campaign.
All content should be written in plain English. You should also make sure you use language your audience will understand. Use the Plain English Campaign’s A to Z of alternative words to avoid complex language.
Phone numbers should be split into at least three groups of digits for readability, ideally with no more than four digits in any single group. For example: 020 7378 1705; 0343 222 6666; 0762 480 4299. See also the design pattern for contact details.
Use single quotation marks in all cases.
Use double quotation marks if using a quote within a quote.
If a quote runs on longer than one paragraph, include quotation marks at the beginning of each subsequent paragraph but only at the end of the final paragraph.
Place full stops and commas inside quotes when they are complete sentences, otherwise place them outside: 'I want to buy a ticket,' said Mr Smith; When he said 'I promise', he didn't really mean it.
There are five rail zones in the West Midlands.
Not rail areas, railway zones or train zones.
Where possible, use 'live' instead of 'realtime' or 'real time'
real time (noun): this information is being updated in real time.realtime (adjective): realtime service information.Not real-time.
Use lower case for spring, summer, autumn and winter.
Do not use long sentences. Check sentences with more than 25 words to see if you can split them to make them clearer.
sign in or log in
Use sign in rather than log in (verb) for calls-to-action where users enter their details to access a service.
Do not use login as a noun - say what the user actually needs to enter (like username, password, National Insurance number).
Lower case. For example, Birmingham New Street station. Do not say tram station, say tram stop.
Lower case. For example, Summer Lane bus stop.
Do not capitalise 'Card'.
A route between street and platform that doesn't require the use of stairs or escalators.
terms and conditions
Not Terms and Conditions or terms & conditions.
text message alerts
Not SMS alerts.
See entry on Transport for West Midlands.
use 'to' in time ranges, not hyphens, en rules or em dashes:
- 10am to 11am (not 10-11am)
- 5:30pm (not 1730hrs)
- midnight (not 00:00)
- midday (not 12 noon, noon or 12pm)
- 6 hours 30 minutes
Midnight is the first minute of the day, not the last. You should consider using "11:59pm" to avoid confusion about a single, specific time.
For example, "You must register by 11:59pm on Tuesday 14 June." can only be read one way, but "You must register by midnight on Tuesday 14 June" can be read in two ways (the end of Monday 13, or end of Tuesday 14).
Timetables and printed passenger information use the 24-hour clock in HHMM format.
See entry on rail zones.
Transport for West Midlands
Avoid referring to Transport for West Midlands (TfWM). Users don't need to know about it while getting travel advice.
Explaining the relationship between Transport for West Midlands, TfWM and West Midlands Combined Authority (WMCA) is complicated. Use "we" instead. For example, "we manage the Key Route Network (KRN)" with a link to the TfWM policy page.
Requires a hyphen in all cases. This is true whenever referring to age groups: under-16s; under-18s; over-60s.
Avoid the common error of adding an apostrophe when making a word or abbreviation plural as this makes it possessive: under-16s not under-16's.
Upper case. No need to explain the acronym.
Not "user name".
Not web-site or web site.
West Midlands Combined Authority
Avoid referring to West Midlands Combined Authority (WMCA). Users don't need to know about it while getting travel advice.
The exception is if you referring to a statutory responsibility or a contract. For example, concessionary passes or terms and conditions.
Lower case, no hyphen.
See entry on West Midlands Combined Authority.
If you are linking to another page, you should use an in-text link rather than the full URL. See the entry on links for more information.
Sometimes it is better to show the full URL. For example, when telling users to click a link to verify something in an email.
It is important to use the right URL. Only use wmnetwork.co.uk.
Do not prefix the URL with ‘www.’ as this makes our URL hard to read. The domain extension ‘.co.uk’ makes it obvious to users that it is a URL.
See entry on wmnetwork.co.uk.
Not "zero-hour contract" or "zero hours contract"