> 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-u-girder-bridge-workflow/reports-cug/quantity-takeoff-report-cug.md).

# Quantity Takeoff Report \[CUG]

***

### title: Quantity Takeoff

## General

Based on the unit price data provided by the user, the total cost will be presented according to the project specifications.

**Pay Item Type \[Pay Items/WSDOT Pay Items/Kiewit Pay Items]:** This parameter is used to select the pay item type.

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

1. **Cost Breakdown per Component (Graphical Representation)**

* A visual representation of the cost distribution across components. ![image-20241122-120552.png](https://openbrim.atlassian.net/wiki/download/attachments/2126151815/image-20241122-120552.png?api=v2) 2. **Tables for Each Defined Component**
* Detailed tables listing quantities and corresponding prices for each component.![image-20241122-120706.png](https://openbrim.atlassian.net/wiki/download/attachments/2126151815/image-20241122-120706.png?api=v2)
  {% 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.openbrim.org/templates/concrete-u-girder-bridge-workflow/reports-cug/quantity-takeoff-report-cug.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.