Every platform in the inventory is monitored continuously. The people operating them are assessed at the morning brief.
Sloane Labs is the human readiness layer for defence and government operations. It reads recovery, circadian state and operational load across watchfloors, analysis cells and response teams, forecasts where readiness will fall short of the tasking, and acts before the deficit reaches the mission.
Readiness is reported as a status. It is actually a physiological state that decays on a known curve.
A watchfloor reports itself green because the posts are manned. Manning is not readiness. The variable that decides whether a watchkeeper catches an anomaly at 04:00 is sleep debt, circadian phase and the number of consecutive nights already worked, and none of those appear on a manning board.
Extended operations compress the recovery that the roster assumes. Multi day crisis response, surge tasking and sustained analysis push people past the point where the shift pattern was designed to work. Leadership finds out from the incident review rather than from the roster.
Four places capacity turns into outcome
The watchfloor
Sustained attention on low signal, high consequence monitoring degrades sharply in the back half of a night watch, and further again across consecutive nights.
The analysis cell
Fatigue does not make analysts slower, it makes them narrower.
The handover
Most continuity failures trace back to a transition where the outgoing shift was at the end of its physiological rope.
The retention pipeline
A vetted specialist represents years of investment and a replacement lead time measured in quarters.
A surge cycle, read the way you read a platform
Cell readiness across a seven day window, with the forward projection that lets you rotate a watch, move a handover or hold a reserve back before the tasking lands, rather than explain it in the after action review.
Select an operating state to redraw the forecast.
Standard three shift rotation, no surge tasking. Recovery is clearing between cycles and the index holds inside the tolerance band.
No intervention. The morning brief confirms the rotation is sustainable and flags nothing to leadership.
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 delivered before the command brief. Cell readiness, what changed overnight, the two groups to watch, and one recommended action for the day.
Cohort readiness by cell
Watchfloor, analysis, response and headquarters reported as separate cohorts with trend lines across the operational year. No cohort renders below five people.
Forward risk alerts
When a cell is forecast to cross a readiness threshold inside 72 hours, the alert fires with contributing factors and confidence attached, so command can weigh it rather than take it on faith.
Rotation simulation
Model a watch pattern before you commit to it. Change the shift length, the handover time or the reserve commitment, and see the projected effect on the cell.
Individual agent, opt in only
Personnel who opt in get their own coach: circadian guidance around the rotation, recovery targets between watches, and answers grounded strictly in their own data. Nothing discussed is visible to the chain of command.
Sovereign deployment
UK region hosting as standard, with private tenancy, on premise and air gapped configurations available for classified environments. No dependency on consumer cloud services in the data path.
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 fitness for duty tool
Explicitly excluded from clearance decisions, medical boards, posting decisions 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.
The platform is monitored to the second. The watch is assessed by how people look at the morning brief.
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 accreditation
Agree cells, success measures and the data boundary. DPIA and security questionnaire completed. Deployment pattern confirmed, including region and tenancy.
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 operations or chief of staff level
- Twenty to fifty volunteers across two or three cells, ideally including a night watch
- Roster and calendar integration approved by IT security and the DPO
- Two review sessions across the eight weeks
What you get
- Full platform access for the pilot cells, configured to your rotation
- Direct roadmap influence on defence specific capability
- A written readout of accuracy, adoption and decisions changed
- Security documentation pack suitable for accreditation review
The questions we get asked first
Is this a wellbeing programme?
No. It is a readiness system. Wellbeing programmes ask people how they feel and offer resources. Sloane measures capacity against the tasking calendar and changes decisions: rotation, handover design, reserve commitment, workload distribution.
Can it be deployed in a classified environment?
Yes. UK region hosting is standard. Private tenancy, on premise and fully air gapped configurations are supported, with model inference kept inside the boundary where required. Deployment pattern is agreed before any data moves.
Could this be used against an individual?
Architecturally, no. Individual physiology is never exposed to the chain of command; leadership sees cohorts of five or more. Use in clearance, medical board, posting or disciplinary process is contractually prohibited.
What does integration require from our IT team?
Roster ingestion, plus optional calendar and messaging metadata connections. No agents on endpoints, no changes to the network, no access to operational or mission systems. A technical review pack is available before any contract.
How does it sit with our existing human performance staff?
It reports to them. Physiologists and occupational health teams have the expertise and often the devices. What they lack is a continuous, aggregated, forward looking view across several hundred people.
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 operation observed.
Instrument the watch the way you instrument the platform
A thirty minute conversation covering the architecture, the deployment pattern and what an eight week pilot would look like inside your operation.