> 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/use-ai-on-a-project.md).

# Use AI on a project: the AI summary, suggested items and Add update

AI helps with three parts of a project. It points out what the project's records say beyond what the page already shows, suggests items the project checklist is missing, and turns an emailed or texted update into proposed changes. It only summarizes and suggests: nothing on the project changes until a person approves it, and AI never creates a visit or an invoice.

> **Where to find it:** Scheduling > Jobs, open the job. The AI summary is at the bottom of the **Project Overview** card in the right column, **Suggested items** is below the job's summary panel (when there are suggestions), and **Add Update** is in the ⋮ menu at the top right of the summary panel, on the row with the job number.

## Before you start

* The job must be a project. See [Track a job as a project](https://learn.withessential.com/customers-and-work/jobs/track-a-job-as-a-project.md).
* You need office (web) access.
* AI works only from what you can see. The AI summary mentions money only to roles that can view invoices, in businesses that use invoicing. Tasks you can't open on the Tasks page are left out.

## The AI summary

At the bottom of the **Project Overview** card, below a line, AI adds at most two short sentences with what the page doesn't already show. It reads the job's notes and comments and the details of what tasks are waiting on, and says what they reveal: a blocker or a risk and its cause (such as why an inspection or test failed), a decision still pending and who it's waiting on, or what's holding up the next step. For example: "The hydro test failed at 175 psi with a leak at the 2nd-floor riser flange; it's retested once the flange is fixed."

It never repeats what's already on the page: the phases and their progress, how many tasks are done, the next visit, the project's dates, money totals, and the billing status. When the records add nothing beyond that, there's no AI summary and no line. It doesn't tell you what to do next; that's your team's call.

* Under the summary, "Written by AI · updated Oct 20, 2026, 9:53 AM" shows when it was written. It reads "last updated" when the project has changed since then.
* The summary is rewritten in the background when you open the job and the project has changed. While a new one is being written, it shows **Updating…** (or **Writing the summary…** the first time), and the new one appears without reloading the page.
* Select **Refresh** to ask for a new summary now.
* If a new summary can't be written, the card keeps the last one and shows "Couldn't refresh — last updated" with its date. Select **Refresh** to try again; otherwise it tries again later on its own.

The summary is shared by everyone who sees the same project records. Someone who can't view invoices gets their own, written without any billing figures.

## Suggested items

**Suggested items** is the card below the job's summary panel. AI reads the job's quotes and visits and the project checklist, and suggests the items it is missing: office to-dos such as ordering materials or sending closeout documents, and the permits, inspections, tests and sign-offs the work has to pass. Each suggestion sits under the phase it belongs to, with a short reason, such as what in the quote calls for it. A phase marked **New phase** isn't on the checklist yet.

* The tasks are suggested once per project, the first time someone who can view quotes opens the job after the project starts. The card appears, without reloading the page, once AI has suggestions. It doesn't show while AI is still working on the first ones, or when there's nothing to suggest.
* You need permission to view quotes to see the card. Without it, the job page doesn't show it.
* Tasks you can't open on the Tasks page are left out of what AI reads.

To add suggestions to the checklist:

1. Tick the tasks you want. Nothing is ticked at first.
2. Select **Add N to Plan**. The items are added to **Project Management > Project Checklist** in their phases, and a suggested new phase is added with them (or, if a phase with that name already exists, the items go in it). The job's Timeline shows which suggested tasks were added.

The tasks you didn't tick stay on the card. A suggestion disappears once the checklist has an item with the same name.

* Select **Suggest again** to ask for a new set. Tasks you already added stay added. The card shows **Suggesting items…** while AI works. If the new set is empty, the card goes away and a message says "Nothing more to suggest. The Plan covers this job."
* Select **Dismiss** to hide the card for this project. It doesn't come back.
* If AI couldn't suggest tasks, the card says so. Select **Try again**.

When your business turns projects off in Settings, no new suggestions are made, but you can still add the ones the card shows.

## Add an update

Use **Add Update** for news that arrives outside the app, such as an email from the GC, a text from the inspector, or notes from a call.

1. On the job page, open the ⋮ menu at the top right of the summary panel and select **Add Update**.
2. Paste or type the update in **Update**, and select **Read update**.
3. Review **Suggested changes**. Each one shows the words of the update it comes from. Clear any you don't want. A suggested change can be one of these:
   * **Mark a task done**. When the update says an inspection or test passed, this marks its task done.
   * **Put a task on "waiting on"**: who it's waiting on, and the follow-up date if the update gives one.
   * **Set a task's follow-up date**, for a task that's waiting on someone. A follow-up for a task that isn't waiting on anyone is listed under **Not applied**, unless the same update puts that task on "waiting on": then the date goes with that change.
   * **Add a note** to the job's Timeline. When the update says an inspection or test failed, or that there's no result yet, it's suggested as a note, and its task stays open.
4. **Not applied** lists what the update says that AI didn't turn into a change, and why: for example, a request for new work or a price, scheduling a visit, or a payment. Handle these yourself. A task gets one change: if the update says a task is done and also that it's still waiting on someone, only what the update says later is suggested.
5. Select **Apply** (the button shows how many changes are selected). Select **Back** to edit the update first.

Each change goes through the same process as making it by hand, so the usual rules apply. If every change goes through, the dialog closes with "Applied N changes". If one can't be applied (for example, someone else changed the task first), the dialog lists each change with **Applied** or the reason it wasn't. Select **Done** to close it. If the connection drops while a task change is being sent, the dialog checks the task: if the change went through, it shows **Applied**; if not, it shows the error and the change isn't sent again, so make it by hand.

Marking a task done also ends its "waiting on". If the task was marked done but its "waiting on" couldn't be cleared, the change shows **Applied** with what's left to do: open the task's **Waiting on Others** and select **No longer waiting**.

Notes go on the job's Timeline, where everyone on the job can read them, so a money amount in an update is never added as a note, whether it's written in figures ("$12,400") or in words ("twelve thousand dollars", "two grand"). It's listed under **Not applied** instead.

## Related guides

* [Track a job as a project](https://learn.withessential.com/customers-and-work/jobs/track-a-job-as-a-project.md)
* [Manage a project's checklist and phases](https://learn.withessential.com/customers-and-work/jobs/project-plan-phases-and-tasks.md)
* [Bill a project: progress invoices, retainage, and change orders](https://learn.withessential.com/customers-and-work/jobs/project-billing-progress-invoices-retainage-and-change-orders.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/use-ai-on-a-project.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.
