EIM NC II common mistakes
EIM NC II · Understand the traps and how to avoid them.
Writing the incident or hazard report only after being told to, and leaving out the date, exact location, people involved, and immediate action taken, so the report cannot be used to trace or correct the hazard.
Candidates treat documentation as paperwork to finish quickly and copy a template without checking that each field is filled with real facts. They often think verbal reporting to a supervisor is enough.
What to do instead
Keep a small notebook or log sheet on the job and record the five Ws (what, where, when, who, what was done) at the moment of the event. Before submitting, re-read the report and confirm every field is complete, legible, and signed. Practice filling one sample report per shift until it becomes routine.
Answering a mock interview or self-assessment by describing what the company does or what the team achieved, instead of naming personal skills, training completed, and specific career goals with a timeline.
Candidates memorize generic answers and are not used to talking about themselves in concrete terms. They underestimate how much the assessor looks for self-awareness and a realistic career plan.
What to do instead
Prepare a one-page personal profile listing technical skills, certificates held, and two or three short-term and long-term goals with dates. Rehearse answers using the pattern: skill, evidence of where it was used, and how it links to the target job. Ask a peer to check that every answer is about you, not the team.
Giving instructions to teammates as orders without confirming understanding, and failing to report back to the supervisor when a task is delayed or a team member is overloaded.
Under exam pressure candidates focus on finishing their own task and assume others understood the first time. They also fear that reporting a delay looks like admitting failure.
What to do instead
Use a short briefing before each task: state the goal, who does what, the deadline, and ask the listener to repeat it back. Report progress at agreed checkpoints even when nothing is wrong. Practice a two-minute handover script so reporting becomes a habit, not an exception.
Handling a rigging or cable task without inspecting the equipment first, and continuing to work when a damaged connector, frayed cable, or missing safety pin is found, relying on 'it will hold for the event'.
Time pressure and the desire to look competent lead candidates to skip pre-use checks. Many have never seen a failure and underestimate how quickly a damaged sling or unrated clamp fails under load.
What to do instead
Follow a written pre-use checklist for every item: visual inspection, rating label, connector lock, cable insulation, and load calculation. Tag out and report any defective item before use. Rehearse the checklist on practice equipment so it takes under a minute per item and becomes automatic.
Skipping the calibration and zeroing step on sound level meters or other measuring instruments, and recording readings without noting the instrument ID, calibration date, or measurement conditions.
Candidates see calibration as a formality and assume the instrument was calibrated by someone else. They also do not realize that an uncalibrated reading invalidates the whole measurement record.
What to do instead
Before measuring, verify the calibration sticker and perform the field check with the reference source, recording the result. Log instrument ID, calibration due date, time, location, and conditions on every record. Treat any out-of-calibration instrument as unusable and report it.
Saving work files to the desktop or a personal USB drive with names like 'final2', and leaving the workstation logged in when stepping away.
Candidates default to the fastest save location and are not used to shared-file conventions or account security. They assume the next user will sort out the files.
What to do instead
Adopt the organization's folder structure and naming convention (project, date, version) and save to the designated network or shared drive. Lock the screen every time you leave the station. Practice the save-and-lock routine until it is automatic, and check the file location before closing any application.
Connecting powered audio and lighting equipment with the main switch on, or plugging line-level and microphone-level sources into the wrong inputs, then blaming the equipment when there is hum or no signal.
Candidates rush to get sound or light quickly and skip the power-down sequence. They also do not consistently check signal level and connector type before plugging in.
What to do instead
Follow a fixed power sequence: connect all cables with power off, set levels and gain to minimum, power on sources first and amplifiers last, and reverse the order when shutting down. Label inputs by source and level, and verify each channel with a test signal before the event. Keep a signal-flow diagram at the console.
Setting up a projector or display without checking native resolution, aspect ratio, and keystone correction, so the image is stretched, cropped, or blurry during the event.
Candidates plug in the cable, see an image, and consider the job done. They do not check the source output settings or the projector's input mode, and they adjust keystone by eye rather than by geometry.
What to do instead
Before the event, match the source resolution to the projector's native resolution, set the correct aspect ratio, and position the projector so minimal keystone is needed. Test with the actual presentation file and check text legibility from the farthest seat. Record the working settings so the setup can be repeated.
Troubleshooting a dead channel by swapping random cables and components instead of working through a signal path from source to output, and not writing down what was changed.
Candidates panic under time pressure and rely on guesswork. They do not have a mental model of the signal chain, so they replace parts without isolating the fault.
What to do instead
Use a divide-and-conquer method: confirm the source with a known-good signal, then test each link in order (cable, connector, mixer channel, amplifier, speaker). Change one variable at a time and log each change. Keep a known-good test cable and signal generator in the toolkit and practice the routine on a bench setup.
Giving a one-line reply such as 'done' or 'ok' when asked for a status update, without stating what was completed, what remains, and any issue that needs a decision.
Candidates think brevity sounds professional and assume the supervisor already knows the context. They also avoid raising problems because they fear being blamed.
What to do instead
Use a three-part update: completed, in progress with expected finish time, and blockers or decisions needed. Keep it to a few sentences and confirm the supervisor understood. Practice with a partner who asks follow-up questions until the update answers them without prompting.