> 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/improvements/revising-estimate-calculation-logic.md).

# Revising estimate calculation logic

## Context

An estimate can be revised due to following reasons.

1. Due to revision in rates.
2. Due to deviations (less/excess) in SOR/ Non-SOR quantities.

And for both the revision, logic to calculate estimated to be implemented as given below.

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

1. For an estimate system should know the used and unused quantities of all the SORs/Non-SORs.
2. Used quantity to be fetched from approved MBs. In workflow MBs will not be considered to determine the used quantity.
3. Current effective rates to be applied to calculate the revised estimate amount and it will be calculated SOR/ Non-SOR wise as given below.
4. Amount = (Unused Quantity + Additional Quantity (if added any))\* current effective rate.
5. For newly added SOR/ Non-SOR, current effective rates are applied.

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

The revised estimate amount is calculated using current effective rates on unused quantities of SORs.


---

# 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/specifications/functional-requirements/user-stories/improvements/revising-estimate-calculation-logic.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.