> 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/job-summary-questions.md).

# Job summary questions

Ask your technicians custom questions when they submit a job summary from the mobile app. Their answers appear on the job's task in the office, so the team reviewing the job sees them alongside the tech's visit notes.

> **Where to find it:** Settings > **Technician App** — the **Additional Questions** card, just below the Job summary switches.

## Before you start

* You need settings admin access to add or edit questions.
* Technicians answer the questions on the **Job / Visit Summary** screen in the mobile app when they finish a job.

## Add a question

1. Go to Settings > Technician App and find the **Additional Questions** card.
2. Click **Add question**.
3. Write the question — for example, "Did you leave the site clean?"
4. Pick **Asked when**: ask on every job summary (**Any job status**), or only when the technician picks a specific job status — Job Complete (Ready to Invoice), Job Complete (No Invoice Needed), or Job Incomplete (Needs Another Visit).
5. Optionally pick a **Visit Type**. Leave **Any visit type** selected to ask the question on every kind of visit. When you select a type, the question appears only when the visit includes that type. If a visit has more than one type, matching any one of them is enough.
6. Pick the **Answer type**:
   * **Dropdown** — the tech picks one of the options you define. Add the options below the type picker.
   * **Yes / No**
   * **Short text** or **Long text**
   * **Number**
   * **Date**
7. Turn on **Required** if the technician must answer before they can submit the job summary.
8. Click **Save**.

The Job Status scope, Visit Type scope, and answer type can't change after the question is created. To change one of them, delete the question and create a new one. Existing answers remain available on their tasks.

## Reorder questions

Drag the handle at the left of each row to arrange the order technicians see, then click **Save order**. Questions appear on the mobile summary in this order. Dropdown options reorder the same way — drag them inside the question's edit modal.

## Job summary options

The **Job summary** section on the same Settings > Technician App page has two related switches:

* **Preselect the Job Status** — on by default. When on, the Job Status dropdown starts on "Job Complete (Ready to Invoice)". Turn it off to make technicians actively pick a status before they can save.
* **Require visit notes** — off by default. When on, technicians must enter Visit Notes before submitting the job summary.

## What technicians see

When a technician submits a job summary, the questions matching both their selected job status and the visit's current Visit Types appear between the Job Status picker and Visit Notes. Required questions are marked with an asterisk, and the summary can't be saved until they're answered.

## Where answers show up

Answers are saved with the job task created by the summary. Open the task from the Tasks inbox — each question appears with the technician's answer in the task's details.

## Edit or delete a question

* **Edit** changes the question text, whether it's required, and (for dropdowns) the options. Renaming an option updates it everywhere. Removing an option only stops it from being offered — answers that already used it keep showing on their tasks. To change the Job Status, Visit Type, or answer type, delete the question and create a new one.
* **Delete** stops the question from being asked. Answers technicians already gave stay on their tasks.

## Related guides

* [Working a task: changing its status and saving notes](/field-operations/tasks/working-a-task-changing-its-status-and-saving-notes.md)
* [What creates Jobs tasks and moving them between folders](/field-operations/tasks/what-creates-jobs-tasks-and-moving-them-between-folders.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/field-operations/tasks/job-summary-questions.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.