“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 thought it worth an extra reference about limitations of design knowledge (different to the design checking).

    1
    Bohn, R.E.: ‘Measuring and Managing Technological Knowledge’, in ‘The Economic Impact of Knowledge’ (Elsevier, 1998), pp. 295–314 linkinghub.elsevier.com (fee)
    Same Article in Sloan Management Review · January 1994 (MAM)

    DOI: 10.1016/B978-0-7506-7009-8.50022-7

    That said, I do remember the transition for circuit & PCB design layout from hand draughted circuits and separately hand crafted black crepe, and later red-blue masters, through checking continuity with highlighter pens, to complete connectivity checks on computers. Things like the "NC" component that has one connection (to consume the otherwise dangling 'no connection') and the 'dot' component that required [2-n] connections to be a junction, and every wire had just two ends, both of which must be connected.

    It's this level of 'dumb' checking and rules that is often missing. 

Reply
  • Hi thought it worth an extra reference about limitations of design knowledge (different to the design checking).

    1
    Bohn, R.E.: ‘Measuring and Managing Technological Knowledge’, in ‘The Economic Impact of Knowledge’ (Elsevier, 1998), pp. 295–314 linkinghub.elsevier.com (fee)
    Same Article in Sloan Management Review · January 1994 (MAM)

    DOI: 10.1016/B978-0-7506-7009-8.50022-7

    That said, I do remember the transition for circuit & PCB design layout from hand draughted circuits and separately hand crafted black crepe, and later red-blue masters, through checking continuity with highlighter pens, to complete connectivity checks on computers. Things like the "NC" component that has one connection (to consume the otherwise dangling 'no connection') and the 'dot' component that required [2-n] connections to be a junction, and every wire had just two ends, both of which must be connected.

    It's this level of 'dumb' checking and rules that is often missing. 

Children
No Data