Home · Solutions · HR & people
Solution · HR & peopleCover finds itself: a message goes to the qualified, and the first to confirm takes the shift
Room schedules and cover without phone calls
A robot collects availability, drafts the rota by your written rules, publishes it where the team actually looks, and turns a sudden absence into a cover offer instead of an hour of phone calls. The manager approves; she does not dial.
Executive summary
The rota is rebuilt every week from scratch: availability arrives by text and paper notes, a sudden absence starts a phone chain, and the version on the break-room wall differs from the one at reception.
A form collects availability, the robot drafts the rota from written rules, and an absence becomes a message to staff qualified to cover: the first to confirm takes the shift.
The manager gets over an hour a day back, the rota has one binding version, and patient appointments stop colliding with absences, because the robot compares the rota with the calendar.
an availability form (Microsoft Forms); the rota in SharePoint; the appointment calendar; messages and cases in Microsoft Teams
Business problem
The same puzzle, week after week
In a service firm with treatment rooms the rota is not an admin extra; it is the condition of the business existing: a room needs its specialist and a patient needs the person they booked. Yet in most small firms the rota is built the way it was twenty years ago: in a spreadsheet or on a printout, with availability collected by text, inside the head of one person who “has it all arranged”.
The expensive part is not the arranging but the falling apart. Sick leave at 6:40, a child with a fever, a car that would not start: from that moment the manager calls everyone who might take the shift, and every unanswered call is five minutes and one more uncertainty. Meanwhile reception is checking in patients booked with a person who will not be in today.
Changes agreed by phone rarely make it back to the spreadsheet. Two weeks later nobody can say who actually worked which shift: payroll is built from memory and notes, and overtime disputes are settled on someone’s word. The wall version, the phone version and the spreadsheet version of the rota each live their own life.
And there is the cost no column shows: building the rota is one to two hours a day of a person who should be managing quality and sales, not dialling. In a small firm that person is often the owner.
How it works today
Below is what the work looks like before anything is automated.
- PersonAvailability arrives by text, email and paper notes; someone retypes it into a spreadsheet
- PersonThe manager builds the rota by hand, holding contracts, qualifications and preferences in memory
- Risk of errorA sudden absence starts a phone chain; every unanswered call costs five minutes
- WaitingPatients booked with the absent person wait until reception notices and starts rebooking
- Risk of errorChanges agreed by phone never reach the spreadsheet; versions drift apart
- Risk of errorPayroll is built from memory; overtime disputes are settled on someone’s word
Why the current process costs more than it appears
The bill that never shows up in a budget.
- An hour a day at the rota is, over a year, more than a month of work by the person meant to run the firm, not the phone.
- Every unnoticed conflict between rota and calendar is a patient turned away at the door and a slot to rebook.
- Shifts without a trace in the records come back as payroll disputes, always in the worst week of the month.
- A team that learns about changes last treats the rota as a verdict, not an agreement; you can see it in the turnover.
Cost of inaction
The first row is simple arithmetic: the rota-builder’s time at full cost. In many firms that person is the owner, so the real cost is higher than the payroll rate, because the hour is taken from sales and growth.
The second row is cautious: it counts only visits lost or rebooked because a patient was booked with someone absent. In firms that never compare rota and calendar, such collisions happen weekly.
A model organisation with realistic proportions – the numbers exist so you can run the same maths on your own data; they are not a client result.
A physiotherapy and massage centre: five rooms, fourteen staff on assorted contracts, reception, the appointment calendar in an industry system, Microsoft 365.
The rota built weekly in a spreadsheet by the manager; availability collected by text; on average two sudden absences a week.
Cover found by phone; changes agreed verbally do not always reach the spreadsheet; payroll needs a monthly investigation.
Patients sometimes get booked with people who are not on the rota, because nobody compares the two.
The robot collects availability by form until Wednesday, drafts the rota from written rules, the manager adjusts and approves; an absence triggers a message to qualified staff, the first to confirm takes the shift, and the system immediately checks whether the absent person has appointments to rebook.
In the modelled case rota work falls from 90 to about 20 minutes a day, and calendar collisions surface before the patient reaches the door. Model numbers, not the firm’s records.
Proposed solution
We start by writing down the rules that currently live in the builder’s head: contract hours, room and treatment qualifications, pairs that cannot work together, preferences, minimum staffing across opening hours. It is a two-page document; the robot drafts from it, a human approves. The rules can change at any time.
Availability is collected by a form with a nudge: whoever has not filled it in by Wednesday gets a reminder, and on Thursday the manager sees the gaps. The approved rota is published in one place and only there; every change has an author and a time. A sudden absence is one message: the robot writes to people with the right qualifications and hours to spare, the first to confirm gets the shift, the rest get a thank-you.
The robot also compares the rota with the appointment calendar: if the absent person has patients booked, reception immediately gets a Teams list of visits to rebook, before anyone reaches the door. At month end, the record of worked shifts and covers goes to payroll as it actually happened, with the history of every change.
UiPath Orchestrator: availability schedules, a cover queue, retries and an audit trail; UiPath Integration Service connectors for Microsoft Teams, Outlook 365 and SharePoint; Microsoft Forms for availability
Versioned staffing rules, a draft rota for approval, cover handling with confirmations, calendar conflict checks and a monthly payroll summary
The rota and change log in SharePoint; the appointment calendar via the industry system’s export or API; messages via Teams, and SMS for those not on Teams
How the automated process works
- AutomationThe availability form goes out on Monday; a nudge on Wednesday, gaps visible to the manager
- AutomationThe robot drafts the rota from the rules; the manager adjusts and approves
- SystemThe rota is published in one place; every change has an author and a time
- AutomationAn absence triggers a cover offer to the qualified; the first to confirm takes the shift
- PersonReception gets a Teams list of the absent person’s visits to rebook, before the patient arrives
- PersonAt month end the shift and cover record goes to payroll with its full history
Human-in-the-loop model
Automation handles
- Availability collection with nudges and the draft rota from written rules
- Cover handling: offers, confirmations, rota updates and notifications
- Calendar conflict checks and the monthly payroll summary
People decide
- The staffing rules: contracts, qualifications, minimum cover, preferences and exceptions
- Approval of every rota and decisions in contested cases
- Conversations with the team: leave, conflicts, matters no message can settle
Before and after
Systems and integrations
The stack is short on purpose: one engine, one execution layer, one place where a person decides.
Inputs
- availability from the form
- staffing rules and qualifications
- the appointment calendar (export or API)
- absence reports
Automation layer
- UiPath Orchestrator
- UiPath Robots
- UiPath Integration Service
- UiPath Action Center
Target systems
- the approved rota with change history
- covered shifts with confirmations
- the rebooking list and payroll summary in Microsoft Teams
Human touchpoints: rota approval once a week; cases in Microsoft Teams; the payroll summary once a month
Technologies used
schedules, the cover queue, retries, a record of every rota change
Acover offers, reception cases, rota publishing
Aavailability collected by form instead of texts
Athe rota and change log with versions and permissions
Athe source of visits for conflict checks; scope depends on export or API
BIllustrative economic model
Numbers you can check against your own data.
The model assumes the building does not vanish but shrinks to approving and exceptions; a human still sets the rules. Rates and volumes belong to the scenario; your own numbers go into the calculator alongside.
Run the maths on your data
An illustrative estimate based on your inputs. It models freed capacity, not promised savings.
Business benefits
- The manager gets over an hour a day back for work that grows the firm
- Cover is filled in minutes, without a phone chain at dawn
- One binding rota version ends the “but I was told otherwise” disputes
- Patients stop being booked with the absent; collisions surface a day early
- Payroll is built from the real change history, not from memory
The management view
- The rota stops depending on one person and her notebook; the rules are written and survive her holiday
- The history of shifts and covers is complete: who, when, for whom, with whose approval
- A growing team does not mean growing chaos; rules scale better than memory
Board-level KPIs
time spent building and patching the rota · time to fill sudden cover · rota collisions with the calendar · shifts with no trace in the records · payroll disputes per month
Security and governance
The automation has exactly the permissions it needs. Not one more.
- The robot works on a minimal data scope: name, contact, qualifications, availability and shifts; no absence reasons in messages
- Every rota change has an author, a time and a reason
- Staffing rules are versioned; only an authorised person changes them
- Payroll summaries are visible to management only; the team sees its rota
- Data stays in your Microsoft 365 tenant; the robots run in the EU region of UiPath Automation Cloud
Why now
The employee’s market in services persists: teams expect a predictable rota and honest records, or they leave for a firm that provides them.
Contract forms multiply (employment, freelance, B2B); watching the limits by hand has stopped being realistic.
The owner’s and manager’s hour costs more every year; dialling for cover is the most expensive possible use of it.
Relevant executive roles
Gets an hour a day back, and the certainty that the firm does not stand on one person’s notebook
Approves and decides exceptions, instead of building, dialling and untangling versions
Sees the rota in one place, takes cover with one tap, and trusts that the records add up
Common questions and objections
Exceptions are rules, just unwritten ones: who cannot work with whom, who does not do what, whose Tuesday is sacred. We write them down once and the robot drafts, it does not finalise; the manager adjusts and approves. After a month there are usually few adjustments left, because the exceptions stopped getting lost in memory.
Which is why a cover offer can go out by SMS in parallel, with confirmation working the same way. The availability form opens on a phone in half a minute. The requirement is not digital fluency; it is a phone number.
The record of shifts exists today too, only in the version that loses disputes: memory and paper notes. The system writes down what is being agreed anyway, and does it openly: everyone sees their rota, their covers and their history. In practice the team gains most, because “but I was told otherwise” disappears.
When this is not the right solution
- A team under five people on fixed hours: a spreadsheet and a conversation suffice
- A rota changed verbally a dozen times a day with no will to record changes: first the discipline of one version, then automation
- Expecting the system to resolve personal conflicts: it arranges shifts, not relationships
A question for the next management meeting
How many hours a week does building and patching the rota cost us, and whose hours are they?
Implementation approach
Scope without ambiguity, before anything is signed.
We deliver
- Written staffing rules, versioned
- Availability collection by form with nudges
- A draft rota for approval and cover handling with confirmations
- Calendar conflict checks and reception cases in Teams
- The monthly shift and cover summary for payroll
We need from you
- The current rota and the informal rules, which we write down together in one meeting
- The team list with contracts, qualifications and contacts
- Access to the appointment calendar (export or API), if conflict checks are to run
Stages
Discovery
How the rota is built today: rules, exceptions, versions, time and flashpoints
Rules
Staffing, qualifications, limits, preferences; cover message templates
Build
The form, the draft rota, cover offers, conflict checks, summaries
Parallel run
Two weeks: the robot drafts, the manager compares with her own version
Go-live
The rota moves to the system; a rules review after the first month
A quick win. The form, rota and cover run on the Microsoft 365 you already have; the only integration is the appointment calendar, depending on its interface.
Wednesday, 6:40 a.m.: a sick-leave text. Patients from 8:00. The manager is dialling the seventh person, and reception still knows nothing.
Describe your rota to us: how many people, how many sudden absences a month, who builds it and how long it takes. We return the arithmetic of the hours and a draft of the rules we would start from.
Count your rota hoursThe neighbouring process usually has the same problem
Three rates, four contracts, hours from memory. Payday ends in a discussion every month.
See the solution HR & peopleEmployee onboarding in a small firmThe new person starts on Monday. Account, access, check-ups, training: which of it will be ready?
See the solution Management & planningThe owner’s morning report in one messageYesterday’s takings, today’s staffing, overdue payments. One message instead of three systems.
See the solutionIndustries where we deploy this most oftenAesthetic medicineSmall business & services