> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wizflow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Financial Plan Model

> A shared data model that carries a customer's adjustments and recommendation across chatflows and live pages

The **Financial Plan Model** is a built-in [data model](/features/data-model-editor) that holds the plan a customer is working on — the adjustments they have made, the recommendation they were given, and the products involved. Because it is stored centrally rather than inside a single chatflow's responses, the same plan can be read and updated from **several chatflows and live pages**.

<Frame caption="Reading and updating the financial plan across a flow">
  <video controls className="w-full aspect-video rounded-xl" src="https://mintcdn.com/dreamplan-d87d53ea/6qZPpNfd1MUcB5j1/resources/pr-8094-financial-plan-model.mp4?fit=max&auto=format&n=6qZPpNfd1MUcB5j1&q=85&s=6fe9af25e1748aa387c1d42a7de01056" data-path="resources/pr-8094-financial-plan-model.mp4" />
</Frame>

***

## Why This Matters

Before this model, everything a customer decided lived in the chatflow they happened to be in. A second flow — a follow-up conversation, an advisor's review, a results page — started from nothing.

<CardGroup cols={2}>
  <Card title="One plan, many flows" icon="arrows-split-up-and-left">
    A customer can start a plan in one chatflow and continue it in another without re-entering anything
  </Card>

  <Card title="Advisor and customer see the same thing" icon="users">
    The plan an advisor adjusts is the plan the customer sees on their live page
  </Card>

  <Card title="Persisted, not session-bound" icon="database">
    Stored against the customer, so it survives a closed browser or a later visit
  </Card>

  <Card title="Referenceable like any data model" icon="link">
    Its fields can be used in entity labels, live page blocks, and conditional logic
  </Card>
</CardGroup>

***

## What It Holds

The model is structured around the plan the customer is building:

* **Adjustments** — the changes the customer or advisor has made to the baseline situation
* **Recommendation** — the recommendation produced for this customer, and the figures behind it
* **Products** — the specific pension policies and mortgage products the plan points at

<Note>
  Product fields hold **product ids**, which are dynamic. Populate them from the [List Policy Products and List Mortgage Products triggers](/features/triggers-automation) rather than typing an id by hand.
</Note>

***

## Using It in a Flow

<Steps>
  <Step title="Add the model to your flow">
    Open the **Data Models** panel in the flow builder and add the financial plan model. It appears alongside your custom models.
  </Step>

  <Step title="Map values into it">
    Use the [master-detail form editor](/features/data-model-editor) to map entity responses, trigger outputs, and calculation results onto the model's fields. Hover a field's info icon to read what it expects.
  </Step>

  <Step title="Reference it elsewhere">
    Once populated, the model's fields are available as resources — in entity labels, [live page blocks](/features/live-page-builder), and [conditional logic](/features/conditional-logic-routing).
  </Step>

  <Step title="Read it back in another flow">
    A second chatflow or live page that includes the model reads the same stored plan for that customer.
  </Step>
</Steps>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Data Model Editor" icon="table-list" href="/features/data-model-editor">
    How to map values onto a data model's fields
  </Card>

  <Card title="Triggers & Automation" icon="bolt" href="/features/triggers-automation">
    The product catalogue triggers that feed the plan's product fields
  </Card>

  <Card title="Calculation" icon="calculator" href="/features/calculation">
    Where the recommendation figures come from
  </Card>

  <Card title="Live Pages" icon="browser" href="/features/live-pages">
    Presenting a customer's plan on a page
  </Card>
</CardGroup>