For Home Care Agencies
Curalis brings caregiver scheduling, verified care delivery, credentialing, and your placement pipeline into a single multi-tenant platform — so your office isn’t stitching together spreadsheets, paper MARs, and a separate CRM to run the agency.
Build weekly schedules across all of your care recipients, assign caregivers, and use shift templates for recurring visits. When a shift needs coverage, publish it as open and let qualified, available caregivers claim it directly instead of your office working the phones.
Caregivers clock in and out from the recipient’s location, so shift status updates in real time and you can trust that a visit happened where and when it was scheduled. Shift notes and any medication given during the visit stay attached to that shift.
Caregiver credentials live in the same system used to build the schedule, so you can see who’s currently qualified for a given recipient’s care before you assign the shift — not after a compliance question comes up.
If your agency also places clients into assisted living, every inquiry becomes a tracked lead, matched against candidate facilities and moved through your pipeline in the same platform — so leads never live in a disconnected spreadsheet.
Yes. Curalis is multi-tenant, so your organization’s data — recipients, caregivers, schedules, and records — is isolated at the database level (Postgres row-level security) from every other organization on the platform, while your own staff can work across your locations.
When a shift is published as open, caregivers who are eligible to work it based on their credentials and existing schedule can see and claim it themselves, instead of a scheduler calling around for coverage after a callout.
Yes — scheduled and as-needed (PRN) medications, witnessed administration, and refusal or missed-dose documentation all live in the electronic record, attributed to the caregiver who recorded them, so there’s no separate paper MAR to reconcile.
Activity across the platform is captured in an audit log as part of the same security model that isolates tenant data and encrypts it in transit with TLS 1.3.