> 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/detailed-estimate/change-in-edit-estimate.md).

# Change in edit estimate

## Edit Estimate

1. There is no change in the role-action and edit process.
2. Edit screen will get changed based on changes to have detailed estimate.

### Notification

Not applicable.

### Actions

On Save, Changes in the detail estimate are saved and no workflow changes done, fresh analysis is generated.

On submit, based on logged-in user role, workflow pop-up window is displayed.

<table data-header-hidden><thead><tr><th width="189.5"></th><th></th></tr></thead><tbody><tr><td><strong>Role</strong></td><td><strong>Workflow Window</strong></td></tr><tr><td>Estimate Creator</td><td>Submit pop-up window, estimate gets forwarded to verifier with changes saved and fresh analysis generated.</td></tr><tr><td>Estimate Verifier</td><td>Verify and Forward pop-up window, estimate gets forwarded to technical sanctioner with changes saved and fresh analysis generated.</td></tr><tr><td>Technical Sanctioner</td><td>Technical Sanction pop-up window, estimate gets forwarded to approver with changes saved and fresh analysis generated.</td></tr><tr><td>Approver</td><td>Approval pop-up window, estimate gets approved with changes saved and fresh analysis generated.</td></tr></tbody></table>

## UI

Same as created detailed estimate screen with additional estimate number displayed on top.

## Acceptance Criteria

1. Role based access based on configuration.
2. The estimates which are in workflow can only be edited.
3. Estimate is opened in editable mode.
4. The details given in table can be edited by user.


---

# 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/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/detailed-estimate/change-in-edit-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.