Workload Peaks and Staffing Issues - Visualrota

Recently, I was speaking with a client who was struggling with a familiar problem: unpredictable workload spikes. Their team was overwhelmed at the start and end of every month, phones ringing off the hook, staff stretched thin, and customer frustration rising.

On paper, nothing seemed unusual. The staffing levels were stable. The processes hadn’t changed. Yet every month, like clockwork, the same tidal wave hit.

So we stepped back and looked at their demand profile — not just the numbers, but the story behind the numbers.

And the answer was surprisingly simple.

They sent out all their bills at the start and end of the month.
Customers received them.
Customers had questions.
Customers called.

The spike wasn’t a mystery. It was a perfectly predictable human response.

The client had already started brainstorming ideas. One suggestion was to let customers choose their own billing date. In theory, this would spread the workload more evenly.

But when we looked at it through the lens of real human behaviour, the picture changed.

Most people get paid at the end of the month.
Most people budget around that.
Most people want bills to arrive when they actually have money in their account.

So if customers were given the choice, they wouldn’t spread themselves evenly across the month. They’d cluster — right back at the start and end.

The spike would remain.
The workload pressure would remain.
And the organisation would still be firefighting.

This is the heart of demand and capacity modelling:
You’re not just analysing numbers.
You’re analysing behaviour.

Why do people call?
When do they call?
What triggers the peak?
What constraints shape their choices?

Once you understand the “why,” the “what to do about it” becomes much clearer.

In this case, the organisation had two realistic options:

or

 A wave of unpaid bills because customers received them at a time they couldn’t afford to pay?

 Sometimes the most efficient solution is to work with the pattern, not against it.
   If spreading demand is essential, you need a billing date that customers won’t cluster around.
 Two options emerged:

•  Bill customers on the date they signed up
•  Bill customers on their birthday each month

 Both approaches spread demand naturally, without forcing customers into financial stress.

Workload spikes rarely happen by accident. They’re usually the result of:

The key is recognising that demand isn’t random. It’s shaped by human needs, habits, and incentives.

When you understand those drivers, you can design staffing, shifts, and processes that actually fit the real world — not the theoretical one.

This is the work we do every day: helping organisations understand their demand, redesign their staffing, and create systems that work for both customers and employees.

If your team is wrestling with workload spikes, unpredictable demand, or shift patterns that never quite fit, it might be time to look at the story behind your numbers.

Because once you understand the “why,” the “how” becomes a whole lot easier.