MILabs
Integrations

Custom development for Deputy: bespoke tools for shift-based workforce teams

Custom Deputy tools for shift teams, built around how your rosters, timesheets and leave really work, with upkeep covered by your retainer.

Updated 2026-07-13

Custom development with Deputy

Some shift-based businesses reach a point where Deputy is still the right place for rosters and timesheets, but the workflow around it no longer fits a standard setup. A cafe group might need its opening checklist tied to the roster. A childcare centre might need leave cover matched to ratio rules it tracks by hand. Custom development is the route for those gaps. MILabs, a Sydney agency that works remotely elsewhere, first looks at the new requirement with the owner or team lead, then builds an internal tool or integration that reads from Deputy through its API where the account permissions allow. You keep ownership of the build. Changes to Deputy's own settings stay with your team, and anything touching pay calculations is checked by a qualified person before it leaves the system.

How it works

  1. Discovery: the owner or team lead describes the requirement that the current Deputy setup does not handle, such as a rule for leave cover.

  2. Mapping: the team lists which Deputy records the tool needs, such as rosters, timesheets or leave, and who may read or change each one.

  3. Scoping: MILabs confirms the connection route, either the Deputy API or an export, and the account permissions it depends on before building begins.

  4. Build: the tool is built and tested against sample data so that live rosters and pay runs are left undisturbed until the team signs off.

  5. Handover: the team receives the tool, a written record of its logic, and a review step that a person completes before any result reaches payroll.

  6. Upkeep: maintenance stays within the retainer, so changes to Deputy's API or to your own pay rules can be handled without a new project.

good questions, straight answers

Frequently asked questions

Can custom development start with part of Deputy?
Yes. Many businesses start with one gap, such as timesheet checks or leave summaries, and leave the rest of Deputy as it is. The build reads only the records it needs, through an API or export route that the account's plan and permissions allow. That keeps the first project small enough to review closely. Once it works for one team, it can extend to other sites later.
What happens if Deputy changes during custom development?
Deputy changes its features and API over time, so a connection can break even when your business has not changed. Maintenance within your retainer covers checking the connection after such changes and repairing it. Tell us about any Deputy setting that affects shifts, leave or pay codes, so the tool can be adjusted early. Keeping a short change log helps too.
Can I combine custom development with another service for Deputy?
Yes, and the combination can make sense when the custom tool produces data that needs a plain summary. For example, custom development can build the timesheet connection while workflow automation moves approved hours into a payroll tool such as Xero on a schedule your team sets. The scope is agreed at the start, so each service keeps its own boundaries. Your team still approves anything that affects pay.
What does custom development mean for a business using Deputy?
It means Deputy stays the record of rosters, timesheets and leave, while a separate tool handles the one task your current setup cannot. You own the build, so the logic belongs to your business rather than to a vendor product. Upkeep sits within your retainer. The trade-off is one more system to understand, which is why written documentation is part of handover.
Does custom development change how my team uses Deputy?
Usually very little changes for shift staff. They keep clocking on and off and requesting leave in Deputy as before. Managers may notice a new summary or a flagged timesheet, and that step asks them to check the result rather than accept it. Where a tool writes back to Deputy, the team should be told in advance which fields change and why.
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.