> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/features/future-state-repository.md).

# Future State Repository

Plan records that do not exist yet, explore alternative futures in scenarios, and make a plan real when it is ready.

The Future State Repository holds the parts of your landscape that do not exist yet. A planned application, a new interface or a future organizational unit can be modeled as a real, named record and placed on roadmaps and maps next to what exists today. Your live data stays a clean record of the present.

## What it is

| Concept                                                                                                | What it means                                                                                                               |
| ------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- |
| **Current state**                                                                                      | The records that exist today in ServiceNow.                                                                                 |
| **Future state**                                                                                       | Planned records that do not exist yet. They are kept apart from the live data and marked as future on their form.           |
| [Scenario](https://docs.ins-pi.com/command/the-portal/content-types.md#scenario)                       | One possible future: which records are added, modified, removed or kept, with target dates and what-if values for measures. |
| [Scenario Comparison](https://docs.ins-pi.com/command/the-portal/content-types.md#scenario-comparison) | Several scenarios side by side, on cost, risk, benefit and rating.                                                          |

## When to use it

* You plan a new application or replacement and want to show it on a roadmap before it is built.
* You weigh two or three options for the future landscape and need to compare them.
* You want to plan a retirement without changing the live record.

## How to

### Create a future record

1. Open the [Data Hub](https://docs.ins-pi.com/command/the-portal/data-hub.md#create-a-future-state-record) and choose a table.
2. In the **Future state** section, click **New**. A form opens for the planned record.
3. Fill it in and save it. If planning is not switched on for this record type, Command says *Not saved: Planning is not enabled for …* and nothing is kept.
4. Drag it onto a roadmap or a map next to current records.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-f82b530356f347d6279de0f7ef135fb22b940bd6%2Fcommand-datahub-open.png?alt=media" alt="The Data Hub with the Current state and Future state sections and the New button for adding a future state record."><figcaption><p>Future state records sit under their own section in the Data Hub</p></figcaption></figure>

To drop a planned record you no longer need, use **Delete** on its row and confirm **Abandon**. This retires the planned record and removes it from the view.

### Make a planned record real

When a plan is ready, you can turn it into a real record in your live data. Your administrator decides, for each record type, whether you do this yourself or ask for approval first.

1. Open the planned record's form and save any changes. Only the saved plan is used.
2. Under the note saying what the plan is about, read what you can do:
   * **Make current** appears when you can create this kind of record yourself.
   * **Request approval** appears when this kind of record needs an approver's agreement first.
   * When neither appears, the note says why, for example that you cannot create this kind of record.
3. Click **Make current**. The confirmation, **Make this plan current?**, says whether it will create a new record or update an existing one.
4. For a plan that creates a new record, check its status in the confirmation. Command keeps the status the plan already has or, without one, suggests one from the plan's current lifecycle phase and says so under the field. A plan whose phase has not reached operation is never suggested as in production. Choose another status if it fits better.
5. Confirm. The plan becomes a real record, with its lifecycle phases, measures and the chosen status, and the form links to it.

To ask for approval instead:

1. Click **Request approval**.
2. Optionally, say why in **Why (optional)**. Your approver sees it.
3. Click **Request approval**. The form shows that approval was requested, by whom and when.

When the approver agrees, the plan becomes a real record. They decide in **My Tasks**, like any other approval (see [Tasks, Notifications and Approvals](https://docs.ins-pi.com/command/the-portal/tasks-and-notifications.md#approvals)).

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-ab8fdb95b47930143057ea2d92bf8fd00bc2b69e%2Fcommand-future-state-make-current.png?alt=media" alt="The form of a planned Business Application, with a note saying the plan creates a new record and a Make current button beside it."><figcaption><p>Making a planned record current</p></figcaption></figure>

{% hint style="warning" %}
Making a plan current creates or updates a real record. It cannot be undone from the portal.
{% endhint %}

### Show current, future or both

On a Table or a Roadmap, use the **State** filter: **Current**, **Future** or **Both**.

### Work in a scenario

1. Create a **Scenario** and add records to it.
2. Mark each record as added, modified, removed or kept, and give it a **Target date**, for example a decommission date.
3. Set what-if values for measures on a record. They apply in this scenario only.
4. Read the summary cards: **Cost (TCO)**, **Risk**, **Benefit** and **Rating**.
5. Move the scenario through its status: **Draft**, **Under review**, **Approved**, **Active**, **Archived**.

### Compare scenarios

1. Create a **Scenario Comparison**.
2. Click **Add scenario** and pick from **Scenarios in My Space**, or drag scenarios onto it from My Space.
3. Compare **Cost (TCO)**, **Risk**, **Benefit**, **Rating** and the records each one adds, shares or keeps unique. The strongest option is marked **★ Recommended**.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-dee729e46c24867025dd4c514f655c44f4117638%2Fcommand-scenario-comparison.png?alt=media" alt="A Scenario Comparison with three scenarios side by side, their cost, risk, benefit and rating, and one marked Recommended."><figcaption><p>Three scenarios compared</p></figcaption></figure>

## Good to know

* Planning never overwrites a live record until you make a plan current. Removing a record in a scenario retires it only inside that scenario.
* A plan about an existing record updates that record when it is made current. A plan about a new record creates one.
* If a plan replaces another record, the form suggests what to do with the old one after the plan is made current, for example *Consider retiring Legacy App*. Nothing is changed on the old record for you.
* If an approver rejects the request, the plan stays planned and you can ask again. The form tells you the last request was rejected.
* If a request was approved but the plan could not be made current, the form says so, and you can try again.
* After a plan is made current, a Roadmap shows the live record it became. **Open record** on a planned Roadmap row opens the plan's form, with **Make current**.
* An **Archived** scenario is read-only and is never marked **Recommended**. Change its status to edit it.
* Whether a record type needs approval is set in [Global Settings](https://docs.ins-pi.com/command/administration/global-settings.md#choose-how-planned-records-become-real).
* A draft scenario needs to be activated before it is scored in a comparison.
* [Data Governance](https://docs.ins-pi.com/command/features/data-governance.md) can check the quality of planned data in a scenario.
* Measures, Lifecycle and Roadmaps all work with future records, so the plan uses the same views as the present.
* Committing a whole scenario to the live data is not available from the portal yet. You make plans real one record at a time.

## Related

* [Lifecycle](https://docs.ins-pi.com/command/features/lifecycle.md)
* [Measures](https://docs.ins-pi.com/command/features/measures.md)
* [Data Hub](https://docs.ins-pi.com/command/the-portal/data-hub.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 by asking a question.

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

```
GET https://docs.ins-pi.com/command/features/future-state-repository.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.
