> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/reports-cbg/quantity-takeoff-report-cbg.md).

# Quantity Takeoff Report \[CBG]

The quantity takeoff report turns the project's pay items into a cost estimate. It collects every pay item of the selected **Pay Item Type** (defined under **Reports > Pay Item Table** as Pay Item, WSDOT Pay Item or Kiewit Pay Item), groups them by their **Category**, and prices each quantity item of a pay item with its unit price. The report itself holds no prices and no component selection: to estimate the cost of the whole bridge, define pay items whose quantity items cover every component to be priced.

### General

**Pay Item Type \[Pay Items/WSDOT Pay Items/Kiewit Pay Items]:** Selects the kind of pay item the report collects. All pay items of one category must use the same unit of measure; otherwise the report shows an issue.

{% hint style="info" %}
**Quantity Takeoff Report Includes**

1. **Cost Breakdown per Category (Graphical Representation):** a pie chart of the cost of each pay item category, with the total cost in its title. ![image-20241122-120552.png](https://openbrim.atlassian.net/wiki/download/attachments/2126151815/image-20241122-120552.png?api=v2)
2. **Tables for Each Category:** one row per quantity item, with its object, the pay item's description, the quantity in the pay item's unit of measure, the unit price and the cost, and a total row. ![image-20241122-120706.png](https://openbrim.atlassian.net/wiki/download/attachments/2126151815/image-20241122-120706.png?api=v2)
   {% endhint %}

The report is opened from the document view (**Docs**) as **Quantity Take Off Report**.


---

# 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.openbrim.org/templates/concrete-box-girder-bridge-workflow/reports-cbg/quantity-takeoff-report-cbg.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.
