From the weekly plan to the unexpected callout.

One connected workflow for planning care, handling a change, and knowing what still needs attention. Explore the current development preview through fictional examples.

Three care professionals sharing a handoff in the entrance to a community home

Two connected workflows

Explore the work in more detail.

Before the week begins

AI Scheduler

Compare plans with availability, continuity, qualifications and working-time requirements in view.

When the plan changes

Coverage Recovery

Keep the visit, caregiver questions, human decisions and source confirmation together.

AI-assisted planning

A schedule is more than a list of open slots.

Availability is only the beginning. Our scheduler compares combinations of caregivers with the qualifications, continuity, team size, and working-time constraints recorded for each visit.

Coordinators review the suggested plan, compare changes, and keep the final decision. Overnight care, multi-person visits, and changes to an existing plan are part of the work we are developing for.

Current development is tested locally with fictional records. Agency rules and live source access require separate evaluation.

Weekly planningIllustrative example

Morning supportContinuity considered

Two-person visitReview both caregivers

Overnight coverageCheck rest and hours

Coordinator review

Compare the proposed changes before deciding what to approve.

Selected case · C-3407A question changes the path.

Review required

Transfer assistanceGlen Burnie · 7:30 AM

Shift V-91703 · synthetic record

What changedA modeled arrival request falls outside the client's service window.

What stays trueThe candidate remains unselected. The original service window stays bound.

Permitted next moveAnswer the bounded questionHuman-controlled timing handoff

This synthetic view sends no response and creates no outreach, assignment, or EHR effect.

A question should narrow the path, not disappear.

When a caregiver requests a different arrival time, the coordinator needs to know whether it meets the person’s care requirements. Work keeps the original timing visible and gives someone responsibility for resolving the question.

See the safety model

01 / Queue

Know which gaps need your attention.

Separate gaps you can act on from visits waiting for an answer, cases that need escalation and assignments already confirmed. Give each one the attention it needs.

Needs actionOperator can advance
PendingEvidence or answer required
BlockedNo safe automated action
VerifiedAssignment confirmed in the record

Decision queue · syntheticDifferent work needs different treatment.

4 example cases

C-3312Respite careSevern · 7:00 AM
Constraint review due
Safe next actionReview travel boundary
C-3316HomemakingCrofton · 1:30 PM
Source read-back due
Safe next actionRead assignment source
C-3321Personal supportAnnapolis · 9:00 PM
Human answer required
Safe next actionOpen coordinator handoff
C-3324Companion careGambrills · 12:30 PM
Evidence complete
Safe next actionPreserve verified result

Selected case · C-3411Resolve the source before retrying.

Outcome ambiguous

ShiftV-91826 · Columbia

ServiceOvernight support · 10:00 PM

Modeled writeTimed out · result unknown

Read evidenceRequired before retry

The one safe next actionRun source read-back

Determine whether the modeled write exists before any retry can be considered.

Open read-back rehearsal

A timeout is not a failure receipt. This rehearsal makes no live source request.

02 / Action

The interface gets quieter when the situation gets harder.

If a scheduling update times out, making it again could duplicate the assignment. In this example, Work pauses the action and asks the coordinator to check the scheduling record first.

Product rule

“No safe action” is a valid product state.

03 / Evidence

See who decided, and what happened next.

A handoff should carry the question, its owner, and the answer. This fictional example shows how the product keeps that history alongside the coverage decision.

See the pilot path

Exact-chain receiptEvidence stays attached.

rev 02

Modeled handoff acknowledgedProduct evidence only · no external effect

Case: C-3420
Owner: OPS-07 · fictional
Handoff: HO-118 · rev 02
Policy: BP-HANDOFF-v2
Result: Modeled acknowledged
External effect: False

Exact bindingACK-C3420-OPS07-HO118-r02

The work around the gap.

Coverage is the entry point. The broader product model keeps the adjacent people, conversation, observation, and audit surfaces aligned.

AI Scheduler

Compare weekly plans with availability, continuity, qualifications, and working-time constraints.

Coverage

Prioritize gaps, pending decisions, verified work, and hard blocks.

Conversations

Keep consent, delivery, questions, interest, and acceptance distinct.

On-call

Give the on-call owner the question, its context and a clear next step.

Caregivers

Review qualifications and restrictions alongside the visit that needs coverage.

Audit

Keep the decision, its owner and the confirmation history attached to the work.

Start with a workflow your team knows well.

Describe how your team plans a week or handles a callout. We’ll explore it with fictional records first, including the difficult cases.