Stockertim Dictionary · Project management
Network diagram
Also called project network diagram, precedence diagram, activity-on-node diagram
In short
A drawing of a project's activities as boxes joined by arrows that show which activities must finish before others can start.
- Intermediate
- Concept
- Checked
In detail
A network diagram shows the logic of a schedule. Each activity is a box, usually labelled with its duration, and arrows show dependencies: an arrow from A to B means B cannot start until A has finished. The most common style, activity on node, puts activities in the boxes; older diagrams put them on the arrows.
From the diagram the team calculates the earliest and latest times each activity can start and finish. A forward pass works from the start, adding durations to find early start and finish dates; a backward pass works from the end to find late dates. The difference between the two gives each activity's float, and the chain with no float is the critical path.
Dependencies are not all finish-to-start. Some activities can start when another starts, or finish together, and lags or leads can be added. Getting the logic right matters more than the drawing: a missing dependency can make a plan look shorter than reality allows.
In practice
Scheduling software draws the network from the activity list and dependencies, but planners still review the logic with the team, because the software only calculates what it is told.
Watch out
- A Gantt chart can hide missing dependencies that a network diagram makes visible.
- Dates typed in by hand instead of driven by logic break the critical path calculation.
Learn it properly
Official sources
- Government Functional Standard GovS 002: Project Delivery · UK Government (Cabinet Office)
- NASA Cost Estimating Handbook · NASA
Facts last checked on 3 November 2026.
Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.