Projects

Projects group related jobs together and track overall progress toward a defined goal. A project provides the campaign-level view — you can see how much of the planned work has been executed across all crews and all work orders at a glance.

Where Projects Fit in the Hierarchy

Project
  └── Job  (planned unit of work — geometry, resource requirements)
        └── Work Order  (assignment of a job to a worker or team)
              └── Report  (worker's record of what was actually done)

A project is the top-level planning container. It owns a set of jobs. Those jobs get assigned to workers via work orders, and workers submit reports to record what they did. Progress rolls up from reports → jobs → project.

Project Lifecycle

Created → In Progress (work underway) → Completed
            ↓
          Cancelled (work halted or redirected)

Project status is set manually by the project manager. The progress metrics on the project detail page show how much work has been reported — helping PMs decide when to mark the project complete.

Creating a Project

1. Navigate to Fulfillment → Projects
2. Click New Project
3. Fill in:
   • Name — short, descriptive
   • Description — scope, objectives, notes
   • Ordered By — the person or team who commissioned the work
   • Due Date — target completion date (optional)
4. Click Save

Adding Jobs to a Project

Project jobs define the units of work that make up the project. Each job carries its own geometry, resource requirements, and tracks its own completion state.

1. Open the project
2. Navigate to the Jobs tab
3. Add jobs directly from the project, or associate existing jobs from the Jobs page

Jobs in a project are the same Jobs found under Fulfillment → Jobs — they are not a separate object type. Adding a job to a project is an association, not a copy. The same job can appear in multiple projects if needed.

Progress Tracking

The project progress metrics answer a simple question: how much of the planned work has actually been reported as done?

How a job's progress is calculated

Each job carries one or more resource targets — the planned work (e.g., 200m cable, 10 ladders). Reports filed against that job record what was actually completed, per resource.

For each job:

Resource % = min(100%, reported volume / planned volume)
Job %      = average of the job's resource %'s

• Resource percentages are capped at 100% individually. Over-reporting on one resource doesn't carry an unreported resource along.
• Only resources with a positive planned volume contribute to the job average. Resources with no plan are ignored.
• A job with no planned resources shows 0%. That's a deliberate signal — the job doesn't yet have enough definition to be measured.

How a project's progress is calculated

Project % = equal-weight average of job %'s across jobs that have a plan

• Each job contributes equally, regardless of how much work it represents. A small job with 100% completion weighs the same as a large job with 100%. This makes the number easy to read and avoids mega-jobs dominating the average.
• Jobs with no resource plan don't contribute. They don't count for or against the project.

Where the numbers show up

• Project list page: each project card shows two progress bars:
  • Assigned — distinct jobs with at least one work order referencing them, over total project jobs. Answers "how much is scheduled?"
  • Reported — distinct jobs with at least one report filed, over jobs that have been assigned. Answers "how much of the scheduled work has been reported?"
• Project detail page: the full rollup. Per-job percentages shown alongside the project-level total.

Important honest notes

• Reports can exceed the plan (e.g., 205 m cable reported against a 200 m plan) — the resource % is still capped at 100% for rollup purposes, but the raw numbers remain visible in the report detail.
• A partially-reported job (cable at 50%, conduit at 0%) shows as 25% — the average of 50% + 0%. This can under-represent real progress when a job has resource types with different lead times. The average is chosen deliberately over the minimum so that future-dated resources don't keep the bar at 0%.
• Project % is not the same as "jobs completed / total jobs." A job doesn't have a binary completion flag — it has a reported-vs-planned ratio. The project % reflects that ratio.

The progress data is available for external dashboards and reporting tools — contact your system administrator for integration details.

Drill Down

From the project page you can:

• See all jobs with their individual status
• Filter jobs by status (pending, in-progress, completed)
• Click a job to open its detail and linked work orders

Assigning Project Jobs to Work Orders

A project job can be referenced by one or more work orders. This is how the work gets distributed to field teams:

1. Open the Work Orders page
2. Create a new work order (or edit an existing one)
3. In the Job field, select or drag in the project job
4. Assign workers and set the timeline
5. Save

When a worker submits a report against a work order that references a project job, the job's completion state updates automatically, and the project's progress bar advances.

Removing Jobs from a Project

When you remove a job from a project:

• The system checks whether the job is still referenced by active work orders and logs a warning if so
• The job is not deleted from the system — only its association with the project is removed

To fully retire a job, delete it from Fulfillment → Jobs (requires jobsDelete right).

Deleting a Project

1. Open the project
2. Click Delete (requires projectsDelete right)
3. Confirm

Deletion is a soft delete — the project is hidden from all views but preserved for audit. Work orders and jobs that referenced the project are not affected. The deletion is recorded in the audit trail.

Permissions

Tips

Use projects for campaigns, not single pieces of work. A one-off installation or repair can be a standalone work order or a single job; a multi-week fibre rollout across 50 poles belongs in a project.

Projects do not auto-complete. When the progress metrics show all work is done, the project manager reviews and manually marks the project completed.

Progress report. Project completion data — including percentage complete, job counts, and due date — can be consumed by external reporting tools or dashboards. Ask your system administrator to set up this integration.