SolverForge
Search docs Ctrl K

Healthcare workforce coverage

688 shifts. 50 employees. 28 days of staffed coverage.

Hospital scheduling shows scalar assignment at serious density: every shift needs a qualified employee while overlap, rest, availability, preferences, and balance remain visible.

688 Shifts
50 Employees
28 Days
9 Constraints
6 / 3 Hard / soft split
2 Schedule views

Coverage planning breaks when qualification, availability, rest, overlap, and fairness are handled by separate tools. A schedule that fills every slot but violates rest or skill rules is not operationally usable.

The current app keeps location schedules, employee schedules, solver status, score analysis, data tables, and REST endpoints available from the same retained job.

Coverage Required shifts must receive staff.
Skills Employees must satisfy role and qualification requirements.
Overlap prevention Employees cannot be double-booked across overlapping work.
Rest and day limits Work sequences respect rest and one-shift-per-day rules.
Availability Unavailable employees are excluded from assignments.
Soft balance Preferences and workload balance remain inspectable tradeoffs.
Runtime walkthrough Watch the coverage plan fill, then read the same retained job from the location view, the employee view, and score analysis. Narrated walkthrough (2:29): the location schedule, the employee schedule, solver status, score analysis, the data tables, and the REST surface of one retained hospital solve.
Location Schedule Location schedules keep coverage pressure visible by department and day.
  1. Department rows expose where coverage is required.
  2. Dense shift placement stays visible across the 28-day horizon.
Employee Schedule Employee schedules reveal whether the same plan works from the worker perspective.
  1. Employee rows expose workload and assignment spread.
  2. The same retained job can be inspected by people instead of only by locations.
Solver Status Solver status keeps lifecycle and telemetry visible during retained workforce planning.
  1. Status controls keep solve lifecycle explicit.
  2. Telemetry remains visible while the schedule is being reviewed.
Score Analysis Score analysis explains which staffing rules are hard legality and which are soft tradeoffs.
  1. Hard staffing legality and soft balance are separated for audit.
  2. Each row exposes contribution and match counts for review.
Data View Data views keep the facts behind the schedule close to the plan being inspected.
  1. Employees, shifts, locations, and availability remain inspectable.
  2. Input facts stay adjacent to the generated schedule surface.
REST API REST endpoints expose the same retained workforce workflow for product integration.
  1. Endpoints expose solve creation, status, snapshots, and analysis.
  2. The UI and integration API share the retained-job lifecycle.