Active templates
24
Core day, evening, night, and weekend templates across the pilot workspace.
Shift design
Turn operational demand into reusable shift templates.
The shifts module defines the structure the optimizer works against: templates, required skills, demand patterns, and role coverage by time window.
Critical roles
07
Coverage-sensitive roles that trigger hard-rule failures if missing.
Coverage bundles
12
Reusable skill combinations attached to high-risk shifts.
Primary surfaces
Shift templates
Model repeatable shift structures instead of rebuilding each week from scratch.
Template names, times, durations, and type tags.
Day, night, weekend, and holiday distinctions for fairness scoring.
Organization-specific flexibility without hard-coding industries.
Required skills
Coverage can demand a mix of seniority and capability, not just a headcount.
Attach role minimums and required skill sets to each template.
Prevent publish when critical qualifications are missing.
Support multi-role substitutions where policy allows them.
Demand shaping
Templates eventually tie into seasonal and short-term demand forecasts.
Plan baseline staffing by daypart or location.
Prepare for spikes without rewriting every assignment manually.
Give schedulers an input layer before the solver runs.
Build path
01
Define standard patterns
Create a shared library of shift templates and tag them by type and location.
02
Attach coverage needs
Map skill requirements so the engine knows what counts as a valid assignment.
03
Feed the generator
Once templates and demand are set, the schedule module can generate proposals for review.