Caretech AITechnology that Cares
Workforce & operations

The right person, cleared, on the right shift.

Discovery by role and readiness, availability-based matching, approval-led confirmation, calendar visibility and time capture — with double-bookings refused at the gate. An open shift asks four questions at once, and Caretech holds all four in view at the moment somebody confirms.

The problem

A gap in a rota is four questions at once.

Who is the right role. Whose credentials are current for that date. Who is actually free. And what this particular facility insists on before anyone walks through the door.

Each answer lives somewhere else — a rota, a credential folder, a text message, a facility's own rulebook. A coordinator reconciles them by hand, at speed, usually while someone waits on the phone. The failure is rarely a bad decision. It is a decision made without one of the four in view.

Filling the shift is the easy half. Filling it with someone who is genuinely allowed to work it, on that date, at that facility, is the half that goes wrong.

The matching model

Four conditions converge. Then a person confirms.

Four independent conditions have to agree before anyone is eligible at all. Caretech models an open shift as that convergence — role, credential readiness, availability and the facility's own requirements — and then hands the shortlist to a person.

How an open shift becomes a confirmed assignment

01 · OPEN SHIFT A facility posts a shift Role, date, hours, location 02 · MUST ALL AGREE Role requirement Credential readiness Availability Facility requirements 03 Eligible clinicians Everyone all four conditions allow 04 Match & rank A shortlist, ordered by the rules 05 · HUMAN REVIEW The facility or coordinator confirms 06 Confirmed assignment 07 · THEN Time capture Communication Follow-up

01 Open shift

  • A facility posts a shift
  • Role, date, hours, location

02 Must all agree

  • Role requirement
  • Credential readiness
  • Availability
  • Facility requirements

03 Eligible clinicians

  • Everyone all four conditions allow

04 Match & rank

  • A shortlist, ordered by the rules

05 Human review

  • The facility or coordinator confirms
  • No assignment is made by the software alone

06 Confirmed assignment

  • Booked, and visible on a calendar

07 Then

  • Time capture
  • Communication
  • Follow-up
What it supports

Flexible shift models, for people who are not interchangeable.

Clinicians, nurses, caregivers, allied health staff and support workers — each with a different set of things that must be true before a shift is theirs. The platform runs:

Finding the shift

Discovery is filtered by what the clinician is, not only by what is open.

Shift discovery based on role and readiness Availability-based matching Facility-specific shift posting Approval-led shift access

Holding the schedule

Once confirmed, the assignment has one place to live and one calendar to appear on.

Booked schedule management Calendar visibility Shift reminders Mobile scheduling workflows Attendance and time capture

Working the shift

Communication that knows which shift it is about, rather than a general inbox.

Shift-aware support Facility and clinician communication

Built for healthcare staffing operations, home care networks, post-acute centers, behavioral health facilities and institutional care settings.

One open shift, from request to confirmation.

Open shift · Ward 3B Thu 07:00–15:00 · Sample Facility Status Requests Discovery by role and readiness 3 received Credential check Current against the date worked 2 cleared Availability Back-to-back allowed; overlap is not 1 conflict Confirmation A scheduler confirms — a person A. Sharma, RN Calendar The same conflict shown before the click Updated
RequestsDiscovery by role and readiness3 received
Credential checkCurrent against the date worked2 cleared
AvailabilityBack-to-back allowed; overlap is not1 conflict
ConfirmationA scheduler confirms — a personA. Sharma, RN
CalendarThe same conflict shown before the clickUpdated

Product illustration with sample data.

The gate, step by step

Watch the gate refuse a double-booking.

One request, followed to the moment it is refused. The calendar warns before the click, the gate enforces at the click, and the refusal is written down with a name and a time — the same sequence a scheduler sees on the floor, drawn here with sample data.

A REQUEST ARRIVES THE CALENDAR SHOWS THE CONFLICT FIRST A SCHEDULER CONFIRMS ANYWAY THE GATE REFUSES THE REFUSAL IS ON THE RECORD CONFIRMATION · WARD 3B · THU R. Kulkarni · scheduler 06:05 · Shift request A. Sharma, RN asks for Thu 12:00–20:00 Received A. Sharma, RN · Thursday Overlap 12:00–15:00 HELD · 07:00–15:00 REQUESTED · 12:00–20:00 06:00 12:00 15:00 23:00 06:11 · Confirm attempted R. Kulkarni confirms A. Sharma onto 12:00–20:00 Sent to the gate 06:11 · REFUSED AT THE GATE Overlaps a held shift · no assignment written · the shift stays open 06:11 · Refusal recorded Who: R. Kulkarni · Rule: overlap of a held commitment · When: Thu 06:11 On the record Months later, “why was this refused?” still has an answer.

A request arrives

At 06:05, A. Sharma, RN asks for Thursday 12:00–20:00 on Ward 3B. Discovery has already filtered by role and readiness, so the request itself is legitimate — the kind a scheduler sees twenty of before breakfast.

The calendar shows the conflict first

A. Sharma already holds 07:00–15:00 that day. The requested block overlaps it by three hours, and the calendar marks the overlap before anyone clicks — the same rule the gate will enforce, shown early, because it is one rule with two callers.

A scheduler confirms anyway

At 06:11, R. Kulkarni confirms the request. Fast mornings produce exactly this click. The confirmation does not write to the rota — it goes to the gate.

The gate refuses

The confirmation is rejected: it overlaps a commitment already held. No assignment is written and the shift stays open for someone else — while a legitimate back-to-back, 15:00–23:00 after 07:00–15:00, would have been allowed.

The refusal is recorded

Who confirmed, which rule refused it, and when — written down with the same care as a clearance. When somebody asks in March why this shift was not double-filled in November, the record answers.

Why a person confirms

Ranking is a shortlist. Confirming is a commitment.

A ranked list is an argument the software can make from rules it was given. Putting a named human being into a building on a named date is a different kind of act, and it belongs to a person who can be asked why.

  • Ranking is rule-based and inspectable. Anyone can be told which condition put a clinician where.
  • Eligibility is a filter, not a recommendation. Failing any one of the four conditions removes a clinician from the set entirely.
  • The calendar shows the same conflict before the click that the gate enforces at the click — one rule with two callers.
  • Approval-led access means a shift becomes workable when a person says so, not when a queue empties.
Your decisions

Four decisions that stay with your organization.

The platform runs the rules. Who is competent to work a shift, and on what terms, is a judgment the organization that employs or contracts them makes — and Caretech records.

Rule-based ranking

The rules produce a set and an order; a person produces the assignment, and Caretech records who confirmed it, against which shift, and when.

The confirmation gate

A double-booking is refused at confirmation, no assignment is written, and the shift stays open — while a legitimate back-to-back 07:00–15:00 then 15:00–23:00 is allowed.

Requirements at the gate

Credentials are checked at request, at confirmation and at clock-in, with expiry judged against the date of the shift being worked.

Working-time obligations

Rest periods, fatigue policy and working-time law are the employer's to set and enforce. Caretech surfaces the schedule they are enforced against.

Approval-led access means a shift becomes workable when a person says so, not when a queue empties — and the ranking behind the shortlist stays inspectable, so anyone can be told which condition put a clinician where.

How we think about trust

Questions

What schedulers ask first.

Five questions that decide whether a scheduling system holds a rota or just displays one.

01

What stops a clinician being double-booked?

The confirmation gate. Confirming a worker onto a shift that overlaps a commitment they already hold is rejected, no assignment is written, and the shift stays open for someone else. A legitimate back-to-back — 07:00–15:00 then 15:00–23:00 — is allowed.

02

Does the calendar show the same conflicts the gate enforces?

Yes. The calendar shows the same conflict before the click that the gate enforces at the click, because it is one rule with two callers. A coordinator is never surprised by a refusal the screen did not warn about.

03

Does the software assign shifts on its own?

No. Rule-based ranking produces a set and an order; a person produces the assignment, and Caretech records who confirmed it and when. Ranking is inspectable, so anyone can be told which condition put a clinician where.

04

How are credentials checked against a shift date?

Requirements are checked at request, at confirmation and at clock-in, with expiry judged against the date of the shift being worked rather than the moment of the click. Clearances and refusals are both recorded against the shift.

05

Which operations is it built for?

Healthcare staffing operations, home care networks, post-acute centers, behavioral health facilities and institutional care settings — running clinicians, nurses, caregivers, allied health and support staff, each with a different set of things that must be true before a shift is theirs.

The shift that goes wrong is the one filled without one of the four in view.

Caretech is built so all four are in view at the moment of confirmation — a lapsed credential, a double-booking and a double confirmation are all the same failure, and the gate refuses all three. See what the platform does in your setting.