> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/budgets-and-forecasts/contributor/edit-values-in-a-worksheet/revert-to-the-baseline-values.md).

# Revert to the baseline values

Undo all the changes you make in a worksheet.

{% hint style="info" %}
User permission: Budgets & Forecasts
{% endhint %}

Budgets are often created using actuals from a prior period or values from another stream as the baseline. You can then edit those values for the current budget period.

If you no longer want to use an edited value, you can revert a cell, row, or selection of cells and rows to the baseline.

You might want to revert to baseline to:

* Discard all changes you and others made and return to the baseline values.
* Pick up updated values from the underlying database or stream. This is particularly useful if you based your budget on a forecast stream that has since been updated. Revert to baseline to bring the budget back in line with the updated forecast.

| Baseline values                                                                                                                                                                                                  | Edited values                                                                 |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Display in black font.                                                                                                                                                                                           | Display in blue font.                                                         |
| Don't have cell history unless they were previously edited and reverted to baseline.                                                                                                                             | Have cell history showing changes made to the cell.                           |
| Update automatically when the underlying value changes in the database. (These values can be [fixed](/budgets-and-forecasts/owner-and-administrator/fix-the-baseline-in-a-budget.md) to stop them from updating) | Don't update automatically when the underlying value changes in the database. |

{% hint style="info" %}
**Reverting a value doesn't remove its cell history.** If you revert an edited cell to baseline, its previous changes remain in the cell history.
{% endhint %}

### Revert cells to their baseline values

1. Select the cell or range of cells.
2. Use one of these methods:
   1. Right-click the selection and select **Revert to baseline**.
   2. Click the **Cell** menu > **Revert to baseline**.

<figure><img src="https://content.gitbook.com/content/aNH5UMuZXBHuAbFF7nI2/blobs/jX4wjDlKzRqhLQaA0JdZ/3467608150.png" alt="image-20240430-220323.png" width="985"><figcaption></figcaption></figure>

### Revert rows to their baseline values

1. Select the row or range of rows,.
2. Use one of these methods:
   1. Right-click the selection and select **Revert to baseline**.
   2. Click the **Row** menu > **Revert to baseline**.

<div align="left"><figure><img src="https://content.gitbook.com/content/aNH5UMuZXBHuAbFF7nI2/blobs/KfNap6DlDZFOS6LBmRUN/3467706372.png" alt="image-20240430-214736.png" width="295"><figcaption></figcaption></figure></div>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.phocassoftware.com/budgets-and-forecasts/contributor/edit-values-in-a-worksheet/revert-to-the-baseline-values.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
