Service maturity assessments

Date adopted: 
November 9, 2018
Last update: 
May 21, 2024

All new and existing public-facing digital services and websites must meet the government's digital service standards. These standards are made up of requirements from several government departments. eServices has brought them together in one assessment so project teams can see what they need to do to pass and eventually launch their service to the public.

To assess hwo well a digital service meets the standards, eServices completes service maturity assessments. The number and frequency will depend on the size and complexity of your project. They can occur at the end of discovery, prototype development (alpha), and beta testing phases of a project.

The goal of these assessments is to make sure the government releases consistent, quality digital services that are easy to use and accessible. 

Benefits of service maturity assessments

  • You get feedback from a panel of experts.
  • It allows the team to solve problems while you build. This reduces the risk of bigger problems happening later.
  • You have an opportunity to:
    • share your knowledge;
    • learn more about how to build services; and
    • promote the work you’re doing.

Start an assessment

eServices runs and approves these assessments, but you can work with your team and vendor to start pulling together your supporting materials before you meet with eServices.

Schedule an assessment

Your eServices project manager or service delivery manager will reach out to schedule a service maturity assessment. 

If you have been preparing your own service maturity assessment, email [email protected] to schedule an assessment.

Who to bring to a service maturity assessment

Required: Department service owners (subject matter experts, director responsible for the service)


  • people from your team to answer questions about your service;
  • an employee who interacts with the public on a regular basis;
  • the manager of your existing offline service; and
  • a functional analyst.

What you have to do at an assessment

At an assessment, a member of the eServices for Citizens team and your department group need to:

  • give a brief overview of the service;
  • demonstrate the service by walking the panel through an end-to-end transaction; and
  • answer questions from the expert panel, demonstrating how the service meets the service standard.

Read the digital service standards to find out more about what you'll have to discuss, show, or explain.

Get your assessment results

You should get your assessment results within 5 working days. eServices will email you and the department service owner who is responsible for the service you're building.


Your website or service met the criteria.

  • If you pass the discovery assessment you can proceed to prototype development (alpha).
  • If you pass the prototype development (alpha) assessment you can proceed to beta.
  • If you pass the beta assessment:
    • you can launch your website to the public; or
    • launch your service as a beta on You'll need to create a page from to link to your service.

Didn't pass

Your website or service didn't meet the criteria. We'll provide you with feedback and recommendations on how you can make adjustments to meet the standard.

You’ll then have to get your service assessed again.

Partial reassessment

You may need a partial reassessment if your website or service doesn't meet one or two of the criteria. We'll check to make sure you've addressed points that didn't pass.

Full reassessment

If your service had multiple problems, or it’s been a long time since your service’s original assessment, you may have to get it fully reassessed.

Didn't pass, stop development

This means your website or service didn’t pass the assessment. The panel recommends that you stop development.