Build queue
Workforce intelligence: what is next, and what it waits on
This is the workforce build queue as it stands on September 4, 2026 — the same list carried internally, published with the same identifiers so the two cannot drift. Each item states what an operator would be able to ask, what is in scope, the condition it waits on, and the claim we are not making. None of it carries a delivery date, because a date published before the gate is cleared is a sales artifact rather than a roadmap.
- Items disclosed
- 6 in the workforce queue
- Reconciled
- September 4, 2026 against the internal queue
- Dates published
- None — conditions only
- Automated determinations
- None at any stage
Evidence posture. Status is stated per capability below. Nothing here runs in operator production. It is not accompanied by published operator-production outcome data, and no savings figure or payback period is claimed. Industry ranges shown are published third-party ranges used to size exposure and to model a case from an operator’s own history. Last reviewed October 16, 2026.
Published queue
The workforce build queue
Read each item as a question an operator cannot answer today, plus the condition that has to be true before it can be answered. Status uses four labels and nothing else.
1.Supervisor effectiveness scorecard
Not builtThe question it answers: Which supervisors are carrying schedule volatility, call-off recurrence, and slow incident response — as a reviewable record rather than an impression?
In scope
- One per-supervisor rollup of retention, schedule volatility, call-off recurrence, training completion, and incident response timing
- Every figure attributed to the source system and the survivorship rule that produced it
- Trend over time and peer comparison within a community and region
- Reviewable export for a supervisor conversation, with the definition of each measure on the artifact
What it waits on
- Definitions frozen for each measure before any supervisor is compared to another
- Human review required — no employment, discipline, or compensation determination is produced or automated
The claim we are not making: No claim that a scorecard improves retention. It makes management quality observable; the intervention remains a human decision.
2.Scheduling stability index
Not builtThe question it answers: Is the schedule getting more stable or less stable in this building, this shift, this month?
In scope
- One composite stability measure per community, shift, and supervisor
- Inputs held separately and disclosed: last-minute schedule changes, swap frequency, overtime reliance, call-off recurrence, open-shift volatility
- Surfaced alongside labor risk, not folded into it
- Threshold alerts routed to a named human owner
What it waits on
- Component weights published before the index is used in any review
- Overtime and hours reconciled to payroll before the index is computed
The claim we are not making: A composite index is a summary, not evidence of cause. Component values remain visible so a summary can never replace them.
3.Outcome-linked recognition
Not builtThe question it answers: Can recognition be tied to the resident outcomes staff actually produced, rather than to who was noticed?
In scope
- Recognition events tied to governed resident outcome records — recovered function, avoided transfer, family-reported milestone, survey-cited staff
- Recognition history visible to the employee and their supervisor
- Recognition cadence carried as an input into the supervisor scorecard
What it waits on
- Resident outcome records governed with named authoritative sources
- Clinical review of any outcome used for recognition, so recognition never distorts clinical documentation
The claim we are not making: No claim about the retention effect of recognition. Nothing here derives a clinical determination or changes a resident record.
4.Senior Care Workforce Risk Benchmark
Method published, collection not builtThe question it answers: How does our labor risk compare with peers, measured from systems rather than recollection?
In scope
- Methodology v1.0 is published: seven frozen measures, sample frame, suppression rules, participation floor, and field dates
- Participant payroll and scheduling extracts mapped to the frozen measures
- Edition artifact publishing sample size, field window, refusals, partials, missing measures, and limitations
What it waits on
- Published participation floor met for a field window
- Participant data-use terms reviewed before any intake
The claim we are not making: No edition has been fielded or published. Any benchmark value attributed to this program today does not exist.
5.Acuity-weighted scheduling, open shifts, and agency rails
GatedThe question it answers: Can the schedule be proposed against acuity, and can an open shift be filled internally before agency is called?
In scope
- Acuity-weighted demand from care plans, assessments, recent incidents, and state ratio rules
- Proposed roster only — never published automatically; the scheduler approves with a difference view and the reason for each assignment
- Internal open-shift offer to eligible credentialed staff before any external fill
- Agency versus internal cost attribution held on the governed record
What it waits on
- Platform change-control gate cleared
- Hours, credentials, and census reconciled to authoritative sources first
- No automated employment or staffing determination at any stage
The claim we are not making: No overtime, agency-spend, or fill-rate improvement claim. Scope and sequencing are not committed.
6.Cross-operator workforce comparison
Design decided, build not scopedThe question it answers: What do wages, turnover, and recruitment look like across a region, on definitions that match ours?
In scope
- Regional wage, turnover, and recruitment patterns computed on shared definitions
- Coordination for crisis staffing across participating organizations
- Regional comparison feeding the supervisor scorecard and stability index
What it waits on
- Founding cohort data live under governed definitions
- Supervisor scorecard and stability index in place first
- Participant consent and suppression rules established before any cross-operator view
The claim we are not making: Nothing is aggregated across organizations without participation terms. No individual is identifiable in a cross-operator view.
How to read this
The rules this page is published under
- Nothing on this page carries a delivery date. A date published before the gate is cleared is a sales artifact, not a roadmap.
- Nothing on this page is sequenced as a commitment. Order here reflects dependency, not a schedule.
- Every item is tracked in the internal build queue under the same identifier, so the public list and the internal list cannot drift.
- Status changes only against engineering-verified evidence. "Built" is not claimed from a design decision or a demonstration.
- No item produces an automated employment, clinical, coverage, or admission determination. Human review is a design constraint, not a phase.
Where a capability is already in the operating record rather than in this queue, it is described on the workforce intelligence hub.
Boundary
Predictive decision support is not an automated employment decision
Predictive turnover scoring in SeniorCRE is decision support for retention operations. It is not an automated employment decision tool: it does not screen, rank, hire, promote, discipline, or separate anyone, and no action reaches an employee without a named human confirming it. Operators subject to automated-employment-decision rules should still confirm scope with their own counsel, because the controlling question in those rules is how an employer uses an output, not what a vendor calls it.
| Question | Predictive decision support | Automated employment decision |
|---|---|---|
| Who decides? | A named human manager decides, and the decision is recorded against the person who made it. | A system issues or filters an employment outcome without a human decision-maker in the record. |
| What is the output used for? | Prioritizing attention: which conversations, schedule changes, and staffing actions happen first this week. | Screening, ranking, hiring, promotion, discipline, or separation outcomes. |
| Can the output be acted on unattended? | No. Every intervention requires human confirmation before it is executed or communicated. | Yes — the action executes on the score. |
| Is the individual score a verdict? | No. A risk band is a hypothesis about workload and schedule conditions, not a judgment about the employee. | The score functions as the judgment. |
| What is excluded from the model? | Protected characteristics and proxies for them are excluded by design; the published exclusion list is part of the methodology. | Feature sets are frequently undocumented and unbounded. |
| What is auditable afterward? | Inputs, score version, the human who confirmed, the action taken, and the outcome are retained as an immutable record. | Often only the final outcome is retained. |
Download the methodology
Both files are ungated, machine-readable, and versioned to October 16, 2026. Use them to compare any vendor’s method against a written one.
Frequently asked questions
Does this roadmap commit SeniorCRE to delivery dates?
No. Every item publishes the condition it waits on rather than a date, and order reflects dependency rather than a schedule. Scope and sequencing can change; the disclosure is reconciled against the internal build queue and re-published when it does.
Has the Senior Care Workforce Risk Benchmark published results?
No. Methodology v1.0 is published, including frozen measures, suppression rules, participation floor, and field dates. No edition has been fielded or published, so any benchmark value attributed to the program today does not exist.
Will any of these features make employment or staffing decisions automatically?
No. Every item on the workforce queue is designed as decision support with a named human owner. No employment, discipline, compensation, clinical, coverage, or admission determination is produced or automated at any stage.
How is a roadmap item moved to built?
Only against engineering-verified evidence in the operating record. A design decision, a demonstration, or a pilot conversation does not change a status label, and the four labels used here are the only ones published.
Continue in this cluster
Retention analytics best practices
Metric definitions, a 13-week workforce forecast example, human-reviewed retention signals, data requirements, measurement plans, and downloadable methodology.
Retention ROI calculator and model
The interactive model plus the structure behind it: components, source authority for each line, frozen-baseline rules, attribution discipline, and the limitations that invalidate a result.
Payroll forecasting: method, checklist, and variance review
Seven forecast components held separately, five accuracy measures, a readiness checklist across data, model, controls, and governance, and the weekly variance review that keeps a 13-week forecast honest.
Agency labor reduction
Where premium labor originates, how invoices are reconciled against worked hours, and the internal-fill sequence that has to work before agency hours come down.
Workforce benchmarks and the Senior Care Workforce Risk Benchmark
Frozen measures, system-derived collection, suppression rules, participation floor, published field dates, and stated sample limitations. No edition published yet.
Measurement methodology
Definitions, hours reconciliation, human-confirmed intervention, frozen baselines, and honest accuracy reporting, each with the test for whether it is actually in place.
- Product: WRIE — Workforce Retention Intelligence Engine™
- Model methodology: WRIE methodology and governance
- Vendor shortlist: Best workforce analytics software for senior care
- Pillar: Workforce intelligence for senior housing & care · Workforce analytics hub
The owner’s language
What governed labor does to NOI, and to coverage, at one building
Labor is the largest controllable cost in the building, and it is the one an owner tests against a covenant they have already signed. So the workforce case has to land on the NOI line. Nothing below is a result we have measured — each amount is the operator’s own, taken from payroll, the schedule, agency invoices and separation history.
Line 01
Agency and premium hours above the governed plan
Ungoverned today: Scheduling, timekeeping and payroll are reconciled after the pay period, by hand, once the premium has already been spent.
Line 02
Care hours staffed against governed census
Ungoverned today: A signed deposit is counted as occupied, so hours are scheduled and paid against a bed nobody has moved into.
Line 03
Replacement cost of separations nobody saw coming
Ungoverned today: The exit signal sits in scheduling, payroll and credential data that no one reconciles into one record per employee, so the cost is recognized at the exit interview.
The three lines are the operator’s figures, not ours. What SeniorCRE supplies is the definition each line is measured on, which system holds authority for it, the reconciliation rule, and the lineage back to source — so the amount can be defended when it reaches the owner.
What that does to debt service coverage
Debt service coverage ratio = property NOI ÷ annual debt service.
Coverage is usually tested at the property, on trailing NOI, against a covenant the owner has already signed. That makes an NOI line item and a covenant test the same conversation — an amount that never reaches NOI never reaches coverage, and a definition nobody governs is where the amount goes missing.
Illustrative arithmetic on stated assumptions
One 100-unit assisted living community. Annual debt service of $1,200,000. Trailing NOI of $1,560,000, which tests at 1.30×.
If the owner’s own worksheet puts $120,000 of annual NOI on the lines above — care levels billed in period, hours staffed against governed census, occupancy read on one definition — NOI of $1,680,000 tests at 1.40×.
That is division, not evidence. The assumptions are stated so the owner can replace them; substitute the property’s own debt service and NOI and the arithmetic answers for that property instead of this one.
No email is required and nothing is gated. If the arithmetic does not clear the covenant on your own numbers, that is the answer, and we would rather you find it on your own sheet than in a briefing.
No operator runs SeniorCRE in operator production today, no third-party integration is live in operator production, and no operator outcome is claimed or independently validated. Figures above are arithmetic on the assumptions shown. Commercial terms are not published; they are provided under NDA in a written quote scoped to the portfolio.
Govern the truth before you automate the decision — and before you ask an owner to fund it.
Next: hold us to the evidence register
Everything on the roadmap is unbuilt until the evidence register says otherwise. Read what is claimed today.