In This Article

Overview

Enable Edit Mode

Modify Existing Nodes

Add New Nodes

Node Types

Modify Hierarchy and Structure

Update Calculation Logic

Best Practices

What Happens Next

Next Steps

Overview

Once a Value Driver Tree has been created and populated with KPI data, you may need to refine its structure, update calculations, or adjust how drivers are organised. This article explains how to edit a Value Driver Tree, modify nodes, and restructure hierarchy and logic.


Editing a Value Driver Tree allows you to adapt the model as requirements change, without rebuilding it from scratch.

Enable Edit Mode

All structural changes to a Value Driver Tree are performed in Edit Mode.


To enable Edit Mode:

  1. Open the Value Driver Tree
  2. Select the edit slider in the toolbar

When Edit Mode is enabled, you can add, edit, move, and remove nodes within the tree.

Modify Existing Nodes

You can edit any node in the Value Driver Tree to update its configuration.


To edit a node:


  1. Ensure Edit Mode is enabled
  2. Select the edit (pencil) icon on the node
  3. Update the required fields, such as:
    • Node name
    • Expected trend
    • Decimal display
    • Calculation expression (for parent nodes)
    • Comments or notes
  4. Save the changes

You can drag and drop a node to connect to a different parent node.


Changes to a node take effect immediately and may impact calculations higher up the tree.


Add New Nodes

You can extend the Value Driver Tree by adding new nodes at any point.


To add a node:

  1. Enable Edit Mode
  2. Select the + icon on the parent node
  3. Choose the appropriate node type
  4. Configure the node settings
  5. Click Save

The new node becomes part of the tree structure and can be used in calculations.

Node Types

Value Driver Trees support multiple node types, each serving a different purpose. Selecting the correct node type is important for maintaining a clear and maintainable model.


  • Parent (Calculation) Nodes
    • Parent nodes aggregate and calculate values from their child nodes using a defined formula. They do not contain original data and rely on child nodes for inputs.
  • KPI Nodes
    • KPI nodes link a KPI into the Value Driver Tree. They provide numerical values (Actual, Target, Baseline) and typically sit at the lowest level of the tree.
  • Constant Nodes
    • Constant nodes hold fixed values that do not change over time. These are often used for assumptions or static inputs.
  • Reference Nodes
    • Reference nodes reuse the value of another node within the same Value Driver Tree. They allow the same metric to be used in multiple calculations without duplication.
  • VDT Nodes
    • VDT nodes represent imported Value Driver Tree structures. They allow entire subtrees to be reused within a larger model.

Each node type behaves differently and should be used intentionally to keep calculations transparent.


Modify Hierarchy and Structure

You can change the hierarchy of a Value Driver Tree to better reflect business logic.


Common structural changes include:

  • Moving nodes to a different parent
  • Reordering drivers within the same level
  • Adding or removing layers of detail

When restructuring:

  • Ensure calculation expressions are updated to reflect new child nodes
  • Validate results after changes to confirm calculations remain correct

Update Calculation Logic

Parent nodes use expressions to define how child node values are combined.


When updating calculation logic:

  • Use node references (A, B, C, etc.) consistently
  • Ensure each referenced node exists and is correctly ordered
  • Test changes by reviewing calculated results at higher levels

Calculation changes affect all downstream results and should be reviewed carefully.

Best Practices

  • Keep calculation logic in the Value Driver Tree where possible, rather than in KPIs
  • Use clear, descriptive node names
  • Limit the use of reference nodes to avoid hidden dependencies
  • Validate calculations after structural changes
  • Avoid unnecessary complexity in deeply nested trees

What Happens Next

At this stage, you can:

  • Continue refining the Value Driver Tree structure
  • Reuse or extend existing models
  • Store updated Value Driver Trees in the library for reuse

In the next article, we will cover how to import KPIs and data into a Value Driver Tree.

Next Steps

To learn how to import KPIs and data into your Value Driver Tree, see:

  • Importing KPIs and Data into a Value Driver Tree