Since July 16, 2026, Power Automate has been able to calculate the time and cost saved by desktop flows from company-defined baselines, according to Microsoft’s release plan for measuring desktop-flow savings. The next task is therefore not simply to deploy version 2607 correctly—covered in our guide to the Power Automate Desktop 2607 update—but to turn the new feature into credible management information.
The starting point: replace assumed savings with measurable value
Your company may already use Power Automate Desktop to enter data, retrieve files, reconcile spreadsheets, or update business applications. However, when management asks how much these automations actually save, the answer often depends on an outdated estimate or an irregularly maintained spreadsheet.
The target is practical: by the next monthly close, each priority automation should produce a total number of hours saved and a value in euros based on successful production runs. Power Automate can associate a manual processing-time baseline with an hourly rate or a direct saving per run, then aggregate the results. This mechanism is documented in Microsoft’s Power Automate savings documentation.
Name the result correctly. Time released by automation initially represents additional operational capacity. It becomes a budget saving only when it removes an identifiable cost, such as overtime, outsourced work, planned recruitment, or another expense.
Prerequisites: collect the evidence before configuring the tool
Have the following ready:
- A defined scope of production flows, including their business owner, technical owner, and automated process.
- Usable run history. Microsoft documents how to review and export twenty-eight days of run history to analyze run counts and durations in its guide to assessing the business impact of automation.
- An observed manual baseline for the work being replaced, including normal exceptions.
- A written finance decision defining whether to use a loaded hourly cost, an external-service cost, or a direct saving per transaction.
- The required Power Platform permissions. Microsoft states that viewing and editing saving rules requires privileges on the Saving Rule and Flow Aggregation tables; Environment Maker is one example of a suitable role.
- An approval rule naming the person authorized to change the baseline when the business process evolves.
Do not begin with technical configuration. An automated calculation based on an unverified assumption will still be an unreliable calculation.
The step-by-step rollout
1. Build the automation measurement register
Who does what: the automation lead exports the active flows and their run history. Each business owner confirms the task covered, its actual frequency, and any remaining manual intervention.
Realistic duration: one portfolio review based on the available history. Microsoft documents a twenty-eight-day window for reviewing and exporting flow runs.
Deliverable: a register listing each flow, its environment, owner, trigger, successful-run volume, business purpose, and baseline status.
Temporarily exclude test flows, abandoned automations, and processes whose functional boundaries are still changing.
2. Measure the manual work that is genuinely avoided
Who does what: the operations manager observes and times the manual procedure under normal conditions. The operator records its start and end, controls performed, exceptions, rework, and any work that will remain after automation.
Realistic duration: an observation cycle covering representative executions until the business owner can explain the main variations.
Deliverable: an approved baseline sheet stating the manual time avoided per successful run.
Do not automatically use the entire duration of the former procedure. If a person still reviews or completes the output, that residual work must be removed from the claimed saving. Microsoft recommends comparing the original and automated processes using run counts and duration data in its business-impact assessment guide.
3. Have finance approve the valuation rule
Who does what: the finance controller chooses the conversion method. The business owner identifies the staff category involved, while the automation lead explains the unit recorded by Power Automate.
Realistic duration: one joint operations and finance workshop, extended only when several cost categories are involved in the same process.
Deliverable: an approved rule based either on an hourly rate applied to the time saved or on a direct amount saved per execution. Microsoft confirms both options in its documentation for Power Automate saving rules.
Report released capacity separately from realized budget savings. This prevents additional staff availability from being presented as cash already removed from the cost base.
4. Configure the saving rules
Who does what: the Power Platform administrator or authorized owner opens the selected flow, accesses the savings function, and enters the approved manual-duration baseline. They then add the hourly rate or direct monetary baseline.
Realistic duration: one configuration session for each group of similar flows, followed by a business review.
Deliverable: an active and documented saving rule for every selected flow, including its approval date and approver.
The feature does not produce meaningful figures merely because a desktop flow exists. Microsoft states that time-saving and money-saving rules must be configured explicitly. Savings are then calculated from successful runs and accumulated automatically.
5. Test the calculation without contaminating the results
Who does what: the technical owner triggers a normal production-like execution, verifies its final status, and checks that the saving appears. The business owner compares the result with the approved baseline.
Realistic duration: allow up to one hour after the run for it to appear in the saving total, as specified in the Power Automate savings documentation.
Deliverable: an acceptance record containing the execution, status, applied rule, and value displayed in Automation Center.
Only successful runs generate savings, and successful test runs are excluded according to Microsoft. Testing only through the designer’s test function is therefore insufficient to validate the complete measurement cycle.
6. Establish a monthly value review
Who does what: the automation lead presents the results, business owners explain volume changes, finance validates the valuation, and the sponsor decides which flows to maintain, repair, or extend.
Realistic duration: one review at each monthly close, aligned with the run-analysis window. Microsoft states that automation results can be examined over a thirty-day period.
Deliverable: a management dashboard showing validated savings, failures, baseline changes, and recorded decisions. Where several environments must be consolidated, apply the principles in our guide to building a Power BI management dashboard.
How to measure whether it works
- Validated time avoided = approved manual time avoided per run × successful production runs. This follows the calculation principle described by Microsoft for saving rules.
- Value of released capacity = validated time avoided × the hourly rate approved by finance.
- Flow reliability = successful production runs divided by all production runs. Track this alongside ROI because Power Automate generates savings only from successful runs.
- Portfolio coverage = active flows with approved saving rules divided by active flows included in the measurement scope.
An increasing financial estimate combined with deteriorating reliability is not a satisfactory outcome. It usually indicates higher transaction volume rather than better-controlled automation.
Mistakes that cause ROI measurement to fail
- Do not confuse process duration with human time avoided. An automation may run for a long time without requiring employee attention.
- Do not use a time estimate recalled from memory. Observe the procedure and document exceptions before entering the baseline.
- Do not let the developer choose the hourly rate alone. Finance must own the valuation method and keep it consistent across departments.
- Do not automatically report released capacity as an accounting saving. Show expenses that have genuinely disappeared separately.
- Do not mix test runs, production runs, and old flow versions. Stabilize the deployment first by following our Power Automate Desktop 2607 playbook.
- Do not retain an old baseline after the process changes. A new interface, removed task, or additional control requires renewed approval.
- Do not assess automations solely on gross savings. Place the results within a structured process optimization approach that also monitors reliability, quality, and processing delays.
Get support to produce decision-ready ROI figures
D1 Consulting can inventory your flows, measure manual baselines, formalize valuation rules with finance, configure them in Power Automate, and build the management dashboard. Our Automation & Process Optimization service can also identify and repair unstable flows before they are scaled.
👉 Book your free 30-minute diagnostic and receive a clearly defined scope for your first automation ROI measurement campaign.
