Report types and statuses

CloudEval uses two related report concepts:

Report payloads are generated outputs such as cost, architecture, and template or unit-test style results.
Cloud Evaluation report tabs are the end-user review surface that combines payloads with project context, inventory, evidence, confidence, freshness, and exports.

Cloud Evaluation report tabs

Tab	Purpose	Common fields
Brief	Stakeholder readout and first-pass triage.	Posture score, critical count, run rate, savings, maturity, confidence, freshness, assumptions, and warnings.
Action Plan	Prioritized remediation and decision planning.	Finding, severity, owner, effort, target date, confidence, business impact, suggested action, and drilldown links.
Architecture & Dependencies	Architecture quality and dependency review.	Well-Architected pillar signals, dependency context, affected resources, graph links, and design recommendations.
Security & Compliance	Security-themed findings and evidence review.	Control context, confidence, source evidence, related resources, and remediation guidance.
Cost & FinOps	Cost exposure and optimization review.	Monthly run rate, annualized context, savings opportunities, service family breakdowns, pricing assumptions, and unmatched resources.
Resources	Resource-level inventory behind the report.	Resource identity, type, provider, region, resource group, status, severity, issue count, cost, savings, evidence, and primary action.
Evidence & Progress	Trust, freshness, and change context.	Source artifacts, warnings, assumptions, evidence links, trend snapshots, and report history where available.

Payload families

Cost

Cost payloads can include:

daily, weekly, monthly, and annualized values
currency and region
service-family breakdowns
resource-level cost context where available
savings opportunities
pricing assumptions, usage assumptions, and unmatched resources

Architecture and Well-Architected

Architecture payloads can include:

overall posture or score
pillar scores
critical and high-severity findings
category and resource-type breakdowns
dependency and graph context
remediation recommendations

Unit tests and template validation

CloudEval also tracks unit-test or template-style statuses in supported workflows. These are most useful for IaC review, CI, imported template validation, and pre-deployment checks. They may contribute pass/fail context, source-file references, and evidence to the report experience.

Status values

Across sync and report families, CloudEval uses these operational states:

Status	Meaning
`pending`	The sync, evaluation, or report run has been requested but is not finished.
`completed`	The run finished and produced usable output.
`failed`	The run did not produce usable output. Review the project or troubleshooting details before relying on the report.

Higher-level reporting summaries can also bucket freshness as:

Freshness	Meaning
`fresh`	The backing snapshot is recent enough for normal review.
`stale`	The report may still be useful, but the team should confirm whether the project changed.
`outdated`	Do not use the report for a high-stakes decision without rerunning or refreshing the project.
`missing`	CloudEval does not have the expected report or snapshot for that area.

Export depths and formats

Report exports can be generated for different audiences.

Depth	Use it for
Brief	Concise stakeholder readouts, status updates, and meeting prep.
Detailed	Team review, remediation planning, and technical decision support.
Evidence	Audit-style review, source-backed handoff, and deeper engineering investigation.

Format	Use it for
PDF	Shareable report packet or meeting attachment.
Markdown	Internal docs, issue trackers, PR summaries, and team notes.
JSON	Automation, archival, and downstream analysis.

Why freshness and confidence matter

Freshness is the difference between an informative project and a misleading one. If a share page is backed by an old report snapshot, it can create false confidence even when the report itself looks polished. Confidence explains how strongly CloudEval can stand behind a recommendation. A high-severity finding with weak evidence should be reviewed differently from a high-confidence finding tied to a specific resource, source artifact, and remediation path.

Next step

Use Review report findings for a practical review flow, Reports for the end-user model, or Feature matrix for rollout decisions.

Trust and limits

Platform reference

Cloud Evaluation report tabs

Payload families

Cost

Architecture and Well-Architected

Unit tests and template validation

Status values

Export depths and formats

Why freshness and confidence matter

Next step

​Cloud Evaluation report tabs

​Payload families

​Cost

​Architecture and Well-Architected

​Unit tests and template validation

​Status values

​Export depths and formats

​Why freshness and confidence matter

​Next step

Cloud Evaluation report tabs

Payload families

Cost

Architecture and Well-Architected

Unit tests and template validation

Status values

Export depths and formats

Why freshness and confidence matter

Next step