> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/navigating-the-excel-add-in/model-roll-forward/help-i-accidentally-rolled-forward.md).

# Help! I accidentally rolled forward?!

No worries - we know it happens.

## Option 1: Select an older version in Excel History

1. In Excel, click on "File"
2. Click on "Info"
3. Click on "Version History"
4. Select the previous or an older version of your SmartModel™

If there was a significant time delay or other team members have already made significant changes to the SmartModel™, you are also able to roll back your model. Click on the links below to learn more.

## **Option 2: Roll Model Back**

1. Open the Drivepoint Add-In
2. Click on "Roll Model Forward"
3. Click on "Roll Back" on the bottom of the screen
4. Select the date you would like to roll the model back to
   1. *💡 The date of current actuals is highlighted. You will need to select a PREVIOUS month to roll back actuals to forecasts.* 
5. Click "Model Roll Back"
6. View all selected tabs of your model by default
   1. *💡 Partial roll back: only select the tabs you want to roll back specifically*
7. Click "Roll Model Back"
8. Your model will now get rolled back


---

# 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.drivepoint.io/navigating-the-excel-add-in/model-roll-forward/help-i-accidentally-rolled-forward.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.