> 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/works-v1.0/programmes/muktasoft-v2.0/specifications/functional-requirements/user-stories/detailed-estimate/search-and-view-detailed-estimate.md).

# Search and View Detailed Estimate

## Scope

View Detailed Estimate

Search Estimate → View Estimate.

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

No change.

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

1. There is no change in existing search estimate.
2. Changes are for the attributes added newly.

### Attributes <a href="#attributes" id="attributes"></a>

1. Estimate Number
2. Estimate Type
3. Project ID
4. Project Sanction Date
5. Project Name
6. Project Description
7. Project Details \[\*The project details is shown as view project detail in a separate TAB\*]
8. Estimation Details
9. ***SORs - Below information is displayed in the grid.***
   1. Type
   2. Code
   3. Description
   4. Unit
   5. Rate
   6. Quantity
   7. Amount
      1. Measurements
         1. Type
         2. Description
         3. Numbers
         4. Length
         5. Breath
         6. Height/ Depth
         7. Quantity
         8. Total
   8. Grand Total - Grid total.
10. ***Non SORs - Below information is displayed in the grid.***
    1. Description
    2. Unit
    3. Rate
    4. Quantity
    5. Amount
    6. Measurements
       1. Type
       2. Description
       3. Numbers
       4. Length
       5. Breath/ Area
       6. Height/ Depth
       7. Quantity
       8. Total
    7. Grand Total - Grid total.
11. ***Other Charges - Below information is displayed in the grid.***
    1. Head
    2. Percentage/ Lump-sum
    3. Amount
    4. Total - Grid Total
12. Total Estimated Amount
13. ***View Analysis Statements***
14. ***Relevant Documents***
15. ***Timelines*****&#x20;\[**&#x44;IGIT standard way if displaying the timelines,refer wire-frame and as description in workflow stor&#x79;**]**
16. ***Actions*** - Based on the workflow state and role logged-in user has.

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

Not applicable.

### Configurations <a href="#configurations" id="configurations"></a>

Not applicable.

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

1. For 'In Workflow' Estimate, actions are the workflow actions based on the role of logged-in user.
   1. Save as Draft
   2. Verify and Forward
   3. Technical Sanction
   4. Approve
   5. Send Back
   6. Send Back To Originator
   7. Edit Estimate
   8. Reject
2. For Approved Estimate, actions based on the role of logged-in user.
   1. Create Work Order - If the work order is not created.
   2. View Work Order - If the work order is created and not in **Rejected** status.
   3. Create Revised Estimate - In v2.1
3. For Rejected Estimate, No action/ even action button is not enabled.

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

Not applicable.

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

<figure><img src="/files/wWBx5seOtDwQ3CxTkQUg" alt=""><figcaption></figcaption></figure>

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

1. Estimate details is displayed as described in the story.
2. Actions are enabled as per the estimate workflow state and role logged-in user has.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/works/works-v1.0/programmes/muktasoft-v2.0/specifications/functional-requirements/user-stories/detailed-estimate/search-and-view-detailed-estimate.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.