How to Prioritize Simultaneous Incidents

Prioritization items give you several incidents at once and ask which gets attention first. They are testing whether you can reason about urgency under time pressure, not whether you have memorized a rulebook. The reasoning is learnable, and it is more consistent across scenarios than most candidates expect.

Before anything else: on the job, your agency protocol governs. Every center has its own call priority scheme, its own dispatch policy, and its own standards for what goes out first and with what resources. Those documents outrun any general principle, including everything in this article. What follows is reasoning for answering test items and for thinking clearly about urgency. It is not operational guidance, and a working dispatcher will rightly argue with anything presented as universal, because in their center it may simply not be true. Learn the reasoning for the exam. Learn the protocol at the academy, and then follow the protocol.

POST refers to the California Commission on Peace Officer Standards and Training. DispatchDrills is an independent study resource and is not affiliated with, endorsed by, or sponsored by POST.

The reasoning hierarchy

Three considerations do most of the work, in roughly this order.

Life safety over property. A threat to a person outranks a threat to things. This is the least controversial principle in the whole domain and it resolves a large share of test items on its own. A person not breathing outranks a burglary. A person trapped outranks a vehicle on fire with nobody in it.

In progress over cold. Something happening now outranks something that finished. An assault occurring as the caller speaks outranks an assault reported an hour after the fact, because the first can still be interrupted and the second cannot. Time changes what a response can achieve.

Confirmed over reported. Where two calls are otherwise comparable, better information generally earns priority, because you can act on it with more confidence.

That third principle carries an important exception, and test items lean on it. An unconfirmed report of immediate danger to a person is not outranked by a confirmed property crime. If someone thinks they hear a child screaming next door, the uncertainty does not demote it below a confirmed break-in at an empty storefront. The cost of being wrong is asymmetric: send someone to check on the screaming and you have wasted a unit, ignore it and you may have missed the only thing that mattered all shift. Life safety sits above the confidence question, not underneath it.

Sort the whole set, not pairs

The most common process error on these items is comparing incidents two at a time. You weigh A against B, decide A wins, then weigh B against C, and by the time you reach the end you have a chain of local comparisons that do not add up to a coherent order. It is slow, and it produces inconsistent answers on scenarios where you actually knew the reasoning.

Sort the whole set instead, in one pass, using a simple sieve:

1. Scan for life threat. Read every incident and mark which involve a person in immediate danger. Nothing else matters until this group is identified.
2. Order within that group by immediacy. Happening now beats about to happen beats already over. Number of people at risk breaks near ties.
3. Order the remainder by whether it is in progress. In-progress property crime, then recent, then cold reports and paperwork.
4. Break residual ties on information quality. Confirmed detail before secondhand, everything else equal.

One pass, four questions, and you have a full ordering rather than a tangle of pairwise judgments. It is also faster, which matters when the item is timed. Our prioritization module presents sets rather than pairs specifically so you can rehearse this sieve, and the decision-making module extends it to situations where the right answer is a choice of action rather than an ordering.

Traps that catch good candidates

Loudness is not severity

The most reliable trap in the whole category is emotional intensity standing in for urgency. A caller who is screaming may be reporting a fender bender. A caller who sounds flat and controlled may be describing a person who has stopped breathing, either because they are in shock or because they are trained. Test writers know this and construct items around it.

Separate the caller from the incident. Ask what is actually happening, to whom, and whether it is still happening. The caller's volume tells you how to talk to them. It tells you nothing about where their call belongs in the queue.

The flip side matters too. A hysterical caller reporting something minor still outranks nothing at all. A distressed person reporting a stolen bicycle is a real call that gets handled. Recognizing that a call is low priority is not the same as dismissing it, and items sometimes check whether you can hold both thoughts.

Detail is not importance

Scenarios that give you a lot of description can feel more significant simply because there is more of them on the page. Length is a writing artifact. A three-line incident with a person in danger outranks a paragraph about a parking dispute, no matter how much texture the paragraph has.

Resolved is not urgent

Items often include something that sounds alarming and then resolves inside its own description: a fire that has been put out, an intruder who has left, an argument that ended before the call connected. The alarming words stay in your head. Read to the end of every incident before ranking any of them.

Do not over-invent

Candidates who know a bit about the job sometimes add facts: the caller might be lying, the fire might reignite, the person who left might come back. Those are reasonable operational instincts and they wreck test items. Rank what you are told. If two incidents genuinely tie on the information given, the item is usually testing something else.

A worked example

Four incidents arrive together. All names, streets and plates here are invented.

Call	What you have
A	Confirmed break-in at a closed hardware store on Ospringe Lane. Alarm company on the line, no persons on site.
B	Caller thinks the neighbor at 3312 Marmot Ridge is having a medical emergency. Has not seen inside. Caller is calm.
C	Screaming caller reporting a two-car collision with no injuries, both vehicles drivable, blocking one lane.
D	Report of a vehicle theft that occurred sometime overnight. Owner discovered it this morning.

Pass one, scan for life threat. B is the only incident with a person possibly in immediate danger. It is unconfirmed and the caller is calm, but neither of those demotes it. B goes first.

Pass two, in progress. A is happening now, and although nobody is on site, the situation is live and changing. A is second.

Pass three, the rest. C is minor but current, and a blocked lane is a hazard even without injuries, so it takes third. D is cold, complete and going nowhere. It is fourth.

The instructive part is C. It is the loudest call in the set and it ranks third, while the calm caller ranks first. If you ordered on emotional intensity, you would have inverted the two most important placements.

How to practice the reasoning

Work in sets of four or five, not pairs, and give yourself less time than feels comfortable. Then, before checking the answer, write one sentence of justification per placement. If you cannot say why an incident sits where you put it, you guessed, and the guess will not generalize.

When you get an item wrong, identify which pass failed. Did you miss a life threat on the scan, misjudge immediacy, or get pulled by the loudness of a caller? Those are three different errors with three different fixes, and lumping them into a general sense of having done badly teaches you nothing.

Prioritization also rarely appears alone. On the job and on the exam, the calls that need ranking arrive while you are still holding details from earlier ones. Our guide to memory techniques for retaining caller details covers keeping several sets straight, and why candidates fail multitasking covers what happens when the tasks overlap.

Common questions

Is there one correct priority order that applies everywhere?

No, and this is the single most important thing to take away. Priority schemes are set locally and differ between agencies, sometimes substantially. Exam items are written against broadly shared reasoning, so learning the reasoning is the right preparation for the test. On the job you follow your center's protocol, which supersedes all of it.

What if two incidents look genuinely equal?

Recheck them for immediacy first, then for how many people are exposed, then for how much the information has been confirmed. If they still tie, the item is probably testing your treatment of the other incidents in the set. Pick one and move on rather than burning time.

Does a caller who is uncooperative or rude change the priority?

No. Demeanor changes how you handle the conversation, not where the incident ranks. This holds in both directions: a polite caller with a minor problem does not move up, and a hostile caller with a serious one does not move down.

How much should I know about response protocols before testing?

Very little is required, and going deep can hurt. Entry-level assessments test reasoning and are written to be answerable without agency knowledge. Candidates who import specific protocols sometimes reason past the intended answer. Protocol is taught in the academy, and our overview of the POST entry-level dispatcher battery covers what the written stage does and does not expect of you.

Do these items ever have more than one defensible answer?

Occasionally the second and third placements are arguable. The first placement almost never is, and it usually carries the most weight. If you are unsure, get the top of the list right and accept some uncertainty further down.