Staffing governance

Staffing governance, not just scheduling

Baseline enforcement, role coverage rules, and Hard / Soft / Monitor enforcement on every shift. The difference between a rota and a safe rota.

Book a demonstrationSee pricingWatch the walkthrough

A rota is an operations tool. Staffing governance is a safety tool.

Most rota systems publish whatever the manager builds. Governance asks whether the rota is safe before it lands.

No baseline

Every day is improvised. Coverage decisions are made shift-by-shift with no documented minimum. CQC asks for the policy and there isn't one to show.

No enforcement

Baselines exist on paper but the rota tool does not enforce them. Understaffed shifts get published anyway and the breach is discovered later, if at all.

No evidence

Breaches happen and nobody can reconstruct who authorised what. The audit trail is informal: a Slack message, a verbal approval, a memory.

How staffing governance works

Four connected steps from baseline to evidence. Each one is a working primitive, not a concept.

1

Baseline defined

Per location, per shift, per role: the minimum safe staffing baseline is set with explicit Hard, Soft, or Monitor enforcement on each row. The baseline is the policy, not the suggestion.

CQC Regulation 18: minimum staffing baselines documented
2

Rota built against baseline

The rota is constructed with live coverage feedback against the baseline. Met, short, and breach states are visible per role before publishing, not after the shift starts.

CQC Regulation 18: coverage validated before publish
3

Enforcement applied

When an assignment attempts to breach a baseline or staff a shift with an unqualified worker, the system applies the configured enforcement: Hard blocks, Soft warns and logs, Monitor logs only. Every decision is deterministic.

CQC Regulation 18: enforcement decisions deterministic
4

Evidence persisted

Every override, every breach, every authorising signature is captured as immutable evidence and attached to the relevant Assurance Pack. CQC sees the policy and the exceptions, not anecdotes.

CQC Regulation 18: override and breach evidence

Six staffing governance capabilities

Each one is a control, not a feature. Together they make the rota a governed surface.

Per-location baselines

Each location has its own minimum staffing baseline by shift and by role. No global one-size-fits-all assumptions.

Hard / Soft / Monitor enforcement

Each baseline row has its own enforcement level. Hard blocks the assignment, Soft warns and logs, Monitor logs only.

Role coverage rules

A nurse breach is not the same as a care assistant breach. Coverage rules are role-specific and severity-aware.

Override evidence

Every override is captured with the authorising manager, the reason, the timestamp, and surrounding context. CQC sees the policy and the exceptions.

Agency backfill tracking

Agency cover dispatched against breach risk is recorded with the cost delta and the credential check. Agency is not a black box.

Reg 18 evidence mapping

Baselines, overrides, and breach evidence map directly into Reg 18 Assurance Packs, not assembled afterwards.

Connected to enforcement

Staffing governance is upstream of attendance and downstream of training. The whole loop is one record.

Training & CredentialsAssignment Block

Expired DBS, lapsed mandatory training, or overdue competency prevent the assignment from happening. Training enforcement and staffing enforcement are the same control.

Baseline BreachCompliance Score

When a baseline is breached, the compliance score reflects it the same minute. Staffing is not separated from compliance. It is one of its loudest signals.

Override DecisionAssurance Pack

Every override and approving signature feeds the Reg 18 audit trail and attaches to the Assurance Pack with the surrounding context.

Regulatory context

CQC Regulation 18: Staffing

Regulation 18(1) requires sufficient numbers of suitably qualified, competent, skilled and experienced staff to meet the needs of people using the service. Sufficient is a baseline question. Suitably qualified is a training question. Statixs enforces both, with the same control.

The training and credentials layer ensures an unqualified or expired worker cannot be assigned. The staffing governance layer ensures the shift cannot be published below baseline. Together they are the Reg 18 enforcement model.

Connected to every other module

Staffing governance is the planning layer. Operations and compliance pick up downstream.

Scheduling and AttendanceTraining and CredentialsCompliance IntelligenceGovernance

Baseline breaches logged

Every breach captured with the override reason and the authorising manager. Nothing lost.

Enforcement, not advisory

Hard, Soft, and Monitor enforcement applied deterministically, not policy in a folder

Reg 18 evidence

Override and breach evidence attached to Assurance Packs, not assembled afterwards

Staffing governance questions

What care providers ask about baselines, enforcement levels, and override authorisation.

A baseline is set per location, per shift, per role. For each row, you specify the minimum number required and the enforcement level: Hard, Soft, or Monitor. Baselines can vary by day of week, by shift type (early, late, night, twilight), and by location. The baseline is the policy, and the system enforces it deterministically.
Hard enforcement blocks the assignment outright. A Registered Nurse baseline of 1 with Hard enforcement means the night shift cannot be published with zero nurses. Soft enforcement permits the assignment but warns the manager and logs the override for review. Monitor enforcement permits and logs only, with no warning and no block. The three levels let you express which baselines are clinical (Hard), operational (Soft), or informational (Monitor).
Soft and Monitor enforcement always permit override with a logged reason. Hard enforcement requires named manager authorisation with a documented justification, typically a clinical risk assessment. The override is captured immutably with the manager's signature, timestamp, and reason text. CQC can see exactly which overrides were authorised, by whom, and why.
Override authorisation is configured per organisation. Typically Registered Managers, Clinical Leads, or named compliance officers can authorise Hard overrides. The system enforces the named-approver list, so the override cannot proceed without it. This prevents informal escalation paths and keeps the audit trail clean.
A rota app schedules shifts. Staffing Governance enforces them. The difference is the baseline layer, the enforcement levels, the override audit trail, and the connection to compliance scoring. A rota app lets you publish an understaffed shift. Statixs blocks it or logs the override. A rota app tracks who worked when. Statixs evidences why every staffing decision was made the way it was, in a form CQC will accept.

See staffing governance in your environment

A demonstration tailored to your locations, your role mix, and your enforcement policy.

Book a demonstrationSee pricing