Practice exam review and test-day strategy

Six weeks before her exam, Lena took her first full practice test under real conditions: the code book she would bring, the calculator she would bring, a timer and no interruptions. She scored 68. Two weeks later she scored 73, and the week before the exam she scored 81. The improvement did not come from reading more of the code. It came from studying her mistakes. This last lesson sets out the method she used: how to take a practice exam, how to review it, how to turn the review into a study plan, and how to manage the clock and the book on test day. It ends with what happens after the score report arrives in each Kansas system.

The method works for any designated master exam, because those exams are national and share the same basic shape, as Lesson 4 explains. The numbers in this lesson's examples are illustrative. Use the question count, time and passing rules from your own exam's candidate bulletin.

Taking a practice exam properly

A practice exam is useful only if it is taken the way the real exam will be. That means the full number of questions in one sitting, the real time limit, only the references the bulletin allows, the same calculator, and no looking at answers until the end. Lena took hers at the kitchen table on Saturday mornings, with her phone in another room. Partial practice sets are fine for drilling a topic, but at least three full timed exams, spaced out over the study period, show whether pacing and endurance are where they need to be.

Use practice exams written for the same kind of exam and the same code edition. Questions written for an older edition can teach the wrong answer, and questions written for a journeyman exam will not show the depth of a master exam. The core courses in this series, MELU-101 through MELU-107, include practice questions by topic that can be used for drilling between full exams.

Reviewing every question

The review is where the learning happens, and it should take longer than the exam. Go through every question, not just the wrong ones, because a right answer reached by a lucky guess is a weakness too. For each question, find the code section that answers it, confirm the answer, and if you got it wrong or guessed, decide why. Lena sorted every miss into one of five causes.

• Did not know where to look: the section was not familiar, and the index search failed or took too long.
• Found the wrong rule: the right article, but the wrong section, exception or table.
• Misread the question: missed a word such as minimum, maximum, not or except, or a detail such as the voltage or the occupancy.
• Calculation error: a wrong step, a skipped factor or a keying mistake.
• Ran out of time: never reached the question or guessed in the last minutes.

Each cause has its own fix. Not knowing where to look calls for more index practice and better tabs. Finding the wrong rule calls for reading the whole section, including exceptions, when looking something up. Misreading calls for slowing down on the question stem. Calculation errors call for working each calculation the same way every time and checking units. Running out of time calls for the pacing plan below.

The error log

Lena kept an error log: a list with one line for each missed or guessed question, giving the topic, the code section, the cause and a one-sentence note on what she should have done. After each practice exam, she counted misses by topic and by cause. The counts told her where to spend the next two weeks. After her first exam, her biggest cause was not knowing where to look, mostly in the special occupancy chapters, so she spent a week on those chapters and their index entries. After her second, the biggest cause was calculation errors, so she reworked every load calculation in MELU-102.

# Error log summary after a practice exam (illustrative entries)
from collections import Counter
log = [("special occupancies", "where to look"), ("calculations", "calc error"), ("grounding", "wrong rule"),
       ("calculations", "calc error"), ("special occupancies", "where to look"), ("services", "misread"),
       ("motors", "calc error"), ("special occupancies", "where to look"), ("wiring methods", "time")]
by_cause = Counter(cause for _, cause in log)
by_topic = Counter(topic for topic, _ in log)
print("By cause:", ", ".join(f"{c} {n}" for c, n in by_cause.most_common()))
print("By topic:", ", ".join(f"{t} {n}" for t, n in by_topic.most_common()))

By cause: where to look 3, calc error 3, wrong rule 1, misread 1, time 1
By topic: special occupancies 3, calculations 2, grounding 1, services 1, motors 1, wiring methods 1

The last two weeks

The last two weeks are for consolidation, not new material. Take a final full practice exam about a week out, review it the same way, and use the remaining days to drill the topics and causes the log still shows. Re-read the bulletin. Check that the code book has no notes or loose material that the bulletin forbids. Confirm the test center address or the remote setup, the start time and the identification needed. And sleep. A tired candidate misreads questions that a rested one would not.

A pacing plan

Timed exams reward a plan. The usual approach is three passes. On the first pass, answer every question you can answer quickly, from memory or with a fast lookup, and flag the rest without dwelling on them. On the second pass, work the flagged questions that need a longer lookup or a calculation. On the third pass, use the time left to check flagged answers and make your best choice on anything still open. The passes keep a few hard questions from eating the time needed for many easy ones.

Set checkpoints. If the exam allows four hours for eighty questions, as in the illustrative example in Lesson 4, the first pass might aim to finish within about half the time, leaving the rest for the second and third passes. Check the clock at each quarter of the questions and adjust.

# Three-pass time plan (illustrative; use your bulletin's real numbers)
total_minutes = 240
plan = {"first pass: quick answers, flag the rest": 0.50,
        "second pass: flagged lookups and calculations": 0.38,
        "third pass: check flags, final choices": 0.12}
start = 0
for step, share in plan.items():
    minutes = round(total_minutes * share)
    print(f"{step}: minutes {start} to {start + minutes}")
    start += minutes

first pass: quick answers, flag the rest: minutes 0 to 120
second pass: flagged lookups and calculations: minutes 120 to 211
third pass: check flags, final choices: minutes 211 to 240

Using the book under time pressure

On test day the book is for confirming, not for learning. For a lookup question, go to the index or a tab, find the section, confirm the detail and move on. For an application question, read the question first and decide what rule you are looking for before opening the book. For a calculation, write the steps on the scratch material the test center provides, in the same order every time, and use the book only for the tables and factors. If a lookup takes more than about two minutes, flag the question and come back.

Answering when unsure

Many designated exams score only correct answers, with no penalty for a wrong one, which means a blank answer is always a lost point. Confirm the scoring rule in your bulletin. If it scores only correct answers, answer every question, even if the last few minutes go to making educated guesses. Eliminate options you know are wrong first; on a four-option question, eliminating two doubles the chance of a right guess.

Be wary of changing answers on the third pass without a reason. Change an answer when the code shows the first one was wrong, not because of a vague feeling. And watch for options built from common mistakes, as Lesson 4 explains: if a calculation matches an option suspiciously easily, check the step the question writer was most likely testing.

Using the core courses for final review

The error log points to topics, and the core courses supply the review for each. Lookups in general requirements and definitions go back to MELU-101 on navigating the code. Service, feeder and dwelling calculations go to MELU-102. Conductor sizing, adjustment and overcurrent protection go to MELU-103. Grounding and bonding go to MELU-104, motors, transformers and generators to MELU-105, and the special occupancy chapters to MELU-106. Business and law topics, if the bulletin lists them, go to MELU-107. Lena kept a short table matching each line of her error log to a lesson in one of those courses, so that each study session had a clear target and ended with a set of practice questions on the same topic.

Drill sets should be short and specific. Twenty questions on motor branch circuits, timed at the exam pace, teach more than an hour of reading about motors, because they force the same lookup and calculation steps the exam will. Lena ended each drill set by adding any new misses to the error log, so that the log stayed current until the last week.

Managing nerves

Most candidates are nervous, and some nervousness helps concentration. Too much makes people misread questions and forget lookups they know. The best cure is familiarity: by exam day, the format, the clock, the book and the calculator should all feel routine because the practice exams made them so. On the day, if a run of hard questions shakes your confidence, remember that the exam is built with a spread of difficulty, flag the hard ones, and go back to answering what you can. One bad stretch rarely decides the result; a panic that wastes twenty minutes can.

A Kansas checklist for the last week

• Confirm the exam is still on the approved list of each authority you plan to apply to, such as MABCD and Johnson County.
• Confirm the code edition in the bulletin matches the book you will bring.
• Confirm your experience proof is complete, so you can file the week you pass.
• Have the application form and fee ready for the first authority.
• Tell the company's office manager the exam date, so the qualified person filing can follow quickly.

Test day

Arrive early, with the identification the bulletin requires, the code book and any other allowed references, the allowed calculator and a spare battery. Expect the test center to inspect the book, and allow time for it. Store everything else in the locker. If you test remotely, start the system check early and clear the desk and room as the rules require. During the exam, use breaks if they are allowed and you need them, but know whether the clock stops; often it does not. Eat beforehand, because four hours is a long time on an empty stomach.

After the exam

Most computer-based exams give a result at the end of the session or soon after, with a score report. If you passed, the next steps are the ones in Lesson 3: file the application with the authority, with the score report, the proof of experience, the form and the fee. For Lena that meant MABCD first, then Johnson County, and then a filing by Little River to name her as a qualified person. If you did not pass, the score report usually shows performance by topic. Add it to your error log, check the retake rules and waiting period in the bulletin, and plan the next sitting with the same method.

Lena passed with 83. She filed with MABCD the following week and with Johnson County once her MABCD certificate issued. Pat filed the change of qualified person the day the certificate arrived. Gene took his first full week off in eleven years the month after.