I am a mechanical engineer by training, but no MEP discipline works in isolation. A chiller, air-handling unit, fire pump, exhaust fan, boiler, or packaged rooftop unit can be properly selected and still create permit or field problems when voltage, phase, overcurrent protection, disconnecting means, available fault current, controls, emergency power, or equipment responsibilities are not coordinated.
That is why I am launching Daily Code Talk: Sparky Edition. This series is part of an intentional effort to expand my electrical-code knowledge, better understand how electrical systems are designed and reviewed, and learn directly from the engineers, electricians, contractors, inspectors, manufacturers, and plans examiners who work with these requirements every day.
I am not starting this series because I have every answer - I am starting it because one of the best ways to understand a code is to study it, break it down, connect it to actual projects, and invite experienced professionals to challenge the interpretation.
What This Series Will Cover
The series will approach the 2026 NEC from the perspective of a mechanical engineer working at the MEP interfaces, with attention to: - Electrical design and permit documentation - Services, feeders, branch circuits, and equipment loads - Grounding, bonding, fault current, and overcurrent protection - Disconnects, listings, ratings, and manufacturer requirements - Emergency power, fire alarm, controls, and life-safety coordination - Mechanical-equipment electrical requirements - Existing-building verification and renovation risk - Field installation, inspections, and constructability - How electrical decisions affect overall building functionality
Most posts will publish in the evening. That timing is partly intentional - when the workday starts winding down, Sparky Edition powers up. We will begin with NEC Article 90, which establishes the Code's scope, purpose, organization, enforcement framework, and application.
Electrical professionals, feedback, corrections, field examples, and differing AHJ interpretations are welcome throughout the series. The goal is not simply to quote the NEC - it is to better understand how each requirement affects the drawings, equipment, installation, inspection, and final building operation.
How To Use This Series
Read Sparky Edition the same way you would read the IMC series on this site: as a coordination reference, not a substitute for the applicable code, the locally adopted edition, or a licensed electrical engineer's stamped design. Use it to recognize where mechanical, plumbing, and electrical scopes intersect, so those interfaces get flagged during design and plan review instead of being discovered in the field.
Masterbuild QA Lens
Most permit rework at the MEP boundary does not come from a single discipline getting its own code wrong - it comes from two disciplines each being individually correct while their interface was never checked. Sparky Edition exists to close that gap from the mechanical side: understanding enough NEC to ask the right coordination questions before a set is submitted, not after an inspector or contractor raises them in the field.
Professional Boundary
Osmany Portal, PE is a licensed mechanical engineer studying the NEC from the MEP-coordination perspective. This series is not a licensed electrical engineer's design authority. Project-specific electrical design, load calculations, and stamped electrical documents require a licensed electrical engineer of record. Always verify the locally adopted NEC edition and applicable AHJ amendments before applying any post in this series to a real project.
What electrical topic would be most valuable to examine from an MEP-coordination perspective?