Templates Operations

Operations

Staff Scheduling

Computes coverage rosters that provably satisfy your staffing rules — or names the exact rules that collide.

What's inside

  • Staff entity — team members with roles (RN, MA, front desk) and scheduling notes
  • Shifts entity — the coverage slots your roster fills, by date and shift
  • Roster Requests entity — one record per computation; the workflow writes the result back onto it
  • Compute Weekly Roster workflow — a deterministic solve step reads your current staff and shifts, turns your staffing rules into a valid roster, then records it (or the conflicting rules) on the request
  • 3 sample staff members and 4 sample shifts so it runs end to end the moment you install it

Staff Scheduling

Stop wrestling the coverage grid by hand. Declare your staffing rules once — who’s qualified for what, how many people each shift needs, no one works a day shift straight after a night — and the roster is computed for you. Not suggested: computed. Every roster this template produces either satisfies every rule you declared, or tells you exactly which rules collide so you can decide what gives.

How it works

  1. Your team and coverage slots live in the Staff and Shifts entities — plain records you edit like any other data.
  2. Creating a Roster Request record fires the Compute Weekly Roster workflow.
  3. The workflow reads your current staff and shifts — add a nurse or a shift and the next roster includes it, no workflow editing — then evaluates your rules (coverage minimums, one-shift-per-day, no-day-after-night, fairness) with a deterministic engine, not AI guesswork. The same records always produce the same roster, and the run is recorded on your audit trail like every other workflow step.
  4. The result is written back onto the request: the assignments when a valid roster exists, or the named list of conflicting rules when one doesn’t (“you require an RN on both Tuesday shifts, but only one RN is available Tuesday”).

The template ships with three sample staff members and four sample shifts, so it runs end to end the moment you install it — then keeps working as you replace that sample data with your own.

What you can extend

  • Edit the rules on the workflow’s solve step, or describe a change in plain language and let Studio reformulate them for your review.
  • Add rules from the built-in vocabulary: availability and time-off, per-person shift caps, maximum consecutive working days, incompatible pairings, pinned assignments.
  • Route infeasible results to a human: add a notification step that posts the conflicting rules to your team channel so the tradeoff gets decided, not buried.
  • Add an approval step before publishing the roster — computed schedules propose; your practice manager disposes.

Data handling

Rosters are workforce data, not patient data. The solving runs entirely inside your HASP environment — nothing is sent to an AI model or any outside service, and every computation is recorded on the same tamper-evident audit trail as the rest of your workspace.