Long-Term Plan · Short-Term Plan · Production Plan · Demand Forecast ·
Revenue & Cost Models · Budget Allocation · Capacity Plan · Performance to Plan
Plans aren’t static. More context becomes available as execution gets closer. Each horizon can adjust, respond and stretch performance – while staying connected to the plan above.
| Jan | Feb | Mar | Q1 | |
|---|---|---|---|---|
| Ore mined (t) | 548,310 | 510,710 | 517,654 | 1,576,674 |
| Waste mined (t) | 772,685 | 785,977 | 760,863 | 2,319,525 |
| Truck hours | 8,625 | 8,442 | 8,430 | 25,497 |
| t / truck hour | 153.2 | 153.6 | 151.7 | 152.8 |
VLOOKUP reference is broken.Start with a standard structure or configure your own. PlanCascade supports the horizons your business actually uses.
Name it. Set its duration and grain. Place it anywhere in the cascade.
Every plan carries its version, ownership, permissions, approval state and definitions with it.
One live plan. Previous versions remain traceable.
Permissions and approvals follow the business hierarchy.
Every change records who, what, when and against which version.
Definitions and calculations are governed once and used throughout the cascade.
Getting started is easy. Import the plans you already use, keep your existing KPI names, or start with industry-standard definitions. You don't have to rebuild your planning process from scratch.