Text size: A A A

What do you mean I need ‘permission’?

Licence, permit, registration, certification, accreditation — government has lots of different ways for people to get permission to do something. They all do the same thing — they’re all authorisations by government for an individual or organisation to do something (or not do something).

Together with some of our colleagues at agencies and departments across the UK government, we’ve just completed a discovery about what “getting permission from government” looks like now, and what it might look like in a world of government as a platform.

We’re not trying to create a uniform, one-size-fits-all permissions system. But, we are looking into how common frustrations and similar processes might be opportunities to bring consistency to getting permission for users, and ease of service delivery for government.

What does ‘permission’ mean?

There are hundreds of government permissions written into our laws. Over 100 million permissions are issued in the UK each year.

Each one allows us to do specific activities that would otherwise be illegal, such as drive a car, import chemicals, cross international borders, transport waste, look after children, sell alcohol, fish with a rod, and so on.

These permissions exist for a number of reasons, from collecting money to upholding a particular standard that keeps people safe, from protecting a natural resource or environment to regulating trade. However, more often than not users need to get several licences, exemptions or certificates to do one activity, like run a pub. These separate pieces often need to be completed in a particular order and are provided by different parts of government – meaning that users need to act as a government go-between to get permission for the activity they need to do.

Users who haven’t done that activity before often find themselves in a position where they don’t know if they need permission to do something or which permissions they might need, from where. At this point, they will often need to consult with someone who has done the thing before, or a paid expert to negotiate government’s technical terms or legal jargon on their behalf.

Changes to the rules of these permissions can also have an impact on their lives and businesses — something that users often aren’t aware of until the change has been made.

Defining a good permission

We think that the ways government gives permission could be better for users, and cheaper to provide.

Our team have been asking the question “What does a good permission look like?”.

Put simply, a good permission should meet user needs, be cost effective and serve the regulatory objectives it was created to uphold (safety, resource protection, fair trade etc).

What we learned in discovery

We’ve spoken to people needing permission to do a broad spread of activities (such as childminding, running a pub, driving a car, buying a fishing boat, selling caviar, getting a job in security) in order to understand where there are similarities and differences in the way they understand “permission” as well looking closely at the ways that agencies across government process and issue permission.

So far, our discovery has revealed two things:

  1. While each permission itself supports a specific unique activity (or set of activities), the fundamental process of applying for a permission for the user and granting and issuing for each agency is very similar.
  2. Common frustrations and problems seem to exist for users and agencies along the permissions journey.

This is where government as a platform comes in

Common user problems + similar government processes = opportunities for service standards and platforms.

Among other things, GDS is focussing on six main areas of improvement:

  • help users to find what permission they need for an activity (like childminding) before they do it
  • help users who don’t need permission, or can’t have permission because they aren’t eligible to know before application
  • remove manual process steps for users and government — like requesting a criminal record check — and replace them with automated checks conducted with a user’s consent
  • make the process of change to a permission by government faster and more transparent for users
  • make proving you have permission easier and more secure
  • make it more consistent to apply for a permission or easier for government to set up a service

We are gradually widening the debate and testing our ideas. Recently we held a Show and Tell for the agencies involved in our discovery work. The feedback was very encouraging. The big question for everyone was: “What would this look like in reality?”. And that’s what we are working on next.

This article was first published on the UK GDS blog as “Let’s talk about permissions“.

Author Bio

Stephen Blackmore & Louise Downe

Stephen Blackmore and Louise Downe are managers at the UK Government Digital Service, responsible for business transformation and service design.