CRM
Case historyRequest, owner, actions and outcome
CRM, Workspace, Meet, Approvals and ERP are designed to give teams a consistent way to serve members.
The operating tools link a member request to work, decisions and resources. Shared reference numbers and scoped permissions connect the records.
The tools support a continuous service journey without granting everyone the same access.
Request, owner, actions and outcome
Tasks, discussions, agendas and handovers
Decisions, budgets and operational records
Active mandate · Purpose · Sensitivity · Traceable changes
Officers see assigned work, due actions, referrals, correspondence and the member’s updates in one case history.
Tasks, team discussions, documents and handovers link back to the work they support. Role changes should update team access.
Appointments, team reviews and community forums can create agendas, minutes and tasks. Recording requires suitable consent.
Appointments, expenses, publications and referrals follow the relevant approval route. A live mandate determines what a person may authorise.
Budgets, subscriptions, procurement, people, assets and programme records support responsible operations.
Officers and leaders see information at the scope they need. Public and institutional reports use suitable aggregates rather than unrestricted member records.
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.
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.
An officer’s appointment ends while a request remains open.
A supervisor reassigns the record, checks open tasks and transfers authorised access. The member is told who now owns the next step.
Service continuity depends on the record and process, rather than one person’s private messages.