Sub-jobs & dependencies¶
Sub-jobs are the individual units of work within a work order. Dependencies let you define which sub-jobs must complete before others can begin.
Managing sub-jobs¶
Reordering¶
Drag sub-jobs to reorder them, or use the Reorder action to set a specific sequence. The order determines the default execution sequence.
Optional sub-jobs¶
Mark sub-jobs as optional when they're nice-to-have but not required for work order completion. Optional sub-jobs are excluded from the "all required" completion rule.
Blocking¶
When a sub-job has unresolved dependencies (predecessor sub-jobs not yet complete), it is automatically blocked. Blocked sub-jobs:
- Show a blocked indicator on the dispatcher board
- Cannot be started by technicians
- Are automatically unblocked when all predecessors complete
Dependency types¶
| Type | Behavior |
|---|---|
| Finish-to-Start | Task B cannot start until Task A finishes |
Planning tip
Set up dependencies while the work order is in Draft status. You can still add dependencies after activation, but blocked sub-jobs will be immediately flagged.
Example: HVAC installation¶
| Order | Sub-Job | Depends On | Type |
|---|---|---|---|
| 1 | Site inspection | — | — |
| 2 | Equipment procurement | Site inspection | Finish-to-Start |
| 3 | Duct installation | Equipment procurement | Finish-to-Start |
| 4 | Electrical hookup | Duct installation | Finish-to-Start |
| 5 | System testing | Electrical hookup | Finish-to-Start |
| 6 | Customer walkthrough | System testing | Finish-to-Start |
When the site inspection completes, equipment procurement is automatically unblocked. Each subsequent phase waits for its predecessor.