All public-facing online services must go through eServices and the Executive Council Office (ECO). This is under the authority of the government’s “Governance of Digital Services” policy (GAM 1.20). eServices are the authority on the service design and technical guidance and standards and ECO is the authority on content design guidance and standards.
As a group (eServices, ECO and all departments) we have the responsibility of coordinating and delivering government digital services that are user-centred, align with corporate goals and meet user expectations, as well as being secure, private, accessible, bilingual and mobile-friendly. This applies to all government-to-public digital services and digital communications.
How does a department get an online service built or know what cloud service to subscribe to?
There are two different approaches to putting a new public-facing service online, whether custom-developed or via a cloud-based provider.
Management Board submissions
One of the ways we identify there is an online service being built is through Management Board submissions. Generally speaking in this scenario:
- Departments propose projects.
- An evaluation committee makes a prioritized list of discretionary (projects) and non-discretionary (software licenses, computers, etc.) budget columns.
- The management board secretariat reviews and approves projects.
- The funds are allocated to departments for project work. The project budgets are governed by various government policies. This includes GAM 1.20 for digital service delivery.
- Departments are responsible for moving the project forward and meeting with eServices for a pre-discovery meeting to plan how to get the work done.
Another way we find out about these projects is when a department approaches us. In this scenario:
- Department has money and wants to get something built or subscribe to cloud-based software to provide an online service.
- Department contacts eServices. Our unit will explain roles, responsibilities, process etc. We have been adding more and more of this documentation to the digital standard and we are always building on it and refining it.
- The department and eServices will come up with a plan to deliver the project as efficiently as possible. This includes connecting the department with vendors to do the development work or help with technical plans.
- The work can then start.
Through the government’s content migration to Yukon.ca
As ECO meets with departments to execute our transition plan they dive into the department website content and often find applications, forms and other elements that could be future online services. We add these to the list of Yukon.ca features and builds. In these cases, the department would follow the process outlined above.
If you have any questions about this process email email@example.com.