Beginner Time: 15 min Type: Code Application Focus: Panel Design / NEC
After this module: Apply Table 110.26 correctly — read depth, width, and height requirements by condition of maintenance and voltage level.
Prerequisites: NEC Code Reading Fundamentals

Purpose

This module uses working-space review as a training example for how to read NEC tables and condition statements carefully.

Why this example matters

Working-space questions are useful training examples because they force the reader to:

NEC 110.26 defines working space for equipment operating at 1000 V nominal or less to ground. The table requires knowing the voltage to ground and the condition of the space on the opposite side.

Table-reading discipline

Use this order every time you open an NEC table:

  1. Verify the table title
  2. Identify the row logic
  3. Identify the column logic
  4. Read notes and condition descriptions
  5. Confirm the answer against the actual equipment condition

Do not jump straight to the number

A common mistake is to see a familiar table and grab a value before checking:

Conditions 1, 2, and 3 in Table 110.26(A)(1) describe what is on the opposite side of the working space:

Condition Description
1 Exposed live parts on one side and no live or grounded parts on the other
2 Exposed live parts on one side and grounded parts on the other
3 Exposed live parts on both sides

Getting the condition wrong changes the required depth from roughly 900 mm (3 ft) to 1.2 m (4 ft) or more.

Practical use outside an exam

The same discipline applies when reading any NEC table in real design work:

Working takeaway

Tables are not shortcuts around reading.

They are compact rule structures that still require:

Getting those three things right before reading the number is the discipline that prevents field rejections.


← NEC Code Reading Fundamentals ↑ NEC for Machines and Panels Motor and Panel Code Application →
Trust Boundary — Engineering Judgment Required

This site is a personal-use paraphrase and navigation reference for industrial automation standards. It is not a substitute for authoritative standards documents, professional engineering judgment, or legal review. All content is sourced from a local RAG corpus and has not been independently verified against current published editions.

Items marked TO VERIFY have limited or unconfirmed local coverage. Items marked NOT IN CORPUS are not covered in the local repository. Do not rely on this site for compliance determinations, safety-critical design decisions, or legal interpretation.