IAED EFD common mistakes
IAED EFD · Understand the traps and how to avoid them.
Reading back a fire address or callback number without verifying it digit by digit against what the caller said, then dispatching to a transposed street number or a mistyped phone number.
Candidates treat verification as a formality because the address 'sounded clear', and they are thinking ahead to the next protocol question instead of confirming the data already collected.
What to do instead
Adopt a fixed verification script: repeat the full address including direction, street type, and apartment/suite, and the callback number in grouped digits, and require the caller to confirm each element before moving on. Practice by having a partner read addresses with deliberate transpositions.
Jumping into fire-specific questioning (flames visible, floor of fire, occupants trapped) before locking in location and callback number.
Fire calls feel urgent and candidates want to gather incident detail fast, so they invert the priority order taught in EFD calltaking.
What to do instead
Drill a hard sequence: location, callback, then incident interrogation, then protocol-specific questions. Use a mental checkpoint after each stage and do not advance until the prior stage is confirmed.
Selecting a determinant or response level from the chief complaint alone without completing the protocol's key questions that modify the code.
Candidates memorize common complaint-to-code pairs and shortcut the remaining questions under time pressure, missing upgrades such as trapped occupants or a confirmed working fire.
What to do instead
Work the protocol card top to bottom every time and treat every key question as mandatory unless the card explicitly allows a bypass. Build flashcards pairing each determinant with the exact answers that change it.
Failing to capture and relay safety-critical scene information such as hydrant location, gate codes, locked entries, hazardous materials, or hostile bystanders.
These details surface incidentally in conversation and candidates focus only on structured protocol fields, so the information is heard but never recorded or passed to responders.
What to do instead
Maintain a running 'scene notes' habit: after every caller statement, ask whether it changes access, safety, or resources. Practice scenarios where a gate code or chemical name is mentioned once mid-call and must appear in the dispatch remarks.
Giving pre-arrival instructions inconsistently or improvising them instead of using the approved scripted instructions for the situation.
Candidates are nervous about saying the wrong thing and either omit instructions or paraphrase them from memory, which changes meaning and liability.
What to do instead
Memorize the approved instruction sets verbatim for the highest-frequency fire scenarios and practice delivering them while simultaneously typing. If no approved instruction applies, escalate to a supervisor rather than improvising.
Letting the caller's emotional state dictate call control, either by matching the panic and speeding up or by arguing with an uncooperative caller.
High-stress fire calls trigger natural mirroring, and candidates have not practiced a consistent calming and structuring technique.
What to do instead
Use a rehearsed control phrase set: acknowledge the emotion in one short sentence, then give a direct instruction ('I am going to ask you three questions; answer as I ask them'). Practice with recorded role-players who yell, whisper, or refuse to answer.
Mishearing or failing to clarify similar-sounding letters and numbers (B/P/V, M/N, fifteen/fifty) without using phonetic clarification.
Candidates assume clarity rather than confirming it, and background noise or accents make audio genuinely ambiguous.
What to do instead
Default to phonetic alphabet for letters and digit-by-digit repetition for numbers whenever any ambiguity exists. Practice transcribing noisy audio and confirm the spelling of street names back to the caller.
Dispatching the wrong apparatus or alarm assignment because the candidate did not match the determinant to the local response matrix.
Candidates learn the protocol but not how their agency maps determinants to unit types and quantities, or they apply a neighboring jurisdiction's matrix.
What to do instead
Study the actual local response matrix alongside the protocol and practice translating sample determinants into a full unit list. Verify the matrix version in use and note any recent changes.
Dropping or delaying the transfer of critical information between calltaker and dispatcher, such as a later-reported change in conditions.
Candidates treat the initial dispatch as final and do not have a routine for updating an active incident when new information arrives.
What to do instead
Establish an update habit: any new safety or location information triggers an immediate remark update and, if it changes the determinant, a documented upgrade. Practice scenarios where a caller calls back with new information mid-incident.
Prematurely ending the call before confirming the address, repeating the callback number, and advising the caller what to do next.
Relief at completing the protocol leads candidates to close quickly, and callers are left without instructions or with an unverified location.
What to do instead
Use a fixed closing checklist: confirm address, confirm callback, state what will happen next, and give any final safety direction. Practice full calls end-to-end with a partner scoring the closing sequence.