> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/rate-analysis/analysis-statements.md).

# Analysis Statements

## Scope

Analysis Statements

Analysis statements are generated for an estimate. These can be navigated from estimate view screen using view analysis statement.

## Actors <a href="#actors" id="actors"></a>

ULB: Estimate creator, verifier, technical sanctioner, approver and viewer.

## Details <a href="#details" id="details"></a>

1. The analysis statements are generated out of saved estimate details.
2. First, these analysis statements are generated SORs wise.
3. Second, they consolidated to have Material, Labour , and Machinery Wise.
4. The attributes and format is same for all three statements
5. Option to download into these statements into PDF is provided.
6. The attributes defining detailed estimate are given in below table.

<table data-header-hidden><thead><tr><th width="89"></th><th width="147"></th><th></th></tr></thead><tbody><tr><td><strong>Sr. No.</strong></td><td><strong>Field Name</strong></td><td><strong>Description</strong></td></tr><tr><td>1</td><td>SOR Description</td><td>SOR item from the estimate.</td></tr><tr><td>1.1</td><td>Code</td><td>The item code from the lead charges</td></tr><tr><td>1.2</td><td>Name</td><td>The item name from the lead charges</td></tr><tr><td>1.3</td><td>Unit</td><td>The unit of measurement</td></tr><tr><td>1.4</td><td>Rate</td><td>Rate per unit</td></tr><tr><td>1.5</td><td>Quantity</td><td>Total quantity required for the given SOR item.</td></tr><tr><td>1.6</td><td>Amount</td><td>Amount calculated rate*quantity.</td></tr><tr><td>1.7</td><td>Total</td><td>Total of all the material required for a given SOR item.</td></tr><tr><td>2</td><td>Grand Total</td><td>Total of all the material required.</td></tr><tr><td></td><td></td><td><strong>Material Wise Consolidation</strong></td></tr><tr><td>1</td><td>Code</td><td>The item code from the lead charges</td></tr><tr><td>2</td><td>Name</td><td>The item name from the lead charges</td></tr><tr><td>3</td><td>Unit</td><td>The unit of measurement</td></tr><tr><td>4</td><td>Rate</td><td>Rate per unit</td></tr><tr><td>5</td><td>Quantity</td><td>Total quantity required.</td></tr><tr><td>6</td><td>Amount</td><td>Amount calculated rate*quantity.</td></tr><tr><td>7</td><td>Total</td><td>Total of all the material required.</td></tr></tbody></table>

### Actions <a href="#actions" id="actions"></a>

Not applicable.

### Validations <a href="#validations" id="validations"></a>

Not applicable.

### Configuration <a href="#configuration" id="configuration"></a>

Not applicable.

### Notifications <a href="#notifications" id="notifications"></a>

Not applicable

### User Interface <a href="#userinterface" id="userinterface"></a>

HTML View:

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/KsNGicipRinHJyl9AXhg/Analysis%20Statements.png" alt=""><figcaption></figcaption></figure>

PDF View:

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/2unkxrKei3QUc7EyOZ9t/Analysis%20Statements%20PDF.png" alt=""><figcaption></figcaption></figure>

## Acceptance Criteria <a href="#acceptancecriteria" id="acceptancecriteria"></a>

1. Analysis is generated of Material, Labour and Machinery required.
2. The format and template is same.
3. Option to download these into PDF to be provided.


---

# 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.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/rate-analysis/analysis-statements.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.