> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/zh-hk/performance-appraisal/appraisal-results.md).
# 考核結果
## 1. 考核結果分析
* 完成考核後，在考核結果分析頁面中，可見被考核員工的等級和人數，管理員亦可用名字和部門搜尋員工並查看詳情。
## 2. 員工績效檔案
* 可見詳列被考核員工的績效資料，參與過績效考核的員工將顯示相關統計數據，管理員亦可選擇導出檔案。
## 3. 績效面談記錄
* 可見詳列被考核員工的面談狀態和記錄，管理員亦可選擇導出檔案。
## 4. 年度統計表
* 年度統計表詳列被考核員工的考核記錄，並可按年度/半年/季度/月份搜索，方便管理員快速查找。
---
# 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.coreway.com/coreway-hr/zh-hk/performance-appraisal/appraisal-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.
