Projects

Projects group related work orders together and track overall progress toward a defined goal. A project moves through a lifecycle automatically as the work orders and tasks within it are completed.

What Is a Project?

A project is a named collection of tasks (not to be confused with work-order tasks — see the distinction below). Projects are used when you need to:

• Track a campaign of related work across many work orders
• Report aggregate completion to stakeholders
• Group related tasks and monitor overall progress

Project vs Work Order:

• A project is the planning container (the campaign)
• A work order is a specific allocation of work to a person or team
• Work orders are assigned tasks from projects; a single project task may span multiple work orders

Project Lifecycle

Created → Active (tasks added) → In Progress (first task started) → Completed → Closed

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
   • Assigned To — responsible team members or managers
   • 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 tracks its own completion state.

1. Open the project
2. Click Add Task (or drag an existing task from the Tasks page into the project)
3. Fill in task details:
   • Name and description
   • Resource requirements (materials, labour, equipment)
   • Location (map geometry if applicable)
   • Estimated effort

Tasks added to a project are not the same as the top-level work Tasks on the Fulfillment → Tasks page. Project tasks are scoped to the project and track project-level completion, while work-order tasks define what field workers execute day-to-day.

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 let an unreported resource get carried along.
• Only resources with a positive planned volume contribute to the task average. Resources with no plan are ignored (nothing to measure against).
• 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 against the hero map, with a project-level total.

Important honest notes

• Reports can exceed the plan (e.g., 205m cable reported against a 200m 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 the task has mixed resource types with different lead times (e.g., sales activity vs. actual work). 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 % is sensitive to that ratio, not just to "is the task closed."

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, done)
• 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 Available Tasks field, drag or select 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 project task's completion state updates automatically.

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. Once billing and reporting are wrapped up, set it to closed.

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.