How Does IBP Work?

IBP works through a monthly cycle of five sequential reviews, each owned by a different function, that moves a plan from product decisions through an unconstrained forecast, a supply-constrained draft, a financialized reconciliation, and finally an executive sign-off. Each step's output becomes the next step's input, so by the time the plan reaches the executive team, it's already been tested against supply capacity and priced against the P&L. The whole cycle runs on a rolling horizon of 24 months or more, repeating every month rather than resetting once a year.

For the broader definition of IBP and how it grew out of S&OP, see What Is Integrated Business Planning?

Step 1: Portfolio review

Owner: product management.

What happens: the team reviews the health of the current product lineup against the company's growth strategy: new launches moving through a stage-and-gate process, reformulations, and phase-outs of products that no longer earn their place. This step runs first because everything downstream, demand, supply, finance, needs to know what's actually being sold before it can plan around it.

What it produces: a validated portfolio plan, the "what and when" of the product roadmap, along with the revenue and resource assumptions attached to each change.

Step 2: Demand review

Owner: the senior commercial or revenue officer.

What happens: the team builds a statistical baseline from historical sales, then layers in judgment: promotions, marketing campaigns, competitive moves, and the launch timing that came out of the portfolio review. Critically, this forecast is built unconstrained, without checking yet whether supply can actually deliver it, because constraining it too early hides real capacity gaps instead of surfacing them.

What it produces: a single consensus demand plan across the rolling horizon, representing what the business believes the market will actually buy, not a target dressed up as a forecast.

Step 3: Supply review

Owner: supply chain or operations leadership.

What happens: planners test the unconstrained demand plan against manufacturing capacity, warehouse space, transport, and supplier limits. Where the numbers don't fit, this is where it shows: a shortfall gets prioritized (which orders get fulfilled first) or resolved (added shift capacity, an alternate supplier, a phased launch). What-if testing happens here too, evaluating a handful of ways to close a capacity gap before it goes further up the chain.

What it produces: a constrained operational plan, including production and inventory targets that are actually buildable, not aspirational.

Step 4: Integrated reconciliation review

Owner: the IBP process leader or a finance manager.

What happens: this is the step that turns the operational plan into a financial one. Every assumption, risk, and opportunity behind the numbers gets documented explicitly, the plan gets compared against the annual operating plan or strategic target to find gaps, and the team resolves whatever conflicts it has the authority to resolve on the spot. What's left, the decisions that need executive sign-off, get packaged into a small set of priced options rather than a wall of raw data. This packaging matters: without it, the executive review turns into a data dump instead of a decision.

What it produces: a financialized plan, a documented list of gaps and risks, and a short set of scenario options ready for the executive team.

Step 5: Management business review

Owner: the general manager or CEO.

What happens: the executive team isn't debating whose numbers are right at this point; that work already happened in the four steps before it. They're choosing between the priced options the reconciliation review surfaced: fund this launch or hold the line on cost, take the volume at that price or protect margin, accelerate this investment or wait a quarter. Management by exception governs the agenda; the team spends its time on the gaps and decisions that actually need it, not a line-by-line review of everything.

What it produces: the committed operating plan for the rolling horizon, the single set of numbers the whole business executes against until the next monthly cycle updates it.

What keeps the cycle from becoming bureaucratic

Two things. First, exception-based management: the executive review only spends time where something changed materially, not on every product and customer every month. Second, the cycle has to connect to a faster layer underneath it.

IBP plans in aggregate, months out; it isn't built to catch a stockout happening next week. That's handled by a separate weekly process, often called S&OE, that rebalances near-term supply and demand back to the IBP commitment without pulling executives into the fix.

Without that second layer, the monthly cycle either gets ignored when a crisis hits or gets pulled into firefighting it was never designed for.

For the pillars and mechanisms that hold this cycle together, see What Are the Key Components of an IBP Process?

Where speed decides whether this cycle actually works

The design above assumes each step can move fast enough to matter. In practice, the reconciliation step is where most companies lose the most time: financializing an operational plan by hand, pulling separate demand, supply, and cost files into one P&L view, can take days, which means the executive team is often deciding on numbers that are already a week old. AI-native platforms close that gap by running the full scenario, demand through capacity constraints to P&L and cash impact, directly.

SIMCEL, for instance, prices a complete scenario in under 60 seconds, which is what lets the reconciliation and executive review steps run on the same numbers instead of numbers built days apart.

---

Curious what your own monthly cycle would look like end to end? Learn more about SIMCEL.