What a schedule is for

Free visual lesson · about 5 minutes · short quiz at the end

ccPlanning academy · scheduling

What a schedule is for

The job that turns a forecast into people in seats at the right time.

The handover

Forecasting ends; scheduling begins.

Forecasting gives you a requirement — how many people you need in each interval to hit service. Scheduling’s job is to build shifts whose coverage matches that requirement as closely as real life allows.

The core idea

Match a smooth curve with blocky shifts.

The requirement rises and falls smoothly through the day. But people work in chunks — 8-hour shifts, 4-hour part-times. Scheduling is the art of tiling those blocks under a curve.

The two failure modes

Every gap costs; every surplus costs.

Where coverage falls below the requirement, service drops and queues build. Where it sits above, you’re paying for idle time. Good scheduling minimises both at once — not one at the expense of the other.

Why it’s hard

It’s a constrained jigsaw.

Shifts must respect contracts, breaks, skills, fairness, fatigue rules and people’s lives — while still hugging the curve. That tension, not the arithmetic, is what makes scheduling a craft.

The mindset

You’re shaping supply to fit demand.

Forecasting is about predicting demand. Scheduling is about shaping supply — start times, lengths, days off, flexibility — so the people you have land where the work is. The forecast is the target; the schedule is the response.

Why blocks never fit perfectly

The 10am problem

The requirement says you need 18 at 10am and 31 at 11am. But you can’t hire someone for one hour — the person covering 11am is already in at 8, idle-ish at 10, and still there at 2 when you only need 22.

That mismatch is unavoidable; the craft is making it as small as possible with smart start times and part-time cover, not eliminating it.

The takeaway

A schedule is a forecast made real.

Its only job is to put coverage where the requirement is, within the constraints of real people and contracts. Everything else in this track is about doing that well.

Now test yourself ↓

1 / 7

Slides done? Here’s the same idea in a bit more depth — the part worth keeping.

In depth: turning a requirement into people in seats

Forecasting hands scheduling a clean output: a requirement — how many people you need in each interval to hit service. Scheduling’s entire job is to build shifts whose coverage matches that requirement as closely as real life allows. Forecasting predicts demand; scheduling shapes supply — start times, shift lengths, days off, flexibility — so the people you actually have land where the work is. The forecast is the target; the schedule is the response.

A smooth curve, blocky people

The difficulty is structural. The requirement rises and falls smoothly across the day, but people don’t work in smooth slivers — they work in chunks, eight-hour shifts and four-hour part-times. Scheduling is the art of tiling those blocks under a curve, and the blocks never fit perfectly. Where coverage falls below the requirement, service drops and queues build; where it sits above, you’re paying for idle time. Good scheduling minimises both failures at once, rather than fixing one at the other’s expense — a flat “just add people” removes the gaps by creating expensive surpluses everywhere else.

Why it’s a craft, not arithmetic

If shifts could be any shape, the tiling would be easy. They can’t: they have to respect contracts, break rules, skills, fairness, fatigue limits and people’s actual lives, all while still hugging the curve. That tension — between the shape demand wants and the shapes real people can work — is what makes scheduling a craft rather than a calculation, and it’s what the rest of this track is about handling well.

The principle to remember: a schedule is a forecast made real. Its only job is to put coverage where the requirement is, within the constraints of real people and contracts — minimising gap and surplus together.

What a schedule is for