> 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/creating-estimates.md). # Creating Estimates Learn how to create new estimates in PaintScout, navigate the estimate page, and use core estimating features. This section covers the core estimate workflow in PaintScout. Start a new estimate, learn the estimate page, use the sidebar tools, understand sales rate, manage estimate actions, and save your work properly. ## In This Section * [Create a New Estimate](/support/estimating/creating-estimates/how-to-create-a-new-estimate.md) — Start a fresh estimate from scratch or from a template * [The Estimate Page](/support/estimating/creating-estimates/introduction-to-the-estimate-page.md) — Understand the layout and components of the estimate interface * [Sidebar Overview](/support/estimating/creating-estimates/sidebar-overview.md) — Use the sidebar for activity, chat, follow-ups, calculations, terms, and payment settings * [What is a Sales Rate?](/support/estimating/creating-estimates/what-is-a-sales-rate.md) — Understand total price compared to total project hours * [Estimate Actions](/support/estimating/creating-estimates/estimate-actions.md) — Preview, share, invoice, copy, download, archive, and delete estimates * [Saving & Syncing](/support/estimating/creating-estimates/saving-syncing-estimates.md) — How PaintScout saves your work and keeps estimates in sync across devices --- # 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/creating-estimates.md?ask=&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.