> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/customers-and-work/jobs/clock-in-and-clock-out-records-on-a-job.md).

# Clock in and clock out records on a job

Technicians clock in and out while working a visit, and the job page collects those records on the Clock In / Clock Out tab. Each entry pairs a clock-in with its matching clock-out and shows the scheduled visit start time, the clock in and clock out times, the time spent, which technician it belongs to, and where the entry came from.

Records are organized per technician, so if more than one person worked the job you see each person's sessions separately, and a technician who clocked in and out several times will have a row for each session.

The Source column tells you what produced each row's hours:

* **Phone** — exactly what the technician's device recorded.
* **No clock out** — the technician clocked in and the session is still open, so it shows as Ongoing with no duration yet.
* **Edited** — the times were corrected, either by your back office from the job page or by the technician themselves from their own mobile timecard (when Time cards is on). Hover the label to read why.
* **Removed** — the session was taken off the job. The row stays visible, struck through, and its hours no longer count.
* **Manual** — time added by hand for work that was never clocked.

The Visits card on the same page also surfaces a clocked-in total for each visit and an overall total across the job, drawn from these same records, so you can see at a glance how much time has been logged.

If your business has Time cards turned on, this same clocked time also lands on the technician's timecard, valued at their cost rate on the Job Costing card. See [Review, approve, or send back timecards](/field-operations/timecards/review-approve-or-send-back-timecards.md).

With the Edit Clock In/Out permission you can fix these records without leaving the job — see [Edit a technician's clock in or clock out](/customers-and-work/jobs/edit-a-technicians-clock-in-or-clock-out.md). Without it, the tab is read-only.

> **Where to find it:** Open a job from Scheduling > Jobs; select the Clock In / Clock Out tab in the tabbed panel

## Related guides

* [Edit a technician's clock in or clock out](/customers-and-work/jobs/edit-a-technicians-clock-in-or-clock-out.md)
* [Job inventory: reserved vs used parts, transfers, and shortages](/customers-and-work/jobs/job-inventory-reserved-vs-used-parts-transfers-and-shortages.md)
* [Job Costing on a job: revenue, costs, and margin](/customers-and-work/jobs/job-costing-on-a-job.md)
* [Link quotes and invoices to a job](/customers-and-work/jobs/link-quotes-and-invoices-to-a-job.md)
* [Recurring service completions on a job](/customers-and-work/jobs/recurring-service-completions-on-a-job.md)
* [The job detail page: what it shows](/customers-and-work/jobs/the-job-detail-page-what-it-shows.md)
* [What is a job, and how does the Jobs list work?](/customers-and-work/jobs/what-is-a-job-and-how-does-the-jobs-list-work.md)


---

# 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://learn.withessential.com/customers-and-work/jobs/clock-in-and-clock-out-records-on-a-job.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.