Don't use completion – use end.
How we write for Smart
At Smart, we have different audiences depending on what channel we're using, and what product or service we're talking about.
Most of the time we're talking to people directly about their personal finances and their pension savings. We sell and explain sophisticated products to our clients and customers. We need to make sure they understand us and trust us – or where to go if they need help.
These principles should apply to everything we write, and they form the backbone of our tone of voice.
We know our audience
It's easier to write well if you understand who you're writing for.
By knowing what your audience is interested in or worried about, your content will:
- be relevant
- catch their attention
- answer their questions
It's important to know how your audience talks. This will help you use the same terms and phrases as them when talking about an issue or topic. Your content will then be easier to understand and find.
We put the user first
Don't publish everything you can. Only tell someone what they need to know so they can complete their task. Nothing more.
People don't usually read text unless they want information or instructions. When you write, the first question you should ask is "what does the user want to know?".
Meeting a user need means being:
- specific
- informative
- clear and to the point
We're compliant
As a leading fintech operating our own master trust, we need to make sure all our content is compliant.
Some of the things we write will have to go through specific compliance and legal sign off to meet regulation. But even if it doesn't, our content should always stick to these guidelines to make sure it's compliant.
- Don't make any wild, misleading, or untrue claims. For example, "Our pension scheme means you'll be rich in retirement"
- Give guidance, never advice. Refer people to The Pensions Advisory Service, Pension Wise and other services if they need advice
- Always use the right names for things such as products, services and legislation. For example, it's Smart Pension Master Trust not The Smart Pension scheme
- Make it clear who or where communications are coming from. This will usually be us, but it could also be one of our partners, a director or trustee, or another third party
We make our content easy to read
Our content should provide clear, easy to understand information to our users. Complicated writing and large blocks of text get in the way of this information.
Easy to read content uses:
- short sentences
- sub-headed sections
- bulleted lists (like this one)
We use plain English
The average reading age in the UK is about 9 years old. Even if our audience contains those with a higher reading age, we should use words that are easy to understand wherever possible.
Try to avoid jargon or difficult terms. If you have to use them, make sure you explain them.
Plain English doesn't mean "dumbing down" your writing or only using short words. It's about getting your message across efficiently and in a friendly manner.
Using plain English is as simple as writing in the way most of us speak.
- Write in the active voice wherever appropriate (see below)
- Use 'you' and 'we'
- Use everyday words you know the reader will understand
- Use contractions when it feels natural to do so
- Avoid turning a process into a noun – this is known as "nominalization". For example, "upon arrival" should be "when you arrive"
If you find yourself about to write, type or dictate a word you wouldn’t use in every day conversation, look it up in the A to Z of words to avoid. You should find a simpler alternative. Often there will be a choice of several words. You need to pick the one that best fits what you are trying to say.
Using the active voice
When writing for Smart, we use the active voice and avoid the passive voice.
Active voice:
- "we've set up your workplace pension"
Passive voice:
- "your workplace pension has been set up"
We avoid the passive voice because it's often wordier, difficult to read, and overly formal – meaning it can alienate readers.
It can be difficult to spot the passive voice. A good rule of thumb is that if your clause could end with "...by monkeys." and still make sense, you're probably using the passive voice. For example:
- "50% of your to-do list has been completed" (...by monkeys)
- "contributions of £123 were made by your employer" (...by monkeys)
- "a pension transfer was initiated (...by monkeys) last month"
There are some exceptions to avoiding the passive voice. For example, if you're talking about an action that will be taken by someone other than Smart, the user, or someone known to them:
- "your funds will be invested"
You may also choose to use the passive voice in error messages or in negative communications, to avoid placing blame on the user:
- "your password was entered incorrectly"
- "your scheme will be cancelled unless you..."
Don't use comply with – use keep to or meet.
Don't use component – use part.
Don't use comprise – use make up or include.
Don't use conceal – use hide.
Don't use concerning – use about or on.
Don't use conclusion – use end.
Don't use concur – use agree.
Don't use condition – use rule.
A conjunction is a "joining word", that links different parts of a sentence together – such as "and" or "but". And they can be used to start sentences.
Don't use consequently – use so.
Don't use considerable – use great or important.
Don't use constitute – use make up or form.
Don't use construe – use interpret.
Don't use consult – use talk to, meet, ask.
Don't use consumption – use amount used.
Don't use contemplate – use think about.
Our preferred CTA for continuing an action.
Should say "Continue" rather than "Next" or "Proceed".
Use "Continue" where it's not necessary to explain to the user exactly what the button does. For example, if the button submits the information they've entered and takes them to the next step in an application, "Continue" is better than "Submit details and continue".
A contraction is a shortened version of two words, written as one word. Often, they use apostrophes to signify missing letters ("didn't", "can't", "shouldn't")
Use these to make your content informal and friendly, but don't overdo it. Too many contractions can make content hard to read.
Don't use contrary to – use against or despite.
In the first instance on a page or document style as "Coronavirus (COVID-19)" at the beginning of a sentence, or "coronavirus (COVID-19)" in the middle of a sentence. In any further instances, just say "coronavirus".
Don't use correct – use put right.
Don't use correspond – use write or email.
Instead of using the term costs the sum of use the term costs instead
Instead of using the term counter use the term against instead
Instead of using the term courteous use the term polite instead
Instead of using the term cumulative use the term added up, added together instead
Instead of using the term currently use the term now (or edit out) instead
Instead of using the term customary use the term usual, normal instead
How we refer to our customer service department ("If you need help, our customer support team is happy to help")
Dashes work well when used in place of colons. Use en dashes (–), not em dashes (—). A hyphen doesn't count as a dash – it's a hyphen.
On a Mac, type an en dash by selecting the Option + Minus keys at the same time.
Don't use dashes in lists or tables of numbers or financial information, as they can look like a minus sign.
Instead of using the term deduct use the term take off, take away instead
Instead of using the term deem to be use the term treat as instead
Instead of using the term defer use the term put off, delay instead
Instead of using the term deficiency use the term lack of instead
Instead of using the term delete use the term cross out instead
Technical term for a very small pension pot. Translated from Latin the term means "pertaining to minimal things".
Not 'de minimus'. Use sparingly.
Instead of using the term demonstrate use the term show, prove instead
Instead of using the term denote use the term show instead
Not dependant.
Instead of using the term depict use the term show instead
Always a small 'r', even if forming part of a name like the Smart De-risking Fund.
Instead of using the term designate use the term point out, show, name instead
Instead of using the term desire use the term wish, want instead
Instead of using the term despatch or dispatch use the term send, post instead
Instead of using the term despite the fact that use the term though, although instead
Instead of using the term determine use the term decide, work out, set, end instead
Instead of using the term detrimental use the term harmful, damaging instead
Instead of using the term difficulties use the term problems instead
Instead of using the term diminish use the term lessen, reduce instead
It's a proper noun and needs to be capitalised.
Instead of using the term disburse use the term pay, pay out instead
Instead of using the term discharge use the term carry out instead
Instead of using the term disclose use the term tell, show instead
Instead of using the term disconnect use the term cut off, unplug instead
Instead of using the term discontinue use the term stop, end instead
Instead of using the term discrete use the term separate instead
Instead of using the term discuss use the term talk about instead
Instead of using the term disseminate use the term spread instead
Instead of using the term documentation use the term papers, documents instead
Instead of using the term domiciled in use the term living in instead
Instead of using the term dominant use the term main instead
We say "flexible income (income drawdown)" in the first instance, and "flexible income" after this. An exception is when referring to the legal or financial process of drawdown – in this instance, say "drawdown" (for example, "your pension fund is now in drawdown").
Instead of using the term due to the fact of use the term because, as instead
Instead of using the term duration use the term time, life instead
Instead of using the term during which time use the term while instead
Instead of using the term dwelling use the term home instead
Instead of using the term economical use the term cheap, good value instead
Use "Edit" and not "Change" or "Amend".
Don't use these – use "For example," instead.
Instead of using the term eligible use the term allowed, qualified instead
Instead of using the term elucidate use the term explain, make clear instead
Should be all lower case for readability. For example:
For example, "please can I have your email address so I can email you that document" or "I received your email at my email address."
Instead of using the term emphasise use the term stress instead
Instead of using the term empower use the term allow, let instead
Instead of using the term enable use the term allow instead
Instead of using the term enclosed use the term inside, with instead
Instead of using the term encounter use the term meet instead
Instead of using the term endeavour use the term try instead
Instead of using the term enquire use the term ask instead
Instead of using the term enquiry use the term question instead
Instead of using the term ensure use the term make sure instead
Instead of using the term entitlement use the term right instead
Instead of using the term envisage use the term expect, imagine instead
Instead of using the term equivalent use the term equal, the same instead
Instead of using the term erroneous use the term wrong instead
We use two types of error messages – alerts (boxes that pop up out of the form or page) and inline errors (error messages that appear by the incorrectly filled form field).
Alerts
Alerts should lead in with a simple statement of fact, followed by a broad description of the options available on the page. For example, "It looks like your income could run out when you're 78.”
If you want your income to last longer, you could lower your monthly income or move more money into this pot".
Avoid stating whether an alert is positive or negative. In the example above, it would be wrong to say "There's a problem - your money might run out when you're 78. To fix this, (...)" – as it's impossible to know the user's future plans or overall financial situation.
Inline errors
Unlike regular error messages/alerts, inline error messages don't necessarily need to explain what went wrong. Telling the user the solution is often enough to prompt them to correct the error, especially in simple forms. For example, "Please enter your name" is enough to prompt a user to fill in a form field they accidentally missed.
Explaining the error can make the message unnecessarily long and harder to read. For example, "You didn't enter your name. Please enter your name" is overkill for a simple to understand and easy to fix error.
Instead of using the term establish use the term show, find out, set up instead
Don't use it. If you find yourself in a situation that calls for the use of something like this use "and more" instead.
Instead of using the term evaluate use the term test, check instead
Instead of using the term evince use the term show, prove instead
Instead of using the term exceptionally use the term only when, in this case instead
Instead of using the term excessive use the term too many, too much instead
Use them sparingly – they may be useful in specific cases (such as celebration moments) when there is less need to be formal!
Instead of using the term exclude use the term leave out instead
Instead of using the term excluding use the term apart from, except instead
Instead of using the term exclusively use the term only instead
Instead of using the term exempt from use the term free from instead