Capacity Planning: Long-range plan
Objective. Read the long-range plan and explain it is a directional requirement over a long horizon whose confidence decays with distance, not a budget-locked commitment.
The long-range plan extends the capacity requirement over a multi-quarter horizon so the customer can plan hiring, budget and facilities ahead of the long lead times that in-week fixes cannot cover.
See it in the demo
What this screen answers
A Sales or CSM person opens this to answer 'what will we need months out, so we can hire and budget in time?' Hiring and training have long lead times, so capacity has to be seen far enough ahead to act. This screen projects required capacity across the long horizon against expected availability.
The task
Scope to the horizon and the client or portfolio, then read the requirement trajectory and where it diverges from available capacity. Use it to frame the hiring runway. Describe the view as 'the requirement over the long horizon', not specific labels you have not verified.
How to read it
A long-range plan is directional, and its confidence decays with horizon. The far quarters rest on forecast assumptions that are much softer than the near term. The misread is treating the out-months as a committed budget or a precise number. Read the near term as actionable and the far term as a planning signal to revisit. It is a simulation on assumptions, not an executed commitment.
Honest limits
This screen does not lock a budget or guarantee the out-year number; it must be revisited as reality moves (see capacity reviews). Forecast method and the volume assumptions behind the long horizon must be confirmed with product. Treat distant figures as a direction to plan around, not a promise.
Interpretation check
A long-range requirement is a directional simulation whose confidence falls with horizon - it is a planning signal to revisit, not a budget-locked or precise out-year number.
In the field
An RCM operator planning a new client ramp: the long-range view sets the hiring runway months ahead, while being explicit that the distant quarters are a direction to revisit, not a signed budget.
Practical task
Read the long-range trajectory for one scope and write two lines: the near-term hiring runway it implies, and a note that the out-months are directional assumptions to revisit at the next review.
Self-check
Finance wants to lock the out-year headcount from this screen. What do you flag?
The far horizon rests on softer forecast assumptions; confidence decays with distance. Use it as a directional planning signal to revisit, not a locked budget commitment.
Why does a long-range plan need a review cadence?
Because its assumptions move. A plan set once and never revisited drifts from reality; the value depends on refreshing it as volume and shrinkage actuals come in.
What is actionable now versus later on this screen?
The near term is actionable (hiring runway); the far term is a signal to plan around and revisit, not a precise commitment.
Verified vs demo. Screen is live in the demo at /#/lrplan; exact controls and figures are SME-validation-pending.