> 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.

The acknowledgments themselves are produced and sent from the related job task - opened from that task you can email an acknowledgment request to the customer's contacts - not from this page. Once a customer completes one, it appears here with its submitted date filled in.

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.withessential.com/customers-and-work/jobs/work-acknowledgments-on-a-job.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
