Every patient in the building is monitored continuously. The clinicians treating them are monitored by whether they turned up.
Sloane Labs is the workforce readiness layer for clinical operations. It reads recovery, circadian state and rota load across wards, theatres and emergency departments, forecasts where capacity will fall short of the roster, and acts before it reaches the patient.
Fatigue is treated as an individual failing. It is a property of the rota.
A ward is staffed to establishment and reports itself safe. Establishment is not readiness. Whether a registrar catches a deteriorating patient at 04:00 is governed by sleep debt, circadian phase and how many consecutive nights they have already worked, and none of that appears on the staffing board.
Rotas are built against availability, not against recovery. The same pattern that looks compliant on paper produces very different physiological outcomes depending on the direction of rotation, the length of the run and the gap that follows it. Those differences are measurable.
Four places capacity turns into outcome
The night run
Sustained attention degrades sharply in the back half of a night shift and further across consecutive nights.
The decision point
Tiredness does not slow clinicians down, it narrows them.
The handover
Most continuity failures trace to a transition where the outgoing team was at the end of its physiological rope.
The retention pipeline
A senior nurse or consultant takes years to build and quarters to replace.
A rota cycle, read the way you read a patient
Ward level readiness across a seven day run, with the forward projection that lets you change the rotation direction, add an overlap or protect a rest day before the trough arrives.
Select an operating state to redraw the forecast.
Forward rotating days with protected rest. Recovery clears between shifts and readiness holds inside the tolerance band.
No intervention. The morning brief confirms the pattern is sustainable and flags nothing to the clinical lead.
What we read, and what each signal decides
A signal earns its place only if it changes an operational decision. Anything that does not is telemetry for its own sake.
What is actually running, not what is on a roadmap
Morning readiness brief
A single page before the operational meeting. Ward readiness, what changed overnight, the two areas to watch, and one recommended action.
Cohort readiness by area
Emergency, theatres, critical care and wards reported as separate cohorts with trend lines across the year. No cohort renders below five people.
Forward risk alerts
When an area is forecast to cross a readiness threshold inside 72 hours, the alert fires with contributing factors and stated confidence.
Rota simulation
Model a pattern before you publish it. Change rotation direction, run length or turnaround gap and see the projected effect on the cohort.
Individual agent, opt in only
Clinicians who opt in get their own coach: circadian guidance around the run, recovery targets between shifts, answers grounded strictly in their own data. Nothing is visible to management.
Safety evidence record
An aggregated, anonymised record of how fatigue was managed across the year. Defensible with the safety committee, the board and staff representatives.
Reading human capacity only works if the boundary is unambiguous
Trust is the adoption constraint. These are commitments, written into the agreement, not preferences.
Never a clinical governance tool
Explicitly excluded from appraisal, revalidation, incident investigation and disciplinary process. That exclusion is contractual and enforced in the data model.
Opt in, always
No one is enrolled by default. Participation is individual, explicit and revocable at any time, with data deleted on withdrawal.
Five person minimum cohort
Aggregate views suppress any group smaller than five. Leadership sees cohorts, never a named individual's physiology.
Metadata, never content
Calendar and messaging integrations read timing, density and participant counts. Titles, bodies and message content are masked at ingestion and never stored.
Separated from selection
Contractually and architecturally excluded from selection, appraisal and disciplinary processes. That separation is written into the agreement.
UK GDPR and DPIA ready
Lawful basis, retention schedule, data subject rights and a pre drafted DPIA template supplied for your DPO before the first device is connected.
Every patient is monitored continuously. The clinicians are monitored by whether they turned up.
An eight week pilot with a defined exit
We take a small number of design partners per sector. A partner shapes the roadmap directly, gets preferential terms, and keeps the right to walk away at week eight with no obligation.
Scope and governance
Agree cohorts, success measures and the data boundary. DPIA reviewed and signed. Integrations connected in a sandbox with a small internal group.
Baseline
Volunteers connect wearables and calendars. Individual baselines establish across a normal cycle and a peak one. No alerting yet, observation only.
Live briefing
Morning readiness briefs start reaching leadership. Forecast alerts switch on. Calibration against what the organisation already believes about its own load.
Readout and decision
Joint review of accuracy, adoption and the decisions the signal changed. Written readout, roadmap input, and a clear go or no go.
What we need from you
- One sponsor at chief nurse, medical director or operations level
- Twenty to fifty volunteers across two or three areas, ideally including a night rota
- Rota and calendar integration approved by IT and the DPO
- Two review sessions across the eight weeks
What you get
- Full platform access for the pilot cohorts, configured to your operating calendar
- Direct roadmap influence on capability specific to your sector
- A written readout of accuracy, adoption and decisions changed
- Preferential terms and first refusal on the sector in your market
The questions we get asked first
Is this a wellbeing programme?
No. It is an operational readiness system. Wellbeing programmes ask staff how they feel and offer resources. Sloane measures capacity against the rota and changes decisions: rotation direction, run length, turnaround gaps, cover allocation.
Does it touch clinical systems or patient data?
Never. There is no connection to the EPR, PAS or any clinical system. Sloane reads wearable signals from consenting staff plus rota and calendar metadata. No patient data enters the platform at any point.
Could this be used against an individual clinician?
Architecturally, no. Individual physiology is never exposed to management; leadership sees cohorts of five or more. Use in appraisal, revalidation, incident investigation or disciplinary process is contractually prohibited.
How does it sit with occupational health?
It reports to them. Occupational health has the expertise but not a continuous, aggregated, forward looking view across several hundred staff. Sloane is the instrumentation layer beneath their judgement.
What does integration require from IT?
Rota ingestion plus optional calendar and messaging metadata. No agents on endpoints, no network changes, no clinical system access. A DSPT aligned technical pack is available before any contract.
How do we know the signal is real?
Every score is deterministic and reproducible from versioned features, every forecast carries stated confidence, and the pilot readout compares what the system predicted against what the service observed.
Instrument the workforce the way you instrument the patient
A thirty minute conversation covering the architecture, the data boundary and what an eight week pilot would look like inside your service.