Staff scheduling when half your team is part-time

Where a paper rota fails first

Three things go wrong with a mixed team specifically. Part-time staff are less likely to walk past the physical board on a day they were not already coming in, so a change made Tuesday for Thursday may simply never reach them. A person can end up scheduled at two things — a shift here and a commitment elsewhere — with nothing catching the overlap until they do not show. And nobody notices a day is short-staffed until the day arrives, because a paper grid does not add itself up.

None of these are staffing problems. They are visibility problems, and a mixed team makes them worse because the people most likely to miss an update are also the people the schedule depends on most heavily to fill gaps.

The weekly grid

The model that actually works at this size is simple: every staff member as a row, Monday through Sunday as columns, and each cell cycling through morning, day or evening. It is the same paper rota by the staff door, just visible from a phone instead of a wall — which is the part that matters for a part-timer who is not walking past that wall most days.

The grid is also where a double-booked person becomes visible before it becomes a problem. A part-timer who agrees to two things for the same evening — a shift here, a commitment elsewhere — is easy to miss on paper and hard to miss on a grid where their row for that day only has room for one answer.

A coverage minimum, not a labour-cost optimiser

Underneath the grid, a coverage row totals how many people are on each day, and a threshold flags any day that falls under it. This is deliberately not trying to calculate the cheapest possible staffing — rostering at this size is a judgement about specific people, not an optimisation problem — but making the shortfall visible before the day arrives instead of during it.

Set the threshold at whatever your property actually needs to run safely — two on a slow weekday, three on a weekend — and a day that drops below it shows up as a problem on Monday, solvable with a phone call, rather than a surprise on the day itself.

One anchor, then part-time fills the rest

A practical rule for a mixed team: no shift should depend entirely on part-time or on-call staff showing up. Cover every shift with at least one full-time anchor who is reliably there, and let part-time staff fill the remainder around that anchor.

Headcount is not the whole story

A coverage number answers 'how many people' and quietly assumes those people can do the same job, which for a mixed team is not always true. A day covered by two people who can both run the front desk is a different day from one covered by two people where only one can — the second one is not actually covered, it just looks covered on the grid.

This is the practical argument for the anchor rule above rather than pure headcount: the full-time anchor is usually the person who can run whichever part of the operation cannot be handed to whoever happens to be available that day, and scheduling around that is a judgement the coverage number alone cannot make for you.

Matching part-time availability to actual demand

Most mixed teams do not need part-time coverage spread evenly across the week — they need it concentrated where demand actually peaks, usually weekend evenings and check-in windows, and thinner on a quiet Tuesday morning. Cycling each day through morning, day or evening on the grid is what makes that pattern visible: a property can see at a glance whether its part-time hours are landing on the shifts that are actually busy, or just on whichever days people happened to volunteer for.

When someone cannot make their shift

A part-time team has more last-minute changes than a full-time one, almost by definition — a second job, a class, a family commitment can all move at short notice in a way a primary job usually does not. The grid does not prevent that; what it does is make a swap a visible edit rather than a private arrangement two people made over text message that nobody else knows about.

A cell changed from one person to another the day before a shift is still recorded against that day and that shift type, which means the coverage total for that day stays accurate through the swap instead of quietly going stale the moment the original plan changes.

The failure mode worth watching for is the swap that happens verbally and never reaches the grid at all — two staff agree between themselves and the schedule keeps showing the original name. That gap is invisible until the day the original person also does not show, at which point the property is one person short with a grid that insists it is not. Making the edit itself as fast as the phone call it replaces is what keeps the grid the actual source of truth rather than a record of the plan before reality intervened.

What this does not solve

A visible grid does not make a part-time staff member more available, and it does not replace an honest conversation about whether your team is actually large enough for your room count. What it does is turn a shortage that would otherwise be discovered on the day into one that is visible a week ahead — which is the entire difference between a solvable problem and a Sunday-morning scramble.

It also will not fix a team that is genuinely too small for the property, however well the gaps are flagged. If the grid is flagging most weeks rather than the occasional one, the honest reading is not a scheduling problem — it is a headcount problem wearing a scheduling problem's clothes.