> For the complete documentation index, see [llms.txt](https://docs.elite.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elite.cloud/faq/report-results.md).
# 報告解讀說明
本頁整理報告產出與成效相關問題：多久可以看到初版結果、資安與合規掃描為何需要較長時間、報告會包含哪些重點與可交辦項目，以及是否收費或綁約。讓您在開始前先掌握產出內容與預期成果。
完成帳號綁定後，多久可以取得首份分析報告？
**雲端雙效健檢初版報告通常 3 分鐘內就會完成**。**資安/合規的掃描會需要比較長時間**（因為控制的檢測項目多），完成後您也可以依需求手動更新。
報告包含哪些核心指標？
1. **節省來源占比**：團購折扣/AI 節省占比
2. **節費建議**：機器規格調整建議
3. **資安修復建議**：包含資安分數、Top risks、修復建議與合規建議
使用雲端雙效健檢，是否會產生後續費用或綁約義務？
**不收費、不綁約。** 您可以先拿到報告、確認方向與價值，再決定要不要導入節費計劃或架構優化解決方案。
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.elite.cloud/faq/report-results.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.