02 / care matching
Two funnels, running at once, converging on a match
Applications are scored against the rubric the moment they land, with the reason attached and the resume lines it keyed on. Family inquiries are answered in minutes and become a written care plan. As both sides fill, the pairing engine runs across the whole registry and proposes one pairing, with the near-misses and the single fact that ruled each of them out.
Both outer columns run at once, on their own clock. The center waits for one of each, then runs the pairing.
the caregiver supply funnel
0 scoredA ranked call list, not an inbox
Every application is read the moment it lands and scored against the rubric, with the reason attached. Work the list top down.
The Indeed posting is live. Nothing has come in since 6:02 this morning
the match
0 proposedThis caregiver, this family, this schedule
Getting both funnels to produce structured information at the same moment is the hard part. Ranking a registry against a written care plan is arithmetic.
Waiting on a care plan. The moment one is written this runs against the whole registry
the client demand funnel
0 writtenAnswered in minutes, then a care plan
Any hour, in your voice, qualifying as it goes. Nobody has to be at a desk for this to happen.
Nothing in the queue. The form and the phone line are both open
Caregiver scoring, the care plan, and the ranking are three different model calls against one record. The SQL panels above ran in this browser tab while you watched. Every name here is synthetic.