MILabs
Integrations

Onboarding assistant for Deputy: starter checklists and first-week schedules

An onboarding assistant for Deputy that drafts starter checklists and first-week schedules, with a team lead reviewing each output before use.

Updated 2026-08-28

Onboarding assistant with Deputy

New starters at shift-based businesses often arrive to a roster, a stack of forms and a list of duties that nobody has gathered in one place. An onboarding assistant can help the team lead assemble that material before the first shift, drawing on Deputy as a reference wherever a starter's site and scheduled hours are recorded. The assistant can draft a checklist from a standard template, lay out a first-week schedule around rosters already in place, and produce a short welcome note for the team lead to review. Deputy holds the rostering side of this work, so the question for a business is which parts of a starter's record can be read from it and which must be entered by hand. Personal details such as tax file numbers, bank details and emergency contacts should stay out of any outside model. A team lead keeps the final say on every checklist and every schedule change.

How it works

  1. Collect the starter's role, site and scheduled hours from Deputy, using whichever fields the account's permissions expose through the API or an export.

  2. Pass those details, with no personal identifiers, to a model that fills a standard onboarding checklist and a first-week schedule template.

  3. Route the draft to the team lead, who confirms pay conditions, required training and any site rules before anything is shared with the new starter.

  4. Create the approved first-week shifts in Deputy by hand, or through an API write if the account permits it, so the roster stays the single record.

  5. Keep a log of each draft, each edit and each shift created, so any later question about a starter's first week can be traced to its source.

good questions, straight answers

Frequently asked questions

Can an onboarding assistant work with Deputy?
Yes. Deputy provides an API for working with workforce records, and the account's permissions shape what a connection can reach. The assistant itself runs outside Deputy and works from what it is given, such as a starter's role and start date, then drafts a starter checklist and a first-week schedule for your manager to pick up. Your team keeps rostering in Deputy exactly as it does today.
What does an onboarding assistant write to Deputy?
Ideally very little. The assistant produces drafts: a checklist, a first-week schedule and a welcome note, all for a team lead to read. Any change to Deputy, such as creating a first-week shift, should be made by a person or by a write route the account permits through the API. The assistant should not alter pay settings, qualifications or personal records.
What does an onboarding assistant with Deputy need from me?
It needs a clear list of what a starter must complete, such as a standard checklist, required training and site rules. You will need to confirm that the account's permissions allow the chosen API or export route, and to name the person who reviews every draft. You also need a documented decision on privacy and consent before any staff details leave Deputy. Finally, decide how the approved output is handed to the new starter.
What does an onboarding assistant not do with Deputy?
It leaves the decisions to your team. Checking a starter's right to work, qualifications and identity, and setting pay, award classification and tax treatment, stay with the people who own them, and the assistant keeps everything organised with tidy checklists and reminders. It drafts welcome messages and first-week plans ready for your manager to send, and roster changes happen in Deputy when your team makes them.
Which tools sit between an onboarding assistant and Deputy?
Automation platforms such as Zapier, Make, n8n and Power Automate can move data between Deputy and other apps, so a team may use one to pass starter details to an assistant. Xero may be relevant once a starter reaches payroll, since pay data should move there only after review. Claude or ChatGPT can generate the draft text. Which tool fits depends on the account's plan, the data involved and the business's privacy decisions.
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.