Cost optimization is not a one off project, it is a habit, and the quarterly review is where the habit lives. A good review finds the savings, assigns the owners, and keeps the estate lean in the months between reviews rather than letting it drift back to bloat.
The reason most cost optimisation gains evaporate is that they were achieved once, in a project, and never maintained, so the estate drifts back to bloat within a year as new resources are provisioned and old ones are forgotten. Cost is not a problem you solve, it is a state you maintain, and the mechanism for maintaining it is a regular review that happens whether or not anyone feels like doing it. A quarterly cadence works for most organisations because it is frequent enough to catch drift before it compounds and infrequent enough that the review stays substantial rather than becoming a box ticking ritual. This guide sets out a repeatable quarterly review process, what to look at, who attends, and how to make sure the findings turn into action rather than a report nobody reads. It sits within the Oracle Cloud Cost Optimization pillar guide and is the operational rhythm behind it.
The case for a fixed cadence is that it removes the question of when, which is the question that kills cost reviews, because a review that happens when someone remembers happens rarely and then not at all. A standing quarterly slot means the review is a commitment rather than a good intention, and the regularity is what catches drift, the slow accumulation of idle resources, untagged spend, and oversized shapes that builds up between reviews. Quarterly fits the natural rhythm of most planning and budgeting cycles, which makes the cost review a natural input to those conversations rather than a separate chore. Faster than quarterly and the review struggles to show meaningful change between sessions, slower and the drift has time to become a large problem before anyone looks, so the quarter is the sweet spot for most estates.
| Review stage | Question it answers | Output |
|---|---|---|
| Trend | Where is total spend going? | Direction and forecast |
| Movers | What changed since last quarter? | List of significant changes |
| Waste sweep | What is idle or oversized? | Optimisation backlog |
| Actions | Who does what by when? | Owned, dated commitments |
A good review opens with the big picture, the total spend trend and the forecast, so everyone shares the same context before diving into detail. Then it moves to the movers, the lines that changed materially since last quarter, because a change is where something happened and therefore where attention pays. Some movers will be expected, a planned migration landing, a workload retired, and naming those keeps them from distracting from the unexpected ones, which are the real subject of the review. The trend tells you whether the overall trajectory is acceptable and the movers tell you what specifically to investigate, and reading them in that order keeps the review grounded in the whole before it gets lost in the parts. This is the dashboard work of Building an OCI Cost Dashboard put to use in a meeting.
Every quarter the review should run the same waste sweep, because the same categories of waste reappear no matter how many times they are cleared. Idle and unattached resources accumulate as covered in Finding Idle Resources on OCI, shapes drift away from their right size as workloads change, storage grows into the wrong tiers, and untagged spend creeps up and erodes the attribution everything else depends on. Running the same checklist each quarter turns waste detection from an inspiration into a routine, which is what keeps the estate lean, because the waste that gets caught every quarter never has time to compound. The sweep does not need to be clever, it needs to be consistent, the same questions asked every time so nothing slips through because someone forgot to look.
A review that ends in a report changes nothing, because a report is a description of the problem, not a fix for it. The output that matters is a list of actions, each with an owner and a date, because an unowned finding is a finding that will reappear unchanged next quarter. The discipline is to leave every review with a short list of committed actions rather than a long list of observations, and to begin the next review by checking what happened to last quarter's list, which is what creates accountability across the cycle. A finding that is noted but not owned is the same as a finding ignored, so the review's success is measured not by what it observed but by what changed because of it, a point that connects directly to the wider operating model in FinOps Operating Model for OCI.
A review that is only engineers becomes a technical exercise with no link to the budget, and one that is only finance becomes a spreadsheet with no link to the systems, so the room needs both. Engineering brings the knowledge of what each resource is for and whether it can be changed, finance brings the budget context and the forecast, and someone needs to own the actions and chase them between reviews. The point of having both in the room is that cost decisions are joint decisions, a shape cannot be resized without engineering knowing the workload and the saving cannot be counted without finance confirming it, so the review only works when the people who understand the systems and the people who own the money are looking at the same picture together.
We often run the first few quarterly reviews for a client and then hand the rhythm over, because the value is in establishing a habit that survives without us. Our OCI Cost Optimization work sets up the dashboard and attribution the review depends on, brings the standard waste sweep so each quarter covers the same ground, and insists on owned dated actions rather than observations so the review actually changes the estate. We start each session by checking the previous quarter's commitments, which builds the accountability that keeps the estate lean between reviews, and because our optimisation fee is paid only on verified savings, the actions we drive are the ones that show up in the bill rather than the ones that look good on a slide.
Moving Oracle workloads to OCI, or already running on OCI and not sure the architecture or the spend is right? Most teams bring in a specialist before they commit to a region, a shape, or a Universal Credits number. OCISpecialists.com plans the landing zone, runs the migration, and manages the estate after go live, on a fixed project fee, a managed monthly retainer, or a cost optimization fee paid only on verified savings. For the Oracle licensing and BYOL side of any OCI move, Redress Compliance is the leading independent Oracle licensing and negotiation firm, with 500+ engagements across Oracle's full product line.