Safer staffing

A ward is safely staffed or it isn’t, and the answer changes every shift. commvita holds the establishment, the actual roster and the gap between them on the same record the incidents sit on — so “we were short that night” stops being a recollection and becomes something the board can see, count and act on.

First to market

An incident names the team it concerns. Attribution resolves against the one staff hierarchy, so incidents group by team worst-first with the harm outcome attached, instead of landing in a pile nobody owns. The same hierarchy drives the training compliance view.From commvita’s own assessment of this module against the systems it competes with. Our assessment, not an independent one.

The gap, not the plan

Most staffing systems record what was intended. The safety question is about what actually happened, on which shift, and what followed from it.

Establishment

What the ward is funded and assessed to hold

Planned establishment by ward, shift and skill mix, with the professional judgement and acuity basis recorded alongside it rather than in a separate paper review.

Where in commvita/safe-staffing

Actual

Who was really on the shift

The filled roster, including bank and agency, late changes and unfilled lines — the version that existed at handover, not the one drafted a fortnight earlier.

Where in commvita/rostering · /bank-agency

The gap

Fill rate, red flags and what was done

The shortfall computed, not typed, with the escalation raised, who took it and what changed as a result. A red flag with no response is itself a finding.

Where in commvita/safe-staffing · /shift-priority

Why it belongs beside the incidents

Staffing data kept in a workforce system and incident data kept in a governance system can only ever be correlated by hand, in retrospect, by someone who already suspects the link. On one record the question is a query.

The question a board actually asks

Were the shifts on which harm occurred the shifts we couldn’t fill? That needs the roster and the incident to share a ward, a date and a shift — which they do, because they’re entries against the same organisational structure not two exports being reconciled in a spreadsheet.

The answer carries its evidence

Where a staffing shortfall is named as a contributing factor in an incident, the roster for that shift is reachable from the incident, and the incident is reachable from the shift. No one has to be trusted to have looked it up correctly.

Where it lives

Capability	What it does	Route
Safe staffing	Establishment, actual, fill rate and red flags by ward and shift	/safe-staffing
Rostering	The roster as worked, including late changes	/rostering
Bank & agency	Temporary fill, cascade and the cost of covering the gap	/bank-agency
Job planning	Committed activity against available time	/job-planning
Staff wellbeing	The load carried by the people who covered the shortfall	/staff-wellbeing
Incident reporting	Where staffing appears as a contributing factor	/incident-reporting

Safer staffing is a governance capability, not a clinical decision-support one. commvita records establishment, roster and gap, and makes them answerable together with incidents; the professional judgement about whether a shift is safe to run remains the responsibility of the people running it. Non-SaMD.