What happens at a service assessment
You may need to book a service assessment to check youāre meeting the Service Standard. Check if you need an assessment if youāre not sure.
Your assessment will be run by a panel of experienced specialists from the Government Digital and Data community. Panels are normally made up of a lead assessor, a user researcher, a designer, a technical lead and sometimes a performance analyst. There might also be one or two observers, but they will not ask questions.
Assessments usually last about 4 hours.
Check with your departmentās assessment team for more information about what will happen at the assessment.
Preparing for an assessment
It can be tempting to spend a long time preparing for assessments.
But try not to over-prepare. Do just enough to make sure you can give an open and honest account of the work youāve done and what youāve built.
And remember that the panel is not there to catch you out. They offer a peer review of the work youāve done and help you understand anything youāll need to change or improve.
What to cover on the day
Spend the first 30 minutes of the assessment talking about and demonstrating what youāve built. During that time, youāll need to:
- give an overview of your service
- walk the panel through the user journey
Give an overview of your service
In any assessment, itās useful to start by briefly setting the scene. This usually means talking about the things you learnt during your discovery and alpha, including:
- why youāre solving the problem youāre solving
- who your users are and what theyāre trying to do
- the work youāve done to understand the userās wider journey, if there is one
Itās also useful to explain any changes you made based on the feedback the service got at its previous assessment, if it had one.
Aim to spend no more than 10 minutes covering these issues.
Walk the panel through the user journey
Once youāve explained what your service is and why youāre building it, spend around 20 minutes walking the panel through what youāve built.
You might not have time to show every screen, but you should make sure to show any particularly important interactions.
Do not just focus on the happy path. Also show what happens to users who are not eligible, or who cannot provide a piece of evidence at the right time.
Remember to talk about the whole user journey, including offline channels. This means explaining the processes that support staff need to follow to deliver the service, as well as the skills and capabilities they need to have.
At the alpha stage, you only need to prototype enough to test your riskiest assumptions - not necessarily the entire user journey. It might be worth bringing along a set of user needs or a rough journey map to your assessment too.
This post on the services in government blog gives advice about how to .
Answer questions from the panel
Once youāve demonstrated your service, the panel will spend the remaining time asking questions about the decisions youāve made and how youāve built your service.
Thereās no specific set of questions that a panel will ask during an assessment. Itāll differ depending on the service youāve built and which development phase youāre in.
Itās a good idea to make sure you and your team are familiar with:
- the Service Standard
- the requirements for the development phase youāre working in
Thereās also guidance on how assessors will apply the Service Standard.
Get your result
Your service will be assessed as āgreenā, āamberā or āredā.
āGreenā means that the service has met the standard and can continue to the next phase of delivery.
āAmberā means that the standard has not yet been met, but the issues are not critical. The service can continue to the next phase of delivery while you work on the amber issues.
You need to fix amber issues within a reasonable period of time, usually up to 3 months. You must record your progress in a live ātracking amber evidenceā document which will be visible to the assessments team.
āRedā means that the standard has not yet been met and the issues are critical. The service will stay in its current phase of delivery. Further work needs to be done on the points that did not meet the standard before they can be reassessed. .
If your service has been assessed by a cross-government panel youāll get your result in a report within 3 to 5 working days.
What happens next depends on the result of the assessment, and the delivery phase your service is in.
Departmental assessments
There can be exceptions to red, amber and green assessment ratings.
Your service may be assessed as āmetā or ānot metā if the assessment was done by a panel from your own department. Contact your departmentās assurance team to ask how your service will be assessed and when youāll get the result.
Assessment reports
GDS will publish the outcome of the assessment - see the list of published Service Standard Reports. Youāll have the chance to fact check it before itās published.
Examples and case studies
Read the Department for Work and Pensionsā blog post on .
Read the Office of the Public Guardianās (OPG) blog post on how they .
Related guides
You may also find the following guides useful:
Updates to this page
-
Corrected timings and updated out of date references.
-
This guidance has been updated to reflect a change in the way assessments are rated.
-
Added detail on how and what to prepare for a service assessment.
-
Clarified guidance on what happens at a service assessment.
-
Updated the address for GDS assessments to The White Chapel Building.
-
Added link to 'How your assisted digital support will be assessed'.
-
Guidance first published