Works with your rota system
Connect Loup to the rota or scheduling system you already use. Carers and the people you support are entered once and kept in step, and your rota knows straight away if a carer can no longer be rostered.
Enter people once
Add a carer or a person you support in either system and the other is updated. Each record is linked to the other system's own reference, so they always match up.
Safe to roster
Your rota can check every carer before booking them. A lapsed DBS, an overdue right-to-work check or someone on leave blocks them, and out-of-date training or missing references are flagged.
Told straight away
When a carer or person supported changes or leaves, or a carer's compliance changes, Loup sends your rota a signed message within seconds.
Missed and late visits
Your rota can report a missed or late visit, and it arrives in Loup as an incident to review. It's linked to the person, the carer and the location.
You choose what's shared
Tick exactly what each connected system may see and do, and limit it to particular locations. Medical notes, DBS details, references and documents are never shared.
Every exchange recorded
An activity log shows every request in and every message out. Disconnect at any time and the connection stops working immediately.
Connected in three steps
- A manager opens Integrations in your Loup system, names the connection and ticks what it may do.
- Loup creates a private key, shown once, which you give to your rota provider. Optionally, add their notification address so Loup can tell them about changes.
- Your rota provider connects using our developer guide, and the two systems stay in step from then on.
| From Loup to your rota | From your rota to Loup |
|---|---|
| New carers and people supported, and changes to their details | New carers and people supported, if added there first |
| Whether each carer can be rostered, and why not | Missed and late visits, which become incidents to review |
| Leavers, so they stop appearing on the rota | Their own reference numbers, so records stay linked |
| Which location each person belongs to | — |
Nothing is shared until you connect
- Each agency decides for itself, and only managers who cover every location can connect a system
- You'll need a data processing agreement with the company that runs the other system
- Only basic details are shared. Care needs are shared only if you tick them, and medical notes, DBS details, references and documents never are
- Secure, encrypted connections with a private key per connection, and messages signed so the other system knows they came from Loup
Build a connection to Loup
A simple, documented API: read and update carers and people supported, check whether a carer can be rostered, report missed or late visits, and receive signed notifications when anything changes.