“Every Engineer Deserves a Buddy Who Never Misses a Code”

As an Electrical Engineer and MEP Consultant working on DEWA and UAE authority submissions, I’ve been thinking a lot lately about a stage of our work that rarely gets talked about outside the industry — the approval process itself.

Most experienced MEP design engineers I’ve spoken with share the same frustration: the approval stage sometimes undoes everything — unexpected errors, missed updates to regulations, or details lost somewhere in a long design process — leading to endless revision cycles.

Reflecting on my own submissions over the years, I keep coming back to the same question: local codes and regulations are accessible, sure, but realistically, how much time do we spend reading through them, cross-checking every clause, just to end up complying to a single reviewer comment weeks later?

What if there was an assistive tool that could help detect, review, and suggest corrections to MEP drawings before submission — something that works alongside how an engineer already thinks and designs, not against it?
I’m not talking about replacing engineering judgment — I’m talking about reducing the hours spent manually cross-referencing codes, so more time goes into actual design thinking, not repetitive compliance-checking.

I’d genuinely love to hear from fellow engineers on this: how much of your time on a typical project goes into revisions caused by things that could’ve been caught earlier? If you had a reliable assistive tool in your corner — something like a trusted buddy at work, quietly double-checking things before submission — would that actually change how you work? Or is there something about the process I’m not seeing?

Parents
  • Hi, thanks for bringing this up! I agree with you on this aspect but to add to it, where possible assistive technology (AI) would be beneficial for the purpose of giving a tentative guide/direction as the case may be, which must be reviewed and validated by human judgement for the purpose of accountability and ownership as somebody must be held responsible where there are mistakes or gaps considering the sensitivity and risk implications of the task involved.

    I’m not talking about replacing engineering judgment — I’m talking about reducing the hours spent manually cross-referencing codes, so more time goes into actual design thinking, not repetitive compliance-checking.

    What if there was an assistive tool that could help detect, review, and suggest corrections to MEP drawings before submission — something that works alongside how an engineer already thinks and designs, not against it?
    I’m not talking about replacing engineering judgment — I’m talking about reducing the hours spent manually cross-referencing codes, so more time goes into actual design thinking, not repetitive compliance-checking.
Reply
  • Hi, thanks for bringing this up! I agree with you on this aspect but to add to it, where possible assistive technology (AI) would be beneficial for the purpose of giving a tentative guide/direction as the case may be, which must be reviewed and validated by human judgement for the purpose of accountability and ownership as somebody must be held responsible where there are mistakes or gaps considering the sensitivity and risk implications of the task involved.

    I’m not talking about replacing engineering judgment — I’m talking about reducing the hours spent manually cross-referencing codes, so more time goes into actual design thinking, not repetitive compliance-checking.

    What if there was an assistive tool that could help detect, review, and suggest corrections to MEP drawings before submission — something that works alongside how an engineer already thinks and designs, not against it?
    I’m not talking about replacing engineering judgment — I’m talking about reducing the hours spent manually cross-referencing codes, so more time goes into actual design thinking, not repetitive compliance-checking.
Children
  • I’m not talking about replacing engineering judgment — I’m talking about reducing the hours spent manually cross-referencing codes, so more time goes into actual design thinking, not repetitive compliance-checking.

    This is a dumb CAD option. That is, it's not some flashy CAD option that can be sold with a glossy advert campaign, such as all the parametric design CAD stuff.

    It is a gap in the market, but then again it's not sexy, and it needs to plug into existing CAD systems, so less likely to be developed.

    It's like clash detection for screwed fasteners. The threads clash (design intent) but need clash detection for incorrect lengths, or diameters. So dumb, so obvious, so not a feature..

  • Henry — appreciate you reinforcing the human-in-the-loop point. Accountability has to stay with the engineer; the goal is removing hours of manual cross-referencing, not decision-making.