The operating system

Connected work behind every service.

CRM, Workspace, Meet, Approvals and ERP are designed to give teams a consistent way to serve members.

Pre-launch edition · 3 min read · Updated October 2026
The idea, in focus

The operating tools link a member request to work, decisions and resources. Shared reference numbers and scoped permissions connect the records.

The system, illustrated

A connected record behind the work.

The tools support a continuous service journey without granting everyone the same access.

01

CRM

Case history

Request, owner, actions and outcome

02

Workspace + Meet

Team coordination

Tasks, discussions, agendas and handovers

03

Approvals + ERP

Authority and resources

Decisions, budgets and operational records

CONNECTING PRINCIPLE

Active mandate · Purpose · Sensitivity · Traceable changes

On this page
01

CRM: manage the case

Officers see assigned work, due actions, referrals, correspondence and the member’s updates in one case history.

02

Workspace: coordinate the team

Tasks, team discussions, documents and handovers link back to the work they support. Role changes should update team access.

03

Meet: turn discussion into action

Appointments, team reviews and community forums can create agendas, minutes and tasks. Recording requires suitable consent.

04

Approvals: check authority

Appointments, expenses, publications and referrals follow the relevant approval route. A live mandate determines what a person may authorise.

05

ERP: manage resources

Budgets, subscriptions, procurement, people, assets and programme records support responsible operations.

06

Dashboards: see the right detail

Officers and leaders see information at the scope they need. Public and institutional reports use suitable aggregates rather than unrestricted member records.

07

A connected record, not unrestricted access

A case can link to a task, meeting, approval or resource decision without exposing its entire contents to every participant. The system should check the active role, service purpose, scope and sensitivity before allowing an action.

08

A practical team rhythm

Planned work queues highlight new requests, waiting items, due tasks and cases needing review. Supervisors check handovers and unresolved concerns; leadership reviews suitable aggregate information and resource needs. Each level sees detail appropriate to its responsibility.

A practical example / Planned experience

A handover without starting again

01

The starting point

An officer’s appointment ends while a request remains open.

02

How the parts connect

A supervisor reassigns the record, checks open tasks and transfers authorised access. The member is told who now owns the next step.

03

What useful progress means

Service continuity depends on the record and process, rather than one person’s private messages.

Explore the connected pathway
How the parts connect

A clear path through the experience.

  1. 01Member need
  2. 02Case
  3. 03Tasks and referral
  4. 04Decision
  5. 05Outcome
  6. 06Learning

Find your way.

Search the community, services, wings and practical questions.

Esc to closeExplore all pages →