Blank whiteboard in a staff break room, overlaid by a glowing technical network that converges into a calendar and a group of people shape, fully AI generated and marked with the EU label
All solutions29 / Staff scheduling

Staff scheduling

Match staff scheduling and shift planning automatically

Availability, qualifications and reported staffing needs are merged automatically into a complete schedule proposal. Only genuine gaps or conflicts go to the planner; everything else is ready as a checked proposal before approval.

Process architecture

From individual availability to a checked schedule.

The process collects employee availability and qualifications, matches them against the reported staffing need per shift, and produces a complete schedule proposal. Gaps, double assignments or violations of working-time rules go to the planner; everything else is ready, checked, for approval before the schedule is published.

Process diagram

  • 09Nodes
  • 09Connections
  • 03Phases
Environment

01Input

Open quotes and their context come together.

The process starts with silence rather than a message: a quote that has had no answer for days. The leading system supplies the quote, its deadline and the contact, together with the correspondence already attached to the case.

2 Steps

02Process

The right message is derived from the state of the case.

The draft comes from the quote itself, not from a template full of placeholders. The rules then check whether a follow-up is allowed at all; anything outside the agreed frame goes to a salesperson.

4 Steps

03Output

The message goes out and the case stays traceable.

The follow-up sits in the same conversation as the quote, sales sees the current state without asking, and every attempt is documented on the case.

3 Steps

Source01

Collect availability

Employees report their availability through an app, a form or a chat command – via Microsoft Shifts, Google Forms or a custom staff app, depending on the environment.Details

Process node 01Source

Collect availability

Employees report their availability through an app, a form or a chat command – via Microsoft Shifts, Google Forms or a custom staff app, depending on the environment.

Interfaces
  • Microsoft Graph API
  • SharePoint API
Next steps
Data02

Load demand and qualifications

The reported staffing need per shift and each person's stored qualifications are loaded from the workforce planning system.Details

Process node 02Data

Load demand and qualifications

The reported staffing need per shift and each person's stored qualifications are loaded from the workforce planning system.

Interfaces
  • Azure AI Document Intelligence
  • Mistral OCR
  • Dataverse API
Next steps
Action03

Calculate the assignment

A rule set matches availability, qualification and demand and proposes the right people for each shift, taking rest periods and maximum working hours into account.Details

Process node 03Action

Calculate the assignment

A rule set matches availability, qualification and demand and proposes the right people for each shift, taking rest periods and maximum working hours into account.

Interfaces
  • Power Automate
  • Azure Functions
  • Microsoft Graph API
Next steps
Decision04

Check for conflicts

The proposal is checked for gaps, double bookings and violations of working-time rules; every anomaly counts as needing clarification.Details

Process node 04Decision

Check for conflicts

The proposal is checked for gaps, double bookings and violations of working-time rules; every anomaly counts as needing clarification.

Interfaces
  • Azure OpenAI GPT
  • Anthropic Claude
  • AI Builder
Next steps
Approval05

Clarify a gap or conflict

For an anomaly, the planner receives the affected shift with the available options for a manual decision.Details

Process node 05Approval

Clarify a gap or conflict

For an anomaly, the planner receives the affected shift with the available options for a manual decision.

Interfaces
  • Teams Adaptive Cards
  • Power Apps
Next steps
System06

Approve the schedule

The planner reviews the complete proposal and approves it, with or without the previously clarified adjustments.Details

Process node 06System

Approve the schedule

The planner reviews the complete proposal and approves it, with or without the previously clarified adjustments.

Interfaces
  • Dynamics 365 API
  • Azure Service Bus
Next steps
Result07

Publish the schedule

The approved schedule is published in the workforce planning system and visible to everyone involved.Details

Process node 07Result

Publish the schedule

The approved schedule is published in the workforce planning system and visible to everyone involved.

Interfaces
  • Power BI API
  • Teams Webhook
Next steps
Result08

Notify employees

Every person automatically receives their assigned shifts, with a note on changes compared to the previous version.Details

Process node 08Result

Notify employees

Every person automatically receives their assigned shifts, with a note on changes compared to the previous version.

Interfaces
  • Power BI API
  • Teams Webhook
Result09

Archive the schedule

The published schedule is filed with the approval timestamp and every manual adjustment, traceable for later evaluation.Details

Process node 09Result

Archive the schedule

The published schedule is filed with the approval timestamp and every manual adjustment, traceable for later evaluation.

Interfaces
  • Power BI API
  • Teams Webhook
  • Standard path
  • Direct path
  • Review required
  • Return

Steps in execution order

System landscape

The same process in three environments.

  • Microsoft

    Microsoft Graph API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    SharePoint API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Azure AI Document Intelligence

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Mistral OCR

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Dataverse API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Power Automate

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Azure Functions

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Azure OpenAI GPT

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Anthropic Claude

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    AI Builder

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Teams Adaptive Cards

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Power Apps

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Dynamics 365 API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Azure Service Bus

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Power BI API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Teams Webhook

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Interfaces in use

    Google Workspace APIs

    Google environment: reads availability from Google Forms and notifies through Google Chat.

  • Interfaces in use

    REST API

    Individual environment: connects the custom staff app with the existing workforce planning system.

  • Interfaces in use

    Webhook

    Forwards a reported availability change immediately so the next schedule proposal takes it into account.

  • Interfaces in use

    Microsoft Power Automate

    Microsoft environment: orchestrates assignment, conflict checking and notification as a workflow.

  • Interfaces in use

    Google Apps Script

    Google environment: orchestrates assignment, conflict checking and notification inside Google Workspace.

  • Possible apps & platforms

    Microsoft Shifts und Microsoft Teams

    Availability reporting and schedule publishing in the Microsoft environment.

  • Possible apps & platforms

    Google Formulare und Google Chat

    Availability reporting and notification in the Google environment.

  • Possible apps & platforms

    Eigene Personal-App

    Availability reporting in the self-hosted environment, connected to the existing planning system.

  • Possible apps & platforms

    Personalplanungssystem

    Leading system for demand, qualifications and the published schedule in the individual environment.

Implementation in context

What the process does and what it deliberately leaves to people.

The process produces a proposal, not a final assignment. The schedule is always approved and published by the planner; the process only handles the mechanical matching of availability and demand.

The environment determines the tools, not the process. In a Microsoft 365 environment availability reporting and publishing run through Microsoft Shifts, in a Google Workspace environment through Google Forms with a connected planning tool, in a self-hosted environment through a custom staff app. Which variant fits depends on where the company already runs its workforce planning.

The assignment rule is unambiguous: qualification, availability, rest periods and maximum working hours determine who is eligible for a shift. If a shift is left without a suitable person or a proposal violates a working-time rule, the case goes to the planner instead of passing through automatically.

Employee availability data stays inside the company's workforce planning system; no additional copy is sent to an external service. Every approval and every manual adjustment is logged with a timestamp.

Starting point

In shift-based businesses, the schedule is often still assembled as a spreadsheet puzzle: availability comes in by phone call, messaging app or paper note, qualifications live in the planner's head, and matching against demand costs several hours every week. Errors often only surface once a shift is left unstaffed.

Target picture

Availability, qualifications and demand are merged automatically into a complete schedule proposal. The planner sees only the shifts that need a genuine decision and approves the checked overall schedule at a glance, instead of assembling it from scratch.

Expected benefits

  • The schedule arrives as a checked proposal instead of a weekly spreadsheet puzzle assembled from scratch.
  • The planner sees only genuine gaps and conflicts, not every single assignment.
  • Violations of rest periods and maximum working hours are caught before publishing, not afterwards.
  • Employees receive their shifts automatically, with a clear note on changes from the previous week.
  • The process adapts to the existing environment instead of making an additional shift-planning tool a precondition.
  • Every approval and adjustment stays traceably documented, even across staff changes in planning.

Prerequisites to start

  • 01A system or app through which employees can report their availability.
  • 02Stored qualifications per employee, where relevant to shift staffing.
  • 03A workforce planning system with the reported demand per shift and period.
  • 04A written rule on rest periods and maximum working hours against which the proposal is checked.
  • 05A decision on the environment: Microsoft 365, Google Workspace or self-hosted – and the matching access rights.

Your next step

Which process costs your team unnecessary time every day?

Give us a short outline. We will tell you honestly where automation is useful—and where it is not.

DiscoverBack to top