How to approve and verify a savings action

Roles and Guardrails

Allowed roles: Admin, FinOps, Security. Action requests go through conflict checks, and most actions default to manual approval mode.

Execution Workflow

1. 1. Open the action from `Today`, `Savings`, or the supporting finding view.
2. 2. Confirm monthly savings, impacted resource, owner, confidence, and recommended action type.
3. 3. Submit action request (or execute now if policy allows).
4. 4. Approve request if pending approval chain.
5. 5. Track status in `Actions` until `completed` or `failed`.
6. 6. Re-scan the scope when the provider action changes cloud state, then watch the receipt checkpoints.

Conflict Checks

Before execution, TurboFinOps checks for IaC ownership tags, freeze windows, policy protection flags and ticket requirements. If a conflict is detected, the action is blocked or sent back for explicit Admin review depending on organization policy.

Verification

• Action execution contains provider response metadata.
• Savings baseline is captured before or during the action workflow.
• Receipt checkpoints verify 7/14/30-day observed cost deltas.
• Audit logs include actor, correlation ID, and execution timestamps.
• Receipt, evidence, or export records can be generated for finance and audit review.

Rollback Path

For compatible actions, rollback plans are attached to execution records. Use rollback controls from `Actions` page to restore previous state when needed.