How it works
RiGEL starts with how the Nation works.
Implementation follows a deliberate path: Discover, Configure, Connect, Launch, and Evolve. RiGEL is not dropped in as a generic template. It is shaped around the Nation's structures, authority, terminology, systems, and priorities.
Implementation begins with understanding, not assumptions
Before anything is configured, RiGEL needs to understand the operating environment it is entering.
The people who hold the relevant operational knowledge help shape discovery — including leadership, administrators, programme teams, trustees, finance, IT, privacy, security, legal, governance, and other Nation-identified stakeholders.
A deliberate path from understanding to operation
Discover
We map how the Nation currently works, where responsibility sits, what systems are already in place, and which processes need the most attention.
- Structure
- Authority
- Systems
- Responsibilities
- Pain points
- Priority workflows
Configure
We configure RiGEL around the operating model identified during discovery.
- Roles
- Permissions
- Departments
- Entities
- Approval limits
- Workflows
- Programme requirements
- Terminology
- Decision pathways
- Record requirements
- Notifications
- Queues
- Access restrictions
- Effective dates
Connect
RiGEL fits into the technology environment that already exists.
Implementation determines what information should move between systems, what should remain in its existing system of record, where an integration is appropriate, and where a manual handoff is more responsible.
Keep authoritative systems authoritative
Accounting, identity, documents, banking, and other specialized systems can remain where they belong.
Connect only what creates value
Not every system needs an integration.
Move only what is necessary
Some information should remain in its existing system or should not move at all.
Make the boundary clear
Each implementation should define which system owns which part of the record.
RiGEL connects operational context where that connection is useful.
Launch
Launch is more than switching a system on.
A member-facing programme and a low-risk internal workflow do not automatically follow the same launch path.
Evolve
Nation operations change. Programmes, policies, leadership, roles, approval limits, departments, and services change over time. RiGEL evolves with those changes while preserving the history of what came before.
The Nation defines:
- Who can request a change
- Who can approve it
- When it takes effect
- What it changes
- What remains historical
- What record of the change is preserved
A new rule takes effect when the Nation says it does. It does not silently rewrite earlier decisions.
Start with a defined operational need
A Nation does not need to implement every RiGEL solution area at once.
An engagement can begin with one:
- Trust
- Benefit programme
- Service workflow
- Governance process
- Administrative bottleneck
- Records challenge
- Defined pilot
Additional capabilities can be introduced where they create real operational value.
Scope before promises
Implementation scope depends on:
- Number of workflows
- Complexity of authority
- Departments or entities involved
- Integrations
- Data migration
- Privacy and security requirements
- Training
- Approvals
- Configuration
- Required product development
A responsible estimate starts with understanding those factors.
Implementation includes the people doing the work
The people who use, manage, approve, and inherit a process help validate:
- Workflows
- Terminology
- Authority
- Scenarios
- Exceptions
- Communications
- Training
- What should — and should not — be automated
Implementation reflects operational reality, not just a diagram.
Training is part of implementation
Training covers more than where to click. Users need to understand:
- What RiGEL is responsible for
- What remains outside RiGEL
- How their role works
- What authority they have
- What they can access
- How workflows move
- What happens when something goes wrong
- Where to get help
Clear boundaries throughout
Start with the part of your operation that needs to work better.
RiGEL begins by understanding the current process, the people involved, the authority behind it, and the systems already in place. From there, we define what a responsible implementation looks like.