> For the complete documentation index, see [llms.txt](https://docs.valq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valq.com/plan/driver-based-planning.md).

# Driver Based Planning

Driver Based Planning is an add-on approach to planning and budgeting apart from the conventional allocation features explained in the previous sections.

With this feature, planners explicitly identify the key business and value drivers, understand how they affect the KPIs, and then perform planning/budgeting by configuring these drivers. 

## Advantages of Driver-based Planning

1. Planners can create a transparent and defined planning/budgeting methodology that clearly explains how certain key operational drivers impact the KPIs. This simplifies your forecast model and facilitates clear communication to all the stakeholders.
2. Forecast demand, risk and opportunities over the long term. Efficient and precise forecasting is achieved by concentrating on the drivers that matter the most and getting rid of superfluous information.
3. Execute fast and flexible planning by changing key metrics in drivers and understanding the effect. You can also create multiple drivers for different periods.

Let us see the steps to configure the drivers and understand how this works in the upcoming sections.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.valq.com/plan/driver-based-planning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.