These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Financial Planning & Analysis
- Features
- Forecast drivers
Forecast drivers
Keep the units, rates and default bases used in driver forecasts clear.
OverviewActive Forecast Drivers×
Financial Planning & Analysis · Forecast drivers
New
Active Forecast Drivers
Forecast drivers
| Driver code | Driver name | Unit | Rate USD | Driver type | Default forecast basis | |
|---|---|---|---|---|---|---|
| DC-149 | Driver 429 | Subscription | 610 | Recurring | Straight line | |
| DC-922 | Driver 917 | License | 290 | One-Time | Milestone | |
| DC-121 | Driver 635 | Seat | 160 | Usage-Based | Usage | |
| DC-609 | Driver 158 | Hour | 240 | Milestone | Straight line | |
| DC-260 | Driver 196 | Day | 500 | Recurring | Milestone |
6 of 6 records
DC-149Forecast drivers · FD-51283
SubscriptionDriver nameDriver 429
Rate USD610
Driver typeRecurring
Default forecast basisStraight line
What you can do
Forecast drivers in daily work
A forecast driver holds the planning unit, rate, type, category and default forecast basis. Forecast versions reference a driver, so a planner can compare a version with the assumption used to create it. Document lines can also reference the driver.
A driver records a planning unit, rate, type, category and default basis. A version links to that driver, while a document line may refer to it for context. The driver is a shared assumption: changing its rate or unit can change how people interpret versions created at different times, so the planner should record which assumption was used.
How the work is organized
- Assumption owner. Admin maintains the driver unit, rate, type and status.
- Version selection. FP&A Planner chooses the driver and forecast basis for a dated version.
- Review trail. The team uses the driver code and version reference when discussing a changed assumption.
What to agree during setup
Agree what one unit means for each driver and which rates are current. Set the standard term where it applies, and retire a driver when it should no longer be chosen. Decide who may change a rate after versions already reference the driver.
Define what a seat, hour or support contract means for each driver and review the rate before using it in a version. Admin and FP&A Planner should agree when a driver is retired and how existing versions remain identifiable. Keep the driver code stable when moving reference data into the app.
Check the handoff on an actual case
Take a support contract driver with a rate and a recurring type. Link it to a forecast version for a defined term, then inspect the amount and actual-to-date value. If the forecast is questioned, the reviewer can return to the driver definition rather than guessing what one unit represented.
Admin opens a Support Contract driver with a recurring type and checks its rate and default basis. FP&A Planner links it to a dated version for a partner and compares the forecast amount with actual to date. If the team later changes the driver rate, the planner checks both the version reference and the driver definition before comparing terms.
What your team sees
- Active Forecast Drivers — Shows the current driver code, unit, rate and default basis.
- Active Forecast Versions — Shows versions that use the planning assumptions under review.
Follow the work through
See the related process for the operating sequence. Use the data model to check references before importing records and roles to agree who can act.
What it keeps track of
Data model- Forecast drivers
- Driver catalogue used to build driver-based forecasts: driver name, unit, rate, driver type, default forecast basis and category.
- Forecast versions
- Versioned forecast records phased across a planning term, linked to a business partner and a forecast driver, carrying forecast amount, actual-to-date, unforecast balance and percent actual.
- Document lines
- Line-level detail behind each accounting document, linked to a forecast driver and forecast version.
Who uses it
Permissions- Admin
- Maintains driver definitions and status.
- FP&A Planner
- Checks each driver before using it in a forecast version.
- Finance Leader
- Reviews the resulting forecast amounts.
Set up Financial Planning & Analysis your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.