> 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/plans.md).

# Plans

Plans are a fundamental concept in Drivepoint. This section provides an overview of plans. Next, we wil l dive into how to use them.

A plan is a saved snapshot of your model at a moment in time, including all your assumptions, all the historical data, and all the outputs of the model. Importantly, it also contains your commentary about the plan, via its name and description (see our tips for naming plans below). Plans are one of the most powerful features of your SmartModel™️. 

An easy way think about plans is that they provide much the same functionality as a "Save As" option that you're used to with traditional documents. You give the plan a different name, just as you would the new file, and you can change the original without making changes the new one. Once you've saved a plan, it's stored safely in the cloud. The goal is that you can easily create and iterate on plans - both what-if's and rolling forecasts. Then, you can compare those plans to each other and your actual performance to better understand your business and find opportunities for growth.

### **Key Points of Understanding:**

* A plan is a point-in-time snapshot.
* Plans are the result of combining data
* Plans contains several critical pieces of information:
  1. Snapshot of the business as it currently exists (historical data)
  2. Forward picture of what the business could do given the available data and a set of assumptions;
  3. Complete record of the assumptions used to generate the plan;
  4. Your commentary about the plan and its purpose (name and description)
  5. Once saved, plans CAN be edited

### Quick links to navigate Plans: 

{% content-ref url="/pages/dS4NAOOBScDVqhmI5vRj" %}
[Saving a Plan](/navigating-the-excel-add-in/plans/saving-a-plan.md)
{% endcontent-ref %}

{% content-ref url="/pages/l68bhQ0BVESQxy8Cc1T9" %}
[Viewing saved Plans](/navigating-the-excel-add-in/plans/viewing-saved-plans.md)
{% endcontent-ref %}

{% content-ref url="/pages/JFz4BbfMIVz1VTjt45ca" %}
[Reloading saved Plans](/navigating-the-excel-add-in/plans/reloading-saved-plans.md)
{% endcontent-ref %}

{% content-ref url="/pages/n6yy4MK1SRNNH5cNUSgt" %}
[Can I edit Plans?!](/navigating-the-excel-add-in/plans/can-i-edit-plans.md)
{% endcontent-ref %}


---

# 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/plans.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.