> 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

Scoring turns several measures into one rated value with a clear headline, so a stakeholder can read a single verdict 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.

## Core concepts

* **Score definition.** A weighted combination of inputs (usually measures) that resolves to one value. The weights are declared, so the result can be explained, not just asserted.
* **Headline.** A score carries a red, amber, or green headline alongside its number, for at-a-glance reading.
* **For one or many.** Score a single element on demand, or a whole portfolio at once for a list or a quadrant view.
* **Explainable.** Because the inputs and weights are recorded, you can trace a headline back to the numbers behind it.

## Reading a score

A score reduces several inputs to one number and one colour. The breakdown stays attached, so you can always see how the headline was reached.

| 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              |
| **Headline**         | **Amber** |        | **A single rated verdict** |

The example is illustrative. The point is that every headline can be opened up into the inputs and weights that produced it, so a red or amber result is never a black box.

## Where you see it

* Scores drive the red, amber, and green headlines in advisory reports and portfolio views.
* A score reads the same wherever it appears, because it is computed once and shown everywhere.
* Portfolio scores such as TIME are expressed this way, so a whole population can be ranked or plotted on a quadrant from the same definitions.

## How it fits together

Scoring builds on [Measures](/command/features/measures.md) for its inputs, and [Data Governance](/command/features/data-governance.md) tells you whether those inputs are complete enough to trust the headline.

> Guides for defining scores and reading their breakdown will follow in this section.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ins-pi.com/command/features/scoring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.