> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/customizations/smart-summaries.md).

# Smart Summaries (beta)

Extra summaries built from a smart tag group — every observation that needs a plumber, or a page per contractor — in the report summary or on a page of their own.

The standard summary lists observations by modifier. A **smart summary** lists them by what they're tagged with: every observation a plumber needs to look at, or a page per contractor to hand to each one.

{% hint style="info" %}
Smart Summaries are set up on the desktop app, and they need the 7.2 compatibility update. See [Updating Company Compatibility](https://docs.scribeware.com/customizations/updating-company-compatibility.md).
{% endhint %}

## Before You Start

A smart summary is built from a [smart tag group](https://docs.scribeware.com/customizations/smart-tags.md), and it can only include observations tagged from that group. You need:

* A smart tag group, such as *Contractors*, attached to the report.
* Observations tagged from that group.

## Which One Do You Need?

| You want                                         | Use                                                                                                 |
| ------------------------------------------------ | --------------------------------------------------------------------------------------------------- |
| Observations grouped by their modifier           | The [standard summary](https://docs.scribeware.com/customizations/customizing-your-summary-page.md) |
| Observations grouped by what they're tagged with | A smart summary                                                                                     |
| Values lined up in rows and columns, with totals | A [table](https://docs.scribeware.com/customizations/tables.md)                                     |

A smart summary can also carry a table, so one page can hold both the observations and their costs.

## A Quick Example: A Page Per Contractor

1. Tag observations from a *Contractors* group, with one tag per trade.
2. In **Settings → Report Templates**, click **Smart Summaries**, then **Add Summary**.
3. Pick the *Contractors* group and name the summary.
4. Set **Show as** to **Separate page**.
5. Set **Divide into** to **Tag**.

Each trade now gets its own summary, holding only the observations for that trade.

## In This Section

{% content-ref url="/pages/OJLTPu0EiRyhsk5x8Un7" %}
[Creating a Smart Summary (beta)](https://docs.scribeware.com/customizations/smart-summaries/creating-a-smart-summary.md)
{% endcontent-ref %}

{% content-ref url="/pages/WmNcnYrXCpRHMSMPwEvY" %}
[Choosing the Observations (beta)](https://docs.scribeware.com/customizations/smart-summaries/choosing-the-observations.md)
{% endcontent-ref %}

{% content-ref url="/pages/GYCZRrHWqfdZeTyUF49I" %}
[Dividing and Laying Out a Summary (beta)](https://docs.scribeware.com/customizations/smart-summaries/dividing-and-laying-out-a-summary.md)
{% endcontent-ref %}

{% content-ref url="/pages/6VKVo3XAM0psDMR4VD7h" %}
[Titles, Intro Text and Tables (beta)](https://docs.scribeware.com/customizations/smart-summaries/titles-intro-text-and-tables.md)
{% endcontent-ref %}

{% hint style="success" %}
The Scribeware AI assistant can list and edit smart summaries too: *"Add a summary of everything that needs an electrician, on its own page."*
{% endhint %}


---

# 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.scribeware.com/customizations/smart-summaries.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.
