Readi combines sleep-related inputs and scheduling context to present predicted fatigue information. Supervisors can review a shift and log interventions, while analysts compare groups and schedules. Input freshness, privacy and an agreed response policy are central to evaluating the system.
Built from vendor sources checked ; AI-assisted drafting. Documentation review, not a hands-on test. How pages are made
Shift-based operations establishing a supervised fatigue-risk programme. A ReadiScore must not by itself authorize or remove someone from safety-critical work. Supervisors need the input source, sync freshness, estimated-versus-measured status, offline staleness and model assumptions. Sleep data is sensitive workforce data: require role controls, retention and deletion terms, labor and privacy review, worker communication, and a non-punitive response protocol. Vendor outcome and ROI claims are not guarantees.
Worth evaluating for shift-based operations establishing a supervised fatigue-risk programme. Budget for programme adoption, wearable logistics and supervision as well as the subscription.
Trial or demo on request. Sources checked .
Vendor visuals—not a QHSEtech hands-on test.
Fatigue Science supplies Readi, a predictive fatigue-risk platform comprising ReadiSupervise, ReadiAnalytics, ReadiOne/ReadiSync and the optional ReadiWatch wearable. ReadiBand is the former name or generation referenced by older material. ReadiScores are model outputs based on sleep, schedule and operational inputs; they are not clinical diagnoses or fitness-for-duty clearances.
| Capability | Evidence | Scope and source |
|---|---|---|
| Individual hour-by-hour fatigue forecast | Documented by vendor | Readi presents an individual forecast extending up to 18 hours. Treat the score as predictive decision support, not direct measurement, diagnosis or clearance. Readi system scope and integrationsReadiWatch scope, forecasts and data boundaries |
| Supervisor score context and time to threshold | Documented by vendor | ReadiSupervise can expose hour-by-hour scores, time to threshold, recent sleep, score source and synchronization context so supervisors can assess data quality before acting. ReadiSupervise mobile views and score contextReadiSupervise web views and input freshness |
| Configurable notifications | Depends on scope | Supervisors subscribe to notifications; they are not necessarily enabled by default. Crew and individual alerts depend on thresholds and configuration, while forecast-based alerts require the optional vendor-enabled ReadiML capability. ReadiSupervise notifications |
| Immediate and scheduled intervention records | Documented by vendor | Supervisors can log immediate or future actions with target, owner, due date, notes and completion status; associated score, shift, location, groups and edit metadata support review. Intervention logs and action trackingScheduled actions and communications |
| Prepared offline supervisor workflow | Depends on scope | Selected shifts, groups and tabs must be loaded while online. Cached views and local action logging can continue, but new scopes and wearable synchronization are unavailable; actions remain unseen by others until reconnection and signing out can discard unsynced work. Offline Mode preparation and limits |
| Organizational fatigue analytics | Documented by vendor | ReadiAnalytics provides organizational snapshots, trends and comparisons across sites, crews and shifts, including projected fatigue views. Interpretation still depends on input coverage and cohort context. ReadiAnalytics scope |
| Schedule scenario simulation | Depends on scope | Simulate accepts roster patterns or uploaded data and can compare hypothetical schedules using user-selected sleep assumptions or AutoSleep. Results are modelled scenarios, not proof of future incident reduction. Schedule simulation and assumptions |
| Wearable-optional predictions | Documented by vendor | The vendor describes fatigue forecasting without mandatory wearable use. Buyers should establish which source supplies sleep information, how estimates are labelled and how missing or stale inputs are handled. Readi system scope and integrationsReadiAnalytics scope |
| ReadiWatch sleep input and worker alerts | Depends on scope | The optional ReadiWatch infers sleep from wrist movement, synchronizes data and can display ReadiScore alerts. It does not continuously measure fatigue; the current page says the watch has no GPS or heart-rate sensor. Confirm hardware generation, battery, replacement and assignment process. ReadiWatch scope, forecasts and data boundariesReadiWatch onboarding and battery expectations |
| Personal and shared synchronization routes | Depends on scope | ReadiOne can synchronize an assigned watch through a phone, including supported background synchronization, while ReadiSync supports shared synchronization workflows. Mobile operating-system restrictions, Bluetooth access and deployment design affect freshness. ReadiOne background synchronizationReadiWatch scope, forecasts and data boundaries |
| Role and privacy controls | Depends on scope | Documented roles separate individual, supervisor and manager access, and alternative identifiers can reduce exposure of names or email addresses. Procurement must test the exact permissions, exports, administration, retention and deletion behavior in the contracted configuration. User roles and privacy identifiersDetailed permission controls |
| Developer API | Depends on scope | A developer API is publicly described, but the overview does not establish endpoint coverage, authentication, limits, write-back behavior, versioning or service commitments. Validate these with current technical documentation and a proof of concept. Developer API overview |
2 additional areas. Status describes reviewed sources, not hands-on performance.
Also watch for: A predicted score is not a diagnosis or clearance to perform hazardous work. Missing or stale data and model assumptions must remain visible to decision makers. Procurement should confirm configuration, support, data handling and the complete commercial scope.
Custom quote
The vendor publishes subscription scope but no numeric rate. Ask the quote to separate software licences, ReadiWatch hardware and replacements, sync equipment, integrations and API work, onboarding, optional ReadiML functions, support and renewal terms.
Pricing sources checked : Selected sources checked; no starting price recorded. The vendor describes a customized subscription and pilot without a numeric public rate or a verified free-pilot offer.
A Readi subscription can cover ReadiScore recipients, web, mobile and offline access, ReadiSupervise, ReadiAnalytics, Instant Insights, hosting, API access and customer-success support. ReadiWatch hardware, replacement devices, synchronization infrastructure, integrations, optional ReadiML forecast alerts, implementation services and programme governance should be itemized in the quote.
Ask the vendor to identify the product, region, modules, billing unit, contract term and included services in writing.
ReadiSupervise Offline Mode requires loading the intended shift, groups and tabs beforehand. Cached information and action logging remain available, but new areas or shifts and wearable synchronization are unavailable. Actions sync after reconnection and remain invisible to others meanwhile; signing out can discard unsynced data.
No. Treat ReadiScore as modelled decision-support information. A competent fatigue-risk procedure must also consider current symptoms, task risk, data quality and local safety rules; the score alone should not clear or disqualify a worker.
The vendor describes wearable-optional use. Ask what source will feed sleep or schedule information for each workforce group, how estimated values are marked and whether the proposed accuracy and freshness are acceptable for that workflow.
Current vendor material uses ReadiWatch and identifies ReadiBand as the prior name or generation. Do not transfer validation or hardware claims from older ReadiBand material to the current device without written confirmation.
The platform may use estimated information where direct sleep data is unavailable. The demo should show source icons, last-sync time, measured-versus-estimated status and the supervisor procedure for incomplete data.
Notifications depend on subscriptions and configuration. The vendor says forecast-based individual alerts use an optional ReadiML capability that it enables; verify thresholds, recipients, escalation and false-positive handling.
The vendor names broad integration categories, but that is not proof of an included connector for a specific product. Require a data map, authentication method, update latency, failure reconciliation, API limits, ownership and implementation cost.
Define purpose, lawful basis, worker communication, role access, alternate identifiers, retention, deletion, exports and permitted management use before deployment. Include labor, privacy, security and safety stakeholders and avoid punitive secondary use.
Drawn from the profiles behind the Alternatives list above: most category tags shared with Fatigue Science (Readi) first, then the closest overlap in documented capability names, then A to Z. Ratings, search demand and sponsorship are not used; rows are shown A to Z.
No shared category tag.
Differs: offline unclassified (this profile: partial workflow); price amount published (this profile: no verified amount); trial free trial documented (this profile: on request).
Same: scope.
No shared category tag.
Differs: offline unclassified (this profile: partial workflow); trial not established (this profile: on request).
Same: scope and price.
Also recorded as Fatigue Science, Readi. Older entries under a previous name may describe a different release or owner.
Star ratings and review counts from the old catalog are not shown: no source for them was recorded.
