Most people managed by software never see a dispatch app; they see a roster. Hospitals, care services, shops and claims departments have drafted rosters and allocated work items with optimisation software for years, and the newest generation adds demand forecasting, automatic offers of open shifts and agents that place work in one person's queue rather than another's. This is where algorithmic management is most common outside platform work and least visible. Yet a roster sets when a person sleeps, how many hours an hourly worker is paid for and who receives the supplements for evening and weekend work, while an allocation settles who gets the complex cases from which people learn. This chapter therefore concerns three management functions: M1 Direction, because rosters and allocations assign, sequence and pace work; M3 Consequence, because hours, premiums and the mix of work reach pay and access to work; and M5 Care, because working time and rest are where the duty of care meets the optimiser.
A rostering system solves a constrained optimisation problem. Its inputs are a forecast of demand, the staff available with their contracts and competences, the rules on working time and rest, the collective agreement and the preferences staff have entered; its output is a roster for two to six weeks and, in home care, a sequence of visits into routes. The objective function weighs coverage against cost, and preferences against both. Every weight is a management choice, recorded or not.
Newer systems forecast demand per hour and draft the roster that meets the forecast at least cost. Where the forecast is updated daily, the roster can be redrafted daily too, and the cost of staffing to a tighter margin falls on the workers whose hours move. This is the mechanism behind just-in-time scheduling. However, the same tools can publish rosters further ahead, keep a stable core of fixed shifts and reserve flexibility for open shifts that staff may choose to take. Which way the tool is used is set by the objectives the employer configures and, in most of Europe, negotiates. Nordvik Region's ShiftWise drafts rosters for the Region's two hospitals and routes for its home care; Hansa Mutual's claims-triage agent allocates claims to individual handlers.
Primary topics explored
- Rosters and routes by forecast
- Unstable schedules
- Allocation by queue and agent
- Pay shaped by software
- Working time, recorded
- Task allocation as high-risk
About AI Boss
AI Boss is Book 7 of The Transformed Architecture. It examines what happens when artificial intelligence takes the manager's chair: algorithmic management of direction, evaluation, consequence, development and care, the effects on people, the management of AI agents, Europe's legal answer, and how to design an accountable AI boss, for European enterprises and public authorities.
It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team, AI Threat and The Transformed Security Architect.
Executives, line managers, HR and people leaders, works councils and trade unions, public employers, architects and AI governance leads, data protection and legal officers, procurement and programme leaders, and risk, compliance and audit.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 9: Scheduling, Pay and the Allocation of Work in AI Boss gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “The AI Boss Today” and is one of 37 drawn from the manuscript.