The Predecessor column uses a compact notation to define dependencies. This allows you to quickly enter dependencies by typing rather than dragging.
| Component | Description | Required |
|---|
| WBS | The WBS code of the predecessor task (e.g., "1", "1.1", "2.3") | Yes |
| Type | Dependency type: FS, SS, FF, or SF | No (defaults to FS) |
| Lag | Days of delay: +Nd for lag, -Nd for lead | No (defaults to 0) |
Examples
| Entry | Meaning |
|---|
3 | Depends on WBS 3, Finish-to-Start, no lag |
1.2 | Depends on WBS 1.2, Finish-to-Start, no lag |
3FS | Depends on WBS 3, Finish-to-Start, no lag |
5SS | Depends on WBS 5, Start-to-Start, no lag |
2FF | Depends on WBS 2, Finish-to-Finish, no lag |
4SF | Depends on WBS 4, Start-to-Finish, no lag |
3FS+2d | Depends on WBS 3, Finish-to-Start, with 2-day lag |
5SS+3d | Depends on WBS 5, Start-to-Start, with 3-day lag |
2FS-1d | Depends on WBS 2, Finish-to-Start, with 1-day lead (overlap) |
1.3FF+5d | Depends on WBS 1.3, Finish-to-Finish, with 5-day lag |
Multiple Predecessors
To link a task to multiple predecessors, separate entries with semicolons:
| Entry | Meaning |
|---|
3;5 | Depends on WBS 3 AND WBS 5 (both FS) |
3FS;5FS | Same as above, explicit notation |
2FS+1d;4SS | Depends on WBS 2 (FS, 1-day lag) AND WBS 4 (SS, no lag) |
1;3;5 | Depends on WBS 1, 3, and 5 (all FS, no lag) |
Real-World Examples
Scenario 1: Simple sequence
Task 2 starts after Task 1 finishes. Task 3 starts after Task 2 finishes.
| Task | Name | Predecessor |
|---|
| 1 | Framing | (none) |
| 2 | Electrical | 1 |
| 3 | Drywall | 2 |
Scenario 2: With curing/drying time
Task 2 starts 3 business days after Task 1 finishes (allowing concrete to cure).
| Task | Name | Predecessor |
|---|
| 1 | Pour concrete | (none) |
| 2 | Set posts | 1FS+3d |
Scenario 3: Parallel work after a predecessor
Tasks 2, 3, and 4 all start after Task 1 finishes, but can run in parallel.
| Task | Name | Predecessor |
|---|
| 1 | Rough framing | (none) |
| 2 | Electrical | 1 |
| 3 | Plumbing | 1 |
| 4 | HVAC | 1 |
Scenario 4: Task depends on multiple predecessors
Task 3 cannot start until BOTH Task 1 AND Task 2 are complete.
| Task | Name | Predecessor |
|---|
| 1 | Electrical | (none) |
| 2 | Plumbing | (none) |
| 3 | Inspection | 1;2 |
Scenario 5: Overlapping tasks with lead time
Task 2 starts 1 day before Task 1 finishes (overlap for efficiency).
| Task | Name | Predecessor |
|---|
| 1 | Install cabinets | (none) |
| 2 | Install countertops | 1FS-1d |
Scenario 6: Tasks that must finish together (FF)
Task 2 finishes when Task 1 finishes (cleanup completes with painting).
| Task | Name | Predecessor |
|---|
| 1 | Painting interior | (none) |
| 2 | Final cleanup | 1FF |
Scenario 7: Complex dependencies
A realistic construction sequence with mixed dependency types.
| Task | Name | Predecessor |
|---|
| 1 | Foundation | (none) |
| 2 | Framing | 1FS+2d |
| 3 | Roofing | 2 |
| 4 | Electrical rough | 2 |
| 5 | Plumbing rough | 2 |
| 6 | Insulation | 4;5 |
| 7 | Drywall | 6FS+1d |
Quick Reference Card
| Want to... | Type this |
|---|
| Simple dependency on WBS 3 | 3 |
| Finish-to-Start on WBS 3 | 3FS or 3 |
| Start-to-Start on WBS 5 | 5SS |
| Finish-to-Finish on WBS 2 | 2FF |
| Add 2-day lag after WBS 3 | 3FS+2d or 3+2d |
| Overlap with WBS 4 by 1 day | 4FS-1d or 4-1d |
| Depend on WBS 1 and 3 | 1;3 |
| WBS 2 with lag, WBS 5 without | 2FS+2d;5 |