Edit
Contact us
Salocin Group Leaders in data and AI-enabled connected customer experiences
Edit Engineers of connected customer experiences
Join the Dots Independent, data-led media thinking for sustainable growth
Wood for Trees Optimisers of future fundraising performance
  • Home
  • Our services
    • Cloud solutions
    • Data science
    • Modern Data Platform
    • Privacy and AI compliance
  • Our partners
    • Apteco
    • Creatio
    • Microsoft
    • Salesforce
  • Our insights
    • Blog
    • Case studies
    • Reports
    • Webinars
    • Whitepapers
  • About Salocin Group
    • Careers
  • Contact Salocin Group
  • Home
  • Who we are
    • B Corp
    • Careers
  • Our work
  • What we do
    • Intelligent data
    • Marketing technology
    • Transformational CRM
    • Our technology partners
    • Privacy review
  • Our insights
    • Blog
    • Case studies
    • Reports
    • Webinars
    • Whitepapers
  • Contact Edit
  • Home
  • Broadcast media
  • Digital media
  • Print
    • Direct mail
  • Data
    • Our work with Herdify
    • EPiC
  • Media agency
  • Our insights
    • Blog
    • Case studies
    • Reports
    • Webinars
    • Whitepapers
  • About Join the Dots
    • Careers
  • Contact Join the Dots
  • Home
  • Services
    • Actionable insight
    • Data discovery
    • Data engineering
    • Data hygiene
    • Privacy review
  • Products
    • InsightHub
    • Apteco
    • Microsoft
    • Data management
    • Consent and preference management
  • Our insights
    • Blog
    • Case studies
    • Reports
    • Webinars
    • Whitepapers
  • About Wood for Trees
    • Operating principles
    • Careers
  • Contact Wood for Trees
Blog

Plain English in your press release: it just makes sense

By Edit | 4 Jan 2017

We published this a long time ago…

Some of the content in this post might be out of date, and some images and links may no longer work.

Discover who we are and how we may be able to help you today:

Learn more

Journalists can often receive over 100 press releases or pitches from PRs every day, so how can you make sure yours doesn’t end up in the trash folder?

We need to make it easy for journalists by communicating our brand’s message quickly and simply. That’s why we use only plain English in our press outreach at Branded3.

What is plain English?

Plain English is a style of writing that gets the writer’s point across simply and quickly. It avoids using more words than necessary, and is easy to understand. This is what makes it perfect for use in brand communications as it speaks to everyone and can capture the reader’s attention in just a few seconds – which is particularly important when trying to catch a journalists’ attention.

It isn’t a new idea; the Plain English campaign has been around since 1979, but is as relevant today as when it first launched. The point of using plain English is to inform rather than to impress. Below are some examples of words and phrases you could change from complex to simple:

Just tell it like it is. Readers don’t like to feel patronised or spoken down to, but simple language can help to create an equal relationship between brands and their audiences.

Why use plain English?

Plain English has many benefits for communication,  particularly when creating content for press. The aim of a press release is to deliver specific and brief information about an event or activity, so this style of writing fits perfectly.

Here are five key reasons why you should start writing your press releases using plain English:

  1. It’s brief

According to the 2015 Edelman media forecast,, brevity is one of the key elements journalists look for in their stories. Simple writing helps deliver the message concisely, giving journalists exactly what they want.

  1. It’s simple

This writing style makes things easy to understand. It avoids confusion about what you are trying to communicate and so delivers a stronger and more effective message.

  1. It’s relatable

By avoiding flamboyant language, it’s easier to create a relationship between the brand and the person you are communicating with. Rather than trying to impress, you can focus on reaching out and building a connection with your audience.

  1. It’s Google friendly

As an SEO company, we like to make Google happy, so using plain English makes sense. It makes things easy for users, which creates a good user experience, and so works well with Google’s algorithm.

  1. It works

In my experience, press releases using this writing style are more successful than those that are lengthier and more descriptive. Journalists tend to respond well to straight forward communication where they don’t have to search for the story you are pitching within a cloud of flowery copy.

Tools to help

In theory, writing in plain English should come naturally. However, so many of us are used to using more expressive language, which can make this task more difficult than you might first expect.

Thankfully, there are tools to help:

  • The newest version of Microsoft Word has a readability tool which gives a score on how easy your writing is to digest. You can find more information on the Office support centre.
  • If you don’t have the right version of office for this, there is an alternative checker called Readability Score. It highlights sentences that are too long, words and phrases which could be confusing, and gives an average reading level for your writing. Unlike the Office version, you can evaluate entire URL’s, not just documents or snippets of text.

Though these tools are a good starting point, the human eye is still the best way to check whether your writing makes sense, so set aside some time to read it yourself, and ask a colleague to check that your work is concise and easy to understand.

We published this a long time ago…

Some of the content in this post might be out of date, and some images and links may no longer work.

Discover who we are and how we may be able to help you today:

Learn more

Share this

  • Email
  • WhatsApp
  • LinkedIn
  • Facebook
  • X (Twitter)

More insights

AI isn’t going to take your job (unless you really want it to) 
Blog

AI isn’t going to take your job (unless you really want it to) 

By Edit | 18 Jun 2024
Customer relationship marketing: How generative AI is revolutionising engagement  
Blog

Customer relationship marketing: How generative AI is revolutionising engagement  

By Edit | 4 Apr 2024
Personalisation as a process
Blog

Personalisation as a process

By Edit | 8 Mar 2024
  • Privacy policy
  • Cookie policy
  • Ts&Cs
  • Report a concern

© 2025 Edit, part of Salocin Group Ltd. All rights reserved. Company no.: 0362​4881. VAT no.: 4208​34911.

Salocin Group Certified B Corporation | Cyber Essentials Certified | British Assessment Bureau, ISO 27001 Information Security Management
Salocin Group
Your cookie preferences

We use cookies to ensure this website functions properly, to analyse website traffic and for marketing purposes.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}