Appendix: The FP&A Operating Model
An optional appendix on the planning model. Why an operating plan is a structured hypothesis rather than a prediction; building revenue from drivers (units times price) and tying cost to revenue so operating income falls out; sensitivity and scenarios; and where AI builds and holds the machinery while the analyst owns the assumptions.
110 min
6
16
5
Learning Objectives
By the end of this chapter you should be able to:
- 1Define what a validated, plan-ready operating model means, and why tying revenue to its drivers and confirming operating income foots comes before any scenario narrative.
- 2Design the workflow so the deterministic arithmetic (revenue as units times price, cost tied to the cost ratio, and operating income footing) sits in a built, checkable calculation, and the model narrates only the drivers and scenarios.
- 3Assemble the minimal folder that briefs a model for operating planning, the driver-based plan itself, and anchor the build to a worked example of a validated plan.
- 4Run the red-lines check for forward-looking plan data, which is sensitive management information, and keep an AI-assisted plan inside the normal FP&A review.
- 5Validate a plan by tying revenue to units times price by segment, cost of goods sold to the cost ratio, and operating income to gross profit minus operating expenses.
- 6Recognize the failure modes of an AI-built operating plan (narrating on a plan that has not been validated, a scenario that moves the wrong input, and an assumption the model supplied without flagging it) and correct them.
- 7Reason about sensitivity and frame the plan for leadership, leading with the base case, the assumptions that move operating income the most, and the price-hold and volume-miss scenarios.
- 8Recap driver-based operating planning and the three-statement logic behind it, treating a plan as a structured hypothesis rather than a prediction, and the established best practices for the operating and cash budget, drawing on Brealey, Myers, and Allen and standard FP&A practice, before any AI is introduced.
Part One: The Operating Plan, Its Drivers, and the Plan-Ready Standard. Section 1 of 6.
Part One · The Operating Plan, Its Drivers, and the Plan-Ready Standard
The Operating Plan, Its Drivers, and the Plan-Ready Standard
Part One
The Operating Plan, Its Drivers, and the Plan-Ready Standard
Before any tool touches the plan, this part recaps the work itself: what a driver-based operating plan is, how revenue is built from units and price, how cost is tied to revenue so operating income falls out, and the three-statement logic that sits behind it. Only at the end does it note why this task suits AI assistance.
An operating plan is a structured hypothesis
You are on the FP&A team at Meridian Components, a mid-market industrial parts manufacturer, and you are building next year's operating plan. It is tempting to treat a plan as a prediction, a single number the business promises to hit. It reads better as a structured hypothesis: a set of linked assumptions about how the business will run next year, arranged so you can see how each one moves the result. Brealey, Myers, and Allen frame financial planning this way in their treatment of the operating and cash budget, where the plan is a model for testing assumptions rather than a forecast handed down whole.
The distinction is practical. A plan stated as one revenue figure leaves nothing beneath it to examine or argue with. A plan built from drivers can be pressure-tested: if you doubt the price assumption, you change it and watch operating income move. That is the whole point of building the plan from its parts rather than asserting a total.
The driver build: revenue from units times price, cost tied to revenue
Standard FP&A practice builds an operating plan from operational drivers rather than from a top-line guess. Revenue starts with units times price, segment by segment. Cost of goods sold is tied to revenue through a cost ratio, so it scales as volume scales. Operating expenses sit below the gross profit line, and operating income falls out as gross profit minus operating expenses. Nothing in the operating statement is asserted directly; each line is assembled from the drivers above it.
Meridian's plan has two segments, and the build makes the logic concrete:
- Industrial Fittings. 480,000 units at a planned $215.25 gives revenue of $103,320,000. At a 62% cost ratio, cost of goods sold is $64,058,400, leaving gross profit of $39,261,600.
- Precision Components. 432,000 units at a planned $200.00 gives revenue of $86,400,000. At a 66% cost ratio, cost of goods sold is $57,024,000, leaving gross profit of $29,376,000.
Summed, the two segments give total revenue of $189,720,000 and total gross profit of $68,637,600, a blended gross margin near 36.2%. Operating expenses of $36,046,800, about 19% of revenue, come off gross profit, so planned operating income is $32,590,800, an operating margin near 17.2%. Read the chain once and the structure is clear: each figure traces to a driver above it, and no line is a free-floating assertion.
The three-statement logic behind it
The operating plan is the top of a larger structure. Its output, operating income, does not stop at the income statement. Operating income flows down to projected net income, net income lifts retained earnings on the projected balance sheet, and the same net income is the starting line of the projected cash flow statement, where working-capital and capital-spending assumptions complete the bridge to projected cash. This is the three-statement logic: the income statement, balance sheet, and cash flow statement are linked, so a change in a revenue or margin assumption in the operating plan tends to ripple through the three statements.
This appendix stays at the operating-plan layer, the income statement built from drivers, because that is where the driver logic lives and where AI assistance is most direct. It is worth holding the fuller picture in view, though: a plan that foots at the operating-income line is the input the rest of the model depends on, so getting the driver build right is what lets the balance sheet and cash flow projection stand on something solid.
Plan-ready is a standard, and why the task suits AI
Define the finish line before any tool touches the plan. A plan-ready operating model has the arithmetic tie: revenue equals units times price by segment, cost of goods sold ties to the cost ratio, and operating income equals gross profit minus operating expenses. It carries a driver commentary that names the assumptions doing the most work, and it is stress-tested with a scenario or two rather than presented as a single certain number. It is the plan a leadership team could pressure-test, not a rough sketch.
Here is why the task suits AI assistance. The plan splits cleanly into two kinds of work. The arithmetic, multiplying units by price, applying the cost ratio, footing operating income, and reflowing the whole build when an assumption changes, is deterministic: for a given set of drivers there is one correct set of totals. The judgment, which assumptions to make, which scenarios to run, and how to frame the result for leadership, is where the analyst adds value. That split, deterministic machinery on one side and owned assumptions on the other, is what the rest of this appendix is built around.
Check Your Understanding
Knowledge Check 1
FP&A & Planning
A segment plans to sell 480,000 units at a planned price of $215.25 per unit. Building revenue from the drivers, what planned revenue does the segment produce?