> For the complete documentation index, see [llms.txt](https://docs.acho.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acho.io/app-builder/app-construction/elements/table-and-chart/score-card.md).
# Score Card
The score card, or sometimes called KPI indicator, iis primarily used to display metrics that represent performance indicators. This visualization element typically highlights crucial data points that help in understanding business's overall performance or specific business aspects. It can be designed to show not just the current value of a metric but also its change or trend over a specified period.
Regarding data sourcing, the scorecard is capable of utilizing a [**Metric**](/app-builder/app-construction/metric.md) or [**Query**](/app-builder/app-construction/query.md), and while it also supports a **Table**, this is not recommended. This is because it displays the value of the first row from the selected column, as specified by the "Display Column" setting. Primarily, aggregation occurs within a **Metric** or **Query**, and the scorecard displays this aggregated value. This approach ensures a focused and clear presentation of the most pertinent data.
### Properties
Data source: Select the data source of the score card
Display column: Select the column field of the data you want to display
Title: A short text describing the value
Prefix: An optional text or symbol placed before the value, such as $
Suffix: An optional text or symbol placed after the value, used to provide context or units (e.g., %, kg, hrs).
Footer: Additional information or commentary about the displayed data, such as a brief note on the data source, the time frame of the analysis
### Supported Event
No event supported
### Supported Action
No action supported
---
# 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.acho.io/app-builder/app-construction/elements/table-and-chart/score-card.md?ask=&goal=
```
`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.