Named for the keeper of records.
Why we built it
Locums desks were running on general-purpose software and human memory
Watch a locums recruiter work and you see the same pattern everywhere: a CRM that doesn't know what a name clear is, a credentialing spreadsheet nobody trusts, a shared inbox where coverage requests go to die, travel booked in a browser tab, and rate structures reconstructed by hand at invoice time.
None of that is a discipline problem. It is what happens when the software wasn't built for the work. So we built for the work — provider records with multi-state licensure, job orders with privileging windows, rate cards that separate pay from bill, credentialing that raises its own alarms, and portals so providers and facilities can answer their own questions.
Then we added AI where the hours actually go: reading CVs, searching public registries, extracting credential dates, ranking candidates, parsing itineraries and answering questions about your own pipeline. Every suggestion arrives with its source and waits for a human to accept it, because in this industry a wrong expiration date is a cancelled assignment.
- Locums-only
- Every object and stage models locum tenens work
- 3 portals
- Internal staff, providers and client facilities
- 24 months
- Admin audit history retained by default
Principles
What we hold to when a shortcut is tempting
Evidence over confidence
If the platform proposes a value, it shows where the value came from. Automation you can't audit is a liability in a compliance-heavy business.
One record, many desks
Recruiting, credentialing, coordination and finance read and write the same record. Every duplicate copy of the truth eventually becomes a dispute.
Security is not a setting
Encryption in transit and at rest, least-privilege access, MFA and immutable audit logging are enforced at the data layer, not left to careful screen design.
Depth in one vertical
We would rather be indispensable to locums firms than adequate for every kind of staffing.