Sensus measures how reliably a hospital responds when the plan breaks down — shift by shift, event by event.
Hospital Operations Reliability Intelligence
The break is visible the moment it occurs — a call-in, a surge, a boarder stacking up — not at the next staffing huddle.
On the unit · 20:15 — telemetry census jumps by four admissions in an hour.
Hospitals do not lack headcount data. They lack visibility into the shift itself: the response chain, the near-misses, and the rescues that almost did not happen.
These moments live between plans and outcomes. They show whether an operation can recover when staffing changes, demand rises, or continuity breaks.
What gets measured at the shift level can be managed. What is not measured disappears at handoff.
The Sensus stack
The measurement stays separate from the action. That boundary protects the integrity of both.
The day-to-day reliability instrument: the house supervisor’s operational record. It measures reliability at the shift level, is non-punitive by design, and is currently in development as doctoral (DNP) research.
A threshold-activated AI reliability relay powered by LWS data. It prepares the brief; the supervisor decides. It never sends anything on its own.
Live demos
All demos run on synthetic data.
The house supervisor's live operations view.
Request demo access →The intake view for recording shift events at the unit level.
Request demo access →The executive view: reliability, response, and continuity signals across the organization.
Request demo access →The LWS shift reliability log in action.
Request demo access →Not ready to request access? Run a synthetic shift yourself — the instrument’s mechanics, no gate, no form.
Product walkthrough
Watch the LWS Live Shift Tracker preserve a unit-level continuity event, update the reliability signal, and carry the record into handoff.
Animated demonstration · synthetic data
Shift stable
Response-chain status updates as the unit record advances.
Want to drive it yourself? Run a synthetic shift →
Evidence
Large observational studies continue to connect staffing conditions and workforce stability with measurable patient outcomes.
Across 223,000+ operations, each one-nurse reduction per shift was associated with 7% more complications and 13% higher mortality.
Read the finding ↗Across nearly 550,000 medical-surgical patients, each additional patient per nurse was associated with 8% higher odds of death and 33% higher odds of nurse burnout.
Read the finding ↗Across 8,584 U.S. hospital units, a 10-point rise in nurse turnover was associated with about 36 additional patient falls per year in a hospital with 1,000 inpatients per day.
Read the study ↗Associations from observational studies do not, by themselves, establish causation.
Every study here measures a level — headcount, ratio, turnover. None of them measures the reliability of the response when the plan breaks. That is the variable the instrument exists to capture. Read the full evidence base →
Our own validation
Twelve synthetic scenarios across mechanics, event classification, scoring behavior, and the supervisor workflow. Result: conditional go — zero genuine failures, zero open Critical or Moderate findings.
What that does not prove: an instrument that survives a tabletop is not an instrument that works on a live unit. The pilot is the test. That’s the point.
Founder
Jordan Lott, MSN, RN Charge nurse for 2+ years on a med-surg/tele unit · MSN in Nurse Executive Leadership, Purdue University Northwest
He spent his shifts watching the gap between what the staffing grid said and what the unit actually needed — and started building the instrument he wished existed: a way to measure how reliably a hospital responds when the plan breaks down.
Lott Workforce Systems is the instrument at the center of his doctoral (DNP) research; Sensus is the platform carrying it to hospitals. Connect on LinkedIn ↗
Pilot pathway
We talk through your operation: how shifts run, where continuity breaks, what your supervisors already see.
LWS runs as the house supervisor's operational record on one unit. Shift-level reliability measurement, non-punitive by design, synthetic data in every demo.
You see where reliability is won and lost, shift by shift — and whether the instrument earns a wider role.
No rip-and-replace. No surveillance. One unit, measured honestly.
A typical pilot runs about 90 days: long enough to see the operation shift by shift, bounded enough to answer a clear question.
The LWS shift-reliability instrument running as the house supervisor’s operational record on one unit, on-unit shift event reporting, and an end-of-pilot reliability readout.
One unit, a house supervisor to lead it, and the usual technology, privacy, and security approvals before any real operational data is used.
Shift-by-shift reliability measurement and an honest answer to whether the instrument earns a wider role.
Demos and early work run on synthetic data. No patient data, PHI, or identifiable employee data is used before institutional approval.
Pilot users
This is where pilot sites open the LWS capture tool — the house supervisor’s operational record. Access is provisioned per site.
Open the capture tool Open the review trackerIf your site’s access isn’t working, talk to your operational sponsor. The tool collects operational entries only — no patient data, ever. The review tracker is for the weekly data review — scored shifts, not live scores.
A short brief on how a pilot runs, what it measures, and what the hospital needs to decide. We send it to your work email — no download gate, no list you did not ask for.
Desk references for trained pilot users. Full training is facilitator-led — these are the guides, not the course.
Scenario-based charge nurse development — twelve modules of unit decisions, scored against expert choices, with mastery required to complete. Access is restricted.
Open Take ChargeQuestions, answered
The pilot starts with clear boundaries: what Sensus measures, what it does not collect, and what the hospital controls.
No. Work stays on synthetic data until institutional technology, privacy, and security approval. Sensus never uses PHI or identifiable employee data before that approval.
Sensus is web-based and runs in the browser. Technical requirements are scoped in the opening conversation so the hospital can evaluate the fit before a pilot moves forward. Read how we handle security and data — it was written for your review.
Sensus is a reliability system, not a staffing-assignment tool. It measures whether the operation holds together shift by shift; it does not make assignments.
No. The unit is the operational object, not the individual. There are no individual rankings, and the instrument is non-punitive by design.
Pilots are scoped individually. Start with a conversation about the unit, the operating model, and what the hospital needs to learn.
Pilot partnerships
We’re speaking with hospital executives, nursing leaders, and house supervisors about pilot partnerships.
