NENA ENP common mistakes
NENA ENP · Understand the traps and how to avoid them.
Treating the PSAP as the sole owner of the emergency number system and answering technology questions as if only the call-taking center matters, ignoring the network, database, and originating-service-provider layers.
Candidates study from a call-taker's viewpoint, where the phone simply rings, so they never learn how the call reached the PSAP or where 9-1-1-specific routing data lives.
What to do instead
For each technology item, draw the full path (caller device, originating carrier, selective router or ESInet, ALI/location database, PSAP CPE) and state which entity owns each hop before answering.
Confusing the functions of ALI with those of the MSAG, or assuming either one validates the other automatically.
Both are location-related databases and are often described together, so candidates collapse them into one concept and miss that the MSAG defines valid address ranges per emergency service zone while ALI stores the subscriber record.
What to do instead
Memorize one-line definitions and a mismatch example for each: an address not in the MSAG is a provisioning error, whereas a missing or stale ALI record is a database error, and each has a different correction path.
Answering call-processing questions with a generic 'gather information then dispatch' sequence instead of applying the domain's specific priority order and interrogation discipline.
Candidates rely on intuition from everyday phone conversation rather than the structured calltaking model, so they invert steps such as confirming location versus obtaining the nature of the emergency.
What to do instead
Practice scripting the first 30 seconds of a call out loud in fixed order, and for each scenario question identify which element (location, callback number, nature, safety) must be established before the next action.
Treating standards documents as interchangeable, attributing requirements to the wrong body or the wrong document.
Several organizations publish overlapping material, and candidates learn content without attaching it to a specific standard, edition, or scope.
What to do instead
Build a one-page matrix mapping each standard to its issuing body and its actual subject (for example, operational calltaking versus technical/functional requirements versus management accreditation), and quiz yourself on the mapping rather than the prose.
Giving a policy answer that ignores the legal or regulatory layer, such as handling a records or disclosure request as a pure customer-service decision.
Candidates default to helpfulness and operational convenience, forgetting that statutes, regulations, and retention rules constrain what a PSAP may release or retain.
What to do instead
For any governance scenario, first ask 'what rule governs this record or request?' and name the controlling authority before describing the operational response.
Answering supervision, discipline, or staffing questions with a single action (for example, 'counsel the employee') rather than a defensible, documented process.
Candidates think in terms of immediate interpersonal resolution and underestimate how much of management scoring depends on consistency, documentation, and progressive process.
What to do instead
Structure every HR answer as: identify the issue with objective evidence, apply policy consistently, document, provide the employee a path to improve, and follow up; then check the answer names each of those steps.
Designing public education responses around a single outreach event or slogan instead of a measurable, audience-targeted campaign with evaluation.
Community relations feels like marketing to candidates, so they propose awareness activities without objectives, partners, or success measures.
What to do instead
Answer with a mini campaign plan: target audience and barrier, message, channel and partner, timeline, and the specific metric used to judge whether behavior changed.
Confusing training evaluation levels, treating a high post-class satisfaction score as proof of on-the-job competence.
Candidates equate positive trainee feedback with learning and performance, skipping the distinction between reaction, learning, behavior, and results.
What to do instead
Label each proposed evaluation method with the level it actually measures, and pair any reaction survey with a skills assessment and a field-observation or performance metric.
Selecting a quality-assurance metric because it is easy to count rather than because it connects to an outcome, and proposing QA as random call review alone.
Candidates reach for familiar measures such as call volume or average handling time and do not distinguish process measures from outcome measures.
What to do instead
For each metric, state the decision it informs and the outcome it predicts; pair any efficiency measure with a quality or outcome measure so the answer shows balance.
Describing interoperability as mutual-aid goodwill or a shared radio channel, without addressing governance agreements, common terminology, or continuity-of-operations planning.
Candidates picture responders talking to each other and stop there, missing the planning, agreements, and standards that make interoperability repeatable.
What to do instead
Answer interoperability scenarios across the full set: written agreements, shared plans and terminology, technology and spectrum, training and exercises, and after-action review, and explicitly name which element the scenario is missing.