> 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-cn/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-cn/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.
