06 — Cost and FinOps Checklist#

Verify that technology spending is attributable, visible, forecastable, and optimized for business value without compromising required quality, reliability, security, or user outcomes. FinOps is a shared product, engineering, finance, and procurement practice—not simply a directive to minimize the cloud bill.

Scope: Shared / cross-cutting. This file is one part of the 06_Cost_and_FinOps.md checklist. Apply the domain-wide release gate across all applicable scope files; each checklist ID remains unique.

Review details#

• Project / product:
• Release / version / environment:
• Scope and applicable jurisdictions / markets:
• Cost scope / providers / billing currency:
• Budget, forecast, and allocation policy references:
• FinOps / product / engineering / finance owners:
• Reviewer / owner:
• Review date:
• Decision: Pending / Approved / Approved with documented exceptions / Blocked

How to use#

1. Copy this reusable checklist into project-specific review records; leave the shared template unchecked.
2. Mark [x] only after verification from provider billing data, ownership metadata, cost forecasts, approved budgets, utilization measurements, unit metrics, or documented decisions. Record failed checks and genuine N/A rationales in project-specific notes or issues using their COST IDs; do not add evidence tables to this repository template.
3. Tailor controls to the technology costs that apply: cloud resources, SaaS, licenses, data platforms, vendor APIs, AI inference, or on-premises infrastructure. Not every project uses commitments, multiple providers, chargeback, or business-unit unit economics.
4. Review ## API Checks and ## Frontend Checks independently where relevant. If one surface does not exist, document N/A and why in project records.
5. Revisit cost baselines, forecasts, allocation rules, and guardrails after major demand, architecture, provider, contract, pricing, or launch changes. Review material contractual and financial decisions with qualified stakeholders.

Cost ownership and allocation#

• COST-001 Inventory all material technology costs for the product, including cloud infrastructure, SaaS subscriptions, data platforms, licensing, AI services, and contracted support where relevant.
• COST-002 Assign an accountable product or business owner and an engineering owner for each material spending scope.
• COST-003 Document the cost allocation hierarchy across accounts, projects, subscriptions, environments, cost centers, products, and teams.
• COST-004 Define a versioned naming and tagging/labeling policy that makes resource ownership, environment, and cost center discoverable.
• COST-005 Apply ownership and allocation metadata when provisioning new resources rather than depending only on retrospective cleanup.
• COST-006 Check tag or label completeness and accuracy for a representative sample of cost-bearing resources.
• COST-007 Identify services whose spend cannot be directly attributed and maintain a documented process to investigate unallocated charges.
• COST-009 Document the chosen method for allocating shared costs, or explicitly decide to retain them in a central budget.
• COST-010 Validate shared-cost allocations reconcile to the underlying charge without double counting or omitted amounts.
• COST-011 Distinguish directly metered costs from allocated, estimated, or centrally funded costs in reports.
• COST-012 Identify how credits, discounts, taxes, support fees, marketplace charges, and commitments are distributed for the reporting purpose.
• COST-013 Maintain clear definitions for billed, effective/amortized, list, and contracted costs where these differ.
• COST-014 Ensure invoices, provider billing exports, and cost reports use compatible billing periods, currencies, and cost semantics.
• COST-015 Verify that financial chargeback figures can be reconciled to the relevant ledger or approved invoiced totals.
• COST-016 Document how newly launched services, regions, environments, and vendors are added to the allocation model.
• COST-017 Track allocation coverage and report material cost with missing, invalid, or conflicting ownership metadata.
• COST-018 Review ownership after personnel, organizational, product, or environment changes so orphaned resources do not remain unassigned.
• COST-019 Set access controls so each owner can see their costs without exposing unrelated customer or financial data.
• COST-020 Agree ownership and escalation for unusual spend that spans multiple business units or shared platform dependencies.

Budgets and visibility#

• COST-021 Define a budget for the product or workload with accountable approval, billing period, currency, and scope.
• COST-023 Separate recurring run-rate spend from one-time setup, migration, licensing, training, and exceptional project costs.
• COST-024 Distinguish current cash/billed costs from amortized commitment costs when those values support different decisions.
• COST-025 Set a clear reporting cadence for cost owners and finance partners suited to spend volatility.
• COST-026 Provide views by owner, product, environment, provider, service, and major cost driver where supported by source data.
• COST-027 Document data freshness, export lag, estimated charges, and known inaccuracies before using dashboards for budget decisions.
• COST-028 Validate the primary cost dashboard against provider billing data or accepted finance records at an agreed frequency.
• COST-029 Calculate budget variance and explain both volume-related and unit-price-related cost differences.
• COST-030 Monitor cumulative spend, expected end-of-period spend, and material changes in daily run rate.
• COST-031 Configure budget threshold alerts and verify that they reach an accountable team through tested channels.
• COST-032 Use anomaly detection or equivalent checks to identify unusual cost spikes that a static threshold might miss.
• COST-033 Define which spend anomalies require immediate action versus routine financial review.
• COST-034 Track anomaly investigations with owner, suspected cause, financial exposure, decision, and resolution date.
• COST-035 Confirm alerts account for legitimate release events, planned load tests, seasonal traffic, and known provider reporting delays.
• COST-036 Set guards for high-risk provisioning actions, expensive services, quotas, and unrestricted external usage where feasible.
• COST-037 Define financial escalation and exception procedures for forecast overruns and urgent increases in capacity.
• COST-038 Keep budget and cost views distinguishable from user-facing pricing, revenue, and gross-margin reporting.
• COST-039 Document assumptions in currency conversion, billing increments, and taxes for cross-provider comparisons.
• COST-040 Periodically verify that reporting includes dormant accounts, subscriptions, SaaS seats, and decommissioned resources.
• COST-041 Apply role-appropriate permissions to cost exports, budgets, invoices, and billing configuration.
• COST-042 Define a process for correcting historical allocations and notifying affected stakeholders when material reports change.

Usage efficiency#

• COST-043 Identify the top cost drivers by service, operation, environment, resource, tenant, or workload segment.
• COST-044 Compare observed utilization and service objectives before changing instance sizes, capacity, or redundancy.
• COST-046 Schedule shutdown or reduced capacity for eligible nonproduction environments while preserving needed availability.
• COST-047 Review resource requests, limits, reservations, and autoscaling thresholds against measured traffic and saturation.
• COST-049 Evaluate storage growth, access patterns, object versions, temporary data, backups, and lifecycle rules for avoidable cost.
• COST-050 Optimize data retention, archival, compression, and tier selection without violating recovery, privacy, or compliance requirements.
• COST-052 Reduce unnecessary polling, redundant queries, chatty interfaces, and repeated high-cost computation on critical flows.
• COST-054 Consider batch processing, queueing, deduplication, and event-driven approaches where they lower cost without unacceptable latency.
• COST-055 Evaluate how third-party API usage, tokens, requests, and model selection affect variable service costs when applicable.
• COST-056 Apply safe usage ceilings or budgets to expensive user-triggered operations without unexpectedly breaking essential functionality.
• COST-057 Review autoscaling, graceful overload behavior, and traffic shaping to avoid runaway resource expansion.
• COST-059 Ensure shared services charge or attribute usage sufficiently to expose high-cost consumers when technically and financially appropriate.
• COST-060 Compare optimized configurations under representative load, measuring cost and performance rather than cost alone.
• COST-061 Verify cost reductions preserve agreed reliability, security, privacy, accessibility, and customer-experience requirements.
• COST-062 Remove obsolete artifacts, test data, build caches, and environments according to retention and recovery policies.
• COST-063 Track sustainability or energy-efficiency considerations when they are an explicit business objective, without claiming cost automatically equals emissions.
• COST-064 Document savings estimates separately from realized spend reduction, cost avoidance, and rate improvements.

Forecasting and optimization#

• COST-065 Maintain a rolling cost forecast with an owner, horizon, update cadence, and documented methodology.
• COST-066 Use historical spend, workload demand, pricing, deployments, and known business changes as forecast inputs.
• COST-067 Model at least expected and higher-demand scenarios for material variable cost drivers.
• COST-068 Record major forecast assumptions, uncertainty, confidence limitations, and known discontinuities.
• COST-069 Compare actual spend against prior forecasts at a consistent cadence and update the model when drivers change.
• COST-070 Define financially meaningful unit metrics such as cost per successful transaction, active customer, inference, or processed gigabyte where applicable.
• COST-071 Specify numerator, denominator, unit, included direct/shared costs, timeframe, and source for each cost-per-unit metric.
• COST-072 Reconcile cost data with product usage measures before interpreting unit economics or margin movements.
• COST-074 Estimate incremental cost of new features, markets, customers, data growth, and release traffic before approval.
• COST-075 Review alternative architectures, services, regions, and pricing tiers against workload constraints and switching effort.
• COST-076 Analyze on-demand versus commitment-based rates only after forecasting reasonably stable eligible usage.
• COST-077 Validate reservation or commitment utilization and coverage and identify unused or expiring commitments.
• COST-078 Include commitment lock-in, prepayment, minimum spend, cancellation terms, and projected demand uncertainty in purchasing decisions.
• COST-079 Review vendor contracts, SaaS licenses, seat counts, tiers, and renewal dates for unused or poorly matched capacity.
• COST-080 Calculate expected payback, engineering effort, risk, and opportunity cost before prioritizing a material optimization.
• COST-081 Document a baseline and verification method before asserting that an optimization produced savings.
• COST-084 Assign optimization initiatives owners, expected impact, completion dates, and post-change measurement.
• COST-085 Include shutdown, migration, exit, or data-transfer costs in decisions to consolidate or change providers.
• COST-086 Reassess financial targets periodically as product strategy, margin, customer value, and reliability needs change.

Release gate#

• The release has named product, engineering, and financial owners for its material technology costs, with an approved allocation approach for shared and direct costs.
• Budget, baseline, forecast, principal assumptions, and potential cost-impacting launch or growth scenarios are documented at an appropriate level of detail.
• Critical spending and usage reports reconcile to trusted provider or financial data within accepted tolerances, and material unallocated charges are explained or assigned for investigation.
• Budget threshold, unusual-spend, and quota alerts or equivalent guardrails have owners and a tested escalation route appropriate to release risk.
• Significant compute, storage, data-transfer, SaaS, API, and frontend cost drivers are reviewed for avoidable use without undermining performance, accessibility, security, or reliability commitments.
• Applicable API and frontend operations have controls against unbounded or duplicate billable actions, with appropriate behavior when quotas or limits are reached.
• Any material over-budget forecast, unaffordable unit economics, unapproved commitment, or other significant cost risk has an explicit authorized disposition and remediation owner.

Domain-specific approval rule: Block cost readiness approval if material spend is unowned and invisible, foreseeable high-impact cost exposure lacks acceptable bounds, or a required budget/contract approval is missing. Meeting a cost target does not justify bypassing legal, security, quality, accessibility, or reliability requirements.

Trusted references and scope#

These review questions are informed by the following primary FinOps and architectural guidance. Source recommendations are not universal compliance obligations; adapt them to the workload and commercial model.

• FinOps Foundation — FinOps Framework — cross-functional technology cost accountability, value, and operating model.
• FinOps Foundation — Allocation — cost ownership, tagging and hierarchy, shared cost treatment, and allocation coverage.
• FinOps Foundation — Anomaly Management — detection, routing, investigation, and resolution of unplanned spend.
• FinOps Foundation — Forecasting — forecast models, business drivers, scenarios, and variance tracking.
• FinOps Foundation — Unit Economics — aligning technology unit costs to product/business outcomes.
• FOCUS — FinOps Open Cost and Usage Specification 1.3 — standardized billing vocabulary and cost/usage data when compatible datasets are used.
• FOCUS — Cost and Usage dataset — distinct billed, effective, contracted, and list cost fields; billing period and metadata.
• Microsoft Azure Well-Architected — Cost Optimization checklist — financial responsibility, budgets, guardrails, unit cost, utilization, optimization, and trade-offs.
• Microsoft Azure Well-Architected — Cost Optimization — usage, rate, and continuous optimization principles.

Applicability: FOCUS 1.3 provides a published data specification, not an assertion that every provider export is FOCUS 1.3-compatible or that 1.3 is the newest version. Cloud-specific rate models and tagging practices do not apply unchanged to every SaaS, AI, data center, or on-premises product. Account for billing delays, discounts, currency, shared services, and business value before claiming realized savings.

Source review date: 2026-11-12.

Suggested testing tools#

Choose tools appropriate to the project's stack and risks; automation supports evidence but does not approve the checklist.

• Test focus: usage tagging, budget alerts, cost estimates, and anomaly scenarios; include shared/cross-team controls where applicable.
• Cross-stack: Infracost.
• Python: Cloud Custodian + pytest; for pytest-based suites, run python -m pytest -q.
• TypeScript: Vitest; for Vitest-based suites, run npx vitest run (or npx playwright test for E2E).
• JavaScript: Jest; for Jest-based suites, run npx jest --ci (or npx playwright test for E2E).
• Evidence: Save tool versions, configuration, test environment, fixtures, results, and links in project-specific review records using the existing checklist IDs. Expert review remains necessary where relevant.

Suggested AI skills for verification#

These are optional agent review aids, not automated passes or release approval. Each linked repository had at least 1,000 GitHub stars when checked on 2026-11-12; counts are per repository, not per skill, and do not indicate security or correctness.

• cost-optimization — Review resource costs and attribution (wshobson/agents, 42,437 repo stars).
• cost-analysis — Review Azure cost data when applicable (microsoft/skills, 3,198 repo stars).
• aws-cost-optimize — Review AWS spending where applicable (github/awesome-copilot, 41,073 repo stars).

How to check: In a project-specific copy, have the agent audit the shared / cross-cutting scope and map findings to this file's existing checklist IDs, with code/configuration references, reproducible test results, failed or inapplicable cases, and uncertainties. Independently verify findings; keep shared template boxes unchecked and retain human approval requirements.

Before use: Read the skill's SKILL.md, referenced scripts, license, and requested tool permissions. Only execute vetted skills with appropriate access in a controlled environment.

Important warning: reference only#

⚠️ Reference only — not a definitive or exhaustive checklist. This template is a starting point for review, not the ultimate authority or a guarantee of project safety, quality, regulatory compliance, accessibility, security, or launch readiness.

Use project-specific judgment and independent verification. Requirements and risks evolve and differ by project, technology, and jurisdiction. Adapt the checks, consult current authoritative sources, perform relevant tests, and obtain qualified specialist review or approval when appropriate. Checking every box does not replace these steps.