CoreFinOps Docs
On this page

Action Center Workflow

Move from recommendation to approved, implemented and verified outcomes.

CoreFinOps uses a controlled sequence: recommendation → action → approval → customer-confirmed implementation → verification → Value Ledger.

Create an action

An action should reference the supporting opportunity, affected AWS resource or workload, expected impact and currency, evidence, owner and implementation risk. Not every recommendation needs to be accepted; rejected or deferred decisions should remain auditable.

Request approval

Where policy requires it, an authorized reviewer must explicitly approve or reject the proposed work. Approval is not evidence that the customer has applied the change.

Confirm implementation

A user records that the work occurred outside CoreFinOps. The application does not need customer AWS write permissions for this workflow. Capture the relevant change time and supporting references.

Security

CoreFinOps does not need write permissions to AWS to support the Action Center workflow. Implementation confirmation is a human record — not an automated AWS operation.

Verify outcome

The verifier reviews baseline, post-change period, cost measure, currency and provenance. Customer-attested results must be labeled differently from independently measured financial outcomes.

Understand status

An action can be a pending decision, approved, implemented or under verification without creating verified savings. Only the governed outcome path should create a defensible ledger entry.