> 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-management/appraisal-details.md). # 考核詳情 ## 1. 查看考核詳情 * 操作步驟： \ ［智能績效］>［考核管理］>［發起考核］>［查看詳情］

## 2. 考核詳情明細 **【考核人員】** 詳見被考核人員的狀態 **【工作達成記錄】** 詳見被考核人員 "未錄入/已錄入" 業務數據的狀態 **【考核結果】** 詳見被考核人員的考核結果，管理員可發起 "考核結果確認/ 確認完成/ 公示結果" **【績效面談】** 詳見被考核人員的績效面談狀態，管理員可添加需安排面談員工資料和時間，面談結束後可記錄面談結果，亦可"編輯/刪除" 資料

--- # 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-management/appraisal-details.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.