Finishing a project

You don’t set a project’s status by hand. It follows its jobs: while any of them is being worked the project is in progress, and when they’re all finished the project is ready to close.

The window has passed with work still open

If a project’s window has ended and jobs are still open, it’s flagged Window ended - 3 open, with the line This project’s window has passed with jobs still open. underneath. It shows on the project’s own page, in its quick view from the dispatch board, and on the project’s block on the board itself.

The flag changes nothing on its own. It’s there so a project doesn’t quietly run past its dates. Review open jobs takes you into the pool console with the open jobs already filtered.

Clearing the last jobs

To close a project past its window, get every remaining job to a finished state. From the pool console there are two sensible moves.

Move to project… the stragglers into another project that’s still running, so the work carries on without rescheduling each job one at a time.

Cancel or fail the jobs that genuinely aren’t happening. Cancelling or failing a job counts as finished for the project, exactly as completing it does.

Moving the last open job out counts too, and often that move is what tips the project into its closing state.

The two ways a project closes

Once every job in it is completed, cancelled or failed, what happens depends on the sign-off form.

With no sign-off form, or one whose completion form has no fields, there’s nothing left to record and the project completes on its own.

With a sign-off form, the project waits for a person. It reads Ready to complete, with Every job in this project is done. Complete it to finish the sign-off. Click Complete project on the project’s edit page and fill the form in. That form is the “everything on this site is done” record for the whole engagement. An engineer sees the same card in the app, and if they can’t close it themselves it tells them the office will.

A project can also be cancelled outright at any point, and that stands whatever its jobs say. Cancel one with work still open and the pool console tells you: Project cancelled, with the number still open.

Adding an open job to a project that had finished puts it back to pending and makes its pool claimable again.

Projects over the API

Your own software can create and read projects, and create jobs inside them.

• Creating a project needs both the create:jobs and read:jobs scopes on the key, because the new project is read back to you in the response. A key with only create:jobs is refused, and the refusal names both scopes.
• Creating a job takes a project in place of a customer. The job inherits the project’s customer, brand and default location, and joins the pool when you leave the schedule off.
• Filtering jobs by project lists a project’s jobs.
• A project doesn’t count toward your job usage over the API either. Its jobs do.

Claiming and releasing are decisions made in the field on the phone, so they aren’t part of the API. Book a crew member onto one of the project’s jobs instead.

See the API reference for the request and response shapes, and Getting started with the API for keys and scopes.