Upload the schedule
Drop a Kronos export, an SSMC workbook, or a planning sheet. The parser maps it to a shift grid the engine can score. No data leaves the unit.
Upload one recent roster. Get a single score for how evenly your unit shares nights, weekends, overtime and long stretches, and see where the load piles up.
Free for one roster: unit score, burden distribution, risk bands and report download. Per-nurse breakdown unlocks with a work email. It scores the period in front of you; it does not predict turnover.
The Burden Index weighs nights, weekends, overtime, and consecutive stretches into a single 0 to 100 score per nurse. A to F grades make the distribution visible at a glance. Add exceptions and the system learns; a two week review prompt asks if the constraint still holds.
Drop a Kronos export, an SSMC workbook, or a planning sheet. The parser maps it to a shift grid the engine can score. No data leaves the unit.
Nights, weekends, overtime, excess hours, and consecutive stretches combine into a 0 to 100 Burden Index per nurse. Weights are visible, not hidden.
A to F grades stack into a unit distribution. Outliers are obvious. The line manager decides what to change; the tool just makes the picture visible.
No new time and attendance system. No HRIS migration. The parsers were built against real hospital exports, so the file your unit produces today is the file Equinurse reads.
Reads the card as a unit manager reads it: annual leave with a stray punch, weekend overtime that was never on the schedule, missed punches and exception flags.
477 SSMC shift codes mapped with their hour values, including the compound codes. Exports paste back into the admin master without breaking its formulas.
A plain columns-and-shifts export from any planner scores the same Burden Index and the same A to F grades. If it carries nurse, date, and shift, it scores.
A single 0 to 100 score per nurse, computed from five weighted components. The exact weights ship with every report:
The math is auditable. No hidden coefficients.
Add an exception — no nights for childcare, reduced hours for recovery — and the system learns. A two week review prompt asks if the constraint still holds. Constraints decay unless renewed. The line manager stays the source of truth.
Equinurse processes schedule structure, not patient data. Files stay in the unit environment. The output is a fairness picture for the line manager, not a record that travels outside the team.
This example is computed from the bundled synthetic fixture. It is not hospital data, a customer result, or evidence of workforce outcomes.
Severe imbalance in this fictional period. The score describes the uploaded roster only; it does not predict turnover.
Green, amber, red. Seven synthetic nurses were included after the audit parser applied its inclusion rules.
The report also exposes per-nurse burden, nights, weekends, overtime, consecutive stretches, and exceptions for manager review.
The free audit scores one roster as it stands. The pilot reads the history you already have — up to three months of past rosters and timecards — and tracks the gap between the promised roster and the hours actually worked. A nurse whose gap keeps growing is surfaced for review before the next roster is signed. The 30 days is the delivery window: baseline, drift read, and manager handoff.
The escalation rules come from a rolling-drift model built on a real surgical unit's rota and timecards. It flags burden drift; it does not predict who will resign.
Card checkout stays closed until the exact price ID and paid-pilot fulfillment are wired. The AED 15,000 annual option is offered only after this pilot has been delivered and reviewed; it has no public checkout action.