Since June 2025, Bizont has been working with the Yukon Government on the Yukon Corporate Online Registry (YCOR), a foundational system that supports corporate registry services used by both government staff and the public.
YCOR is an in-progress custom-built modernization effort. Rather than focusing on the finished outcome, this post shares what the team has learned so far, the decisions shaping the work, and the people responsible for carrying it forward.
One of the earliest, and most important realizations was that YCOR involved more than replacing technology.
"It started as what seemed like a straightforward move from an older system to a newer, more maintainable platform,” says Mariazel, Bizont’s Custom Development Project Manager." “But as we went deeper, it became clear we were also redesigning and digitizing workflows that were still heavily manual.”
That shift moved the work away from replicating existing behaviour and toward understanding the purpose and intent behind long-standing processes
“We’ve spent a lot of time understanding the ‘why’ behind workflows,” Mariazel adds. “That clarity is what allows us to plan and deliver incrementally, without losing sight of long-term responsibility.”
From a business analysis perspective, success depends on how well the system reflects how registry work actually happens.
“We’re not just recreating forms,” says Maricruz, Bizont’s Business Analyst. “We’re rethinking how people complete registry work and how it can be more intuitive and straightforward for both public users and staff.”
For internal teams, that means reducing administrative effort through clearer structure and automation.
“Lowering manual workload allows staff to focus on applying legislation and reviewing requests,” Maricruz explains, “instead of repeating manual steps inside the system.”
For the public, it means guided, self-service workflows that reduce barriers and uncertainty when interacting with government services.
As with many long-standing government systems, YCOR surfaced inconsistencies between legislation, data, forms, and current system behaviour.
“Some workflows were never fully documented for online delivery,” Mariazel notes. “We’ve had to research current behaviour, validate with subject matter experts, and be realistic about what belongs in future phases.”
Rather than rushing to resolve everything at once, the team made a deliberate choice to phase the work — prioritizing accuracy, clarity, and maintainability.
“Managing expectations has been critical,” Mariazel says. “Scope discipline protects the quality of the system over time.”
This approach reflects a shared responsibility to ensure the registry is defensible, reliable, and adaptable as needs evolve.
YCOR brings together many parts of government.
“We’re working with operational subject matter experts, internal platform and access teams, and service design and UX standards groups,” Mariazel explains. “That level of coordination means clear communication and documentation aren’t optional — they’re essential.”
From the requirements side, complexity shows up in the details.
“Many requirements sit at the intersection of legislation, operational practice, and system behaviour,” Maricruz adds. “Even workflows that seem simple become complex once you account for validations, exceptions, usability standards, and bilingual needs.”
Strong documentation and shared understanding help ensure decisions are traceable and accountable, which are essential requirements for long-lived government systems.
“The project feels more stable now,” says Mariazel. “We understand the landscape much better and can move forward with greater confidence.”
That confidence is reinforced through collaboration.
“Having engaged, responsive subject matter experts makes a project like this possible,” Maricruz notes. “It allows decisions to be grounded in real workflows and real rules.”
Strong documentation and shared understanding help ensure decisions are traceable and accountable, which are essential requirements for long-lived government systems.
“Right now, it’s about coordinating delivery while continuing to refine workflows and business rules,” Mariazel explains. “Balancing delivery discipline with ongoing learning is key.”
For Maricruz, success will ultimately be felt by users.
“I’m excited for users to complete processes more easily and confidently,” she says. “For the system to feel structured, intuitive, and reliable.”
Throughout the project, the intent has been to build a system that government teams can understand, maintain, and evolve over time — supporting ownership of the technology and reducing long-term reliance on external support.
Registry systems are foundational public infrastructure. Decisions made during modernization efforts can shape service delivery for years to come.
“When services are digitized thoughtfully, people can complete important tasks without unnecessary barriers,” Mariazel reflects. “And government teams benefit from systems that are maintainable and adaptable as needs evolve.”
That emphasis on clarity, accountability, and long-term stewardship defines how the YCOR project is being delivered today.
If something in this post resonated—or sparked ideas—we’d love to hear from you.
If something in this post resonated—or sparked ideas—we’d love to hear from you.
Join our mailing list to receive fresh insights, stories and updates.
