Duty and coverage

Coordinate rostered shifts, actual on-duty state, and coverage changes

Plan department and ward shifts, mark actual on-duty state, reassign staff when coverage changes, and see current staff availability.

The operational problem

A planned rota and the actual on-duty team are not always the same

Supervisors need to see planned coverage, actual attendance state, and changes without confusing the roster with patient case assignments. CliviQue keeps those concepts distinct.

What CliviQue currently supports

Department and ward shifts

Create and review planned coverage in the relevant facility context.

Actual on-duty state

Record who is currently on duty rather than assuming the plan was followed.

Coverage reassignment

Reflect operational changes when responsibility moves between staff.

Operations visibility

Surface duty gaps and current coverage in facility operations views.

How the workflow progresses

A connected operational sequence

1

Plan the shift

Create the rostered department or ward coverage.

2

Confirm actual duty

Mark the real on-duty state as work begins or changes.

3

Reassign and review gaps

Record coverage changes and use the operations view to identify unresolved gaps.

Current scope and limitations

What this feature does not claim

  • Duty and Coverage is not payroll or biometric attendance software.
  • Automated rota optimization and workload balancing are not included in the MVP.
  • The roster is separate from patient case assignment.

Frequently asked questions

About duty and coverage

Does this include payroll?+

No. The current feature coordinates duty and coverage rather than payroll.

Can actual duty differ from the planned roster?+

Yes. The workflow records actual on-duty state and reassignment separately from the original plan.

Does CliviQue automatically optimize the rota?+

No. Automated rota optimization is outside the current MVP scope.

Guided implementation

Evaluate duty and coverage in your hospital context

A product walkthrough can cover the implemented workflow, roles, facility setup, subscription entitlements, deployment boundaries, and any requirements that remain outside the current MVP.