• apcointl.org
  • Subscribe
  • Advertise
  • Buyer’s Guide
  • PSC Magazine
  • Submit Press Release
  • Contact Us
Public Safety Communications
Show Menu
  • APCO
  • Industry
  • Government
  • Operations
  • Technology
  • Product & Service Announcements

The Great Migration to Plain Talk

Public Safety Communications August 25, 2011 Operations
10 what?
Radiohead; Illustration Paul Combs

Illustration Paul Combs

Dear Radiohead,
There’s been some talk around here about using common language instead of 10 codes. One of the most heated discussions—really I should say arguments—has been on traffic accidents. The powers that be can’t decide if they should call it a “motor vehicle accident” or a “motor vehicle collision.” I vote we stay with the 10 code, 10-50. What do you think?
10-4, Good Buddy

Dear 10-4,
Accident vs. collision vs. 10-50? I bet you work for a police department, not a fire agency (more on that later). There is a trend toward plain language—and for good reason. 10 codes vary.

Even if a 10-50 in many agencies is a vehicular crash—usually with the suffix of PD (property damage), PI (personal injury) or F (fatal)—a 10-50 can also mean “shake down,” “use caution,” “contact medical examiner,” “stopping vehicle,” “homicide,” “now at scene” and “no traffic here.”

Now I’m beginning to see why plain language is important.

Under the National Incident Management System (NIMS), plain language must be used for mutual aid scenarios. NIMS “strongly encourages the use of plain language during day-to-day operations as well.” It’s ridiculous not to practice because we all know when the you-know-what hits the fan, human beings revert to what they know (or use daily).

Excuses, excuses: Some critics (i.e., those with blinders on) have cried their eyes out, saying we can’t go to plain language because “We’ve always done it this way.” Wah, wah! Get out of your comfort zone. Here’s another one: “We can’t afford it.” Plain language doesn’t have an astronomical cost. Now, if your CAD system uses 10-code call types, these will have to be changed, and it may cost some money, depending on how your CAD software operates and who can make changes to it. But someone in house can write the procedure—or steal one from another agency. (We do this all the time.) Then, just conduct training for personnel, include the comm center personnel, set a start date, and get going.

The Department of Homeland Security has two booklets on plain language available: Plain Language Guide: Making the Transition from 10 Codes to Plain Language and Plain Language Frequently Asked Questions (FAQs).

In fact, I’ll help. Here are some tips:

  • Training aids should be a final product of the working group;
  • Team training should be conducted with representatives from line and staff units. (Yes, that includes telecommunicators.)
  • Including representatives from various disciplines will help unite the groups behind the common issues. (Let the turf wars begin.)
  • Feedback received during training should be documented because training may uncover valid issues. (Make the changes and retrain.)
  • The importance of using standard phrases should be emphasized to control use of air time and reduce confusion. (Sounds like the part of the process your agency is having trouble with right now.)
  • It’s best if a working group member is present when their discipline is being trained. (This person should be issued a flak vest.)
  • Handouts showing the old codes and the current, corresponding phrases should be made available.
  • Agencies that use CAD, in-car computers or both should have an IT representative present at each training session to explain when computer updates will be made. (Have this unit in the game plan because they might get their feathers ruffled when they’re not involved—especially if programming is needed.)
  • Support tools, such as visor cards listing the plain language phrases, should be made available.
  • Dispatchers should be trained alongside field personnel to ensure both groups receive the same instructions and same answers to questions. (What?! I might faint.)[1]

If your agency has other departments on your frequency that don’t use plain language, you may have another issue. As part of the planning process, your agency should meet with the other agency(s) and discuss this with them. Wouldn’t it be great if they bought into your plan, and all of the radio system members transitioned at the same time? Monumental.

Now, police or fire agency? I know you’re from a police department. I won’t make my readers happy by saying this, but fire agencies got it right. How long have they been using plain language? It seems to take law enforcement forever to get the idea.

As for accident vs. collision, what about crash? But don’t forget, there’s really no such thing as an “accident.”

Reference

1. www.safecomprogram.gov/SAFECOM/library/interoperabilitybasics/1371_plainlanguage.htm.

Editor’s note: The opinions expressed herein are those of the columnist and do not necessarily reflect the views of APCO International.

Originally published in APCO International’s Public Safety Communications, Vol. 77(1):56, January 2011.

Tags 10 CodesPublic Safety Communications
Share Facebook 0 Twitter 0 Google+ 0 LinkedIn 0
Previous article Us vs. Them
Next article James City County Honors 2 Telecommunicators for Lifesaving CPR Instructions

Follow @apcointl

Follow @APCOIntl
Back to top

Current Issue

PSC Magazine

  • About PSC Magazine
  • Advertise
  • Buyer’s Guide
  • Subscribe
  • Submit an Article
  • Contact the Editor
  • Privacy Policy

Inside APCO

  • About APCO
  • Membership
  • Events
  • Training
  • Technology
  • Advocacy
  • Services
  • Contact APCO

Follow Us

Copyright 2023 APCO International

Close Window

Loading, Please Wait!

This may take a second or two. Loading, Please Wait!