MILabs
Integrations

Shift swap automation with Famly for childcare rosters

How shift swap automation can work alongside Famly for childcare rosters, from request to approval, with the legwork of finding cover taken care of.

Updated 2026-08-11

Shift swap automation with Famly

Childcare services often find out late that an educator cannot work, and the cover search starts with a phone call or a group message. Famly holds much of the roster picture for a service, so the build sits alongside it. The build gives staff one place to request a swap, checks the request against the roster for qualifications, ratios and existing hours, and sends eligible requests to the director or room lead who approves them. Once a swap is agreed, the confirmation goes to everyone involved. Whether a swap can write back into Famly automatically depends on what your version exposes to outside tools, and that should be confirmed with the vendor. Until then, approved changes can be entered by hand. Qualification and ratio rules stay with the service, and no swap is approved without a person who holds the authority to approve it. Use the enquiry form to talk through your roster.

How it works

  1. Staff submit a swap request through a short form that names the shift, the requester and the proposed cover.

  2. Each request is checked against the roster for role, qualifications, ratios and existing hours before anyone is asked to approve it.

  3. Eligible requests route to the director or room lead the service has named as approver.

  4. Confirmation goes to the requester, the proposed cover and the approver.

  5. The approved change is recorded in the schedule, and an educator enters it into Famly by hand unless the vendor documents a supported route.

good questions, straight answers

Frequently asked questions

Who owns a shift swap automation built around Famly?
The service owns its roster, its staff records and the decisions about who may approve a swap. The build itself is a set of rules, forms and messages that the service can keep, change or stop. Access to child information in Famly stays under the service's privacy obligations. Ask MILabs to set out who owns the configuration before work starts.
How does a shift swap automation hand work to a person in Famly?
The automation does the legwork and hands over at the decision points. It proposes a swap, routes it to the named approver and sends a confirmation. The approver accepts or declines in the channel the service chose, and a person enters the final roster change in Famly. That keeps the approver in charge of who works when, and the back-and-forth of finding cover happens in the background.
Can a shift swap automation work with Famly data exports?
Yes, when your roster data comes out as an export with the fields the build needs. The automation reads the file, checks who can cover a swap and lines up the request for approval. Child information is trimmed down to what the roster check needs, so the automation works with just the details it uses. Your approver gets a clear choice to make in a moment.
What should I back up in Famly first?
Before a build touches any roster, export or copy the current schedule, staff list and approval rules so that a change can be reversed. Keep a dated copy of the approved swap log too, since it shows who agreed each change. Confirm with the service's own policy which records must be retained and for how long, because those rules differ between services. This page sets no retention periods or backup method.
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.