Service Compliance Checks (SCCs)

What is a Service Compliance Check?

All new and existing public-facing digital services must meet the Government of Yukon’s digital service standards. These standards are made up of requirements from several government departments. eServices has brought them together under Service compliance checks (SCCs) so project teams can clearly see what they need to do to meet the standards and successfully launch their service to the public.

To assess how well a digital service meets the standards, eServices conducts Service compliance checks and UX Assessments. The number and frequency of these checks depend on the size and complexity of the project. They typically occur towards the end of the Discovery phase, during prototype development (Alpha), and throughout Beta testing.

The goal of these checks and assessments is to ensure the government releases consistent, high-quality, bilingual, and accessible digital services that are secure, reliable, and easy to use.

How to tell when your digital service is ready for a Service Compliance Check (SCC)?

Your service is ready for an SCC when:

• A project plan is in place and being followed to meet compliance requirements related to digital standards.
• You have completed the key deliverables for the current project phase (Discovery, Alpha, or Beta).
• Planned functionality and milestones for that phase are in place and can be demonstrated for eServices review, even if not final (e.g., user research, requirements gathering, wireframes, working prototype).
• Your project team has filled in or updated the compliance log in your SharePoint project folder.
• You are prepared to walk through the service with the eServices project lead (previously called the eServices Delivery Manager) and answer questions about compliance, user experience, and technology.
• If you are unsure, reach out early. Your assigned eServices project lead (previously called the eServices Delivery Manager) will guide you on timing and confirm whether your service is ready for the Service compliance check.

How to schedule a Service Compliance Check

• Plan ahead: When building your project plan or timeline, schedule SCCs in advance. You can reassess readiness closer to the date and adjust if needed.
• Contact your eServices project lead: Reach out to request or reschedule an SCC. We prefer at least one week’s notice to ensure availability of all participants. If there is no assigned eService project lead, email eservices@yukon.ca.
• Initiate the request: Send your project lead a short email update that includes:
  • Current project phase (Discovery, Alpha, or Beta)
  • Key deliverables completed
  • Suggested participants for the SCC
• Prepare your compliance log: Ensure the Service Compliance Check log in your project’s SharePoint folder is up to date to the best of your ability. If you have any questions while filling it out, reach out to your eServices project lead. They will collaborate with the project manager and relevant team members to support completing the log.
• Provide supporting materials: Share helpful documents in advance (e.g., prototypes, user research, wireframes, content drafts, technical notes).
• Work with your team and vendors: Begin gathering supporting evidence before the SCC session so the review runs smoothly.
• eServices coordination: Your project lead will schedule the SCC, and guide next steps if items need to be brought into compliance.

Who should attend a Service Compliance Check?

Required: Project Manager and department service owners (subject matter experts, client project contact)

Optional:

• 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.

How to prepare for a Service Compliance Check

To prepare for a Service compliance check, fill out the relevant tab in the Service compliance check log in your project’s SharePoint folder to the best of your ability. If you have any questions while completing it, reach out to your eServices project lead, who will collaborate with the Project manager and relevant team members to provide support. Additionally, share any documents that may help with the review in advance, such as links to prototypes, user research, wireframes, content drafts, or technical notes.

What happens during a Service compliance check?

The eServices project lead facilitates a call or in-person session with the project team to review the Service compliance check (SCC) log and assess the digital service or website against the Digital Service Standards.

The review typically includes:

• Reviewing the SCC log to ensure accuracy and identifying non-compliant items and actions required to bring the service into compliance before public release.
• Reviewing project deliverables for the current phase (Discovery, Alpha, or Beta), such as prototypes, wireframes, user research, content drafts, and technical notes. Perform a high-level service review to ensure it meets basic expectations.
• Discuss and explore options and strategies for meeting specific compliance criteria, if concerns arise.
• At the end of the meeting, the SCC log will be considered up to date. Your eServices project lead will communicate any necessary timelines and next steps for addressing non-compliant items to bring them into compliance.

These sessions are generally scheduled for 30 to 45 minutes, depending on the project.

What happens after a Service compliance check?

After a Service Compliance Check, the eServices project lead will notify the Project Manager when the SCC log and review is available. The Project Manager will then share the log with the project team and follow up with the eServices project lead to communicate the team’s plan for addressing any compliance gaps. Together, they will work to prioritize and bring non-compliant items into compliance and ensure the SCC log is updated accordingly.

If the SCC identifies that the service is ready for a UX assessment, it can be scheduled at this stage.