Bringing SEAS Applications Online: A Secure Regulatory Portal Success Story
Credential assessment is one of those processes where regulatory technology should just disappear into the background.
- Applicants need to clearly know what happens next.
- Staff need data they can trust to work off.
- Sensitive documents need to be treated carefully.
- Payments, application stages and records should all be connected.
The complexity needs to be in the software, not in the path of the applicant.
This is why we're working with the Association of Canadian Occupational Therapy Regulatory Organisations (ACOTRO) to help in the update of its Substantial Equivalency Assessment System (SEAS).
In recent years SEAS has seen a growing number of applications from internationally educated occupational therapists. Successful completion of the process allows the individual to proceed to registration with a Canadian occupational therapy regulator.
Technology behind a key process for people at a key point in their career matters.
Why This Project Was Important
SEAS is not just an online form.
An application has information about credentials, academic documentation, evidence of fieldwork, identity information, assessments, multiple stages and payments. ACOTRO’s own guidance makes clear that applicants may need to submit sensitive documentation at a number of points in the SEAS process.
Moving that process online wasn’t just a matter of putting the old form online. The underlying system needed to mirror the way SEAS actually works.
What Changed At a High Level
We deployed Nation Builder as the backend infrastructure for the new SEAS application environment and tailored the platform to ACOTRO’s specific workflows.
The project comprised:
- Custom online portal for SEAS applicants, based on the Member Portal
- A dedicated management portal for SEAS staff, to provide a secure environment to manage applications
- A database compiled from SEAS records, terminology and application requirements
- Privacy and security features customised for sensitive documents, application cycle & payment management
- Nation Builder for enterprise-level complex workflows, privacy requirements and future growth
A system needs to be one process where multiple apps work together, not six pieces of software.
The Applicant Portal
The underlying Members Village app is the Member Portal but SEAS applicants are not typical association members.
So we tailored the experience to the task they actually need to do.
With the new SEAS portal, an applicant can start the process online by creating an account and making their first payment. The portal provides an authenticated digital environment to support the application experience as more SEAS process elements go online.
This is an important difference in custom software. Changing a logo and a couple of labels is not the same as understanding the use case.
The goal was to make the Members Village infrastructure act like a SEAS application system. Not for SEAS to act like a traditional membership organization.
SEAS Staff Portal
There’s another side to every applicant portal: the people that are responsible for administering what comes through it.
We extended the association Leadership View into a custom management environment specifically for application administration for SEAS staff.
The management portal provides staff with a purpose-built space to work with SEAS application information securely, rather than having to work through a generic back-office interface.
This also shows an important part of the architecture of the Members Village.
Our apps can offer the starting point, not just the finish line.
The standard Leadership View is designed to bring important organisational information to the surface into a secure, accessible interface with intentional permissions and role-based access. That foundation, for SEAS, was changed to a different need: manage a specialised regulatory application workflow.
Privacy Built into the Architecture
SEAS deals with information that needs careful handling.
ACOTRO advises that the information provided by applicants may include contact details, education and employment history, identification documents and financial information. Its privacy guidance also stresses safeguards appropriate to the sensitivity of the information and access on a need basis.
In this project, privacy couldn’t be an afterthought after the application workflow was built.
We built custom privacy and security features around the documentation, and shaped the system around the way SEAS needs to manage information. With the entire portal hosted in Canada to ensure data residency.
Good security is often invisible to the user of a system. That's the point.
The applicant should be able to do the task in front of them without having to parse through all of the rules working behind the scenes to protect the process.
A Database Built Around SEAS
A specialised portal generates specialised data. Trying to force that information into a rigid, pre-determined CRM structure would simply move the administrative friction from one system to another.
We configured the database based on the actual needs of SEAS using the Database Builder.
Database Builder enables organisations to create custom fields, terminology, record structures, views, rather than forcing them to change their processes to fit a generic database.
For SEAS, this means that the database can mirror the program it is supporting. That seems obvious. Software has to fit the job.
Using Membership Infrastructure for Application Cycles and Payments
The flexibility continues with the Membership Database & CRM.
For the typical association, our database & CRM app could handle membership applications, approval paths, renewals and dues. Members Village doesn’t assume that all organisations are on the same journey. It allows you to configure your intake process, approval gates, and different membership cycles.
We also configured installment payments and tax jurisdiction for SEAS to meet their needs. An example of what a configurable platform should be able to do.
The tool name does not have to define the organization’s process. The process specifies how the tool is configured.
Infrastructure that can grow
The June 2026 launch was just the beginning.
ACOTRO’s bigger improvement project will run from 2025 to 2028 and will involve automating processes, making it easier to navigate the program and bringing more SEAS capabilities online over time.
That made foundation especially important.
SEAS gets a connected foundation that supports applicants & staff, and has a team of experts to guide the next steps.
Complex Regulatory Use Cases
Associations and regulatory groups often have processes that do not fit neatly into standard software.
- An applicant is not always a member.
- Payment does not always mean renewal.
- A portal is not necessarily a member portal.
- A database is useful only if the structure reflects the decisions that people need to make.
The SEAS project demonstrates what can be done when the underlying infrastructure can be shaped to the distinctions.
We started with core Member Village regulatory software and tools. Then we got busy configuring, expanding and customising them around the actual work ACOTRO and the SEAS team had to do.
Does your software fit your Regulatory process?
Some organisations require membership renewals.
Others have applications, credentials, approvals, identity documents, payments and workflows that don’t fit neatly inside traditional association software.
Tell us a little about what your organization has to manage. We’ll look at how Members Village can be customised to fit your data, your users and the processes that make your organization different.
No generic software pitch. It’s just a conversation about whether this platform fits the work.