Trace Logic shows the network around a single activity: its predecessors and successors, and theirs, out to a chosen number of levels. Clicking another box re-centres the trace on it, so you can walk the logic forward or backward. P6 offers it as a bottom-pane view.
How it works
- Pick an activity. Select the activity whose dates you want to explain or check.
- Set the depth. Choose how many predecessor levels and how many successor levels to show. Level 1 is the immediate neighbours, level 2 adds their neighbours, and so on.
- Read the diagram. Each activity appears as a box, usually with its ID, name, dates and float. Lines show the relationships, with their type (finish-to-start, start-to-start and so on) and any lag.
- Find the driver. Among the predecessors, the driving relationship is the one that actually sets the selected activity’s early date. Tools usually mark it, for example with a heavier or coloured line.
- Re-centre and repeat. Click the driving predecessor to make it the centre, and trace again. Repeating this walks back along the chain that controls the date, to the data date or a constraint.
Trace logic doesn’t calculate anything new. It displays the network the CPM engine already scheduled, so what you see depends on the last schedule run. If logic has been edited since, reschedule before tracing.
Worked example
Illustrative: a reviewer asks why drywall on Level 4 can’t start earlier. The scheduler selects it and sets two predecessor levels and one successor level. The trace shows:
| Level | Activity | Link to the next activity | Driving? |
|---|---|---|---|
| Predecessor 2 | MEP rough-in, Level 4 | FS to MEP rough-in inspection | Yes |
| Predecessor 2 | Framing, Level 4 | FS to framing inspection | Yes |
| Predecessor 1 | MEP rough-in inspection, Level 4 | FS to drywall | Yes, drawn heavy |
| Predecessor 1 | Framing inspection, Level 4 | FS to drywall | No, has relationship float |
| Selected | Drywall, Level 4 | FS to tape and finish | Yes |
| Successor 1 | Tape and finish, Level 4 |
Framing inspection finishes earlier, so its link to drywall has slack. The rough-in inspection link is drawn heavy because it is the driving relationship. Clicking the inspection re-centres the trace on it and shows its own driver, MEP rough-in. The answer to the reviewer: drywall waits on the rough-in inspection, not framing, so pulling framing forward won’t move drywall.
Trace logic vs related views
| View or concept | What it shows | Best for |
|---|---|---|
| Trace logic | Predecessors and successors around one activity, a set number of levels deep | Explaining one activity’s dates and checking nearby ties |
| Critical path | The chain of activities that determines the project finish | Seeing which work drives completion |
| Longest path | The continuous driving chain from the data date to the project finish | Finding the controlling path when calendars or constraints distort float |
| Gantt chart with relationship lines | All activities on a timeline, with links drawn between bars | Seeing dates and overlaps at a glance |
| Full network (PERT) diagram | Every activity and relationship as boxes and lines | Small schedules or printed logic reviews |
Why it matters
Grids and Gantt charts show dates, but they don’t easily show which relationship sets them. Tracing logic is how schedulers check that a delay really flows through the path they claim, and how reviewers spot missing or illogical ties.
It’s also a practical way to check schedule quality one activity at a time. A trace makes open-ended activities obvious, because a box has nothing on one side. It also shows activities tied only by start-to-start links with no finish logic, and unusual lags. These are the kinds of issues a DCMA 14-point assessment counts in bulk, and the GAO Schedule Assessment Guide treats complete, logical sequencing as a basic feature of a reliable schedule.
In delay analysis, such as a time impact analysis, a trace helps show that an inserted fragnet or a late activity actually connects to the path that drives completion. Showing the trace, rather than just asserting the path, makes the argument easier for the other party to check.
Common mistakes
- Reading the trace before rescheduling, so the driving flags reflect old logic.
- Assuming every predecessor drives. Only links with no relationship float set the date.
- Tracing too many levels at once, which turns the diagram into a tangle. Trace short and re-centre.
- Ignoring the lags and relationship types on the lines. A start-to-start link with a lag behaves very differently from a finish-to-start link.
- Overlooking constraints. If an activity has a date constraint, the constraint, not any predecessor, may be what holds the date.
- Forgetting progress settings. Under retained logic and with out-of-sequence progress, the driving tie for an in-progress activity can differ from the one in the original plan.
How os.construction handles it
The Planner’s Trace Logic shows 0 to 10 predecessor and successor levels, draws engine-driving relationships heavy, re-centres on click and exports SVG. For a step-by-step explanation of one date, use Why this date? (see longest path).
FAQ
What is trace logic in a schedule?
Trace logic is a view that centres on one activity and draws its predecessors and successors as a small network diagram, out to a chosen number of levels. It lets a scheduler or reviewer follow the logic that sets an activity's dates without scrolling through a full Gantt chart.
Where is trace logic in Primavera P6?
In P6 Professional, Trace Logic is one of the bottom-pane views in the Activities window. You can set how many predecessor and successor levels it shows, and clicking an activity in the trace re-centres it on that activity.
What is a driving relationship?
A driving relationship is a predecessor link that actually determines the successor's early start or finish. If the predecessor slipped, the successor would slip with it. Non-driving links have relationship float, so the successor keeps its dates even if that predecessor slips a little.
How is trace logic different from the critical path?
The critical path is a property of the whole schedule: the chain of activities that determines the project finish. Trace logic is a local view around whichever activity you pick, critical or not. You can use it to walk the critical path one step at a time, but it shows non-critical neighbours too.
How many levels should a logic trace show?
There's no fixed rule. One or two levels each way is usually enough to answer why a single activity sits where it does. Deeper traces get crowded quickly, so it's often clearer to trace a short distance, click the driving predecessor, and trace again.