> 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/faq/attendance-check-in/what-is-the-difference-between-check-in-clock-in-and-field-clock-in.md).

# \[考勤打卡] 簽到、打卡及外勤打卡有什麼分別？

**＂簽到＂**&#x7684;用處是員工報告身處的位置，讓管理員或上司知道員工到達的地點和時間。因此系統不會根據簽到的時間而計算遲到或列入其他考勤資料。

例子一：

員工A任職保險從業員，上班當天被派往上環見客。員工A到達目的地後，可以使用＂簽到＂功能，讓上司可以得知員工A的確實位置及時間。<br>

**＂打卡＂**&#x662F;用於記錄員工的上下班時間。員工打卡後記錄會直接列入考勤資料，如遲到、早退及缺勤等。

例子二：

員工A上班時間為上午9時至下午6時，下午1時會到中環置地廣場見客。員工A需要先在上午9時考勤打卡，下午1時在中環置地廣場簽到，下午6時再進行考勤打卡。

**＂外勤打卡＂**&#x9069;用於如果員工是在見客之後，不用回公司，可以直接下班的話，管理員可以開啟「允許外勤打卡」的設定：當員工身處於指定Wi-Fi和指定GPS範位以外（例：外出見客），員工仍可打卡，而系統會將相關的打卡記錄標誌為「外勤打卡」，系統亦會自動記錄員工的打卡地點和時間。

<br>


---

# 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/faq/attendance-check-in/what-is-the-difference-between-check-in-clock-in-and-field-clock-in.md?ask=<question>&goal=<user_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.
