What an APB Actually Is and How It Gets Put Out
An APB stands for All Points Bulletin. It is an internal law enforcement broadcast that tells every available unit in a jurisdiction to be on the lookout for a specific person, vehicle, or incident. It is not a press release. It is not a social media post. It is a directive that goes over the radio and through dispatch databases so officers in the field know what to watch for and what to do when they see it. The word has been around since the mid-twentieth century, though different agencies use slightly different terms now. Some say BOLO, which is Bulletin Only for Lookout. Some say WAT, which is Wanted Advisory Telephone. The mechanics are basically the same: broadcast a description, broadcast the associated risk, tell units what action to take. Agencies that still use the term APB usually do it because legacy systems and older officers are comfortable with it. That is about it.
What Is An Apb In Law Enforcement The Critical Broadcast That Can Catch Fugitives
People ask this question because they heard the term on a show or read a headline, and they want to know how it actually functions in real operations rather than what a textbook says. An APB is the mechanism that moves information from a desk file to the street. Without it, a warrant sits in a system and a detective waits. With it, a patrol officer in a different county sees the plate, runs it, and makes a contact that might otherwise never happen. The process starts with a case file. A detective or officer writes a request that includes the subject's full name, aliases, date of birth, physical description, clothing at the time of last sighting, vehicle make model color and plate, and the reason for the alert. There should also be a clear statement about whether the person is armed, what charges they face, and what the desired outcome is. Arrest is standard. Stop and release is rare and requires supervisor approval. That request goes to a dispatch center or a criminal justice information division, depending on the agency. The person taking the APB verifies the information, checks for duplicates, and enters it into the state or regional database if applicable. Most states use AMLIS, which stands for the National Crime Information Center and their own state mirror. If the person is already in NCIC, you do not create a new APB for that. You update the existing record and issue a supplemental APB for local awareness. Creating a duplicate in NCIC will get your name on a quality control report and probably a phone call you do not want to take.
Once entered, the APB triggers broadcasts. Patrol units get it read over the talkgroup. Dispatchers see it pop up on their screens. If it is a tier one APB, it might go statewide. Tier two stays county. Tier three is a single precinct. The tier level depends on agency policy and the perceived threat. The turnaround time for a local APB is usually fast. In a well-staffed dispatch center, you are looking at ten to twenty minutes from written request to broadcast. A statewide or NCIC insertion can take longer if the data entry specialist is backlogged or if there is a clerical error that needs fixing. I have seen a straightforward APB sit for forty-five minutes because the dispatcher had to verify a misspelled middle initial before entering it. That delay matters when a suspect is moving.
Get the Full Details

What Makes an APB Work in Practice
The description has to be specific enough to act on and general enough to not miss the actual subject. If you say the suspect is driving a dark blue Ford F-150, and the truck is actually dark green, you lose a contact. If you say the suspect is driving a dark colored truck, you get too many hits and units waste time checking vehicles that are not involved. The sweet spot is accurate but not brittle. Mention the bed cap if it is unusual. Mention the dent on the rear bumper if it is distinctive. Mention the tint level if it is extreme. These details separate a flag from a false alarm. The reason fielded matters more than most rookies realize. An APB for a non-violent property crime gets a different response than an APB for an armed robbery suspect. Units will prioritize the violent one. They will also run plates faster, call for a field interview sooner, and involve supervisors. If you mark it as a wapon involved when it is not, you are wasting resources and you risk damaging credibility. Lie about the threat level and you get called on it during the after-action review. Photos help, but they are not a substitute for a good written description. A blurry mugshot from two years ago does not tell an officer what the suspect looks like today. If you can attach a recent photo, do it. If you cannot, describe the aging factors: facial hair patterns, weight change, scars, tattoos. These are the things that let an officer confirm identity without relying solely on a visual match to an outdated image.
Common Mistakes That Kill APBs
The most common mistake is lazy description. Officers type the minimum and hope for the best. That approach fails under pressure. When a patrol car spots a vehicle that partially matches, the officer has seconds to decide whether to initiate a stop. If the APB says the suspect is wearing a black shirt, and the driver is wearing charcoal, the officer may hesitate. That hesitation is the difference between a capture and a loss. Another mistake is failing to cancel or update the APB. Suspects get arrested. Cases get dismissed. Vehicles get recovered. If the APB stays active, units keep running it and the database gets cluttered. Clean databases matter. Dirty ones make good APBs harder to find. Supervisors should audit active APBs at least once a week. If you cannot remember the last time your agency did that, start doing it. A third mistake is putting out an APB without a follow-up plan. The APB is not the end of the process. It is the beginning of the field net. If you do not tell units where to bring the suspect, what to say on arrival, and who to contact once they have a vehicle in custody, you create confusion. Confusion leads to jurisdictional arguments and procedural messes. Lay that out before you push the broadcast.
An Edge Case That Highlighted the Real Workflow
I dealt with a situation a few years back where an APB was issued for a suspect in a domestic violence arrest. The plate run came back clean locally, but the name matched a partial in another county. The APB was tier two, so it never reached that county's patrol units. The suspect drove through that county on the way to a relative's house and disappeared from the active radar. By the time someone connected the dots, he was gone. The workaround was not dramatic. I called the neighboring county's non-emergency line, got the dispatcher on the phone, and read the APB details directly. She ran the name and plate against their open cases. They had a similar description from a traffic stop three days earlier. That led to a contact and an arrest within two hours. The lesson was practical: inter-agency communication beats database tiers when time is short. A phone call to another dispatch center is faster than filing a formal mutual aid request, and it is acceptable for urgent field information. Just document the call afterward so the paper trail exists.

What Beginners Miss About APB Priority and Risk
APBs are not created equal, and nobody outside the field usually understands that. A felony warrant APB and a failure to appear APB look the same on paper to a civilian. To an officer on shift, they are completely different. The felony warrant carries higher authority and faster response. The failure to appear might get a hold until court date if the department has a policy for low-level non-violent holds. Knowing your agency's policy prevents wasted broadcast effort. Another counter-intuitive point is that APBs sometimes fail because they are too broad. I have seen a county-wide APB issued for a suspect who was last seen in a single neighborhood. That diluted the signal. Units in the opposite end of the county treated it as background noise. When you narrow the geographic scope to the last known area plus a reasonable radius, response quality improves. You trade breadth for depth, and in fugitive recovery, depth wins.
Limitations and Where APBs Fall Flat
APBs do not work when the database is outdated. If the state does not share records quickly, your APB is only as good as the last data sync. Rural counties with slow broadband and understaffed dispatch know this well. An APB that would reach every unit in twenty minutes in a metro area can take hours in a sparse region. That is not a flaw in the concept. It is a resource problem. APBs also struggle with suspects who do not drive and do not appear on standard databases. A person who walks, uses cash transit, avoids cameras, and has no active warrants is hard to catch through an APB alone. The broadcast will generate tips, maybe, but it will not guarantee a contact. In those cases, physical surveillance and informants outperform any electronic bulletin. Tell yourself that upfront so you do not rely on the APB as a cure-all. There is also the issue of fatigue. Officers see dozens of APBs every shift. When everything is tagged urgent, nothing is. Tiering helps, but it does not eliminate the noise. The best agencies use color coding or priority flags in their dispatch software so units can sort by severity without reading every line. If your system does not have that, push for it. It reduces missed details and speeds up triage.
What to Do When You Need to Issue One
Gather the facts first. Do not start typing until you have a complete description, a verified name, and a clear objective. Check NCIC and your state system for existing records before creating a new one. Write the request in plain language. Avoid jargon that a dispatch center in a neighboring county might misinterpret. Include a callback number and the name of the supervising detective. If the suspect is armed, state that clearly at the top. If the case is sensitive and you need limited disclosure, note that too. Follow up within thirty minutes. Confirm the APB is in the system. Ask the dispatcher to read it back to you. Verify the broadcast tier. If it is not moving, escalate to a sergeant or lieutenant. Then continue to monitor. APBs decay if you do not check them. Status changes happen. New information arrives. You need to update or cancel promptly so the field is not working off stale data. The process is straightforward when you treat it like a standard operating procedure instead of an ad hoc request. The problems come from rushing the details, skipping the verification, and assuming the broadcast does the work by itself. It does not. The broadcast puts eyes on the street. The follow-up brings the result.
