# Model Templates

This article explains how **model templates** work in Model Reef.

You will learn:

* What a model template is.
* How to create templates from existing models.
* How to use templates to enforce structure and speed up new builds.

Templates help ensure consistency across models and reduce setup time.

***

## What a model template is

A model template is a normal Model Reef model that you treat as a reusable starting point.

Templates usually contain:

* Branch structures for entities, divisions or projects.
* Preconfigured categories and subcategories.
* Variable stubs or example variables for common lines.
* Standard dashboards and charts.
* Standard reports such as P\&L, Balance Sheet, Cash Waterfall and key KPIs.
* Optional opening assumptions that you plan to overwrite in new models.

When you use a template, you normally duplicate it and then customise the copy.

***

## Creating a template from an existing model

{% stepper %}
{% step %}

### Build or open a model with the desired structure

Start from a model that already includes the branches, categories, reports and dashboards you want to reuse.
{% endstep %}

{% step %}

### Remove client- or project-specific data

Clean out sensitive or specific items before turning the model into a template, for example:

* Remove or anonymise live actuals.
* Reset or simplify assumptions.
* Remove sensitive attachments.
  {% endstep %}

{% step %}

### Save or label the model as a template

Organise or name the model so it’s clear it’s a template, for example:

* Move it into a `Templates` folder.
* Name it `Template - [use case]`, such as `Template - SaaS Model`.
  {% endstep %}
  {% endstepper %}

You now have a template ready for reuse.

***

## Using a template to create a new model

{% stepper %}
{% step %}

### Duplicate the template

Duplicate the template model in the workspace to create a working copy.
{% endstep %}

{% step %}

### Rename the copy

Rename the duplicated model for the specific client, entity or project.
{% endstep %}

{% step %}

### Update the copy for the new use case

Adjust the working copy to reflect the new client or project:

* Update branch names to match the real structure.
* Import or update opening balances and actuals.
* Update key driver assumptions and variables.
* Create or adjust scenario versions if needed.
  {% endstep %}
  {% endstepper %}

All dashboards, reports and valuation settings come across with the template, so you avoid rebuilding them from scratch.

***

## Managing a library of templates

Over time you may build a library of templates, for example:

* `Template - 3 Statement Group Model`
* `Template - SaaS Unit Economics`
* `Template - Retail Multi Site`
* `Template - LBO`
* `Template - Project Finance`

To keep templates useful:

* Review them periodically and update for new best practice.
* Remove or archive templates that are no longer used.
* Align naming conventions and documentation across templates.

Good templates accelerate new work and keep structures consistent across the workspace.

***

## Templates and permissions

Templates behave like normal models for permissions:

* Owners decide who can see and use templates.
* Editors can create new models by duplicating templates.
* Viewers can inspect template structures but cannot change them.

You might keep templates restricted to a core modelling team if they are complex.

***

## Related articles

* [Capacity & Production Planning](/use-cases/manufacturing-and-production/capacity-and-production-planning.md)
* [Build Cross Branch Drivers & Dependencies](/how-tos/data-workflows-and-automation/build-cross-branch-drivers-and-dependencies.md)
* [Variable Overview](/help/drivers-variables-and-timing/variable-overview.md)
* [Manual Time Series Editing](/syntax/variables-syntax/manual-time-series-editing.md)


---

# 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://help.modelreef.io/help/workspace-and-organisation/model-templates.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.