Technical and platform exceptions

Date adopted: 
June 7, 2022
Last update: 
November 15, 2023

eServices for Citizens is the government’s authority on all technical and platform decisions for public facing digital services and websites. Within our team, our web architects determine what our common platform components are. They base this decision on multiple factors including how well they:

  • allow us to meet the government’s Digital Service Standards;
  • integrate with the government’s enterprise technology direction;
  • provide KPI metrics compatible with those we collect elsewhere on the platform;
  • compartmentalize and protect citizen data in accordance with Privacy Impact Assessments (PIAs);
  • we can repurpose them to meet a variety of the most common business and user needs; and
  • follow industry security trends and isolate both Government of Yukon and citizen users from security risks.

When might a person need a technical and platform exception?

Not very often. The common platform components are in place to meet 90% of existing business and user needs. Every once in while, we’re approached by a team that has unique business or user needs that we cannot accommodate.

In these instances, a member of the eServices team will meet with the project team and a web architect to determine how they should proceed.

We’ll also loop in the Executive Council Office digital team to ensure these next steps align with the government’s content strategy.

What does it mean to have a technical and platform exception?

This means you do not have to use one of the government’s approved platform components for your public-facing digital service or website.

You must follow: 

Official exception sign-off

A web architect or another team member on their behalf will email you official confirmation that you have an exception. They will include details for next steps in this email.

What do next steps look like?

It depends. Every project is different and the next steps depend on the type of solution you need and the complexity of the project. A web architect will provide you with these details, but solutions usually fall into these buckets.

  1. Products that were the solutions used by other teams that had this exception. In these instances, our team will have some familiarity with the product and the teams that implemented them have shared what they learned from implementation to the end user experience.
  2. A new to the government product. These can be commercial-off-the-shelf or other products. In these instances, the eServices team will conduct an assessment to determine how well the product meets the Digital Service Standards. This can take some time, but at the end you will know if you can use the product or not. Teams that want to procure a solution should touch base with the eServices web architect and follow our advice for purchasing digital tools and products.