How Microkeeper Automates a Repeating Shift Roster
If your roster follows the same pattern every week, fortnight, or FIFO swing, you shouldn't have to rebuild it from scratch every period. Microkeeper, an Australian all-in-one workforce platform, includes a feature called Roster Cycles built specifically to solve this: map a repeating shift pattern once, and apply it automatically across your team for any date range. This guide walks through how it works step by step, and why each step is built the way it is.
: map a repeating shift pattern once, and apply it automatically across your team for any date range. This guide walks through how it works step by step, and why each step is built the way it is.Why repeating rosters are worth automating
A lot of businesses run rosters that don't actually change much period to period. A mining crew on a 14-on/14-off swing. A hospital ward running a fixed rotation across three shifts. A warehouse team on a standard 5-on/2-off pattern. In each case the underlying pattern is stable, but without automation, someone still has to manually recreate it every single cycle.
The manual rebuild is where rostering time gets lost. It's also where errors creep in: a shift copied to the wrong day, a day-off pattern that drifts out of sync after a few cycles, a new starter who gets missed entirely. Microkeeper's Roster Cycles feature was built specifically to remove both problems at once, less time spent, and a pattern that stays consistent because it's generated the same way every time. It's aimed at the businesses where this pain is sharpest: mining and resources running FIFO rotations, healthcare with rotating shift blocks, warehousing and logistics, construction, and any multi-site business trying to keep several teams on consistent rotations without a roster admin rebuilding each one by hand.
How Roster Cycles automates a repeating pattern, step by step
1. Map the pattern before you build anything
Before opening Roster Cycles, write out the actual pattern: how many days are worked, how many off, and what the shift times are for each worked day. For a simple pattern like 5-on/2-off this takes a minute. For something like a rotating three-shift healthcare roster, it's worth mapping the full cycle length on paper first, this is the step most people skip, and it's usually where mistakes start once you get into the software.
2. Start from a template, or build a custom pattern
Roster Cycles ships with six built-in templates covering the most common rotations: 7-on/7-off, 14-on/7-off, 14-on/14-off, 5-on/2-off, 8-on/6-off, and 21-on/7-off. Any of them can be customised. If your pattern is genuinely unique, a bespoke site rotation or an irregular healthcare block, a fully custom pattern can be built from scratch inside Roster Cycles too, and you only need to build it once.
3. Build once, apply it at the group level
The point of Roster Cycles is that you don't rebuild the pattern for every individual, every period. You build it once, then apply it to a group of employees who share that rotation, not one person at a time. Cycles can be saved as a draft while you're still reviewing them, and switched to active once ready, so there's no risk of a half-finished pattern accidentally going live.
4. Preview before you commit
Before Roster Cycles generates a single shift, a full preview shows every date in the cycle, the calendar date, whether it's worked or off, the shift times, and any notes attached. Nothing is created until this is reviewed and approved. This step catches mistakes while they're still a two-minute fix in the preview screen, not a payroll problem three weeks later.
5. Choose how the cycle applies: Top Up or Replace
Once a cycle is built, it's assigned to a group or an individual employee for a chosen date range, with a set number of repetitions. Roster Cycles gives you two ways to apply it: Top Up, which only fills days that don't already have a shift, or Replace, which overwrites the roster entirely for that range. Top Up is the safer default when you're layering a new pattern onto a roster that already has some shifts in it.
6. Plan for new starters up front
New employees joining a team with an existing rotation are the most common source of roster errors elsewhere, but Roster Cycles handles this deliberately rather than automatically. When someone new joins a team that already has a cycle running, their shifts aren't generated for them straight away. Instead, you reapply the existing group assignment using Top Up. Microkeeper recalculates the matched employee list to include the new starter, fills in their unrostered days, and keeps them aligned with the rest of the group's cycle, while leaving shifts already in place for everyone else untouched.
Practical tips for keeping a repeating roster accurate in Microkeeper
- Check your cycle length against your pay period. A pattern that doesn't divide evenly into your pay cycle can make reconciliation harder than it needs to be.
- Use Top Up as your default when applying a cycle. Reserve Replace for situations where you genuinely want to wipe and rebuild; it's easy to accidentally overwrite shifts you meant to keep.
- Review the preview properly, not just a glance. It's the cheapest place in Roster Cycles to catch an error, before shifts, and pay, are affected.
- Revisit the pattern in Roster Cycles when the underlying roster changes. A cycle built for a 20-person crew doesn't automatically adjust if the crew structure changes significantly; treat it as a living template, not a one-off setup.
- Keep custom patterns documented somewhere outside the software too. If a cycle is unusual, a short note on why it's built that way saves confusion for whoever manages it next.
Frequently asked questions
What counts as a “repeating roster”?
Any roster where the same structure of worked days, days off, and shift times recurs on a set cycle, including FIFO rotations, fixed weekly patterns, and rotating shift blocks common in healthcare and manufacturing. Roster Cycles is built to handle all of these.
Can a repeating roster still handle exceptions, like leave or shift swaps?
Yes. Automating the base pattern in Roster Cycles doesn’t remove the ability to make individual changes; leave, swaps, and one-off adjustments are handled on top of the generated roster, not instead of it.
What's the difference between Top Up and Replace when applying a cycle?
Top Up fills only the days that don’t already have a shift, leaving existing shifts untouched. Replace overwrites the roster entirely for the selected date range. Top Up is generally the safer choice when a roster already has some shifts in place.
How do new employees get added to an existing rotation?
Rather than being added automatically, a new starter is brought into a Microkeeper cycle by reapplying the group’s cycle assignment using Top Up. This fills their unrostered days and aligns them with the group’s existing pattern, without affecting shifts already generated for other employees.
Is this only useful for large teams?
It’s most valuable at scale, mining crews, hospital wards, warehouse teams, but the same principle applies to a small team on a fixed weekly pattern in Microkeeper. The time saved scales with the number of people and the length of the roster period, but the accuracy benefit applies at any size.
Roster Cycles is available on Microkeeper's Enterprise plan, alongside HR, rostering, timesheets and payroll.
