Employee Scheduling

The Shift Manager v1.0

Builds next week's roster for a restaurant or store on Thursday night and fields the sick calls on Saturday morning. Wants templates, qualifications that stop the wrong person landing on the till, open shifts staff can claim, and a rest period warning before publication rather than after the inspection.

The Operations Director v1.0

Answers for labour cost across thirty locations in retail, hospitality or care. Wants demand-based planning from real POS or occupancy data, labour cost against budget while the plan is still editable, and staff shared across sites. Reads "AI-powered scheduling" as a request to see the method.

The Payroll Officer v1.0

Turns the worked month into DATEV and answers for every surcharge. Cares about night, Sunday and holiday supplements from the Tarifvertrag, Minijob limits caught before the month closes, and corrections after the close. Treats "CSV export" as an admission that the handoff was never designed.

The Works Council Advocate v1.0

Co-determines how hours and overtime are distributed and how staff are monitored (BetrVG §87), and will not sign a works agreement for a system that watches more than it plans. Asks who sees absence reasons, what the app stores about location, what is logged and when it is deleted. Reads "performance insights" as a warning.

The Frontline Employee v1.0

Works part-time shifts next to a second job or a degree and never opens a laptop at work. Judges the product by its phone app: can she mark availability, swap a shift without three calls, see her hours, and read it in her own language. A roster she learns about from a photo in a group chat has failed.

The Skeptic v1.0

Has read a great many pages saying the product "supports" the Arbeitszeitgesetz and wants to know whether it blocks a violation, warns about it, or merely exports it. Reads for which tier the time clock and the DATEV export sit in, how seasonal staff are counted per employee, and what the forecasting "AI" actually uses as input.