> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/dashboard-and-reports/dashboard-search-reporting.md).

# Dashboard

Track sales team performance and analyze key business metrics in PaintScout.

{% hint style="success" %}
**Start here:** Begin with [Dashboard Metrics](/support/dashboard-and-reports/dashboard-search-reporting/understanding-your-dashboard-metrics.md) and [Filtering the Dashboard](/support/dashboard-and-reports/dashboard-search-reporting/filtering-on-the-dashboard.md).
{% endhint %}

The Dashboard is your quick view of estimate performance in PaintScout. Use it to monitor sales activity, review conversion metrics, filter results, and open Leaderboards.

## In this section

* [Dashboard Metrics](/support/dashboard-and-reports/dashboard-search-reporting/understanding-your-dashboard-metrics.md) — Learn what each metric means, including Sales, Total Estimates, Estimates Open, Win Rate, Dollars Won, and Close Rate
* [What is Close Rate?](/support/dashboard-and-reports/dashboard-search-reporting/what-does-close-rate-mean.md) — Understand how Close Rate differs from estimates that remain open
* [Filtering the Dashboard](/support/dashboard-and-reports/dashboard-search-reporting/filtering-on-the-dashboard.md) — Narrow Dashboard data by date range, estimate type, and estimator
* [PaintScout Leaderboards](/support/dashboard-and-reports/dashboard-search-reporting/paintscout-leaderboards.md) — Compare Sales and Win Rate performance across the PaintScout network

{% hint style="info" %}
Need deeper analysis? Use [Reports](/support/dashboard-and-reports/reports.md) for detailed reporting across estimates, invoices, payments, and team performance.
{% endhint %}

  

## Related articles

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Dashboard Metrics</strong></td><td>Learn what each dashboard metric means including sales totals, win rate, dollars won, close rate, and open estimates tracking.</td><td><a href="/support/dashboard-and-reports/dashboard-search-reporting/understanding-your-dashboard-metrics.md">Dashboard Metrics</a></td></tr><tr><td><strong>Filter &#x26; Export Estimates</strong></td><td>Use advanced search criteria to filter estimates and export results to CSV files for external analysis and record keeping.</td><td><a href="/support/estimating/managing-estimates-and-work-orders/managing-estimates/how-to-filter-estimates-and-export.md">Filter &amp; Export Estimates</a></td></tr></tbody></table>


---

# 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://help.paintscout.com/support/dashboard-and-reports/dashboard-search-reporting.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.