> 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/mobile/work-on-a-project-on-mobile.md).

# Work on a project from the mobile app

When a visit's job is tracked as a project, the visit shows a **Project** button. It opens the project: every phase at a glance, the project steps the office attached to this visit, and the project's notes. From there you can tick those steps done and add notes. The attached steps also show on the visit under its technician instructions. The office sees what you did, and when, on the project in the web app.

> **Where to find it:** Mobile app > Visits > open the visit > **Project** (below **Start Inspection**)

## Before you start

* The office must have turned the job into a project, and the project must be on. Other visits don't show the **Project** button, except to clear changes that weren't sent (see [When the project is no longer on the visit](#when-the-project-is-no-longer-on-the-visit)). See [Track a job as a project](https://learn.withessential.com/customers-and-work/jobs/track-a-job-as-a-project.md).
* The **Project** button appears with **Add Summary** and **Start Inspection**, so it shows on the same visits those do (today's visits, visits you're clocked into, and recent visits your office lets you reopen).
* To tick a step, you must be assigned to the visit and the office must have attached that project step to the visit. Attached steps can come from any phase.

## What the Project screen shows

Under the button's **Project** label, a short line says how many attached steps are still open, such as "2 open steps". Each attached step is counted once.

The screen shows, from top to bottom:

* The project's name, the customer, and the job number.
* **Phases**: every phase in order. A finished phase shows a check and **Complete**. The others show their state, **In progress** or **Not started**.
* **Steps** attached to this visit, each with a checkbox and its phase. These can include inspections, tests, and sign-offs, such as a hydrostatic test or an AHJ inspection. Each attached step appears on its own. A done step is crossed out and says who marked it done and when, such as "Marked done by Priya Shah · Oct 17, 3:05 PM", or "Marked done by you". That's who changed the step's status, not necessarily who did the work.
* **Notes**: the project's notes, newest first, with who wrote each one, when, and any photos or files. Photos show as small pictures. Other files, such as a PDF the office attached in the web app, show by name. Tap a photo or a file name to open it.

Only steps attached to this visit are shown. Ordinary **Tasks** the office keeps from technicians (such as quote or invoice Tasks you can't open) don't appear.

## Project steps on the visit

When the office puts project steps on your visit in the web app's visit form, the visit shows them under its technician instructions as **Project steps**. Each has a checkbox and its phase, and a done step is crossed out with who marked it done and when. Each step must be attached to the visit separately, including any item that used to be nested under another. The same attached steps appear as **Steps** on the Project screen. Visits without project steps look the same as before.

Tap a step to mark it done, and tap it again to reopen it. It works the same way as on the Project screen (below): the tick goes through the same queue, works offline, and shows **waiting to send** until it's sent. Leave a step open if it isn't finished, and say why in your visit notes.

## Mark a step done

1. Open the visit and tap **Project**.
2. Tap a step to mark it done. Tap a done step to reopen it. Each attached step is checked separately.

For an inspection or test, mark its step done when it passes. If it fails, leave the step open and add a note saying what failed, so the office can book the fix or the re-inspection.

The step is marked right away. It moves to the first Done status of its step folder (reopening moves it to the folder's first to-do status), as if the office had checked it on the job's Project Management > Project Checklist. The office sees the date on the step, and "Marked done by *your name*" and the time when they point at it, and the project's activity records that you marked it done from the technician app. If the step was already in the state you chose (for example, someone else ticked it first), nothing changes, and the activity records that you confirmed it. The office can still change the step.

## Add a note

1. On the Project screen, tap **+ Add note** next to **Notes**.
2. Type what the office and crew should know. To add photos, tap the photo button and take or choose them. A note holds up to 10 photos; if you pick more, the app keeps the first 10 and tells you ("Too many photos").
3. Tap **Post note**. **Post note** stays unavailable until the note has text or a photo. Tap **Cancel** to throw the draft away.

Notes are the project's notes: the office reads them on the job's Timeline, at the bottom of the job page, next to its own notes.

## Work offline

Step ticks and notes work without a signal. They're saved on the phone and sent, in the order you made them, when you're back online. A note's photos are sent before the note. While something is waiting, the Project screen says how many changes are waiting to send, and each one shows **waiting to send**.

If the office's server refuses a change (for example, the project was turned off, the step left the project, or the office took it off your visit), it isn't lost. It shows at the top of the Project screen under **Not sent**, with the reason. Tap **Retry** to send it again, or **Discard** to drop it (it also comes off the **Failed** count in the offline status bar). A refused note whose photos were already uploaded needs a connection to discard, so its photos are removed from the office's server too. The app also tells you once, with "Project change not sent".

### When the project is no longer on the visit

The office may turn the project off while a change of yours is still waiting to send or after the server refused it. The visit then keeps its **Project** button until those changes are dealt with. Under the **Project** label it says what's left, such as "1 change not sent" or "2 changes waiting to send".

Tap **Project** to see them. The screen says "The project isn't available on this visit any more." and lists only your changes: any still waiting to send, and the refused ones under **Not sent** with **Retry** and **Discard**. The project's phases, steps, and notes don't show, and you can't tick steps or add notes. **Retry** sends the change again; while the project is off, the server refuses it again. A change still waiting to send can't be discarded yet: once the server refuses it, it moves to **Not sent**, where you can discard it. When nothing is left to send, the **Project** button goes away. Changes the office's server already took need nothing from you.

## See your project changes in the visit summary

The visit summary lists what you changed in the project on this visit, under **Project changes on this visit**: steps you marked done or reopened, and notes you added, with the time. A step you tick and then untick shows once, as where it ended up, and not at all if it ended where it started. A change that hasn't been sent yet shows **Waiting to send**, and a refused one shows **Not sent**. The list is read-only. Tap **Open Project** to go to the Project screen. **Open Project** also shows when the project is no longer on the visit but a change of yours wasn't sent, so you can retry or discard it there.

## Related guides

* [Open a visit in the mobile app](https://learn.withessential.com/field-operations/mobile/open-a-visit.md)
* [Add a visit summary on mobile](https://learn.withessential.com/field-operations/mobile/add-a-visit-summary.md)
* [Work offline and sync mobile changes](https://learn.withessential.com/field-operations/mobile/work-offline-and-sync.md)
* [Manage a project's checklist and phases](https://learn.withessential.com/customers-and-work/jobs/project-plan-phases-and-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/mobile/work-on-a-project-on-mobile.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.
