Milestones are key checkpoints within a savings record that help track progress toward projected cost reductions, cost avoidance, and overall...
Keep each milestone up to date as a savings initiative progresses, then mark it as complete to turn its projected savings into realised savings. This article is for anyone who manages savings records.
Before you start
Only users with edit access to Savings can edit or complete milestones. If the saving has restricted record access, only its owners and administrators can make changes. See Record Access.
Edit a milestone
Open the Milestones tab
Go to Savings Management > Savings Initiatives, open the saving and click the Milestones tab.
Choose Edit
Click the milestone's Action menu (⋮) and choose Edit. The Edit Saving Milestone window opens.
Change the details
Update any of Milestone Title, Milestone Start Date, Milestone End Date, Baseline Spend, Projected Cost Reduction, Projected Cost Avoidance and Milestone Notes. If the saving isn't in your base currency, you can also change Exchange Rate Against Base Currency.
💡 Note: If you change the baseline spend of a completed milestone, oboloo recalculates its Total Realised Savings %, and the saving's Total Baseline Spend Against Realised Savings and Total Realised Savings %.
Click Update Milestone
The saving's totals update straight away.
Mark a milestone as complete
Choose Mark as Complete
On the Milestones tab, click the milestone's Action menu (⋮) and choose Mark as Complete.
Check the realised savings
In Mark Milestone As Complete, Realised Cost Reduction and Realised Cost Avoidance start with the projected amounts. Change them to what was actually saved. Total Realised Savings and Total Realised Savings % update as you type, based on the milestone's Baseline Spend.
Choose an approver (optional)
To have someone check the milestone first, turn on Does this milestone need to be approved? and select an Approver. See Approving Savings Milestones.
Requiring approval when completing a milestone
Click Confirm Milestone Completion
Without an approver, the milestone becomes Completed. With an approver, it shows Pending Approval until it's approved.
Edit realised savings on a completed milestone
Choose Edit Realised Savings
Click the completed milestone's Action menu (⋮) and choose Edit Realised Savings.
Change the amounts and save
Update Realised Cost Reduction or Realised Cost Avoidance and click Save.
📌 Important: If the milestone was approved, changing its realised savings shows Warning! Re-approval Required. Click Save and Send for Re-approval to continue. The milestone goes back to Pending Approval and its savings count as projected until the original approver or an Administrator approves it again.
Dashboard: completed milestones count towards Total Realised Savings; others count towards Remaining Projected Savings. See Understanding the Savings Dashboard.
Approver: if you chose one, they get an email and notification and use Approve/Reject in the Action menu.
Change Log: every change, including edits to completed milestones, is recorded on the saving's Change Log tab.
Troubleshooting
Edit or Mark as Complete is greyed out
You don't have edit access to this record, for example because its record access is restricted to owners. Ask one of the saving's owners or an administrator.
I can't change realised savings in Edit Saving Milestone
Realised savings aren't in that window. Use Edit Realised Savings on a completed milestone instead.
I completed a milestone but the dashboard hasn't changed
If you chose an approver, the milestone stays Pending Approval until it's approved. Also check that the saving itself is approved and isn't a draft or archived.
My milestone was rejected
Open it from the Action menu, update the realised savings using the reason in the Approval Log tab, and click Update and send for approval.
📌 Need Further Help? If you need further assistance, please contact your internal platform administrator for support. Otherwise please reach out to oboloo's support team. If you are unable to view the above area in the oboloo platform, please check your user permissions and access rights.