> 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-workflow.md).

# Change in workflow

## Scope

Estimate preparation for a work, by the Estimate Creator and then its verification and approval by other users (actors) in the workflow. Hence no change in existing approach.

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

There is no change from existing actors.

<table data-header-hidden><thead><tr><th width="55"></th><th width="237"></th><th></th><th></th></tr></thead><tbody><tr><td>#</td><td>Role (Actors)</td><td>Actions</td><td>User Persona</td></tr><tr><td>1</td><td>ESTIMATE_CREATOR</td><td><ul><li>Create</li><li>Submit</li><li>Search</li><li>View</li><li>Edit/ Re-submit</li></ul></td><td>Junior Engineer/ Assistant Engineer/ MUKTA Implementation Expert</td></tr><tr><td>2</td><td>ESTIMATE_VERIFIER</td><td><ul><li>Search</li><li>View</li><li>Verify and Forward</li><li>Send Back</li></ul></td><td>Executive Engineer</td></tr><tr><td>3</td><td>TECHNICAL_SANCTIONER</td><td><ul><li>Search</li><li>View</li><li>Technical Sanction</li><li>Send Back</li><li>Send Back To Originator</li><li>Reject</li></ul></td><td>Municipal Engineer</td></tr><tr><td>4</td><td>ESTIMATE_ APPROVER</td><td><ul><li>Search</li><li>View</li><li>Approve</li><li>Send Back</li><li>Send Back To Originator</li><li>Reject</li></ul></td><td>Executive Officer/ Municipal Commissioner</td></tr><tr><td>5</td><td>ESTIMATE_VIEWER</td><td><ul><li>Search</li><li>View</li></ul></td><td>MUKTA Program Coordinator</td></tr></tbody></table>

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

1. There is minor change in the workflow.
2. The option to save the estimate as draft to be provided at first before submitting it to verifier and the same is reflected in the below table.

### Workflow States <a href="#workflowstates" id="workflowstates"></a>

<table data-header-hidden><thead><tr><th width="67"></th><th></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td>#</td><td>Action</td><td>Role</td><td>From State</td><td>To State</td><td>Status</td></tr><tr><td>1</td><td>Save as Draft</td><td>Estimate Creator</td><td> </td><td>Saved as draft</td><td>Drafted</td></tr><tr><td>2</td><td>Submit</td><td>Estimate Creator</td><td>Saved as draft</td><td>Pending for verification</td><td>Submitted</td></tr><tr><td>3</td><td>Verify and Forward</td><td>Estimate Verifier</td><td>Pending for verification</td><td>Pending for technical sanction</td><td>Verified</td></tr><tr><td>4</td><td>Technical Sanction</td><td>Technical Sanctioner</td><td>Pending for technical sanction</td><td>Pending for approval</td><td>Technically Sanctioned</td></tr><tr><td>5</td><td>Send Back</td><td>Estimate Verifier</td><td>Pending for verification</td><td>Pending for correction</td><td>Sent Back</td></tr><tr><td>6</td><td>Send Back</td><td>Technical Sanctioner</td><td>Pending for technical sanction</td><td>Pending for verification</td><td>Sent Back</td></tr><tr><td>7</td><td>Send Back</td><td>Estimate Approver</td><td>Pending for approval</td><td>Pending for technical sanction</td><td>Sent Back</td></tr><tr><td>8</td><td>Send Back To Originator</td><td>&#x3C;roles having access></td><td>&#x3C;Current Status></td><td>Pending for correction</td><td>Sent Back</td></tr><tr><td>9</td><td>Edit/ Re-submit</td><td>Estimate Creator</td><td>Pending for correction</td><td>Pending for verification</td><td>Re-submitted</td></tr><tr><td>10</td><td>Approve</td><td>Estimate Approver</td><td>Pending for approval</td><td>Approved</td><td>Approved</td></tr><tr><td>11</td><td>Reject</td><td>&#x3C;any roles having access></td><td>&#x3C;Current Status></td><td>Rejected</td><td>Rejected</td></tr></tbody></table>

## UI <a href="#ui" id="ui"></a>

No change. In the UI, the workflow will start displaying from Submitted state.

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

1. Roles are created as given provided.
2. Actions are configured based on role - action mapping.
3. Workflow states are defined as provided and the state transition done accordingly by updating the status appropriately.


---

# 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-workflow.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.