> 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/enabling-driver-based-plan.md). # Enabling Driver Based Plan You can choose to switch between the driver-based planning approach and the standard planning approach. To create a driver-based plan while adding a new plan series, check the option '**Enable Driver based Planning'** in the **Create a Plan** pop-up window.

Create a Plan with Driver based Planning — **Enable Driver Based Planning**

You can also change to a driver-based plan mid-way through your standard planning cycle by clicking the menu shown below and selecting **Driver Based Plan**.

{% hint style="warning" %} On the contrary, switching back to the **Standard Plan** from the driver-based plan deletes all the applied configurations in the series. {% endhint %} After enabling driver-based planning, the plan window looks as shown below where you can configure the driver inputs.

You can click on the arrows to collapse/expand the driver inputs configuration columns for a better view.

**Collpase/Expand the driver configuration columns**

{% hint style="info" %} Driver configuration options are available only for the leaf nodes to avoid conflicts between the top-down and bottom-up distributions. {% endhint %} Now you can [configure the drivers](/plan/driver-based-planning/configuring-driver-inputs.md) as well as perform the [standard allocations](/plan/allocation-features.md) for your plan. #### **Note:** Nodes with driver-based inputs and nodes with one or more dependencies using driver-based inputs are disabled from the standard allocations or configurations. In the below example, the *Transport Cost* node is disabled for any allocations as it already has a driver-based input (*HC* node) impacting it.

'**Transport Cost' node has a driver based input**

*Company A* and *Overall Result* nodes are also disabled for configurations as their dependency node *Transport Cost* has a driver-based input. All other nodes can be configured or allocated as required.

Subsequent driver based plans can be created newly or can be copied from existing plans. To copy the driver configurations (and the values, if required) you can select the options as shown below while creating a plan.

--- # 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/enabling-driver-based-plan.md?ask=&goal= ``` `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.