Fairness scheduling companion · for nursing units

Your unit's fairness, scored 0 to 100.

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.

Unit fairness auditSynthetic fixture
F
Equity grade
0.6712
Gini
  • Nights 0Weekends 4Unplanned OT 9.5hLongest run 7 days
  • Nights 10Weekends 2Unplanned OT 0hLongest run 4 days
  • Nights 0Weekends 2Unplanned OT 0hLongest run 6 days
  • Nights 0Weekends 0Unplanned OT 0hLongest run 4 days
  • Nights 0Weekends 0Unplanned OT 0hLongest run 3 days
  • Nights 0Weekends 0Unplanned OT 0hLongest run 2 days
  • Nights 0Weekends 0Unplanned OT 0hLongest run 3 days
Per-nurse burden · 4 green · 2 amber · 1 redTap a nurse for the breakdown

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.

  • 0–100Unit Fairness Score
  • A–FEquity grade per unit
  • 0Patient records read
How Equinurse works

From any schedule export to a fairness picture in one upload.

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.

01

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.

02

Score the burden

Nights, weekends, overtime, excess hours, and consecutive stretches combine into a 0 to 100 Burden Index per nurse. Weights are visible, not hidden.

03

Surface the inequity

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.

Fits the systems your unit already runs

Bring the file you already have.

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.

Time and attendance

Kronos / UKG timecard export

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.

Badge-level · plan vs worked hours
Duty rota

SSMC duty-rota workbook (.xlsm)

477 SSMC shift codes mapped with their hour values, including the compound codes. Exports paste back into the admin master without breaking its formulas.

Built from a real C7 surgical unit rota
Everything else

Any CSV planning sheet

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.

Nurse × date × shift · that's the whole contract
Evidence

What this is, and what it refuses to be.

Method

Burden Index, made legible

A single 0 to 100 score per nurse, computed from five weighted components. The exact weights ship with every report:

×3.0night shifts
×2.0overtime · consecutive stretches past four days
×1.5weekend coverage
×0.5hours beyond contract

The math is auditable. No hidden coefficients.

Learning

Constraints that age out

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.

Boundary

No PHI leaves the unit

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.

Clearly synthetic sample report

What the one-roster audit hands back.

This example is computed from the bundled synthetic fixture. It is not hospital data, a customer result, or evidence of workforce outcomes.

Unit read
22 / 100 · F

Severe imbalance in this fictional period. The score describes the uploaded roster only; it does not predict turnover.

Band split
421

Green, amber, red. Seven synthetic nurses were included after the audit parser applied its inclusion rules.

Distribution
0.6712 Gini

The report also exposes per-nurse burden, nights, weekends, overtime, consecutive stretches, and exceptions for manager review.

30-day pilot · one unit

One nursing unit. Thirty days.

AED 5,000once
What the pilot adds beyond the free audit

Plan vs reality, tracked month over month

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.

>25%cumulative drift across three months escalates a nurse to review
3+ daysrising sick trend inside the same window escalates too

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.

  • One-unit onboarding
  • Baseline roster audit
  • Per-nurse burden and unit fairness report
  • One next-month roster run
  • Manager handoff review inside the 30 days
Request pilot checkout · AED 5,000

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.