4D planning links the construction programme (time) to the 3D model, so each activity shows the elements it installs. Played back, the model "builds itself" in the planned order. That makes it easy to see what the bar chart hides: a crane that has nothing to lift for a week, two trades in the same zone at the same time, a slab poured before the services that pass through it.
At a glance
| Who uses it | Planners, construction managers, site teams, clients and neighbours (for explaining the works) |
| Inputs | A programme (activities, dates, logic) and a model whose elements can be grouped the same way as the activities |
| The link | Activity ↔ set of model elements, usually through shared codes: location (level, zone) + work type |
| Software | Dedicated 4D tools, and 4D features in coordination software; programmes come from scheduling software |
| Output | Sequence animations, snapshots per week, clash checks in time (workspace and access conflicts) |
| Main condition | The model must be split the way the work is split (by pour, by zone, by level) |
The key idea: a shared breakdown
The programme and the model must agree on how the job is divided. If the planner schedules "Level 3 slab, pour 2" but the model has one slab for the whole level, nothing can be linked. Teams agree a location breakdown (building, level, zone, pour) and a work breakdown (substructure, frame, envelope, services first fix…), then:
- activities carry a code such as
L03-Z2-FRAME; - model elements carry the same codes in properties (level, zone, work package);
- a rule links every activity to the elements with matching codes.
Rules beat clicking elements one by one: when the model changes, the links follow.
| Programme activity | Code | Model elements matched |
|---|---|---|
| Frame Level 3, Zone 1 | L03-Z1-FRAME | Columns and beams with Level = 03, Zone = Z1, Package = Frame |
| Pour slab Level 3, Zone 1 | L03-Z1-SLAB | Slab parts with Level = 03, Zone = Z1 |
| MEP first fix Level 3 | L03-ALL-MEP1 | Ducts, pipes, trays on Level 03 |
What 4D is good for
- Checking the logic: elements that appear floating, or before what supports them.
- Workspace conflicts: two activities using the same zone or laydown area at the same time.
- Logistics: crane coverage, delivery routes, hoists and scaffold shown against the sequence.
- Communication: one minute of animation explains a phasing plan to a client, a neighbour or a new site team better than a 600-line programme.
- Tender: showing an approach and a sequence that has been thought through.
Worked example
A school extension must stay open during term. The planner's programme shows the new hall built in one block. The 4D model, with the existing building's entrances and the fire escape route drawn as zones, shows the scaffold to the hall's east wall blocking the escape route for four weeks in October. The sequence is changed so the east wall is built in the half-term holiday. Nothing clashed in 3D; the problem only existed in time.
Common mistakes
- Linking elements by hand, so the 4D model breaks at the next model revision.
- A model that can't be split like the work (one element per whole slab or wall run).
- Showing only permanent works: most site problems involve temporary works, plant and access.
- Building a beautiful animation once for the tender, then never updating it.
Where to read more
Scheduling guidance from planning and construction management bodies covers programme structure and logic. Your 4D or coordination software's documentation explains how it links activities to elements by rules.