> 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/schedule-of-rates/rate-analysis.md).
# Rate Analysis
## **Add Rate Analysis**
The "Add Rate Analysis" feature empowers users to add a rate analysis to an SOR with a future effective-from date and closes the existing rate analysis by updating its effective-to date to one day before the newly added rate analysis effective-from date.
It opens the create rate analysis screen, allowing the creation of a rate analysis with a 'future effective from date'.
Create Rate Analysis
Create Rate Analysis
Create Rate Analysis
Create Rate Analysis
## **View Rate Analysis**
The "View Rate Analysis" feature enables users to access and review the details of a specific Schedule of Rate (SOR)’s rate analysis. This functionality provides a comprehensive view, allowing users to compare the existing rate, the rate as per the rate analysis, and the latest rates of the basic SORs included in the rate analysis.
1. Search SOR and open to view the details.
2. For the Take Action menu, select View Rate Analysis. The rate analysis effective as on date is displayed.
## **Edit Rate Analysis**
The "Edit Rate Analysis" feature enables users to edit the existing rate analysis with the same effective-from date. This helps users correct any rate they entered incorrectly.
To edit the rate, select 'Edit Rate Analysis' from the View Rate Analysis page.
View Rate Analysis
It opens the rate analysis in editable mode, allowing modifications from the same 'effective from date'.
---
# 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/schedule-of-rates/rate-analysis.md?ask=&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.
