2.4 Shall, Shall Not, Permitted, and Informational Notes

The verbs carry the rule

Electrical workers often focus on numbers: amperes, volts, conductor sizes, raceway fill, distances, and percentages. The NEC also tests verbs. Words such as shall, shall not, permitted, not required, and informational note tell you whether a statement is mandatory, prohibited, allowed, optional, explanatory, or merely a pointer to other material. On an open-book exam, two answer choices may contain the same equipment and the same number, but one changes a shall into a may. That is enough to make it wrong.

A practical reading system is to mark the force of the sentence before solving the details. If the rule says something shall be done, treat it as required unless a valid exception applies. If it says something shall not be done, treat it as prohibited unless the code gives a specific allowance. If it says a method is permitted, that method is allowed, but the code may also allow other methods. If a note is informational, use it for understanding and cross-reference, but do not treat it as a standalone command.

Permitted does not mean required

Permissive language is a frequent distractor. If the NEC permits a wiring method in a certain condition, that does not always mean the method is required. Another compliant method may also exist. A multiple-choice answer that says must be installed by Method A can be wrong if the code merely permits Method A among several choices. The exam may test whether you recognize the difference between minimum safety requirements and acceptable design options.

The same idea applies to equipment and installation choices. A rule may permit a disconnect at a certain location, permit a raceway type under certain conditions, or permit a conductor identification method. If the question asks which installation is permitted, that language is helpful. If it asks what is required, do not upgrade permitted language into a mandate.

Shall not and negative stems

Prohibitive language deserves slow reading. A stem may ask which installation is not permitted, which condition violates the code, or which statement is false. Combine a negative stem with shall not and the logic can flip. Underline the task: are you finding the compliant option or the violation? Many wrong answers come from selecting a true statement when the question asked for the exception.

A good test habit is to rewrite negative questions in a short phrase. For example: find the violation. Then check each option against the rule. Do not carry the negative wording in your head for all four choices. Convert it once, then test each answer like an inspector.

Informational notes and enforceability

Informational notes can be very helpful. They may point to related standards, explain a hazard, provide a design consideration, or remind the reader about another rule. But an informational note is not the same as a mandatory rule. If an answer depends only on a note, be careful. The correct answer usually needs support from a shall statement, a shall not statement, a table, a definition, an exception, or a listed reference that the exam catalog includes.

This distinction matters for voltage drop, coordination, maintenance, and design guidance. Good workmanship may exceed minimum code. A note may encourage the designer to consider performance or safety issues beyond the strict requirement. The exam may still ask about the recommendation, but the stem should make that clear. If it asks for a code requirement, look for mandatory wording.

Exceptions and conditions

Exceptions are not loopholes to apply broadly. They are conditional instructions. The main rule applies first. Then the exception may remove, reduce, or alter the requirement if the installation meets every condition in the exception. If a question includes details about occupancy type, voltage, supervision, conductor location, equipment listing, or physical protection, those details may decide whether the exception is available.

Read exceptions in this order:

1. State the main rule in your own words.
2. Identify what the exception changes.
3. List the conditions required for the exception.
4. Compare the stem facts to each condition.
5. If any condition is missing, return to the main rule.

This prevents overusing exceptions. The exam may give an answer that quotes the general idea of an exception but omits a condition. That answer is attractive because it sounds code-like. It is still wrong if the facts do not fit.

Case examples

Case 1: A question asks which of four wiring methods is permitted in a location. One option is explicitly allowed when physical damage protection and listing conditions are met. If the stem includes those conditions, that option may be correct. If the stem asks which wiring method is required, the same option may be wrong because permitted does not mean exclusive.

Case 2: A note points to another standard for additional information. If the question asks what the NEC requires, do not use the note alone as the command. If the question asks where additional explanatory information can be found, the note may be the clue.

Case 3: A rule prohibits an installation unless a listed assembly is used. The presence of a listed assembly in the stem is not decoration. It may move the condition from prohibited to allowed. Conversely, if the stem omits listing, do not assume it exists.

A code book is a legal-style technical document. Numbers matter, but verbs decide force. Train yourself to read shall, shall not, permitted, exception, and informational note before picking the answer that merely sounds familiar.