MILabs
Integrations

Staff roster planner for Deputy: how the build works

How to build a staff roster planner that works from Deputy shift data, checks rules and leaves final roster decisions with the team lead.

Updated 2026-03-05

Staff roster planner with Deputy

A staff roster planner for Deputy is an internal tool that works alongside the rosters your team keeps in Deputy. The planner works from Deputy's record of shifts and availability rather than a separate spreadsheet of who is free. The tool keeps the rules in one place: required roles, shift qualifications, and the maximum hours each person can work in a week. When someone builds a roster, the tool shows which shifts remain uncovered and where a rule would be broken. A swap request can be checked against the same rules before anyone approves it. The team lead still decides who works which shift. Any link from the planner to Deputy depends on the API or export route the account allows, so confirm what the account permits first. Begin with one site or one team and check draft rosters against the current ones before widening the scope.

How it works

  1. Confirm which Deputy data the account can reach through the API or an export, since both depend on the plan and the permissions in place.

  2. Map the shift, availability, leave and qualification fields the planner needs, and decide which ones stay in Deputy and which sit in a supporting table such as Airtable.

  3. Run the coverage and hour rules in a Power Automate flow or a similar workflow tool, so gaps, hour limits and missing qualifications are flagged before the team lead reviews the roster.

  4. Let Claude draft a plain summary of each proposed roster and swap, while the team lead approves every change in Deputy.

  5. Log each suggestion the planner makes and each decision the team lead records, so a question about a shift can be traced to a source.

good questions, straight answers

Frequently asked questions

Does a staff roster planner change how my team uses Deputy?
It should leave Deputy as the system of record, so staff keep recording shifts, leave and availability where they already do. The planner works as a separate view that reads from that data. Team leads still publish and change shifts in Deputy, and any draft roster from the planner waits for a person to accept it. Changes to how people enter information should be agreed first.
How do I measure a staff roster planner on Deputy?
Start by recording a few numbers before the planner is used, such as how many shifts go uncovered in a typical week and how many swap requests need a second look. Compare the same measures after a trial on one team. Also count the flags the planner raises and how many the team lead accepts, since that shows whether the rules match how the team really works.
What does a staff roster planner read from Deputy?
It reads only the fields the build needs, which usually include shift times and roles, staff availability, approved leave and contracted maximum hours. Exactly which fields are reachable depends on the API or export permitted for the account. Where Deputy does not hold a field such as a qualification, a supporting table can hold it instead, and the business should decide how that data is stored first.
Is a staff roster planner safe with Deputy data?
Yes, provided access is limited to the fields needed, the token has only the permissions it requires, and the business has a documented privacy and consent decision. Hold staff messages and personal details back from any outside model until that decision is made. Keep a log of what it reads and writes, and have a qualified person confirm pay rules, since the planner does not decide them.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.