> 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/guided-use-cases.md).

# Guided use-cases

Run a guided analysis in YouDesign Command step by step, from the outcome you want through scope, data quality and results to decisions you can track.

A guided use-case walks you through an analysis one step at a time: what you want to achieve, which records it covers, whether the data is good enough, the results, and the decisions you take. You can run it as a **Guided use-case** in its own tab, or in the [Command Dialog](https://docs.ins-pi.com/command/features/command-dialog.md); both are the same run, so you can switch between them.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-da16a2029417a526b0f16372e7f7f0f21cd2741d%2Fcommand-guided-run.png?alt=media" alt="A guided use-case at the Data quality step, with the goal in the header, the steps from Outcome to Track, and the data quality of each table in a grid."><figcaption><p>A guided use-case at the Data quality step</p></figcaption></figure>

## What it is

Every run follows the same steps:

| Step             | What you do                                                                                                                                               |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Outcome**      | Say what you want to achieve, with constraints and a target date. A use-case from the catalog comes with its outcome set, so its first step is **Scope**. |
| **Scope**        | Choose the tables and records, and the fields, features, relationships and related lists the analysis uses.                                               |
| **Data quality** | See how good the data is, table by table and record by record, fill in what is missing, exclude records, or ask their stewards.                           |
| **Results**      | Read the results, starting with a live dashboard for the scope.                                                                                           |
| **Decide**       | Record what should happen, with the evidence. Recording a decision does not change anything yet.                                                          |
| **Track**        | Follow each decision to delivery: owner, date, and **Verify execution**.                                                                                  |

The header shows the run's goal, its stage, and whether there is **Enough data to answer**, the answer **will be partial**, or there are **Data gaps to close first**.

## How to

### Start a run

1. Click **Create** and choose **Guided use-case**. It opens as *Explore what's possible*.
2. Browse the catalog: group it by **Topics**, **Outcomes** or **Roles**, filter to **Use-cases** or **Questions**, or use **Search use-cases and questions**. Pick one.
3. Or click **Start from scratch** to pick your own tables, fields, scores and relationships.

You can also start from the Command Dialog by asking a question, or from a Table with **⋮ > Analyze this scope**.

### Work through the steps

1. Answer each step, then click **Continue to** . **Back** returns to the previous one.
2. On **Scope**, expand a table to choose what the analysis uses. Each field, feature, relationship and related list has a **Use** toggle: required (counted for readiness), used but optional, or left out. Use **Add table** in the grid header, and **Add field** and the other add buttons on the section headers. **Ctrl+Z** (**⌘Z**) undoes a change.
3. On **Data quality**, read **Data quality by table**: how many records are **Good** and how many **Need attention**. Expand a table to see its records, and open a record to see what is missing.
4. Fix what you can: **Add missing data** fills a field in place, the **Use** toggle on a record's row excludes it, and **Notify stewards to complete missing data** asks the people who look after the records.
5. Click **Proceed to Results**. If gaps remain, the result is marked partial and lists them.
6. On **Results**, read the dashboard. **Create dashboard in My Space** keeps an editable copy. **Decide on these results** adds the **Decide** and **Track** steps, and **Create advisory report** turns the result into a decision document.

Click **Edit** in the header to change the goal, constraints or target date at any time.

A record counts as **Good** when every required field is filled. When no field is required, every field in use must be filled.

### Ask stewards, or assign them

1. On **Data quality**, click **Notify stewards to complete missing data**.
2. Read the preview: each steward gets one request listing everything they look after. Optionally, add a **Note to the stewards** (up to 300 characters).
3. Click **Send N requests**.

Records that nobody looks after cannot be asked about. Administrators and Command editors can click **Assign stewards** to open a sheet of those records. Set the **Owner** or **Steward** in each cell, or check several records and use the **Set** bar and **Apply**. **Ctrl+D** (**⌘D**) fills down, and copy and paste work as in a spreadsheet. Click **Save changes**.

The **Data collection** card then tracks progress against the start of the run: how complete the records were **At the start**, **Now**, and what is **Still to fix**.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-d1a0d68239b673fc810cad13913497818a954e02%2Fcommand-guided-assign-stewards.png?alt=media" alt="The Assign stewards sheet listing records nobody looks after, with owner and steward columns and a bar to set a steward on several records at once."><figcaption><p>Assign stewards to records nobody looks after</p></figcaption></figure>

### Pick a run up again

A run is saved as you go. Reopen it from My Space, or click **Resume** in the Command Dialog's greeting. **⋮ > Start over** clears the run and begins again; it cannot be undone.

## Good to know

* You see only use-cases that have been reviewed and set up for your instance. If an analysis is not set up yet, Command says so and offers to record it as an idea.
* Data requests are previewed before they are sent: each steward gets one message listing everything they look after.
* In the Command Dialog, a Command administrator can turn a run's requirements into [Data Governance](https://docs.ins-pi.com/command/features/data-governance.md) rules with **Maintain these requirements in Data Governance**.
* Only the tables the method needs are fixed, marked **Required by the method**. Every field can be made optional or left out; leaving out a field the method uses marks the result partial.
* Approving or tracking a decision is recorded with your identity, so you need to be signed in.
* Share a run with **Copy summary** or **Download dashboard snapshot**.
* A ranked result shows each record's score and confidence out of 100. A large figure is shortened to fit its tile, such as 1.2M; hover it to see the full value.

## Related

* [Command Dialog](https://docs.ins-pi.com/command/features/command-dialog.md)
* [Decisions](https://docs.ins-pi.com/command/features/decisions.md)
* [Use cases](https://docs.ins-pi.com/command/getting-started/use-cases.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/guided-use-cases.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.
