Projects
A project is a batch of jobs for one customer, worked by one crew inside one window: a week rewiring a building, or fifty installs across a site. Rather than assign each of those jobs to somebody, you leave them in a shared pool and the crew claim them as they work through the site.
Start one with New Project, in the top right of the jobs list or the dispatch console.
What a project holds
Section titled “What a project holds”A project has a customer, and every job in it is for that customer. It can also have a name, a window (a scheduled start and end), a crew, a location, a priority and notes. A window can cover 14 days at most, so a longer engagement is split across more than one project.
The project itself has no job type for the work. Each of its jobs has its own, and you can mix them: one project can hold forty-nine fibre installs and one service call. What a project can carry is a Sign-off form, filled in once at the end for the whole site. See Finishing a project.
Projects go one level deep. A project can’t sit inside another project, and a job in a project can’t have jobs of its own. Everything in a project stays in one brand.
Pool, pinned and assigned jobs
Section titled “Pool, pinned and assigned jobs”How one of the project’s jobs is scheduled decides who works it.
| Job | Its schedule | Who works it |
|---|---|---|
| Pool | None, so it runs during the project’s window | Anyone on the crew, once they claim it |
| Pinned | Its own start and end | Whoever it’s assigned to |
| Assigned | Optional | The person an operator picked |
Pool jobs are the default: leave the schedule empty and the job joins the pool. They stay off the dispatch board and out of the unscheduled backlog, because the project’s own block on the board stands for all of them. A pinned job gets its own block, marked Part of project PRJ0001. Auto-assignment skips pool jobs, because claiming is the decision of the person standing in front of the work.
The pool and claiming covers both ends of that: the engineer’s phone and the office’s console.
Finding projects in the jobs list
Section titled “Finding projects in the jobs list”Projects sit in the jobs list alongside jobs, carrying a Project badge. A job in a project shows the project it belongs to in the Project column, linked. The filter beside the search box narrows the list to Job or Project, and the Include project jobs switch, on by default, hides the projects’ jobs when you turn it off.
Numbering and terminology
Section titled “Numbering and terminology”Projects have their own number sequence, separate from jobs: PRJ0001, PRJ0002, PRJ0003.
Project is one of the terms a brand can rename, the same as Job and Resource. See Terminology.
What a project costs you
Section titled “What a project costs you”A project never counts against your plan’s job allowance. Its jobs do, the same as any other job: the allowance is spent when someone is put on the work. For a pool job that moment is the claim, so an engineer taking a job from the pool uses one job from your allowance.
Projects in reports
Section titled “Projects in reports”Reports count the jobs in a project, not the project itself. A project holding twenty jobs adds twenty to the job counts, so volume and completion figures compare like for like across projects and ordinary work.
Who can do what
Section titled “Who can do what”Operators, Operations Managers, Brand Administrators and Tenant Admins can create a project, add and detach its jobs, pin windows, and assign or release pool jobs. Resources claim jobs from the pool, and only on projects whose crew they’re on. Deleting a project needs the Brand Administrator or Tenant Admin role, and takes every job in it with it.
What’s next
Section titled “What’s next”- Creating a project: the window, the crew, and adding jobs
- The pool and claiming: claiming from the phone, managing the pool from the office
- Finishing a project: stragglers, sign-off, and how a project closes