APCO PST1 common mistakes
APCO PST1 · Understand the traps and how to avoid them.
Runs the interview in whatever order the caller offers, so the address or callback number is never obtained, or arrives only after several minutes of narrative.
Adrenaline and a distressed caller feel like a demand for speed; new telecommunicators mirror the caller's urgency and start solving the problem before they know where the problem is.
What to do instead
Drill a fixed anchor order out loud - nature, location, callback, then details - until it survives stress. In scenario items, ask yourself 'do I have all four anchors before I decide anything?'
Assigns a call type and priority from the caller's tone or first sentence and never changes it when later answers alter the picture (a 'fender bender' that turns out to have an injured passenger).
First-impression anchoring plus pressure to clear the call quickly; candidates treat the classification as a label rather than a working hypothesis that must be tested.
What to do instead
Write the specific answers that force a reclassification - weapons, injuries, patient count, fire or smoke, hazmat, caller in danger - and re-ask those before ending the call, stating the priority as tentative rather than final.
Transmits without a call-up, uses pronouns ('tell him to move') instead of unit designators, and skips readback of the address, assigned unit, and response mode.
Conversational habits carry over into the radio; without live practice the formal format is not automatic when the channel is busy and time is short.
What to do instead
Rehearse one fixed format - called unit, self-identification, content, readback of critical items. Read back addresses, unit IDs, and response mode every time, and speak digits individually with standard phonetics.
Treats all traffic as equal: keeps routine transmissions running after a unit declares emergency traffic or presses the emergency button, and cannot say who holds channel priority.
Routine traffic feels productive and urgent; candidates do not recognize the markers of an emergency transmission, such as the words 'emergency traffic' or 'mayday', a unit keying up without speaking, or an open carrier.
What to do instead
Memorize the priority ladder and the required response to 'emergency traffic only' - stop routine traffic, acknowledge, obtain unit status and location. Practice the emergency-button scenario in CAD until the sequence is automatic.
Uses ALI, ANI, Phase I, Phase II, and TTY/TDD interchangeably, and assumes the address on the screen is where the caller actually is.
These terms appear only in the classroom until a real call arrives; candidates memorize acronyms without learning what each one delivers or fails to deliver.
What to do instead
Build a one-page table: what each technology supplies and what it cannot (Phase I gives a cell sector only; Phase II gives coordinates with an accuracy figure; VoIP and text may carry no usable location; TTY requires specific conventions). Adopt the rule that location is always verified verbally.
Freezes when asked what happens if the 911 trunk, the CAD system, or building power fails - cannot describe alternate routing, the backup PSAP, or manual operating mode.
Candidates learn the software, not the failure modes; redundancy procedures are usually trained once, on a day when nothing breaks.
What to do instead
Write from memory the sequence for a CAD outage, a trunk failure, and a power loss, including who notifies whom. Ask a supervisor for the agency's actual backup plan, then rewrite the sequence from memory weekly until it is fluent.
Confirms details of an incident for a friend, family member, or reporter, or posts and comments about calls online, believing that only a formal records request is restricted.
The wish to be helpful and the need to process a hard call by talking about it; the 'need to know' test and the caller's right to privacy are not intuitive to newcomers.
What to do instead
Apply the rule that nothing is confirmed to anyone lacking an operational need to know; route every outside request to the supervisor or records custodian; process difficult calls through peer support or the employee assistance program without identifying details.
Gives medical, legal, or procedural advice ('you don't need an ambulance', 'you can't press charges for that') or promises a response time, then fails to record what was said.
Callers demand answers and the telecommunicator wants to reassure them; scope-of-practice boundaries feel bureaucratic in the middle of a tense call.
What to do instead
Use scripted, non-committal phrasing, stay strictly within EMD or agency protocol, and document verbatim statements, times, and advice given during the call rather than reconstructing them after the shift.
Confuses ICS and NIMS roles - mixing up the Liaison Officer, Public Information Officer, Safety Officer, and unified command - or cannot explain where a PSAP sits relative to the EOC and mutual aid.
ICS is studied as a chart with no scenario attached; telecommunicators rarely deploy to an incident, so the roles remain abstract vocabulary.
What to do instead
Redraw the ICS organization from memory and attach one concrete situation to each role; learn that ESF-2 covers communications and that the PSAP is an operational element supporting the response, not the EOC itself.
Uses acute stress, cumulative stress or burnout, compassion fatigue, and critical incident stress as synonyms, and cannot name the interventions - defusing, debriefing, peer support, EAP - or when each is appropriate.
Stress content reads like common sense, so it gets skimmed; the distinctions are vocabulary the candidate has never had to apply to themselves or a coworker.
What to do instead
Build a four-row comparison table with a personal example in each row, plus timing for each intervention (defusing within hours, debriefing days later, peer support and EAP at any point), and list the warning signs you would notice in a colleague.