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

# Lifecycle

Track where each record is in its life, from planning to retirement, with dated phases and milestones you can see on forms, roadmaps, tables and dashboards.

Lifecycle tracks how a record moves through its phases over time. It answers a simple question on every record: where is this today, and where is it planned to go next. The same dates drive the record's form, the Roadmap, Table columns and filters, and the Dashboard **Lifecycle summary** widget.

## What it is

A lifecycle is a set of dated phases, optionally grouped into stages, plus milestones. A record sits in one phase at a time and moves on when the next phase starts.

| Concept                | What it means                                                                                                                                                                                               |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Phase**              | A period in the record's life, such as Evaluate, Operate or Retire. It has a **Start** and, optionally, an **End**. Only the last phase may be left open; it stays open until a later phase follows it.     |
| **Stage**              | A group of phases, for example Initialization, Productive, Expiration and Non-Productive.                                                                                                                   |
| **Milestone**          | A dated event on a record, such as a vendor end of support or a planned review. It has a **Type**, a **Date** and a **Status**: **Proposed**, **Approved**, **In progress**, **Completed** or **Canceled**. |
| **Several lifecycles** | One record can carry more than one lifecycle side by side, for example internal and manufacturer, so you can compare them.                                                                                  |
| **Scope**              | The same record can follow a different timeline per business unit or region, which matters for matrix organizations.                                                                                        |

The phases of one lifecycle form a continuous *band*: no gaps and no overlaps. Each phase ends on the day the next one starts, and Command keeps it that way as you edit. See [Lifecycle Stages & Phases](https://docs.ins-pi.com/command/reference/lifecycle-stages-phases.md) for the default stages and phases.

## When to use it

* You need to know which applications are in production, being phased out or already retired.
* You plan a retirement or a replacement and want the dates visible to everyone.
* You want to catch records that run past an approved end date.
* You want to report how a portfolio is spread across its phases.

## How to

### See a record's lifecycle

1. Open the record as a [Form](https://docs.ins-pi.com/command/the-portal/content-types.md#form).
2. Read the **Lifecycle** tile at the top. It shows the current phase, and chips for how well the lifecycles align and the risk in the next 12 months.
3. Click the tile to jump to the **Lifecycle timeline** section of the form.

When the record is outside its phases, the tile reads **Ended** or **Not started**, then names the last or first phase and its date, for example *Last phase Retire, ended March 1, 2026*.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-c996608e1023751312c15d9780d462c265653c9e%2Fcommand-form-lifecycle.png?alt=media" alt="A business application Form with the Lifecycle tile at the top and the Lifecycle section showing the internal and manufacturer lifecycle bars on a timeline."><figcaption><p>The Lifecycle tile and the Lifecycle section of a Form</p></figcaption></figure>

### Add or change phases and milestones on a record

1. On the Form, click **Edit**. You need the Command editor role; without it the timeline stays read-only.
2. In the **Lifecycle timeline** section, open the **⋯** menu or click the **+** on a band, and choose **Add phase…**, **Add scope…** or **Add milestone…**. A record with no lifecycle yet shows **+ Add lifecycle**.
3. For a phase, pick the **Phase** and set its **Start** and, if known, its **End**, then click **Add**. Command shows how the neighboring phases change, for example *Continues from Operate, which will end on March 1*. For a milestone, set the **Type**, **Date**, **Status** and the lifecycle it belongs to.
4. Click **Save** on the Form. If the change needs approval, Command says it was sent for approval instead of saved.

In edit mode, a **+** also sits before each phase on the band (**Add a phase before …**). Click it to add a phase in that place.

To change a phase's dates, click its bar in edit mode, change **Start** or **End** in **Edit dates**, and click **Apply**. You can also drag a bar's edge: it snaps to the axis, and holding **Shift** gives day precision. Moving one edge moves the neighboring phase's edge with it. **Remove** deletes a phase; the phase before it takes over its time.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-9b93b5587b489bf707fd375a20271db73b1e5904%2Fcommand-lifecycle-edit-dates.gif?alt=media" alt="The end of the Active phase is dragged later on a Form&#x27;s lifecycle timeline, and the Expiring phase starts at the new boundary."><figcaption><p>Move a phase's dates</p></figcaption></figure>

### Read a portfolio on a Roadmap

1. Create a [Roadmap](https://docs.ins-pi.com/command/the-portal/content-types.md#roadmap) and drag records onto it from the Data Hub or My Space.
2. In the **View** row, choose which **Lifecycle** to show, the **Scope**, and **Group by** **None**, **Table** or **Collection**.
3. Under **Timeline**, set the **Date range**, pick a window preset or change the **Axis** from days to decades.
4. Under **Layout**, switch **Grid lines**, **All disposition colors**, **Show no-lifecycle records** and **Conflicts** on or off. A conflict is a record that runs past the end of its approved lifecycle.
5. Switch on **Edit** to change dates directly on the bars, then click **Save**. The number on the button counts the unsaved changes. Editing needs the Command editor role. Once every change is saved, the Roadmap returns to its read view.

Decisions recorded about a record, such as *Replace*, appear on its row at their due date, and the **Legend** names them. See [Decisions](https://docs.ins-pi.com/command/features/decisions.md).

While you drag a bar or a milestone, nothing changes yet: the count on **Save** rises only when you let go, and a bar released where it started adds no change. If you undo while the milestone confirmation is open, the milestone goes back and the confirmation closes.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-9691bdb6ab52ad85452c50674c3beb23d1564e62%2Fcommand-content-roadmap.png?alt=media" alt="A Roadmap with phase bars colored by stage, the today marker and the at-risk count in the header."><figcaption><p>Lifecycle phases on a Roadmap</p></figcaption></figure>

### Add lifecycle columns and filters to a Table

1. In a [Table](https://docs.ins-pi.com/command/the-portal/content-types.md#table), open **Columns** and choose the **Lifecycles** category.
2. Add the current phase, or **Stage**, **Phase start**, **Phase end**, **Terminal** or **Next milestone date**.
3. Filter on any of these. To find records a lifecycle does not cover yet, filter on the lifecycle with **is not tracked**.

### Summarize a portfolio on a Dashboard

Add the **Lifecycle phases** widget to a [Dashboard](https://docs.ins-pi.com/command/features/dashboards.md) to see how many records sit in each current phase.

## Good to know

* Phase names that do not fit a short bar are cut with an ellipsis. Hover to read the full name.
* Command refuses a change that would leave a gap or an overlap, or put a phase after one that ends the lifecycle, and says why, for example *Start by May 1, when Operate ends, or the band has a gap.*
* ServiceNow's *Life Cycle Stage* fields are shown as *Lifecycle Stage* throughout Command.
* If your organization has an approval policy for phase changes, every new phase and every date change waits for approval in the approver's **My Tasks**; a change to notes only saves right away. One change per phase waits at a time. See [Tasks, Notifications and Approvals](https://docs.ins-pi.com/command/the-portal/tasks-and-notifications.md).
* A [Scenario](https://docs.ins-pi.com/command/the-portal/content-types.md#scenario) can retire a record with a target date inside that scenario only, without touching the live lifecycle.
* Administrators define lifecycles, stages, types, scopes and milestone types in **Global Settings > Lifecycle & Milestones**, and approval policies in **Global Settings > Approvals**.
* A change waiting for approval is drawn on the band as a **Waiting for approval** bar. Point at it to see the phase, its dates, who raised it and when, and who still has to approve it.
* In a Form's **Extended view**, the lifecycle section draws every lifecycle at full size.

{% hint style="info" %}
**Is not tracked** cannot yet be combined with another condition on the same lifecycle.
{% endhint %}

## Related

* [Measures](https://docs.ins-pi.com/command/features/measures.md)
* [Future State Repository](https://docs.ins-pi.com/command/features/future-state-repository.md)
* [Decisions](https://docs.ins-pi.com/command/features/decisions.md)
* [Command Dialog](https://docs.ins-pi.com/command/features/command-dialog.md): ask, for example, `create a market lifecycle with phases idea, launch, growth, retire for products`.


---

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