Evaluation module
The WRIE Proof of Concept: one scope, one closed period, one reconciled labor record
The WRIE Proof of Concept is a bounded evaluation on one operating scope you choose — a single community, a region, or one contested labor measure across the portfolio. It reads from the scheduling, timekeeping, payroll, HRIS, and acuity systems you already run, reconciles one closed period across them, and hands back a written record of where those systems disagree, who currently holds authority for each number, and whether a labor exposure can be traced to a named owner and a dated action. It does not produce a savings figure, and it requires no system to be replaced. Applications route into the Executive Briefing on your labor record — the module never starts before definitions and authority are established there, and every claim on this page is checkable against The WRIE Evidence Record.
- Scope
- One community, one region, or one contested measure
- Period examined
- One closed period, source records intact
- Dates or durations
- None — conditions only
- Savings or ROI figures produced
- None
- Reconciled
- September 4, 2026 against the internal build queue
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.
The module
What is inside it, and what is deliberately outside it
The module is bounded on purpose. It examines one scope, over one closed period, against the systems you already run, and it hands back findings rather than a result.
What is inside the module
- One operating scope of your choosing: a single community, one region, or one contested labor measure across the portfolio.
- Read connections to the systems you name — scheduling, timekeeping, payroll, HRIS, and clinical acuity. No incumbent system is displaced.
- One closed period reconciled across those systems, with variances reported rather than smoothed.
- A definition register for the labor measures in scope: what each one counts, what it excludes, and who owns the definition.
- A written authority rule for every case where two of your systems can disagree about the same number.
- Lineage for each figure produced: a traceable path back to the source record it came from.
- One exposure view built on the reconciled period, with every case routed to a named human owner.
What is deliberately outside it
- No system migration, replacement, or decommissioning. Replacing an incumbent stays your choice, on your timing.
- No savings, ROI, payback, turnover-reduction, or forecast-accuracy figure — the module has no basis for one and will not produce one.
- No benchmark comparison against other operators. No benchmark edition has been fielded or published.
- No employment, discipline, compensation, coverage, clinical, or admission determination, automated or recommended.
- No protected-characteristic data, and no individual-level workforce detail exposed above the direct supervisor and HR.
- No published delivery date or duration. The module opens when the conditions below are met, not on a calendar.
Participation
What you bring, what you hold at the end, and what has to be true first
What you bring
- An executive sponsor who can sign labor definitions — usually the CFO or COO.
- One named data owner who can grant read access to the systems in scope.
- HR and clinical leadership as co-signers on any measure that touches coverage or acuity.
- One closed period you are willing to have examined, including the periods where the numbers already disagree.
- A decision, at the end, about whether the reconciled record becomes your labor number of reference.
What you hold at the end
- A reconciliation report for the closed period: where scheduling, timeclock, payroll, and acuity disagree, by community and by period.
- A signed definition register for the labor measures in scope, with exclusions stated.
- An authority map naming, for each measure, the system of reference and the human owner of the tie-break.
- A lineage trace for each figure produced, from published number back to source record.
- An action trail from the exposure view: owner, date, and disposition for every routed case.
- A written list of what the module could not establish, carried forward as open rather than dropped.
What has to be true first
- An Executive Briefing has been held on the labor record, so the contested numbers are already named.
- Definitions and authority rules for the measures in scope are signed by the operator, not by SeniorCRE.
- Read access is granted to the systems named in the authority map, under the operator’s own access terms.
- A mutual NDA is in place before any operating data is examined.
- One closed period is available with the source records intact.
- A named human owner exists for each routed case; the module does not proceed without one.
The module sits inside the wider sequence published in the WRIE buyer journey: it is how stages two and three are exercised on a bounded scope before anything is adopted portfolio-wide.
Apply
Request the module
The form below is the application. It routes into the Executive Briefing on your labor record; nothing is provisioned, scheduled, or priced automatically, and a person answers every submission.
Trust anchor
Why WRIE Proof of Concept is published against the evidence record
Everything the module does is checkable against The WRIE Evidence Record before you apply. What WRIE does is built; not validated; the rows that are still open — including operator-production outcome data — are published as open. A proof of concept is how an operator moves a row, and it can only move against engineering-verified evidence in the operating record.
How to read this
The rules this module is published under
- The module is disclosed as a program, not as a delivered result. No operator-production outcome data is published from it.
- No stage of the module publishes a date or a duration. Conditions only.
- No savings, ROI, payback, turnover-reduction, accuracy, or benchmark figure is produced, quoted, or implied.
- Applying is not a purchase, a commitment, or a queue position. Every application is reviewed by a person and answered by a person.
- Applications route into the Executive Briefing. The module never starts before definitions and authority are established there.
- Individual-level workforce detail stays with the direct supervisor and HR; executive and board views are aggregate.
- No employment, discipline, compensation, coverage, clinical, or admission determination is produced or automated at any point.
- Capabilities that are not yet built are disclosed in the workforce build queue with the condition each waits on; the module does not depend on them.
The capabilities themselves are 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
Is the proof of concept free?
Commercial terms are set in writing with the Executive Briefing, not on this page. Applying costs nothing and commits nothing; no pricing, discount, or trial term is published here.
How long does it take?
No duration is published. The module opens when the conditions are met — a briefing held, definitions signed, read access granted, a mutual NDA in place, and one closed period available with source records intact.
Will you produce a savings number we can take to the board?
No. The module produces reconciliation findings, definitions, authority rules, lineage, and an action trail. It does not produce a savings, ROI, payback, or turnover-reduction figure, because there is no published basis for one.
Do we have to switch scheduling, payroll, or HRIS systems to participate?
No. The module reads from the systems you already run. Replacing an incumbent system is a choice you make on your own timing, never a condition of participating.
What happens to the data after the module ends?
Handling, retention, and deletion are set in the mutual NDA and the operator’s own access terms before any operating data is examined. Individual-level workforce detail is limited to the direct supervisor and HR, and no protected-characteristic data is collected.
What happens after I apply?
The application routes into the Executive Briefing on the labor record. A person reviews it and replies directly to schedule that session and offer a mutual NDA. Nothing is provisioned or scheduled automatically.
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: what adoption looks like, and who owns each stage
Before you scope a back-test, read the stages, the named human owner of each, and the condition that ends it.