> 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/deployment/configuration/ui-configuration/modules/workorder/time-extension.md).

# Time Extension

Work order is created for an approved estimate in order to award the work to CBO. CBO starts the work to complete it within a given time period.

In case organization comes to know that they are not in a position to complete the work within the given time frame due to various reasons, they need to inform the same to the officer in-charge of project and apply for time extension which is then subject to approval/ canceling of work order based on the analysis done by the ULB.<br>

Requests for time extension can be directly raised by CBO using the mobile application and by the officer in-charge of the project on behalf of CBO using web application. Once a request is raised it goes for verification and approval.

### We have the following screens for Time Extension in Web Interface

* Create Time Extension
* View Time Extension
* Edit Time Extension
* Search Time Extension ( Same as search work order screen)
* Inbox ( Same as work order inbox )

### Conditions to Create a Time Extension Request

* Work order must be in Accepted state
* Existing Time Extension requests, if already created, must not be in workflow
* At Least one muster roll must be approved&#x20;

### How to Create a Time Extension Request in Web-Interface

* Login with work order creator role and Navigate to Home page.&#x20;
* Home > Work Orders > Inbox > Search Work Order >  View Work Order > Request Time Extension (From Action Menu)
* A screen similar to the Work Order View screen is opened along with two new input fields&#x20;
* Enter time extension value (in days) and reason in those two inputs and click on Create action button
* A workflow popup is opened where users can enter the assignee and relevant comments. Click on Submit button
* A response page is opened which shows the newly created revised work order application’s number

### Inbox, View and Search Screen For Time Extension in Web Interface

There is no separate inbox for time extension. Work order inbox will list the time extension requests which are INWORKFLOW state. Clicking on the time extension request will open a view time extension screen where the user can take actions on the request based on the roles defined in the workflow. Alternatively, users can go to the work order search screen to search for any time extension request.

### &#x20;Workflow for Time Extension

| #                   | <p>Action</p><p><br></p>             | <p>Role</p><p><br></p>                                 | <p>From State</p><p><br></p>               | <p>To State</p><p><br></p>                 | <p>Status</p><p><br></p>       |
| ------------------- | ------------------------------------ | ------------------------------------------------------ | ------------------------------------------ | ------------------------------------------ | ------------------------------ |
| <p>1</p><p><br></p> | <p>Submit </p><p><br></p>            | <p>Work Order Creator/ CBO Admin</p><p><br></p>        | <p><br></p>                                | <p>Pending for verification</p><p><br></p> | <p>Submitted</p><p><br></p>    |
| <p>2</p><p><br></p> | <p>Verify and Forward</p><p><br></p> | <p>Work Order Verifier</p><p><br></p>                  | <p>Pending for verification</p><p><br></p> | <p>Pending for approval</p><p><br></p>     | <p>Verified</p><p><br></p>     |
| <p>3</p><p><br></p> | <p>Send Back</p><p><br></p>          | <p>Work Order Verifier</p><p><br></p>                  | <p>Pending for verification</p><p><br></p> | <p>Pending for correction</p><p><br></p>   | <p>Sent Back</p><p><br></p>    |
| <p>4</p><p><br></p> | <p>Send Back</p><p><br></p>          | <p>Work Order Approver</p><p><br></p>                  | <p>Pending for approval</p><p><br></p>     | <p>Pending for verification</p><p><br></p> | <p>Sent Back</p><p><br></p>    |
| <p>5</p><p><br></p> | <p>Send Back To CBO</p><p><br></p>   | <p>\<any roles having access of action></p><p><br></p> | <p>\<Current Status></p><p><br></p>        | <p>Pending for correction</p><p><br></p>   | <p>Sent Back</p><p><br></p>    |
| <p>6</p><p><br></p> | <p>Edit/ Re-submit</p><p><br></p>    | <p>Work Order Creator</p><p><br></p>                   | <p>Pending for correction</p><p><br></p>   | <p>Pending for verification</p><p><br></p> | <p>Re-submitted</p><p><br></p> |
| <p>7</p><p><br></p> | <p>Approve</p><p><br></p>            | <p>Work Order Approver</p><p><br></p>                  | <p>Pending for approval</p><p><br></p>     | <p>Approved</p><p><br></p>                 | <p>Approved</p><p><br></p>     |
| <p>8</p><p><br></p> | <p>Reject</p><p><br></p>             | <p>\<any roles having access></p><p><br></p>           | <p>\<Current Status></p><p><br></p>        | <p>Rejected</p><p><br></p>                 | <p>Rejected</p><p><br></p>     |

### <br>

<br>

<br>

<br>


---

# 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/deployment/configuration/ui-configuration/modules/workorder/time-extension.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.