What Delays an Engineering Project?

The delay ranking I see, project after project: first, information gaps — missing surveys, late geotechnical reports, architectural backgrounds that arrive in pieces. Second, scope changes — the owner or architect revising the design after engineering is underway, which means redoing finished work. Third, decision bottlenecks — equipment selections, system choices, and approvals that wait days or weeks for a signature. Fourth, agency review cycles, which are real but usually predictable. The engineering itself barely makes the list. Notice that three of the four are owned by the project team, not the engineer. That's actually good news — it means most delays are preventable by how the project is run, not by finding a faster engineer.

Engineering is applied information. I can only design from what I know — the survey, the soils report, the architectural backgrounds, the equipment cutsheets, the jurisdiction's requirements. When any of those arrive late or incomplete, I have two choices: wait, or design on assumptions that might prove wrong. Waiting delays the project; assuming risks rework. Neither is free. The fix is sequencing, not pressure. Get the survey and geotechnical work ordered the day the project is conceived, not the day engineering starts. Freeze the information the engineer is designing from, and route changes through a formal process so their schedule impact is visible before they're made. Information discipline is schedule discipline.

The owners whose projects finish on time do a few unglamorous things consistently. They make decisions on a defined rhythm instead of letting questions age. They keep one point of contact so answers don't get lost between parties. They resist scope changes during engineering — or they accept the schedule impact explicitly when changes are worth it. And they respond to their engineer's questions within days, not weeks. None of this is about rushing the technical work. It's about not starving it. An engineer with complete information and quick decisions is a fast engineer.

• Information gaps: late surveys, soils reports, and piecemeal backgrounds
• Scope changes: revising the design after engineering is underway
• Decision bottlenecks: equipment and system selections waiting on signatures
• Agency review: real but predictable — plan for it instead of fighting it
• Owner leverage: decide fast, freeze information, respond to questions in days