Projects
A project groups several work orders that belong to the same larger job — a multi-visit install, a building retrofit, a seasonal maintenance push — so you can manage them as one thing instead of chasing individual orders.
Projects live under Field Service → Projects.
What a project holds
Open a project and you get the whole rollup on one screen:
- Budget KPIs — the budget you set versus actual spend, with a spend breakdown so you can see where the money's going.
- Work orders — every order attached to the project, with their statuses.
- Tasks — project-level to-dos.
- Team — who's assigned.
- Assets — equipment involved.
- Account — the customer the project is for.
Creating a project
Field Service → Projects → New. Give it a name, link the account, set a budget and estimated hours, then attach work orders (existing or new) to it. As those orders accrue labor, parts, and costs, the project's spend and budget KPIs update.
Why use them
- One number for "how are we tracking against budget" across many visits.
- A single place to see all the moving parts for a big job.
- Cleaner reporting — the project ties the revenue and cost of a whole engagement together.
On mobile
Field techs can view projects and link work to them on the mobile app (project create/edit and team/account management stay in the backoffice), so they always know which larger job a visit belongs to.