# 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.

<figure><img src="/files/RkcTWvRj0OcPTHcXWj7y" alt="Create a Plan with Driver based Planning" width="563"><figcaption><p><strong>Enable Driver Based Planning</strong></p></figcaption></figure>

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**.

<figure><img src="/files/enh7QeyKdPD2AxFurTRJ" alt=""><figcaption><p><strong>Choose 'Driver Based Plan'</strong></p></figcaption></figure>

{% 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.&#x20;
{% endhint %}

After enabling driver-based planning, the plan window looks as shown below where you can configure the driver inputs.

<figure><img src="/files/OgstsKJz7eyZ6SLD24X7" alt=""><figcaption><p><strong>Driver Based Plan</strong></p></figcaption></figure>

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

<figure><img src="/files/iEsdwde1YxotLycetFf1" alt=""><figcaption><p><strong>Collpase/Expand the driver configuration columns</strong></p></figcaption></figure>

{% 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.

<figure><img src="/files/8L44eZa6WQQHDsu6gqpk" alt=""><figcaption><p>'<strong>Transport Cost' node has a driver based input</strong> </p></figcaption></figure>

*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.

<figure><img src="/files/7DOhYxUm4xMBZsb1bTIL" alt=""><figcaption><p><strong>Configuration disabled</strong> </p></figcaption></figure>

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.

<figure><img src="/files/rkWtsMJXcLI7N2Oy1tvX" alt="" width="563"><figcaption><p><strong>Copy a Driver Based Configuration</strong></p></figcaption></figure>


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.