> 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/work-acknowledgments-on-a-job.md). # Work acknowledgments on a job A work acknowledgment is a form a customer completes to acknowledge the work performed on a visit - typically capturing a signature (and sometimes photos) - recorded against the visit and surfaced here on the job. Work acknowledgments must be enabled for your business before this tab or related mobile actions appear. On the job page, open the Work Acknowledgments tab to see every acknowledgment tied to this job. Each row shows the date it was created, the date it was submitted (if it has been submitted), and the attached files. When a single file is attached you can open it directly from the row to view the signed document. This tab is a read-only list for reviewing what has been collected. On the related job task, a single work acknowledgment appears as a filename with a send icon beside it. When there are multiple files, the **Work Acknowledgments** card lists them in separate rows, newest first, with a file count in the header. Click a filename to preview it, download it, or move between the other files. Below the files, **Acknowledgment items** shows the saved part numbers, descriptions, and quantities. **Acknowledgment notes** appears when the acknowledgment description differs from Tech Visit Notes. These entries let the office compare what the customer acknowledged with the submitted summary, even when a PDF template does not print part numbers. For older records that cannot be displayed here, open the PDF. If no item usage is recorded for the job, a reminder asks you to review the acknowledgment before invoicing. These entries do not add quantities to the job automatically. Check the recorded job items and any existing invoices before making corrections, to avoid billing the same parts twice. Use the send icon beside a single file, or **Send** in the header when there are multiple files, to share the task’s visit through Job Summaries, or to email its signed work acknowledgment directly when Job Summaries are unavailable. The email history below the files shows recipients of direct work acknowledgment emails for that visit; click the recipient count to expand it. When the acknowledgment form is configured to do so, any photos captured are also added to the job's files; the signature itself stays with the acknowledgment. If no acknowledgments have been created for the job yet, the tab count shows zero and the list is empty. Admins can turn Work Acknowledgments on or off and customize the generated PDF and customer email from Settings. Disabling the module hides new collection actions but does not remove acknowledgments already collected on jobs. > **Where to find it:** Open a job from Scheduling > Jobs; select the Work Acknowledgments tab in the tabbed panel ## Related guides * [Clock in and clock out records on a job](/customers-and-work/jobs/clock-in-and-clock-out-records-on-a-job.md) * [Job inventory: reserved vs used parts, transfers, and shortages](/customers-and-work/jobs/job-inventory-reserved-vs-used-parts-transfers-and-shortages.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) * [Enable and customize Work Acknowledgments](/administration/settings/enable-and-customize-work-acknowledgments.md) * [Feature availability and setup](/getting-started/getting-started/feature-availability-and-setup.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/work-acknowledgments-on-a-job.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.