> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/backoffice/backoffice/projects/set-up-projects/what-is-projects.md).

# What is Projects?

**Projects** groups related work orders under one larger job.

Use it for work that runs across multiple days, weeks, or phases.

A project gives you one place to review:

* linked work orders
* hours, costs, and revenue
* activities, status, and progress

{% hint style="info" %}
**Projects** is included in **Accelerate** and **Maximize**.

**Project Planning** is available in **Maximize**.
{% endhint %}

### When to use Projects

Use Projects when you need:

* one project number for multiple work orders
* budget control across a longer job
* progress tracking per project or activity

### How Projects fits with work orders

A work order is one planned job.

A project is the wider job that contains one or more work orders.

Hours and costs from linked work orders roll up to the project.

### Frequently asked questions

<details>

<summary>Is a project the same as a work order?</summary>

No.

A work order is one task or visit.

A project groups several related work orders.

</details>

<details>

<summary>Do I need Project Planning to use Projects?</summary>

No.

You can use Projects without the planning board.

Project Planning is an extra planning view.

</details>

<details>

<summary>Can I use Projects without activities?</summary>

Yes.

Activities are optional.

They help when the project has clear phases.

</details>

### Related topics

* [**Projects**](/backoffice/backoffice/projects.md)
* [**Create a project**](/backoffice/backoffice/projects/set-up-projects/create-a-project.md)
* [**Link work orders to projects**](/backoffice/backoffice/projects/plan-and-track-projects/link-work-orders-to-projects.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://knowledge.out-smart.com/backoffice/backoffice/projects/set-up-projects/what-is-projects.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.