# About Achieved Savings

The Achieved Savings section shows the **monthly cost reductions** you've already realized. It provides insights into where and how these savings were made, broken down by service, account, and region.

## Achieved Savings Calculation- How it Works

When you resolve a ticket in OneLens, it doesn’t just close immediately. Instead, the ticket moves into a **Pending Verification** stage. During this time, OneLens watches the resource linked to that ticket to check if the recommended action was actually carried out.

This verification period lasts for **5 days** right after you mark the ticket as resolved.

### **What Happens During These 5 Days?**

OneLens continuously monitors the resource to detect specific types of changes that prove the recommended action was implemented. These changes include:

* **Pricing Variance:** Switching pricing models or instance types, such as moving from On-Demand to Reserved.
* **Provisioned Capacity Change:** Rightsizing or scaling down resources.
* **Resource Deletion:** Completely removing the resource.
* **Resource Stop:** Temporarily shutting down a running resource.
* **Resource Upgradation:** Detected when the previous usage type disappears, indicating a replacement or scale-up.

Once a qualifying change is detected, OneLens identifies the **Date of Change (DOC)** — the exact day the change first occurred. To confirm the change is stable and not a short-term fluctuation, it reviews usage data with a 3-day buffer before and after the DOC.

Then, OneLens calculates savings by comparing the resource’s cost over two periods:

* **Pre-Change Cost:** The average daily cost over the 7 days before the DOC.
* **Post-Change Cost:** The average daily cost over the 3 days following the DOC.

If no relevant change is found within the 5-day window, the ticket is automatically marked as **Auto Resolved** with zero achieved savings recorded.

### How Savings Are Calculated

Once the change is confirmed, OneLens calculates the achieved savings by comparing costs before and after the change:

1. **Pre-Change Cost:** It averages the daily cost of the resource over the 7 days before the DOC.
2. **Post-Change Cost:** It averages the daily cost over the 3 days following the DOC.
3. **Daily Savings:** Subtract the post-change daily cost from the pre-change daily cost.
4. **Monthly Savings:** Multiply the daily savings by 30 to estimate monthly  achieved savings.

{% hint style="warning" %}
Keep in mind, this is an estimate and actual monthly savings may vary due to fluctuations in usage patterns, pricing changes, or other factors.
{% endhint %}

{% hint style="success" %}

#### What Happens When Multiple Tickets Are Resolved by One Change?

Achieved savings are calculated at the **resource level**. This means OneLens measures the total savings from a single resource, regardless of how many tickets or policies were involved.

If one change addresses multiple tickets linked to the same resource, the savings from that change are combined into a single achieved savings value for that resource—avoiding double counting.
{% endhint %}

To see how realized savings are tracked and visualized, visit the [Achieved Savings page](https://docs.onelens.cloud/optimize-cost-savings-and-recommendations/saving-dashboard/view-achieved-savings) for a detailed walkthrough of the OneLens UI.