Level five of workforce management maturity is when what actually happened shapes the next plan. The forecast and the schedule are compared with the hours actually worked, and the next plan changes because of the difference. It only works on top of level four, where your rules classify the hours before they reach payroll. A forecast can only learn from hours that are true. The test: when last month's forecast was off, did anything in this month's plan change because of it?
Say a store's forecast calls for 20 people on Saturday mornings in October. Four Saturdays in a row, the morning is quiet and the manager sends four people home at 10. That's sixteen shifts cut short in one month.
Every one of those shifts is recorded and paid exactly right. And the plan for the first Saturday in November still calls for 20 people.
Nothing in that record reached the plan. Closing that gap is the fifth level of workforce management maturity: the point where the record of what happened starts shaping what gets planned next.
In this post:
- What level five is
- Why it depends on level four
- The test for level five
- What closing the loop looks like
- How WorkAxle handles level five
What is level five of workforce management maturity?
The four levels of workforce management maturity describe how a week's hours become pay. Level five takes that record and points it forward. The forecast and the schedule are compared with what actually happened, and the difference goes into the next forecast and the next schedule.
Level five starts from true hours. Not sure where yours stand? The WFM diagnostic takes eight questions, shows your result on screen as soon as you finish, and names the one gap worth closing first.
Why does level five depend on level four?
A forecast learns from whatever record it's given. At level one, the schedule is edited to match the day, so the plan and the "actuals" are the same file. Compare them and the forecast looks perfect every week, because every miss was overwritten.
At level two, the actuals exist but live somewhere else, so the comparison waits for someone with time to line up two files. At level three, the records finally meet. But until the rules have run, nobody can say what the week really cost against what was planned. Level four is where that answer becomes reliable.
The same rules matter on the way forward. A forecast that ignores your limits on hours and rest plans for an ideal week, where anyone can work any day. Real weeks never look like that.
What's the test for level five?
Each level has a question that gives it away. Ask it about last month at one real site, not about the system you'd like to have.
| Level | The question that gives it away |
|---|---|
| 1. The schedule is the only record | Could you put last Tuesday's plan next to what actually happened? |
| 2. Two records | Before the last payroll, how many files did someone line up side by side? |
| 3. One system | When a shift changes on the day, does anyone type it in a second time? |
| 4. The rules run before payroll | Do hours reach payroll already sorted by type, or does someone sort them after the export? |
| 5. What happened shapes the next plan | When last month's forecast was off, did anything in this month's plan change because of it? |
Level five takes three questions to settle, because the loop can break in three places.
- Can you compare last month's forecast with what actually happened, day by day, without building a spreadsheet first? If that takes a project, the comparison isn't happening often enough to teach anything.
- When a day was off by a lot, does anyone know why? A miss on a holiday weekend teaches something different from a miss on an ordinary Tuesday.
- Did the misses change the plan? Circle the three days last month's forecast missed by the most, then look up the same days in this month's plan. If they look the same, the loop is still open.
The third question decides it. Plenty of operations compare the forecast with what happened, and the next plan goes out unchanged anyway. They have the data, and they aren't at level five yet.
What does closing the loop look like?
There are two speeds, and a mature operation uses both. Orange marks the two places where the plan changes.
Close to the day, the plan is adjusted as better numbers arrive. A forecast made weeks ahead gets sharper as the date approaches. The schedule follows it without rebuilding the week. In a union environment that matters, because a published shift is a commitment.
Season over season, the plan's assumptions get tested. If a season carried extra hours for absences and still met its service targets with room to spare, the next season can carry fewer. If the plan missed on the same days every week, those days need a different starting point.
Neither speed has to be automatic to count. Level five is when the comparison happens every cycle and the plan changes because of it. Automation changes how fast that happens and how many sites it can cover.
How does WorkAxle handle level five?
Comparing last month's forecast with what actually happened is where many operations stall, because the forecast, the schedule and the hours worked sit in three different places. In WorkAxle, all three live in one platform, so putting last month's plan next to last month's day doesn't start with an export.
Forecasting is part of what WorkAxle calls Decision Intelligence. It reads your demand history, runs several time-series models in parallel, and your team picks the one that fits each location. The chosen forecast becomes shift templates and work cycles in the scheduler.
When a sharper forecast comes in, the engine re-optimizes the plan within the shifts people already hold, extending, shortening or sliding them within limits you set. The revised plan comes back for your team to review before it's applied. The season-over-season calls stay with your planners. You can see how forecasting and re-optimization work in WorkAxle.
Curious what level five would look like in your operation? Bring us how you plan today and the days your forecast keeps missing, and we'll start from there.