> 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/estimating/areas-and-rates.md).

# Areas & Rates

Add areas and production rates to your estimates, adjust dimensions, coats, and prep hours for accurate pricing.

Areas and rates are the core building blocks of every PaintScout estimate. Add named spaces, choose room or surface area types, apply production rates, and fine-tune dimensions, coats, and hours when the job needs an override.

## In This Section

* [Adding Areas](/support/estimating/areas-and-rates/adding-areas-to-an-estimate.md) — Create named spaces, enter dimensions, choose room or surface mode, and add substrates
* [Adding Rates](/support/estimating/areas-and-rates/adding-rates-to-an-estimate.md) — Apply production rates to surfaces, edit them on the estimate, or create one-off custom rates
* [Adjust Surface Dimensions](/support/estimating/areas-and-rates/how-to-adjust-surface-dimensions.md) — Override surface measurements or switch to direct sqft or lnft input
* [Adjust Number of Coats](/support/estimating/areas-and-rates/how-to-adjust-the-number-of-coats-for-a-substrate.md) — Change coat counts on a surface and update pricing automatically
* [Adjust Painting & Prep Hours](/support/estimating/areas-and-rates/how-to-adjust-painting-and-prep-hours.md) — Fine-tune painting and prep hours when the automatic calculation needs adjustment
* [Prep Hours](/support/estimating/areas-and-rates/prep-hours.md) — Add manual prep time and have PaintScout calculate the prep cost from your hourly rate

&#x20;&#x20;


---

# 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/estimating/areas-and-rates.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.
