> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/planning-sheets/concepts/measure-and-row-based-planning/row-model-the-agile-driver-framework.md).

# Row model - the agile driver framework

### Row Model Concept for Driver-Based Planning

Row model is planning's agile driver framework for building driver-based planning models. It transforms the rows in a planning sheet into dynamic planning elements called **drivers**. Instead of depending on a complex semantic model or prebuilt measures, a row model lets you build planning logic directly in the planning layer.

A row model uses a single row hierarchy, where each member in the hierarchy becomes a potential driver. Typical row hierarchies include:

* Country/Region
* Cost Center
* Chart of Accounts
* Product

{% hint style="info" %}

### Note

**Key concept:** Every row is a potential driver.
{% endhint %}

Each driver can represent an input, calculation, subtotal, or business outcome. You define relationships between rows by using formulas and aggregations to create a connected planning model.

### How a row model works

A row model starts with a row hierarchy that represents the planning dimension. Every member in that hierarchy becomes a planning driver.

For example, a single row hierarchy can contain the following rows:

* Goods Sold
* Cost
* Net Profit

Each row acts as an individual driver. You can define formulas and relationships between these rows so that changes to one driver automatically update the related business outcomes. The row hierarchy is usually evaluated across planning versions (such as **Actual** and **Forecast**), business KPIs, and other scalar measures.

Unlike traditional spreadsheet models that distribute formulas across multiple cells, a row model organizes planning logic into a connected hierarchy of rows, making it easier to maintain and extend.

### When to use a row model

Use a row model when your organization uses lightweight semantic models, such as flat tables, star schemas, or row transactional views, but needs sophisticated planning logic.

Because the planning logic resides in the planning layer, you don't need a complex semantic model or numerous calculated measures in the underlying database.

### Benefits of a row model

A row model provides the following benefits:

* **Rapid deployment** by building planning logic without requiring a complex semantic model.
* **Every row becomes a planning driver**, enabling detailed driver-based planning directly within the planning sheet.
* **Business-user ownership**, allowing finance and operational teams to add new planning drivers by simply adding new members to the hierarchy instead of waiting for IT changes.
* **Flexible planning**, enabling simple source data to be transformed into sophisticated planning models.
* **Centralized business logic**, making models easier to understand, maintain, and extend.
* **Scenario planning**, allowing you to evaluate different business outcomes by changing driver values.

### Common use cases

Use row models for the following use cases:

* Financial planning and analysis (FP\&A)
* Profit and loss (P\&L) planning
* Budgeting and forecasting
* Sales planning
* Headcount planning
* Supply chain planning
* Operations planning


---

# 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.fabricplan.com/planning-sheets/concepts/measure-and-row-based-planning/row-model-the-agile-driver-framework.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.