Engineer Electric Work common mistakes
Engineer Electric Work · Understand the traps and how to avoid them.
When computing per-unit or three-phase quantities, the candidate mixes phase and line values without tracking the √3 factor, for example treating a 400 V line-to-line motor as if its phase voltage were 400 V, or forgetting that apparent power S = √3·V_LL·I_L.
Textbook formulas are memorized in two forms (per-phase and per-three-phase) and the candidate grabs whichever form surfaces first, without a habit of labelling whether each given value is phase or line. Diagrams in study material usually hide the conversion in the worked steps.
What to do instead
Before any substitution, write a small table with columns V_phase, V_line, I_phase, I_line, Z and fill in the knowns with units, then apply the star/delta relations (V_L = √3·V_ph at 30° lead, I_L = √3·I_ph). Do ten mixed drill problems where the given quantity is deliberately ambiguous until you classify it, and check each answer by computing total power twice (per-phase times three, and √3·V_L·I_L·cosφ).
The candidate answers protection questions by selecting the device that 'sounds protective' (for example choosing a surge arrester for an overload, or a fuse for an earth fault on a TN system) rather than checking whether the protective device's characteristic curve and setting actually clear the fault within the disconnection time the earthing arrangement requires.
Protection topics are studied as a list of device names and functions rather than as coordination problems. The candidate has not internalized that the answer depends on fault type, system earthing, and required disconnection time, so recognition memory substitutes for analysis.
What to do instead
Build a one-page decision matrix: rows are fault types (overload, short circuit, earth fault, arc flash), columns are devices (MCB, MCCB, fuse, RCD, IDMT overcurrent relay, differential, distance). For each cell write the sensing quantity and the standard disconnection time it must meet. Practise by reading a coordination study and predicting which device trips first, then verify against the time-current curves.
On installation and wiring-design items the candidate sizes a conductor from current-carrying capacity alone and stops, ignoring voltage drop, derating for ambient temperature and grouping, and the adiabatic check that the protective conductor can withstand fault energy.
Ampacity tables are the most rehearsed part of the topic, so the candidate treats 'Ib ≤ In ≤ Iz' as the whole method. Voltage drop and thermal-withstand checks appear as separate chapters in study material and are not rehearsed as part of one continuous design calculation.
What to do instead
Adopt a fixed six-step design checklist and run it on every conductor question: design current, protective device rating, tabulated capacity, correction factors (Ca, Cg, Ci), voltage drop against the limit (typically 3 percent lighting, 5 percent other), and adiabatic k²S² ≥ I²t. Do three full worked examples end to end, including a long cable run where voltage drop, not ampacity, governs the size.
The candidate treats code and standards questions as general knowledge and answers from site habit or 'what is normally done', rather than from the specific requirement, edition, and clause scope. This shows up as quoting an outdated edition, applying a domestic wiring rule to an industrial installation, or confusing a recommendation with a mandatory requirement.
Codes are learned by osmosis on the job, where local practice and older editions dominate. Candidates rarely practise locating a requirement in the actual standard text under time pressure, so they cannot distinguish 'shall' from 'should' or identify which part of a multi-part standard governs.
What to do instead
Study with the standard open beside the questions. For each topic, note the part number, clause number, and the exact wording of the requirement, and mark whether it is 'shall' or 'should'. Build a personal index of the twenty clauses most likely to be tested (disconnection times, IP ratings, cable support, earthing, isolation). When practising, cite the clause before choosing an answer.
On machinery questions the candidate confuses equivalent-circuit parameters with terminal behaviour: treating magnetizing current as negligible when the question is about no-load losses, misapplying the slip formula, or assuming a transformer's voltage regulation is zero because it is 'just a ratio device'.
The candidate memorized the equivalent circuit diagram but never connected each element to a measurable test result (open-circuit, short-circuit, locked-rotor, no-load). Without that link, the model is a picture rather than a tool, and sign conventions and referred values get muddled.
What to do instead
For each machine, write the test-to-parameter map: open-circuit test gives core loss and magnetizing branch; short-circuit test gives copper loss and series impedance; locked-rotor gives starting current and torque. Then solve five problems where the same machine is asked about efficiency, regulation, and starting performance, and check that your parameter values stay consistent across all three.
The candidate answers generation and grid-operation questions by reciting equipment names without connecting them to the control objective, for example describing a governor as 'controlling voltage' or an AVR as 'controlling frequency', or treating reactive power support and frequency response as interchangeable.
Generation is often studied as plant description (boiler, turbine, generator) rather than as a control system. The candidate has not built the cause-and-effect chain from load change to frequency deviation to governor response, or from voltage deviation to excitation response.
What to do instead
Draw two separate control loops and label them: active power and frequency (governor, droop, primary and secondary reserve), and reactive power and voltage (AVR, excitation, tap changer, compensation). For each, write the measured variable, the actuator, and the timescale in seconds. Then answer practice items by first naming which loop the question is about.
The candidate skips the safety and environmental framing and answers as if the question were purely technical, for example recommending a switching sequence without stating isolation, lock-out/tag-out, proving dead, and earthing, or ignoring arc-flash boundaries and PPE categories when describing work on live equipment.
Safety content is perceived as common sense and therefore under-rehearsed, while technical content absorbs all study time. Candidates also underestimate how often exam items reward the sequenced safe procedure over the technically elegant one.
What to do instead
Convert safety into procedures you can recite in order. Write and memorize a switching-and-isolation sequence (identify, notify, isolate, lock and tag, prove dead, earth, and issue the permit) and an arc-flash response sequence. For every technical scenario you practise, add one sentence on the safe method of working and check whether the answer changes.
The candidate misreads the question stem's qualifiers, choosing the 'best' answer to a question that asked for the 'first' action, or the 'least' likely cause in a list, and then defends the choice because the option is factually true.
Exam items are written so that several options are true statements; only one satisfies the specific demand of the stem. Under time pressure the candidate pattern-matches to a familiar phrase and stops reading before the operative word.
What to do instead
Train a stem-reading habit: underline the operative word (first, best, least, except, primary) and the object of the question before looking at the options. In practice, for every item you get wrong, record whether the error was knowledge or stem interpretation; if interpretation dominates, do sets where you answer only with the operative word circled and no calculation.
The candidate answers ethics and project-management items with aspirational generalities ('act with integrity', 'communicate openly') instead of identifying the specific obligation, the correct escalation path, and the party to whom the duty is owed in the scenario given.
These domains feel subjective, so candidates do not prepare a decision framework. They also conflate personal morality with professional codes of conduct, which specify duties to the public, the employer, and the regulator in a defined order of precedence.
What to do instead
Learn the precedence order in the applicable code of ethics (public safety first, then the law, then the employer, then the profession) and practise applying it to short scenarios: conflicting instructions, undisclosed design changes, sign-off pressure, and conflicts of interest. For each scenario, name the duty, the person owed, the first action, and the record to be kept.
The candidate manages time badly by sinking ten minutes into one calculation-heavy item, then rushing the remaining questions and guessing on straightforward recall items that would have been easy marks.
Calculation items feel productive and candidates dislike leaving a number unfinished, so they escalate commitment. Without a practiced pacing plan, they also do not know their own speed per item type.
What to do instead
Do two timed mock runs and log the time per item by domain. Set a hard per-item cap (roughly one minute for recall, three for calculation), flag and move on when the cap is hit, and reserve the final ten minutes for flagged items and a check that no answer is blank. Practise the deliberate abandon-and-return habit until it feels routine.