1.6 Using the Practice Bank, Error Log, and Code Index

Practice as a controlled feedback system

The local master electrician practice bank has 200 items. The source brief lists 41 items in feeders and branch circuits, 33 in motors and generators, 33 in wiring methods, 32 in special occupancies, 31 in equipment and devices, 21 in services, and 9 in general. That mix is useful, but it is not the same as the R16/T16 domain outline. Your job is to use the bank as training material while keeping the official outline as the weighting source.

Do not measure progress only by percent correct. Percent correct is a scoreboard, not a repair plan. A candidate who scores 78% by guessing quickly on weak questions is in a different position from a candidate who scores 78% with slow but accurate lookups. The first has concept risk. The second has timing risk. The exam does not care which risk caused the missed point. Your study system must identify both.

Build an error log with fixed fields. Use date, question ID, domain, article route, correct source, error type, time spent, why the wrong answer was attractive, and repair action. Error types should be specific: wrong code edition, wrong article, missed definition, used general rule despite special article, calculation setup error, arithmetic error, table note missed, exception misread, continuous load factor missed, conductor count error, grounding versus bonding confusion, or time pressure guess. A vague note such as study services is too weak.

A strong log entry looks like this: Services, Article 230 plus 250, missed bonding jumper route, chose grounding electrode conductor table instead of bonding rule, 5 minutes 40 seconds, repair by building service grounding and bonding one-page route in approved notes if allowed or in study notebook if not allowed. The point is not to write a diary. The point is to make the next similar question faster and more accurate.

Pair the error log with a personal code index. This is not a loose exam-room sheet unless the rules allow it, which the current source brief generally does not for computer-based exams. During study, it is a learning tool. For each recurring topic, write the trigger phrase, likely article, table or section route, and trap. Example: box fill, Article 314, count conductors by function, device yoke allowance, grounding conductor allowance, internal clamp if applicable, volume table. Example: motor OCP, Article 430, separate overload from short-circuit and ground-fault protection, do not use one rule for all devices.

Over time, convert the personal index into legal book navigation. If loose paper is prohibited, the final exam-room version must live in memory, permitted ink notes, highlights, and permanent tabs. That is why every index entry should end with a book action: tab Article 430, highlight table title, underline exception trigger, or add a short ink cross-reference if allowed. The study notebook teaches the route; the reference book executes the route.

Use three kinds of practice sets. Domain sets isolate a topic. They are best after reading or repairing a weak area. Route sets mix topics that share a navigation pattern, such as all conductor ampacity questions or all special occupancy overlays. Mixed timed sets simulate the exam. A mature plan uses all three. Domain-only practice can create false confidence because the question label tells you where to look. The real exam asks you to classify first.

Timing should be logged from the beginning. Mark each question as recognition, lookup, calculation, or stuck. Recognition means you knew the concept and used the book only to confirm if needed. Lookup means the route was known but required source reading. Calculation means arithmetic and setup controlled the time. Stuck means you did not know the route. The repair differs for each. Recognition misses need careful reading. Lookup misses need better tabs or article maps. Calculation misses need setup templates. Stuck misses need concept study.

When using the bank, rebalance against the outline. Services and service equipment are 16% of R16/T16 but only 21 of the 200 local items in the brief. General knowledge is 12% but only 9 items. That means a candidate who only exhausts the local bank may undertrain general and service topics. Add self-made drills from the official references, instructor materials, or additional compliant practice sources, but label any outside material by code edition and source quality.

A weekly workflow can be simple. Day 1: take a 30-question mixed set and log every miss or slow solve. Day 2: repair the top two article routes. Day 3: take a domain set in the weakest high-weight area. Day 4: build or refine the code index for repeated traps. Day 5: take a timed route set, such as wiring methods and box fill. Day 6: take a longer mixed set. Day 7: review only the log, not random new questions. This cycle prevents endless question consumption without learning.

The final two weeks should shift from learning to execution. Use full or half-length timed sets with the exact allowed references and calculator. Practice answering every question, flagging without panic, and changing answers only for evidence. Review the error log for patterns that still repeat. If the same route fails three times, stop taking random tests and repair that route directly. Master-level study is not volume for its own sake. It is controlled correction until the common exam tasks have predictable source paths.

Structured Decision Aid

• Tag every miss by domain, reference route, calculation step, and reason for the wrong answer.
• Rewrite missed calculation setups before repeating the same practice item.
• Keep a code-index notebook organized by problem type rather than by article number alone.
• Retest weak domains under timed conditions after each remediation cycle.