The manager who holds it together is your biggest operational risk
There is someone at almost every nursery group I speak to who makes the whole thing work. She knows every bank staff member by name — who will pick up on a Friday, who is reliable in baby rooms, who to avoid sending to a particular site.
Her system is a WhatsApp group, a spreadsheet she updates on Sunday nights, and a set of relationships she has spent years building.
It works. The shifts get covered. The ratios hold. And when I ask how she manages bank staff across eight or ten sites, she says: we manage fine.
What she does not say, because she has never had cause to think about it, is what happens when she is not there.
The single-site model is built on social capital
A single-site nursery can manage bank staff through relationships because the problem is human-sized. The manager knows her pool personally. She texts three people, someone says yes, the shift is covered.
The problem is that this model does not transfer. Social capital is personal. When you open a second site, you do not double the system. You expose its architecture for the first time — and what you find is that there is no architecture. There is a person.
One site: the manager knows everyone. Two sites: the pools are invisible to each other.
The cost nobody counts
The groups we work with typically spend six to eight hours a week, per site, coordinating bank staff cover. Chasing availability, updating the list, chasing again once the list has gone stale.
At three sites you absorb it. At ten or twelve, that is most of a full-time role spent managing a problem rather than removing it. Nobody ever hired for it. It accumulated — an hour here and there — until it became someone’s actual job in everything but the title.
There is no line on a P&L called ‘time lost to bank staff admin.’ But when I ask operators to add it up properly, the number reliably changes the conversation.
At 10–12 sites, coordination hours exceed a full-time role — with no hire to show for it.
The resignation test
There is a simple question worth asking about any operational system: what happens if the person running it hands in their notice tomorrow?
For most nursery groups, the honest answer when it comes to bank staff is: we start again from scratch. The contacts list is on her phone. The spreadsheet is in her personal drive. The knowledge of who is good, who is available, who works well at which site — all of it lives in her head.
The resignation does not just create a staffing problem. It erases the system entirely.
What good looks like
A group that has solved the bank staff problem looks different in one specific way: the knowledge is in the system, not in a person.
Every available bank staff member is visible across every site. When a gap opens at Site A, the manager does not work through her personal contacts. She posts the shift and it reaches everyone in the group who is qualified, available, and nearby — regardless of which site they usually work at.
This is what BStaff was built to do. Your bank staff only ever see shifts within your group, not across the sector. Your pool stays yours. It just stops being invisible.
One dashboard. All sites. The cover that was always there becomes reachable.
The objection
The most common response is: we manage fine.
Fine compared to what? If Sunday-night spreadsheets and 7am calls are the baseline, then a week where you covered everything does feel fine. It is only once you have seen the alternative that fine starts to look like a great deal of effort spent standing still.
Fine until when? Because fine usually rests on one or two people holding it together. It works right up until the morning one of them is not there.
Most groups are not failing at bank staff. They are succeeding through the wrong mechanism — and the mechanism is more fragile than it looks.