> 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/user-guide/3-create-your-first-planning-app/3-4-create-a-forecast.md).

# 3.4 - Create a forecast

This article explains how to create a forecast in a planning sheet and enter forecast values for open periods.

### Create a new forecast

1. Go to the **Model** ribbon.

<figure><img src="/files/e21vm7R2uWbwg1v192qm" alt=""><figcaption></figcaption></figure>

2. Select **Forecast**.

<figure><img src="/files/8lj4OJLVReY8kWJQntBX" alt=""><figcaption></figcaption></figure>

3. Configure the forecast settings:

* **Measure Name**: Enter a name for the forecast measure.
* **Forecast Period**: Select the forecast period.
* **Closed Period** and **Open Period**: Configure data for closed and open periods.

Consider this example where,

* Closed periods are configured to use the *Revenue* values.
* Open periods use the **Data Input** option without any default values configured.

4. Select **Create**.

<figure><img src="/files/8ZOd7m2aSGIAsvufvjqr" alt=""><figcaption></figcaption></figure>

5. You can optionally configure a baseline source for forecast data.

To create a zero-based forecast, leave **Copy Source** empty by setting it to *None*. To use existing data as a baseline, select a source and then choose **Save**.

<figure><img src="/files/K9zA2oB4ahkzBAVDfJuT" alt=""><figcaption></figcaption></figure>

6. After the forecast is created:

* Closed periods appear in gray and display values from the linked measure (for example, *Revenue*).
* Open forecast periods remain blank since **Data Input** is selected without a default value (Default value: *None*).

<figure><img src="/files/mR3dNMNXK2vyoOAkOjyR" alt=""><figcaption></figcaption></figure>

### Enter forecast values

1. Double-click the cell for the open period that you want to edit.

<figure><img src="/files/3dUdlh6lZw3NNYsbgEVL" alt=""><figcaption></figcaption></figure>

2. Enter a value in the formula bar and press **Enter**.

<figure><img src="/files/vquTydoGqnPKo9WznbtC" alt=""><figcaption></figcaption></figure>

3. By default, forecast values are distributed equally across row and column hierarchies and aggregated to totals.

<figure><img src="/files/8Oq1mGMVYnFIzxE462Iy" alt=""><figcaption></figcaption></figure>

### Distribute forecast values

1. To apply a different distribution method, select a cell and open the **Distribution** menu.

   You can distribute the values by:

   * Trend
   * Weights from an existing series

<figure><img src="/files/cgGFaufucg0eODRmTyYM" alt=""><figcaption></figcaption></figure>

2. In this example, the *2026 Forecast* values are distributed using the weights from *2025 Actuals*.

<figure><img src="/files/uVJ8gqd5O3V7NJJ5vNpi" alt=""><figcaption></figcaption></figure>

3. The forecast values are updated based on the selected distribution method.

<figure><img src="/files/HqPeXccow60XkfvbSalh" alt=""><figcaption></figcaption></figure>

### Related content

To learn more about forecasts, automated period close, and extending time periods, see tutorial [4- Forecasts, rolling forecasts & statistical forecasts](/user-guide/6-forecasts-rolling-forecasts-and-statistical-forecasts.md).


---

# 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/user-guide/3-create-your-first-planning-app/3-4-create-a-forecast.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.
