Somewhere in your organisation there is a coordinator holding a peer-support program together with a roster, a phone and personal credibility. The peers do the work alongside their day jobs. The contacts happen in corridors, car parks and control rooms. And almost none of it is anywhere a program could actually be managed from.
The program everyone relies on and nobody can see
Peer support has earned its place well beyond the emergency services where it grew up. Health services, corrections, transport, utilities and financial services run peer programs for the same reason fire and ambulance services do: when work exposes people to distress, the first conversation is easier with a trained colleague than with a stranger. What most of these programs share is the same operational gap. Contacts logged in notebooks, or not at all. Coverage nobody can state with confidence. A peer supporter quietly worn down by the load, invisible until they step away. Training expiries in a spreadsheet tab that someone updates when they remember.
A peer role with a hard edge
CaseNote gives peer supporters contact logs and wellbeing checks inside a clearly bounded role. Peers never see clinical detail, and the boundary is enforced in the database, on both read and write, not by hiding a menu item. That edge matters three ways:
- It keeps the program consistent with published peer-support guidance.
- It makes peers safe to talk to, because a conversation with a peer cannot bleed into a clinical file.
- It protects the peer supporters themselves from holding information they are not trained or supported to carry.
Capture that fits between jobs
A contact that takes ten minutes to log does not get logged, and an unlogged contact makes the whole program invisible. CaseNote's quick contact logging is designed for non-incident capture at speed: a peer records who they checked on and what came of it in the time it takes to wait for the next job. The record accrues, and goodwill stops being the database.
Coordination without chasing
Follow-ups become tasks, not memories. CaseNote provides internal task assignment with priorities and due dates, and every peer and coordinator works from a my-tasks queue. When a check-in needs to happen by Friday, someone owns it and the queue says so.
The program that looks after its own people
Peer supporters absorb other people's worst days, and every experienced coordinator knows it. In CaseNote, peers track their own wellbeing with short structured check-ins, and a low score, or a request for help, reaches a supervisor immediately. Each peer's own load is tracked across contact volume, escalations and incident-linked contacts, and when it runs high, the system nudges for supervision rather than waiting for someone to notice. Training currency is tracked with auto-calculated expiry for peer-program roles, so an accreditation lapse surfaces before it matters.
Aligned with published guidance
CaseNote's peer-support model aligns with the peer-support guidance published by Phoenix Australia: early contact, a bounded peer role, clear referral pathways, supervision for the supporters, and confidentiality with narrow, sanctioned exceptions. That is alignment with published guidance only; CaseNote is not endorsed by, or affiliated with, Phoenix Australia.