Recommendation workflow

Each savings recommendation moves through a simple status workflow, so the work stays visible and your savings totals stay accurate.

Statuses

A recommendation carries a status that reflects where it is:

• New — open and awaiting a decision.
• In review — you’re evaluating it but haven’t started the change.
• In progress — you’ve started acting on it but haven’t finished.
• Implemented — you’ve made the change; its estimated savings move into your banked total.
• Dismissed — you’ve decided not to act on it, so it stops cluttering the list.

The list’s Status filter defaults to Active, which shows everything except implemented and dismissed recommendations. Switch it to any single status — including Implemented or Dismissed — or to All statuses to see the full history.

Statuses only change when someone changes them — nothing moves automatically. Marking a recommendation implemented or dismissed asks for confirmation first; other status changes apply immediately.

Reviewing

Start from Savings & recommendations. Sort or filter the list — by minimum monthly savings, action type, account, or product — to focus on the opportunities worth your time, using the effort and confidence ratings to weigh quick wins against bigger projects.

Acting on a recommendation

When you make the underlying change (rightsize a resource, delete an idle one, or buy a commitment), mark the recommendation implemented. If it’s a multi-step effort, mark it in progress first so teammates know it’s underway.

Tracking banked savings

As recommendations move to implemented, their estimated savings shift from the open bucket into banked in the headline rollup. That’s how the Savings overview reflects the estimated savings you’ve committed to versus what’s still on the table — so keeping statuses current keeps the numbers honest.

Dismissing

If a recommendation doesn’t apply — the resource is intentionally over-provisioned, or the workload is being retired — mark it dismissed. It leaves the active list without being deleted, so the estimate stops counting toward your open savings.

Undoing an implemented or dismissed recommendation

Marking a recommendation implemented or dismissed hides it from the default Active view — it doesn’t delete it. To bring one back:

1. Set the Status filter to Implemented, Dismissed, or All statuses so the row reappears.
2. Change the row’s status back to New, In review, or In progress.

The recommendation returns to the active list immediately, and its estimated savings move back from banked (or out of dismissed) into your open total. Every status change — including a restore — is recorded in the recommendation’s status history, which you can view from the row at any time.

Note that restores are per-recommendation: the bulk “set all” action only moves active recommendations forward, so bring back implemented or dismissed items one at a time.

Paid feature

The recommendation workflow is available on paid plans; Free plans see a KPI peek of the savings totals. See Plans & billing.

You can drive this workflow through an AI agent connected to the CloudQuell MCP server — for example “mark recommendation rec-123 as implemented”, or to undo a decision, “set recommendation rec-123 back to new.” When updating a status you can also attach optional notes, a realized_savings figure, or a dismissed_reason. Status changes made through the MCP server require an explicit confirmation and a token with write access, so a read-only agent can review recommendations but never change them. See the MCP overview for how those scoped writes work.