> 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/field-operations/tasks/what-creates-jobs-tasks-and-moving-them-between-folders.md). # What creates Jobs tasks (and moving them between folders) Jobs tasks come from how a technician ends a visit. In the mobile app a technician must add a visit summary before they can clock out, and in that summary they choose which folder the job goes to: Complete (Ready to Invoice), Complete (No Invoice Needed), or Incomplete (Needs Another Visit), plus any close-out folders your business has added. Your business can rename these folders and add its own on the Jobs tab of Tasks settings; see [Customize your Jobs task folders](/administration/settings/customize-jobs-task-folders.md). Missing Summary is the exception: if a technician never added a summary they never clocked out, so a background job clocks them out and files the visit under Missing Summary. Never Clocked In is created by a background job when no one ever clocked into the visit at all — 24 hours after the visit's scheduled start, or at midnight in your business's timezone if you [choose that instead](/administration/settings/choose-when-never-clocked-in-tasks-are-created.md). When a technician submits the visit summary, its selected Job Status takes priority. This is also true on a multi-technician visit when another assigned technician did not clock in or out. If the background job filed a Missing Summary or Never Clocked In flag before the summary arrived, the submitted summary moves that same task to the selected Jobs folder instead of creating another task. To clear a Jobs task, mark it done by moving its status to a done stage, or move it to a different Jobs folder using **Move to Folder** in the task's Quick Actions. The move picker offers the built-in close-out folders and your business's added close-out and standalone folders, including folders in custom task categories. For tasks still in Missing Summary or Never Clocked In, it offers only the built-in close-out folders; custom destinations become available after the technician submits a summary. The Missing Summary and Never Clocked In folders are filled only by the background job. A Missing Summary task is just a flag that no summary was captured, so whether you mark it done or move it is up to you — and if the technician later submits the visit summary anyway, that submission moves this same task into the folder they choose instead of creating another one. Every task type can also move into custom folders and back to its original folder through the same action; see [Organize task categories and folders](/administration/settings/organize-task-categories-and-folders.md). Moved tasks keep their existing details and Quick Actions. > **Where to find it:** Tasks page, the Jobs group in the left sidebar; the move action is in a task's Quick Actions ## Review technician time **Time per Technician** in the task overview totals each technician’s recorded work and travel time across the job’s visits. When travel is recorded, a breakdown shows **Onsite** and **Travel** separately. Totals include clock corrections and exclude removed entries. An unfinished work entry is labeled **Still clocked in**, and ongoing travel is labeled **On the way**; totals include completed entries only. ## Review parts, labor, and items **Parts, Labor & Items** shows actual **Used** quantities across the job's visits, including fractional labor and one-off items. These remain visible with Inventory off, without stock warnings or reservation controls. The scheduling plan is separate from actual usage. With Inventory on, the table also shows **Location**, **Reserved**, and **Edit**. If actual usage differs from stock usage, a note such as **2 from inventory** appears below the total Used quantity. For example, 4 used with 2 from inventory means only 2 were deducted from tracked stock; usage recorded while Inventory was off is still included in the total. To adjust items with Inventory on: 1. Choose **Edit** in the section. 2. Adjust stock quantities in the inventory table. **Used** in this editing table counts stock usage only. Adjust labor or one-off quantities in the separate table below; removing a row removes only that actual entry. 3. Choose **Save**, or **Cancel** to discard the draft. Leaving Edit returns to the total actual-usage view. If Inventory was off when a tracked item was recorded, it may not have an inventory link yet. It stays visible under **Other recorded items**, but its task quantity is read-only. Correct its usage in the visit summary. To manage its inventory from the task, add the item to the scheduling plan and save. If the task cannot confirm an item's tracking, refresh it before editing. See [Job inventory](/customers-and-work/jobs/job-inventory-reserved-vs-used-parts-transfers-and-shortages.md) for reservations and stock corrections. ## Review asset group changes When a technician adds or deletes an asset group, adds, edits, or removes an asset (from Visit Details or by submitting an inspection report for the visit), or adds or edits a recurring service from a visit in the mobile app, the job's task shows an **Asset Group Changes** section between Parts, Labor & Items and Recurring Service Completions. It stays one line however much changed — for example *1 asset group added · 12 assets added · 120 attributes updated · 1 recurring service updated* (attribute edits count per attribute, and a recurring service edited more than once counts once). Choose **View details** to open the changes grouped by asset group: each group's name links to its page and timeline; group and service changes are listed as phrases (for example *Recurring service Annual Inspection (every 2 Years) updated on Fire Alarm "Lobby panel" from the visit*), and asset changes roll up into one line per group (for example *120 attributes updated on 12 assets*), so a large field edit never floods the task. A technician's name appears on a line only when the visit had more than one technician or someone other than the visit's technician made the change; times are on the asset group's and the job's timelines. Each Jobs task shows the changes made from its own visit (a job with several visits has a task per visit); the same entries are also on the job page timeline, and a group that has since been deleted is listed without a link. The section only appears when at least one change was made from the visit. See [Manage asset groups and recurring services from a visit](/field-operations/mobile/manage-asset-groups-and-recurring-services.md). ## Related guides * [Customize your Jobs task folders](/administration/settings/customize-jobs-task-folders.md) * [How tasks are created and organized](/field-operations/tasks/how-tasks-are-created-and-organized.md) * [Quick Actions on a task: create a visit, invoice, or quote without leaving the task](/field-operations/tasks/quick-actions-on-a-task-create-a-visit-invoice-or-quote-without-leaving-the-task.md) * [The Tasks inbox: folders, status filters, and search](/field-operations/tasks/the-tasks-inbox-folders-status-filters-and-search.md) * [What creates Deficiencies tasks](/field-operations/tasks/what-creates-deficiencies-tasks.md) * [What creates Invoices tasks](/field-operations/tasks/what-creates-invoices-tasks.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/field-operations/tasks/what-creates-jobs-tasks-and-moving-them-between-folders.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.