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

# Scoring

Turn several inputs into one explainable rated value, with an optional red, amber or green headline, and see it in TIME Analysis, tables and dashboards.

Scoring turns several inputs into one rated value, so a stakeholder can read a single result instead of a table of numbers. Where [Measures](/command/features/measures.md) hold the facts, a score is the judgment built on top of them. The inputs and their weights stay attached, so every result can be opened up and explained.

## What it is

| Concept  | What it means                                                                                   |
| -------- | ----------------------------------------------------------------------------------------------- |
| Score    | A weighted combination of inputs that resolves to one value for a record.                       |
| Inputs   | A record's attribute, a measure, another score, or an assessment answer. Each carries a weight. |
| Headline | Optionally, a red, amber or green result next to the number, for reading at a glance.           |
| Coverage | How many inputs had a value. An input with no value is left out, not counted as zero.           |

A score reads the same wherever it appears, because it is defined once.

### Reading a breakdown

| Input                | Value     | Weight | Contribution        |
| -------------------- | --------- | :----: | ------------------- |
| Business criticality | High      |    3   | Raises the score    |
| Data completeness    | 60%       |    1   | Holds it back       |
| Open risks           | 4         |    2   | Holds it back       |
| **Result**           | **Amber** |        | **One rated value** |

The example is illustrative. The point is that a red or amber result is never a black box.

## When to use it

* You want to rank or plot many records on the same basis, for example on a TIME quadrant.
* You want one headline for a record that combines several facts.
* You need to explain why a record scored the way it did.

## How to

### See why a record scored as it did

1. Open a [TIME Analysis](/command/the-portal/content-types.md#time-analysis).
2. Click the chevron on a record's row to show its score inputs.
3. Read each **Input**, its **Value**, its **Weight** and its **Contribution** to **Business Fit** or **Technical Fit**. Inputs without a value show **Not counted**.
4. To try another value, edit it and click **Save**, or **Discard** to drop the change.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-dedea8e9a51534b3a3c838b013d3a0aa79db8607%2Fcommand-time-score-inputs.png?alt=media" alt="A TIME Analysis with one record&#x27;s score inputs open, showing each input with its value, weight and contribution to Business Fit and Technical Fit."><figcaption><p>A record's score inputs in a TIME Analysis</p></figcaption></figure>

### Show scores in tables and dashboards

* **Table:** open **Columns** and choose a score from the **Scoring** category.
* **Dashboard:** add a **Score tile** for one record's result, or a **Score summary** for how results are spread across a population.
* Scores also position records in TIME Analysis and Orbit.

### Define a score (administrators)

1. Open **Global Settings > Scoring** and click **Add Score**.
2. Give it a name, choose the table it scores, and add its inputs with their weights.
3. Optionally set the output to a red, amber, green headline and choose the thresholds.
4. Use **Preview** and **Compute** to check the value, headline and coverage on real records.
5. Make it active.

## Good to know

* A missing input is shown as missing, never as zero, and coverage tells you how many inputs had a value.
* Where a score is shown with partial coverage, treat the result with care.
* [Data Governance](/command/features/data-governance.md) tells you whether the inputs are complete and current enough to trust the result.
* Recommendations in [Command Dialog](/command/features/command-dialog.md) carry their own confidence and evidence grades, explained on that page.

## Related

* [Measures](/command/features/measures.md)
* [Data Governance](/command/features/data-governance.md)
* [Content Types](/command/the-portal/content-types.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/scoring.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.