Small Operations

Most scheduling advice assumes a workforce planning function. A single café or shop has the same problems and different resources.

What is genuinely easier

Everyone knows everyone, so availability is known without a system.

A conversation replaces a process for most things and does it better.

The rota fits on one page.

And fairness is visible, which cuts both ways: unfairness is visible too, immediately.

What does not scale down

Rest rules, minor employment limits and break entitlements. They apply at twelve people as at twelve hundred.

Contracted minimum hours.

The good-faith estimate, where required.

And the cost of losing a trained person, which in a team of twelve is proportionally larger than in a chain.

Where small operators get caught

Single-staffed breaks, which are common and are unpaid working time when the break cannot be taken.

Clopening, because with twelve people there often seems to be no alternative.

Under-18s, where the limits are strict and the person building the rota knows them approximately.

Publication by text message the night before, which is normal in the sector and is the largest recoverable problem.

And the owner covering everything, which hides the staffing gap until they take a holiday.

A proportionate arrangement

A repeating pattern covering the base load, so most of the rota is decided in advance.

Published a week ahead, which in a small operation is achievable and is a substantial improvement on the night before.

Availability reviewed twice a year, as a conversation.

A written note of who holds which certificate and when it expires.

And one person of slack on the busiest shift, which costs a few hours of wages and removes the scramble.

The single point of failure

In a team of twelve there are usually several tasks only one person can do.

List them.

Cross-train one more person for each, which is a few days of work and is the difference between a holiday and a closure.

When to take advice

Before dismissing anyone on attendance or reliability grounds.

Where a rota change affects contracted terms.

Where an under-18's hours are in question.

And before assuming a local fair workweek rule does not apply, because several count employees globally rather than locally.

The holiday test

One question that reveals the staffing gap.

What happens when the owner takes two weeks off?

In most small operations the honest answer is that several things stop.

Which is the single-point-of-failure list, made concrete.

Cross-train one more person for each item, and the test produces a different answer next year.

A practical implementation prompt

During configuration, use the remote-team use case to prompt questions about fields, ownership and output. Keep the written scheduling purpose in control and document every assumption.

Independent reference

For a thematic point of reference, see the U.S. Small Business Administration. Use this established source as an outside check before turning the principle into a workplace rule.