Use "Quit". Can be more specific, like "Quit transaction".
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..."
Instead of using the term ex officio use the term because of his or her position instead
Instead of using the term expedite use the term hurry, speed up instead
Instead of using the term expeditiously use the term as soon as possible, quickly instead
Instead of using the term expenditure use the term spending instead
Instead of using the term expire use the term run out instead
Lower case.
Instead of using the term extant use the term current, in force instead
Instead of using the term extremity use the term limit instead
Instead of using the term fabricate use the term make, make up instead
Instead of using the term facilitate use the term help, make possible instead
Instead of using the term factor use the term reason instead
One word, not two.
Instead of using the term failure to use the term if you do not instead
We have a "no-FAQs" rule. Our existing content and products should be written and structured in a way that the user does not have to ask questions in order to find out what they need to know or complete a task.
If there is no other solution than to use a question as a subheading, write the question in the first person.
Should be capitalised as it's a proper noun – it's a service offered by Pay.UK.
Use upper-case when referring to file extensions in body copy. For example, "PDF" and not "pdf".
If a link opens a file, then tell the user by specifying the file extension in brackets after the CTA copy. Use lower-case and a stop before the file extension. For example, "Download statement (.pdf)".
Instead of using the term finalise use the term end, finish instead
Not forename.
Two words, no hyphen. Use "first name" rather than "forename", etc. Only capitalise if at the beginning of a sentence.
Smart Retire's drawdown pot. Sentence case.
Instead of using the term following use the term after instead
You should follow the VID (Visual Identity) design guidelines on which fonts to use and how to present them.
Should always be written out in full, not eg or e.g.
Instead of using the term formulate use the term plan, devise instead
Instead of using the term for the duration of use the term during, while instead
Instead of using the term for the purpose of use the term to, for instead
Instead of using the term for the reason that use the term because instead
Instead of using the term forthwith use the term now, at once instead
Instead of using the term forward use the term send instead
Instead of using the term frequently use the term often instead
Use normally in sentences and paragraphs. Don't use them to end headers.
The exception to this is error messages, which should have a full stop at the end of the header. If there are two sentences to the error message, use to end the first sentence.
Where there is a sentence that ends with something in quote marks, the full stop should go "outside the quotation marks like this". It's the other way around for US English.
Don't use full stops:
- to end any text for radio buttons
- at the end of standalone links, for example, "Back"
Should only be used to refer specifically to investment funds. For a sum of money in a scheme/pot use "pension savings" and not "pension funds".
Only capitalise the word "fund" if it forms part of a proper noun (name). For example, "Your savings are divided up between four funds, including the Smart Sharia Fund and the Smart Future Fund".
Instead of using the term furnish use the term give instead
Instead of using the term furthermore use the term then, also, and instead
Instead of using the term further to use the term after, following instead
We never ask a user for their sex or gender unless it is absolutely essential. If we do have to ask for it, we must tell them why we need the information.
The main case for asking for a user's gender is when we have to ask a member for their legally recognised gender. This is because it is a requirement from the government on any RTI (real time information) data that's submitted to do with PAYE. More information can be found here on the government website.
Where we must ask for the member's gender for this reason, we say:
"Select your legally recognised gender. HMRC uses this for tax services."
Or, if the information was already supplied by their employer:
"Your employer told us your legally recognised gender when you joined Smart Pension. HMRC uses this for tax services."
Instead of using the term generate use the term produce, give, make instead
Instead of using the term give consideration to use the term consider, think about instead
Refers to how a user's savings, when using an investment strategy managed by the pension provider, are moved into different investments the closer the user is to their nominated retirement age. This is often done to reduce risk.
The full definition is in progress. This term is used rarely in client-facing comms. This may change in early 2023.
Remember that glidepath is all one word, not glide path.
Not glidepath, glide-path or Glide Path.
Lowercase G. For example, "In a series of indicative votes, the UK government failed to find a consensus on Brexit."
Instead of using the term grant use the term give instead
All external emails should start with "Hi [first name]" and end with "The Smart Pension Team" (or whatever team is most appropriate)
We say "Guaranteed income (also known as an annuity)" in the first instance, and "guaranteed income" in all other instances. The exception to this is if we're referring to a specific annuity product – in which case we would say "annuity".
Don't use (have) regard to – use take into account.
All page titles, headings and subheadings should be written in sentence case (not Title Case).
Use a heading that is specific enough to tell the user exactly what the page or form field does. For example, "Reset your password" not “I don’t know my password”.
People reading just the header, subheader, label or page title should know what to expect.
If the page is part of a collection of pages, we should also make that clear from the title.
Where there is only one action a user can take in a section, use the format "[Verb] the [noun]" or "[Verb] your [noun]".
Where a user can take multiple actions on a page, or for section headers and landing page headers, use a noun that covers all of the actions where possible. For example, "Contributions".
For platform content, we do not use questions as subheadings. Where it is completely unavoidable we use the first person for questions.
Text content should be organised with headings, wherever possible, to make it easier to navigate. For example in long form content, information articles and content that can be organised, like a ‘Setting’ menus.
Some bits of content, like long letters, may not be suitable.
We should also use headings in the right way if we have control over them. For example, if there are sub-topics, we should use H3s under the relevant H2 and so on.
This is an accessibility requirement, meeting Success Criterions 2.4.2 Page Titled, level A, 2.4.6 Headings and Labels, level AA, and 2.4.10 Section Headings, level AAA.
Instead of using the term henceforth use the term from now on, from today instead
Instead of using the term hereby use the term now, by this (or edit out) instead
Instead of using the term herein use the term here (or edit out) instead
Instead of using the term hereinafter use the term after this (or edit out) instead
Instead of using the term hereof use the term of this instead
Instead of using the term hereto use the term to this instead
Instead of using the term heretofore use the term until now, previously instead
Instead of using the term hereunder use the term below instead
Instead of using the term herewith use the term with this (or edit out) instead
Instead of using the term hitherto use the term until now instead
Instead of using the term hold in use the term abeyance wait, postpone instead
Instead of using the term hope and trust use the term hope, trust (but not both) instead
Use when creating compound adjectives. For example, "long-term investment".
Instead of using the term if and when use the term if, when (but not both) instead
Instead of using the term illustrate use the term show, explain instead
When you're using content like images, charts, graphs, or thumbnails, these need to have text alternatives.
For simpler content, like images or thumbnails, you must write a short caption that describes what it is. You must also use the alt text feature of the content management system (CMS) you’re using, This should be a descriptive sentence explaining the information conveyed in the image as the alt text. Alt text is what appears on a page if the content does not load. It is also what screen readers read.
For example, your caption could be ‘Andrew Evans and Will Wynne opening the Smart Building office’. Your alt text could be ‘Andrew Evans and Will Wynne surrounded by Smart colleagues on the ground floor celebrating the opening of the new Smart Building office’.
With content that’s more complicated, like graphs or diagrams, it’s not possible to give the same experience with just a short description. There needs to be more information.
There must be both a short description and a long description. The aim is to create the same experience with your text as you get from the content.
The long description should be on the same page, and close to the content it is detailing.
For example, a graph showing Smart’s growth could say “This graph shows Smart’s growth”.
The long description could say ‘This graph shows that since 2019 Smart has grown almost 2,000%, with growth accelerating. In 2019 growth was 200%, 2020 growth was 250% and growth in 2021 was 330%’.
This is an accessibility requirement, meeting Success Criterion 1.1.1 Non-text Content, level A.
Instead of using the term immediately use the term at once, now instead
Instead of using the term implement use the term carry out, do instead
Instead of using the term imply use the term suggest, hint at instead
Instead of using the term in accordance with use the term as under, in line with, because of instead
Instead of using the term in addition (to) use the term and, as well as, also instead
Instead of using the term in advance use the term before instead
Instead of using the term in a number of cases use the term some (or say how many) instead
Instead of using the term inappropriate use the term wrong, unsuitable instead
Instead of using the term in case of use the term if instead
Instead of using the term inception use the term start, beginning instead
Instead of using the term in conjunction with use the term and, with instead
Instead of using the term in connection with use the term for, about instead
Instead of using the term in consequence use the term because, as a result instead
Instead of using the term incorporating use the term which includes instead
Instead of using the term incurred use the term have to pay, owe instead
Instead of using the term indicate use the term show, suggest instead
Instead of using the term in excess of use the term more than instead
Instead of using the term inform use the term tell instead
A pot in Smart Retire where the user can set aside some money to leave to loved ones or a charity when they die. Write it in sentence case.
Capitalised as a proper noun, according to the way that gov.uk uses it.
Instead of using the term initially use the term at first instead
Instead of using the term initiate use the term begin, start instead
Instead of using the term in lieu of use the term instead of instead
Instead of using the term in order that use the term so that instead
Instead of using the term in receipt of use the term get, have, receive instead
Instead of using the term in relation to use the term about instead
Instead of using the term in respect of use the term about, for instead
Instead of using the term insert use the term put in instead
Instead of using the term instances use the term cases instead
Instead of using the term intend to use the term will instead
Instead of using the term in the absence of use the term without instead
Instead of using the term in the course of use the term while, during instead
Instead of using the term in the event of/that use the term if instead
Instead of using the term in the majority of instances use the term most, mostly instead
Instead of using the term in the near future use the term soon instead
Instead of using the term in the neighbourhood of use the term about, around instead
Instead of using the term intimate use the term say, hint instead