> 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.