Projects

Projects group related tasks 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
  └── Task  (planned unit of work — geometry, resource requirements)
        └── Work Order  (assignment of a task 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 tasks. Those tasks get assigned to workers via work orders, and workers submit reports to record what they did. Progress rolls up from reports → tasks → 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 Tasks to a Project

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

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

Tasks in a project are the same Tasks found under Fulfillment → Tasks — they are not a separate object type. Adding a task to a project is an association, not a copy. The same task 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 task's progress is calculated

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

For each task:

Resource % = min(100%, reported volume / planned volume)
Task %     = average of the task'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 task average. Resources with no plan are ignored.
• A task with no planned resources shows 0%. That's a deliberate signal — the task doesn't yet have enough definition to be measured.

How a project's progress is calculated

Project % = equal-weight average of task %'s across tasks that have a plan

• Each task contributes equally, regardless of how much work it represents. A small task with 100% completion weighs the same as a large task with 100%. This makes the number easy to read and avoids mega-tasks dominating the average.
• Tasks 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 tasks with at least one work order referencing them, over total project tasks. Answers "how much is scheduled?"
  • Reported — distinct tasks with at least one report filed, over tasks that have been assigned. Answers "how much of the scheduled work has been reported?"
• Project detail page: the full rollup. Per-task 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 task (cable at 50%, digging at 0%) shows as 25% — the average of 50% + 0%. This can under-represent real progress when a task 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 "tasks completed / total tasks." A task 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 tasks with their individual status
• Filter tasks by status (pending, in-progress, completed)
• Click a task to open its detail and linked work orders

Assigning Project Tasks to Work Orders

A project task 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 Task field, select or drag in the project task
4. Assign workers and set the timeline
5. Save

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

Removing Tasks from a Project

When you remove a task from a project:

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

To fully retire a task, delete it from Fulfillment → Tasks (requires featureDelete right).

Deleting a Project

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

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

Permissions

Tips

Use projects for campaigns, not individual jobs. A single installation or repair belongs in a work order. 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, task counts, and due date — can be consumed by external reporting tools or dashboards. Ask your system administrator to set up this integration.