> 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/implementation/training-resources/user-manual/web-application-user-manual/registries/estimate-template.md).

# Estimate Template

## **Search Template**

It allows users to search all templates using various parameters, such as Template ID, Template Name, and Active Status.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXcykx8EHGW9yHT11J5pVeTiWYLx4NzlQg5Z_4lUjZIYd4BWhE28vvTj9ehaqV3oqpA4hoBI2ApwWOg84nJFnnLXC1j_iKQteJ1LPO2P57K3VVv7lh_DRo6PrZpLriukTLKb-7N3CjOHuhusVPSkGOJAknk?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>Search Template</p></figcaption></figure>

## Create Template

It allows users to create an estimate template applicable to all ULBs. The estimate template is created at the state level.

1. To create an estimate template, click of Add Master Data from search estimate template screen.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXd4HRiFxDPdTKtRbbZ2MFajUh_6rp6v05GKyl-plX3xcJHgUr14tgdT0OtFQIjFBe-ACcxi4NUOFt6VsIL8QqxASmHFjFHhef073_EzUkzifahJz-XJEKc_OAt0ShNv-c7YtPj32jQCbMOM9x_6bkRbZg?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>Add Template</p></figcaption></figure>

2. Enter the template name.
3. Enter the template description
4. Select project type.
5. Add SOR using the search SOR feature.
   1. Click on the drop-down to search for a SOR.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXdgU3MYS2smwb_jiPxJs9HMo6l7sPfV_Cw-z2BRTYEB-S82_zDgSz_GIy9G6i6lxN0xWRbqO_lBCMOjVNoiQRAv-BlJyCJxbua48SwuMYyuq3Bnyc8Japccy8xPkNJSg5KlubKmws9YNVY4miDZ13cBsQ?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>Add Template</p></figcaption></figure>

b. Click on the view more to search for SORs with more details.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXfymG350QxhaQcQd18HVQ__0QRYUaNDEHYm8Po4z8Fw-LFV5BvqtRzIhd23nfZqrirbK8YI7eNyeJbDFj_Fu2-ALn0InQ15HwLZdWhXDgYOz5BdU2du6MgmAcZT1wwXxypEPlz8yVyzdX7yw5c8wWsZ5-M?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>Add Template</p></figcaption></figure>

3. Select an SOR to add into the estimate template.
4. Add the Non-SORs. Enter the Non-SOR description.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXd-laRyDkAxvzpvQdhuDrpU4IKrl4HCh4tui6ygIdDvlah0DahKp2o5k24-t7XXaFcsHHaJcTTwLyKCMOfv2ezDW1UMNOjmJ1Qj9bn70IgBmwOGYHYwVpZKd6OUzL6oPcsGFgXiHR1xN1Z0yIn0kwMxYGY?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>Add Template</p></figcaption></figure>

3. Click on “Add Data” to create the template. Template ID is created automatically by the system.

## **View Template**

It allows the user to view the estimate template details. The “i” icon against a field displays the complete information of the value of that field.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXeE7j9AYo948gmBlrNZilPgwaCTEIeN76muUGI2TMP1Fvtgh2fHLtCyF2FslR-IZuZicpMy12DMyQ2_7UH6e8xcDWDB3z4v7NRf_7ROj-uZ4IMFKPjSGpKD0D08LiG2_3tTHlh9RxXPDwMgk3OMcwr9GTA?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/QuoN2yTVgYqE4zYXkMNx/unnamed.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/NANigqST9cGWbpaaNQpT/unnamed.png" alt=""><figcaption></figcaption></figure>

## **Edit Template**

It allows the user to edit the details of the estimate template, change the name and description, add/remove the SORs and Non-SORs.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXd_AeaY2Jo-Az8ZKd2q3PbmJnaqWpNLMvgS37P1-PvOfdXUvNZ2f91cytV8UdwZOnLSVh5XA-39BcF6UyXjT95-zZQPJmAxErZYum2vTQV8SjtBS7SrO4wn4_G8nfRJ8VNf-cRRnJH2QQnA8nI_BEMYxKA?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>Edit Template</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/QRKo5I88dsk4AFkrkAzl/unnamed.png" alt=""><figcaption><p>Edit Template</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/0JrWzdagQeS23t9wImRQ/unnamed.png" alt=""><figcaption><p>Edit Template</p></figcaption></figure>


---

# 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/implementation/training-resources/user-manual/web-application-user-manual/registries/estimate-template.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.