Roster building & demand planning
Deputy
Auto-scheduling, demand forecasting, wage and labour budgets, micro-scheduling and multi-location operation are all named as features, but the captured pages stay at feature names: we found no public information on staffing requirements per shift, qualifications, coverage checks before publication, or which data source feeds the forecast. For a works council the decisive question — who proposes the roster and who approves or adjusts it — goes unanswered, and "Auto-Scheduling" with "Deputy AI" in every plan only sharpens that question.
Planday
Week and day templates with draft publication, department, group and skill requirements, open shifts and explained employee suggestions are documented, and no assignment happens without the schedule manager's final say — which I appreciate. But we found no public information tying planning to a named demand source or showing labour cost against budget while planning, and the automatic scheduler is documented only as a higher-tier tool with no public description of what it does.