Why Early Engineering Coordination Matters
The cheapest time to solve an engineering problem is before it reaches a drawing. Bringing engineering in early is often where a project's budget and buildability are really decided.
Key takeaways
- The cost of a change climbs steeply through a project; solving it early is always cheaper.
- Bringing engineering into the early stages informs the design without freezing it.
- Projects that run smoothly on site are usually the ones coordinated before work began.
Building projects tend to follow a familiar order. The architecture is designed, the drawings are issued, and then engineering arrives to make it all stand up. It feels efficient. It usually is not. By the time engineering sees the project, most of the decisions that constrain it have already been made.
Early coordination changes that order. It brings structural and services thinking into the room while the design is still loose, when moving a column or a riser is a line on a sketch rather than a renegotiation.
Decisions get more expensive as they age
The cost of a change climbs steeply as a project goes on. A structural idea reconsidered during concept design costs almost nothing. The same idea revisited during construction can run through the foundations, the programme and the final account.
Early engineering does not freeze a design. It gives the architect the information to push it further with confidence: which spans are comfortable and which are ambitious, where a transfer structure would be needed, and what a given cantilever asks of the floor below it.
The projects that run smoothly on site are almost always the ones that were coordinated before anyone broke ground.
Coordination is cheaper than correction
When engineering is in from the start, the services find their routes, the structure finds its depth, and the architecture keeps its intent, all at once and on paper. When it comes in late, the same needs get met by compromise instead: a dropped ceiling to hide a beam that could have been shallower, a bulkhead around a duct that had nowhere else to go.
None of those compromises is a failure of skill. Each is a problem that reached the engineer too late to solve well.
What early looks like in practice
Early coordination does not mean a finished design before the concept is settled. It means a conversation at the right moments: testing the structural logic of a massing study, sizing the main systems before the layouts harden, and flagging the two or three decisions that will govern everything after them.
This is how ORIRI prefers to work, alongside the architect from the early stages, so the engineering supports the design instead of chasing it. The projects that run smoothly on site are almost always the ones that were coordinated before anyone broke ground.
