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

# Decisions

Record what should happen to an application or other record, such as invest, retire or replace, approve or reject it, put it to a governance body, and see it on the roadmap.

A decision records what should happen to a record, such as *Invest* in an application or *Replace* it, with the reason why. Decisions come out of a TIME Analysis or an R-Analysis, or are recorded straight on a record's Form. Each one moves from proposed to approved or rejected, and shows on the roadmap at its due date.

## What it is

Every decision belongs to a *family* and uses one *framework*:

| Family          | Comes from                                                                                 | Choices                                                                |
| --------------- | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------- |
| **Disposition** | [TIME Analysis](https://docs.ins-pi.com/command/the-portal/content-types.md#time-analysis) | Tolerate, Invest, Migrate, Eliminate                                   |
| **Migration**   | [R-Analysis](https://docs.ins-pi.com/command/the-portal/content-types.md#r-analysis)       | The choices of the R framework used, such as Retain, Replace or Retire |

A record can have one standing decision per family. Recording a new one supersedes the old one without erasing it: the history keeps every decision and its reason.

| Status                      | Means                                                                  |
| --------------------------- | ---------------------------------------------------------------------- |
| **Proposed**                | Recorded, waiting for a decision.                                      |
| **In governance**           | Sent to a governance body as part of a proposal.                       |
| **Approved** / **Rejected** | Decided, by a governance body or by someone allowed to decide for one. |
| **Executed** / **Verified** | Carried out, and confirmed.                                            |
| **Superseded**              | Replaced by a newer decision.                                          |

Recording a decision never changes the record itself.

## How to

### Record a decision

1. In a TIME Analysis or R-Analysis, click a record, or choose **Decide…** in its row. On a Form, click **Record a decision…** in the **Decisions** section.
2. Pick a choice. Command shows the suggested one, and asks for a reason when you choose another.
3. Enter a **Reason**, and optionally a **Due** date and a **Successor** (for choices such as Replace).
4. Click **Record decision**. It is saved as **Proposed**.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-3721a4da349fa360e301c2507670d4795b355ef8%2Fcommand-decisions-drawer.png?alt=media" alt="The decide drawer of an R-Analysis, with Replace chosen, a reason, a due date and a successor filled in."><figcaption><p>Record a decision</p></figcaption></figure>

### Send decisions to governance

1. In a TIME Analysis or R-Analysis, click **Send to governance**. On a Form or in the decision log, use **Send to governance…** on a proposed decision.
2. A new governance proposal opens, filled with the decisions. Check it and save it.

The decisions move to **In governance**, and the body's outcome sets their status. See [Architecture Governance](https://docs.ins-pi.com/command/features/architecture-governance.md).

### Approve or reject decisions

1. Choose **Approve…** or **Reject…** on a decision, in the decide drawer, the Form's **Decisions** section or the decision log.
2. Choose the **Governance body** you decide for, and add a comment. A rejection needs one.
3. Click **Approve** or **Reject**.

You can decide for a body if you are a Command administrator, the body's chair, or a member of its group. Otherwise, send the decisions to governance instead.

### Review all decisions

Open **Governance** in the activity rail and choose **Decision log**. It lists every decision with its record, status, dates and body. Switch on **Group by table**, and select several decisions to approve, reject or send them to governance together.

## Good to know

* The **Roadmap** draws every standing decision on its record's row, as a marker in the choice's color at its due date. A decision without a due date sits at the day it was decided, drawn lighter. Rejected decisions are muted; superseded ones are hidden.
* To show the **Decisions** section on a Form, an administrator adds it to the form layout in **Global Settings > Forms**.
* Recording decisions needs permission to write to the decision log. Without it, the record and change buttons are not shown.

## Related

* [Content Types](https://docs.ins-pi.com/command/the-portal/content-types.md)
* [Architecture Governance](https://docs.ins-pi.com/command/features/architecture-governance.md)
* [Lifecycle](https://docs.ins-pi.com/command/features/lifecycle.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/decisions.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.
