Planning

The schedule is only useful if it is believed. This pillar builds the capability to produce a plan that holds, review it every day, and act on what it finds before the next shift starts.


Pillar Intent

The Planning pillar exists to ensure that the right work is scheduled, resourced, and sequenced, and that when reality diverges from the plan, the gap is visible, owned, and acted on the same day.

Most sites have a schedule. Fewer have a schedule that produces the right output.

The most common failure is not a missing schedule. It is a schedule shaped by the wrong objective. When a site is measured on volume, it learns to make what is easiest to make in the largest quantities. Long runs. Fewer changeovers. High output numbers. The metrics look good. But the wrong product is being made. The right product is short. Inventory of what nobody needs builds in the warehouse, taking up space, tying up cash, and creating handling and storage problems that nobody planned for. Meanwhile the customer is waiting.

The schedule did not fail. It delivered exactly what it was designed to deliver. The problem was what it was designed to deliver.

This pillar builds the capability to produce a schedule that is built around what is actually needed — and to hold that schedule against the pressure to optimise for something easier to measure. It also builds the capability to manage the exceptions that will always arise without collapsing the whole plan.

The Planning pillar owns one core process: the Integrated Schedule. It is reviewed daily, at every tier, using two questions that do not change.


Pillar Owned Losses

The Planning pillar is accountable for addressing these losses

⚠️
Wrong product produced, the schedule built around what is easiest to make rather than what is needed next. Long runs, fewer changeovers, volume metrics that look good while the right product goes short, the wrong product fills the warehouse, and the customer waits. Stockouts, excess inventory, and poor customer service are all consequences of this single failure.
⚠️
Unplanned downtime caused by maintenance that was not scheduled before the failure occurred, because the planning system never created the slot, or the slot was given back to production before the work could be done.
⚠️
Procurement failures, materials not available when the schedule requires them, because lead times were not built into the plan and the order was placed when the need was urgent rather than when it was foreseeable. Expediting cost is the price of this failure.
⚠️
Disconnection from the corporate demand signal, the site running to a plan that does not reflect what the business actually needs.
⚠️
Schedules built on wrong data, run rates, yields, cycle times, or material quantities that no longer reflect what the operation actually does, producing plans that cannot be met and variances that cannot be explained.

Pillar Owned Processes

The Planning pillar owns one process: the Integrated Schedule.

Not three separate schedules reconciled weekly. One plan, covering production, maintenance, and procurement together in a single picture, reviewed daily at every tier using two questions that do not change.

Did we do what we said we would do? If yes, confirm and move on. If no, understand why before replanning.

Do we have what we need for what comes next? If yes, protect the plan. If no, act now.

When the plan changes, the decision is made by the right people with the full picture visible, and the revised plan is the one every function works from. When the plan misses, the cause is investigated and eliminated so it does not repeat.


Capabilities

Process capabilities

The Planning pillar builds capability in three areas:

  • Building the schedule, producing an integrated plan that covers production, maintenance, and procurement, sequenced correctly, anchored to what is actually needed, and built on accurate master data
  • Monitoring and maintaining the schedule, reviewing the plan daily at every tier, acting on gaps the same day, protecting the fixed window, and managing exceptions through a named decision-maker
  • Monitoring and maintaining master data, owning the review and approval process for the data the schedule is built on, so that when actual performance diverges from the plan, the root cause is found in the data rather than managed around it
  • Low stock and out of stock management, defined thresholds set against safety stock targets, daily visibility, named owners, and a same-day escalation path. Low stock is a warning. Out of stock is a failure. The system is designed to act on the warning. Thresholds are not arbitrary minimums. They are set against a calculation that reflects demand variability, lead times, and the consequence of running out, and reviewed on a defined cycle.
  • Inventory management, tracking inventory as a measure of planning health, not just a warehouse metric. The right question is not how much inventory the site holds. It is whether the inventory held is the right inventory, in the right place, at the right time. Excess inventory of the wrong product is a planning failure. Insufficient inventory of the right product is also a planning failure. Days on hand, the number of days of supply currently held, is reviewed alongside schedule adherence and low-stock events as part of the daily and weekly picture.
  • Customer service tracking, the measure of whether the right product reached the customer when they needed it. Tracked as a planning output, not just a logistics one. A service failure that traces to a schedule decision is a planning failure. It is reviewed at Tier 3 alongside schedule adherence and inventory position.
  • The S&OP / IBP interface, the connection between the site schedule and the corporate Sales and Operations Planning or Integrated Business Planning cycle (the process that translates demand into a confirmed supply plan). The site provides a confirmed capacity and supply position. The corporate cycle provides the demand signal and any changes to priorities. The interface defines what moves in each direction, at what frequency, and who owns it at each level.

People capabilities

  • Operations line leaders who can review the production schedule at the line, answer both questions, and escalate when the plan is at risk
  • Operations area leaders who can hold the production schedule across lines and shifts and consolidate the Tier 1 picture for Tier 3
  • Maintenance area leaders who can confirm planned work, resource, parts, and access, and bring a clear position to Tier 3
  • Operations and maintenance site leaders who can hold the full site schedule and represent a confirmed position to the business
  • Procurement leads who can translate the forward schedule into material requirements with lead times applied, and surface supply risks before they become shortages
  • Schedulers and planners who can build and maintain a credible integrated schedule that production, maintenance, and procurement can all work from

Behaviours

The weekly schedule is built on Monday. By Thursday it looks nothing like the plan.

Without the system: Production has been running the same product for four days. A changeover was pushed back twice, once for a maintenance slot given back to production, once because the material had not arrived. Volume is on track. Two products customers needed this week have not been made. One is at low stock. The other is out. Nobody decided this would happen. The schedule just responded to each day's pressure.
With the system: The schedule is built around what is needed next, in the right sequence. The fixed window protects it. Maintenance slots are confirmed before they are locked. Procurement acts on the signal when it is foreseeable. When something disrupts the plan, it is visible the same day, owned by a named person, acted on before it cascades into the following week.

A product is running low. The line manager finds out when the line stops.

Without the system: The low-stock signal was in last week's report. Nobody acted on it. The material was on order but the lead time was longer than the gap. The line stops. An expedite order is placed at premium cost. Production switches to something else while they wait.
With the system: The threshold is set against a calculated safety stock target. When it is breached, it surfaces in the daily review the same day, not in a weekly report. A named owner is assigned before the meeting ends. The response is in place before the line is at risk.

What Good Looks Like

Operations line leader

  • eviews the production schedule for their line at the daily Tier 1 meeting, what was planned, what was completed, what is open for this shift and the next
  • Answers both questions before the meeting ends: did we do what we said, do we have what we need
  • Escalates when the plan is at risk, named, with a proposed path forward, before the meeting ends
  • Does not wait for the weekly review to surface a low-stock signal. Raises it the day the threshold is breached
  • Knows the constraint on their line and understands why the sequence is built around it

Operations area leader

  • Holds the production schedule across all lines and shifts in their area
  • Consolidates the Tier 1 picture for Tier 2: which lines did what they said, which did not, and why
  • Surfaces low-stock signals with a named owner and a response plan, not a list of problems
  • Connects daily schedule performance to the site's strategic objectives. A schedule that consistently misses in the same way is a system problem, not a daily operations problem
  • Ensures the maintenance area leader for their zone is in the same Tier 2 conversation, not in a separate meeting

Maintenance area leader

  • Confirms planned work, resource, parts, and access for their area before the slot is locked
  • Is present at the Tier 1 meeting for the lines they support, not to report on their backlog, but to be part of the shared conversation about equipment condition, planned access, and abnormality response
  • Brings a clear position to Tier 2: what is confirmed, what has moved, what needs a decision at Tier 3
  • Does not allow planned maintenance to be deferred without a named decision-maker and a recorded reason
  • Tracks plan adherence for proactive maintenance tasks. A plan that is consistently deferred is not a plan. It is a list

Site leader

  • Ensures the site's position in the S&OP / IBP cycle is based on a confirmed schedule, not last month's actuals, not an estimate
  • Reviews schedule adherence, customer service, and inventory position together. A site that hits its volume target while the wrong product fills the warehouse has not succeeded
  • Asks in reviews: is the fixed window being held? Are low-stock signals being acted on the same day? Is master data being reviewed on a defined cycle, or only when something breaks?
  • Ensures both operations and maintenance are measured on equipment availability, not just their own function's output. If they are measured on different things, the shared accountability is not real
  • Sets the expectation that a schedule miss is investigated, not just replanned. A miss that is replanned without investigation is a miss that will happen again

Audits and Confirmations

✅
Is the schedule being built around what is needed, or what is easiest to make? Look at the last four weeks of production. Does the sequence reflect customer demand and inventory position, or does it reflect long runs and avoided changeovers? If the same product appears in extended runs while others go short, the schedule is optimising for the wrong thing.
✅
Is the fixed window being held? Count how many changes were made inside the fixed window last week. One or two with a named exception is a system working under pressure. Five or more with no formal process is a schedule that nobody believes. If the window is not being held, find out why, the cause is usually upstream, not in the planning function.
✅
Are low-stock thresholds triggering a same-day response? Pull the last three low-stock events. When did the threshold breach? When was it acted on? If the answer is days later, or at the weekly review, the signal is arriving but not travelling. The threshold is working. The escalation is not.
✅
Are safety stock targets set against a calculation, or a habit? Ask the planning team how the current safety stock levels were set and when they were last reviewed. If the answer is "we've always held that level" or "we added a buffer after the last stockout," the targets are not calculated, they are inherited. Demand variability and lead times should drive the number, reviewed on a defined cycle.
✅
Is master data reviewed on a defined cycle, or only when something breaks? If the last master data review was triggered by a schedule failure rather than a calendar date, the process is reactive. Ask when run rates, cycle times, and yields were last validated against actual performance. A gap of more than six months in a changing operation is a gap that is already affecting the schedule.
✅
Is the site's position in the S&OP / IBP cycle based on a confirmed schedule? Ask what the site submitted in the last cycle. If the answer is last month's actuals, an estimate, or a number from the planning system that has not been validated against current capacity and constraints, the site is not participating in the cycle, it is reporting into it.
✅
Is customer service tracked as a planning output? If a service failure is reviewed only by logistics or commercial, the planning root cause will not be found. Ask whether the last three service failures were investigated for schedule cause. If not, the planning system has no feedback loop from its most important output.
✅
Are schedule misses being investigated, or just replanned? A miss that is replanned without investigation is a miss that will happen again. Ask whether the last three schedule misses were classified, owned, and investigated. If the answer is no, the planning system is managing disruption rather than eliminating it.

Where to Start

Before selecting a process to build, take stock of where you are. These questions are not a formal audit. They are a quick read of the planning system as it stands today.

🔍
Does the site have one schedule that production, maintenance, and procurement all work from?

If not, the first step is not a new planning tool. It is a conversation. Get the three functions in the same room, with the same picture, answering the same two questions. The Integrated Schedule is the output of that conversation, not the input to it.

🔍
Does the schedule reflect what the customer needs, or what is easiest to make?

If the site is consistently making long runs of the same product while others go short, the schedule is optimising for the wrong thing. Start by identifying the constraint and building the sequence around it. Then hold that sequence inside a fixed window.

🔍
Are low-stock signals visible in real time, or discovered when the line stops?

If the signal is arriving in a weekly report rather than a daily review, the escalation system is not working. Set thresholds. Connect them to the daily Tier 1 meeting. Assign a named owner the day the threshold is breached, not the day the line stops.

🔍
Is master data accurate enough to build a schedule on?

If the planning team is maintaining a spreadsheet with "real" run rates alongside the system, the master data is wrong and everyone knows it. Fix the source before building a more sophisticated schedule on top of it. A schedule built on wrong data will miss, reliably, and the team will be blamed for a problem the data created.

🔍
Is the site's position in the S&OP / IBP cycle based on a confirmed plan?

If the site is sending estimates rather than a confirmed schedule, the business is planning around uncertainty rather than around the site. Start by confirming the near-term schedule at Tier 3 before the next cycle submission. That is the minimum the business needs to plan around you rather than despite you.

If the answer to most of these is no, start with Phase 1, Establish. Introduce the Integrated Schedule for the pilot area. Run the two questions daily. Set the fixed window. These are the foundations. Without them, everything else is built on a plan nobody believes.

If the schedule exists but is not being held, changes inside the fixed window, low-stock signals not acted on, maintenance slots consistently deferred, start with Phase 2, Strengthen. The most common gap at this stage is not in the tools. It is in the daily discipline. Fix the escalation before expanding the scope.

If the schedule is running reliably and the site's S&OP position is confirmed, move to Phase 3, Sustain. The goal is not a better schedule. It is a planning capability that is assessed, refreshed, and built into how the site runs, not a project, not a programme. Just how we plan.


Phases

Phase 1 — Establish

The Integrated Schedule is introduced for the pilot area. Production scheduling is confirmed daily at Tier 1. The fixed window is defined and agreed. Low-stock thresholds are set for critical materials, anchored to initial safety stock targets, not arbitrary minimums. The two questions are established as the daily standard.

Maintenance scheduling is added at Tier 2, slots confirmed with resource and materials before they are locked. The connection between the site schedule and the S&OP / IBP cycle is mapped, even if it is not yet fully formalised. Production sequence is reviewed for the pilot area, the constraint is identified and the schedule is built around it.

Phase 2 — Strengthen

The Integrated Schedule extends to all lines and departments. Procurement scheduling is added at Tier 3, material requirements generated from the schedule with lead times applied. The S&OP / IBP interface is formalised: defined inputs, defined outputs, defined frequency, named owners at each level.

Safety stock targets are reviewed and confirmed for all critical materials and finished goods. Inventory management, days on hand, excess, and shortfall, is tracked as a planning measure alongside schedule adherence. Customer service is tracked as a planning output: a service failure that traces to a schedule decision is investigated as a planning failure.

Schedule adherence, customer service, and low-stock management are confirmed processes, audited, owned, and improving. Schedule misses are classified, investigated, and fed back into the system, the causes of disruption are being addressed, not just managed.

Phase 3 — Sustain

The Integrated Schedule runs across the site. The fixed window is held. Low-stock events are rare and acted on immediately when they occur. Safety stock targets are reviewed on a defined cycle and updated when demand patterns or lead times change. Inventory reflects the plan, not what was convenient to make. The site's position in the S&OP / IBP cycle is based on a confirmed schedule. The planning capability is assessed, refreshed, and built into how the site runs, not a project, not a programme. Just how we plan.


Ready to build your pillar?

Before you start, make sure your team is in place, your charter is drafted, and your plan connects to the site's strategic objectives. The Setting Up Your Pillar guide takes you through each step in sequence.