> 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/administration/settings/turn-on-projects-and-manage-project-templates.md).

# Turn on projects and manage project templates

Projects add phases, project tasks, and an optional billing schedule to a job (see [Track a job as a project](https://learn.withessential.com/customers-and-work/jobs/track-a-job-as-a-project.md)). They're off until an admin turns them on. While they're off, nobody sees **Start Project** on a job.

When you turn projects on, you also review the project templates that **Start Project** offers. A project template is the phases and tasks a project starts with. You need at least one before you can save.

Billing isn't set here. Whether a project bills on a schedule, and its deposit and retainage, vary from project to project, so they're chosen per project with **Set Up Billing** on the job's **Billing Schedule** tab. See [Set up billing](https://learn.withessential.com/customers-and-work/jobs/project-billing-progress-invoices-retainage-and-change-orders.md#set-up-billing).

> **Where to find it:** Settings > Work Management > **Projects**. You can also search the Settings menu for "projects" or "project templates".

## Before you start

* Anyone who can open Settings can view this page. Changing it needs a settings setup permission, such as **Set up Business Profile**. See [Roles and permissions](https://learn.withessential.com/administration/settings/roles-and-permissions.md).
* Nothing changes until you select **Save**. If you leave the page with unsaved changes, Essential asks before discarding them.

## Turn projects on

1. Go to Settings > **Projects** and turn on the **Projects** switch.
2. The first time you turn projects on, Essential adds the **Standard project** template under **Project Templates**, open for you to review. It has three phases: **Plan & order**, **Install**, and **Test & closeout**, each with a few typical tasks (permit, inspections, final test, customer sign-off).
3. Rename the project template, change its phases and tasks, or add more project templates (see below).
4. Select **Save**.

**Save** stays unavailable until every project template has a name, every phase has a name, and every task has a name. Hover over **Save** to see what's missing.

## Manage project templates

A project template is a starting point: phases and the tasks in each phase. When someone starts a project, every phase and task in the chosen project template is copied into it, and the tasks show on the job's **Project Management > Project Checklist**. Changing or removing a project template later doesn't change projects already started. A project template has no billing.

**Start Project** lists the project templates in the order they appear here. Drag a project template by its grip on the left to reorder it.

Select a project template's name to open or close it. In an open project template:

* **Name**: the name shown under **Project Template** in **Start Project**. Each project template needs its own name.
* **Phases and steps**: each phase name, with its tasks indented below it.
  * Select **Add step** under a phase to add a task to it, or **Add phase** to add a phase at the end.
  * Drag a phase or task by its grip to reorder it. A task stays in its phase.
  * Select the trash icon to remove a phase (with its tasks) or a task. A project template needs at least one phase.
  * Put inspections, tests, permits, and sign-offs in as tasks in the phase they check, such as "Rough-in inspection" in Install.

A project template can have up to 30 phases and 100 tasks, and you can have up to 20 project templates.

### Add a project template

1. Select **Add Project Template**.
2. Enter a **Name**.
3. Under **Start from**, choose **Blank** (one phase to fill in) or one of Essential's examples: **Standard project**, **Kitchen hood install**, **Small replacement**, **Sprinkler tenant improvement**, or **Fire alarm install**.
4. Select **Add Project Template**. The new project template opens at the bottom of the list.
5. Adjust it, then select **Save** on the page.

### Remove a project template

Select the trash icon on the project template's row, then select **Save**. You can't remove the last project template while projects are on. Projects already started from a removed project template keep their phases and tasks.

## Turn projects off

Turn off the **Projects** switch and select **Save**. Nobody can start a new project after that, and **Start Project** is gone from the job's ⋮ menu. Projects already started keep working: they stay on their job's page with their billing, and the job's ⋮ menu keeps **Add Update**, **Edit Project Details**, **Turn Off Project**, and **Turn Project Back On**. Your project templates are kept for when you turn projects back on.

## 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)
* [Use AI on a project: the AI summary, suggested items and Add update](https://learn.withessential.com/customers-and-work/jobs/use-ai-on-a-project.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/administration/settings/turn-on-projects-and-manage-project-templates.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.
