> 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/administration/settings/choose-when-never-clocked-in-tasks-are-created.md).

# Choose when Never Clocked In tasks are created

When nobody clocks into a scheduled visit, Essential files it as a Never Clocked In task in the Jobs group. This setting controls how long Essential waits before doing that.

> **Where to find it:** Settings -> Technician App -> Scheduling -> Missed visits

1. Under **When to create Never Clocked In tasks**, keep **24 hours after the visit's start time** for the default. A technician who reaches a late-evening visit after midnight is still counted as having worked it.
2. Choose **Midnight after the visit ends** to have the task created at midnight in your business's timezone instead, so every no-show from the day is waiting for you the next morning. A visit that runs past midnight waits for the following night, so an overnight job is never flagged while it is still running.
3. Click **Save**.

This uses the business timezone Essential has on file for your business.

The setting changes only when the task appears. Technicians keep the same 24 hours to clock into a visit late either way, so with the setting on a technician can still clock in after the task has been filed — mark that task done if the visit turns out to have been worked.

Tasks are created by a background job that runs every hour, so a task can appear up to an hour after the deadline passes.

## Related guides

* [What creates Jobs tasks (and moving them between folders)](/field-operations/tasks/what-creates-jobs-tasks-and-moving-them-between-folders.md)
* [Task folder and subfolder meanings](/field-operations/tasks/task-folder-and-subfolder-meanings.md)
* [Add, rename, reorder, or remove task statuses](/administration/settings/add-rename-reorder-or-remove-task-statuses.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/administration/settings/choose-when-never-clocked-in-tasks-are-created.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.