# Results table column settings

Source: https://govform.com/resources/documentation/article/23-23-results-table-column-settings
Topic: Component Settings

Each results-table column defines a header and the content shown for each result row. Use columns to make records easy to scan, not to expose every value returned by a data source.

## Write concise headings and cells

The column title should say what the value represents. The cell template is evaluated for the current row, so it can render a formatted value, link or status.

Keep templates defensive: test missing values, long values and characters that need escaping. Do not output raw HTML from untrusted data.

## Set width and wrapping responsibly

Use a minimum width only where a value needs room to remain understandable. Preventing wrapping can be appropriate for a short reference or status, but it can create horizontal scrolling for names and descriptions.

Use additional cell classes only when a documented service style requires them. Check narrow displays, keyboard navigation and zoom after every layout change.

## Choose the right value path

Each cell template runs for one result row. Start by confirming the shape of a representative result: a simple text property, a nested value, a calculated display value or a link. Keep the template focused on presentation. If a value needs substantial calculation or cleanup, prepare it in the action or an Assign action before rendering the table.

For dates, numbers and statuses, use a consistent display format across all rows. A table is harder to scan when the same kind of value appears in several formats or when blank values are replaced by unexplained punctuation.

## Use links and status text safely

When a column contains a link, make its text explain the destination or operation. Avoid a column full of generic “View” links without the record context. If the table uses colour for a status, include the status in text as well.

Do not use a cell template to inject unreviewed markup from a result. Escape or safely render user-provided and external values, and test unusual characters and long unbroken strings.

## Test checklist

-   The header identifies the value without relying on surrounding columns.
-   Templates handle blank, missing, long and unexpected values.
-   Dates, numbers and statuses use a consistent readable format.
-   Links explain their destination or action in context.
-   Width and wrapping remain usable at zoom and narrow widths.
-   Changes to a result source have been tested against the column templates.

## Related guidance

-   [Results table components](<https://govform.com/resources/documentation/article/23-22-component-results-table>)
-   [Use Markdown and HTML](<https://govform.com/resources/documentation/article/12-use-markdown-and-html>)