No — that statement fails the NIMS management characteristic of common terminology, and it fails it twice. "10-37" and "Code 2" are agency-specific brevity codes drawn from local radio systems, not standardized National Incident Management System language. Under NIMS, responders from different agencies, disciplines, and jurisdictions must be able to understand each other without a shared codebook; a transmission like this assumes the listener already knows one department's numbering. The fix is plain language: state the unit, name the resource or condition, and describe the urgency in ordinary words that any cooperator can act on.
What "10-37 Code 2" Actually Means and Why It Breaks NIMS
"10-37" belongs to the family of ten-codes popularized in American land mobile radio after World War II and adopted unevenly by police, fire, and public works agencies. Its meaning varies by agency: depending on the local codebook, it can mean "wrecker needed," "operator available," "woman with a juvenile," or something else entirely. "Code 2" is even more local, often indicating an urgent-but-not-lights-and-siren response in one jurisdiction and a completely different priority in another.
NIMS common terminology exists precisely to eliminate that ambiguity. The National Incident Management System, maintained by FEMA, defines common terminology as the use of plain language and standardized words and phrases so that people from different organizations can communicate clearly during an incident. FEMA's NIMS documents direct responders to avoid ten-codes, agency-specific codes, and jargon when communicating across agencies, because no single codebook has ever been universally adopted.
The statement has a second layer of trouble: "Unit 1" is itself an identifier that means nothing outside the agency that assigned it. In a single-department operation, that's fine. In a multi-agency response, a listener from a neighboring fire district or a state agency has no way to map "Unit 1" to a resource type, capability, or location. NIMS resource typing asks agencies to describe resources by category, kind, and type so that unfamiliar units can be requested and understood.
So the statement stacks three local conventions — a unit number, a ten-code, and a priority code — into one transmission. Each one is legitimate inside its own agency's standard operating procedures. None of them is common terminology. The characteristic isn't about whether the words are precise; it's about whether a stranger on the same radio channel would understand them correctly on first hearing.
The NIMS Document Language That Sets the Standard
The controlling document is the National Incident Management System, currently maintained by FEMA's National Integration Center, with the third edition published in October 2017. Its foundational component on Communications and Information Management names common terminology as a core principle: communications should use plain language, and agencies should avoid codes and jargon that cooperators might not understand. FEMA's companion guidance for the National Incident Management System goes further, recommending plain-language equivalents for common ten-codes in multi-agency events.
That guidance matters because it shifts the burden. Under NIMS, the sender owns the clarity problem. If a transmission requires the listener to consult a local code sheet, the sender has not communicated; they have encrypted. A dispatcher who says "wrecker needed" is understood by a state trooper, a county deputy, and a towing contractor. A dispatcher who says "10-37" is understood by whoever memorized that department's list.
FEMA's plain-language push isn't abstract policy. After-action reports from major incidents, including the response to the September 11, 2001 attacks, repeatedly identified incompatible codes and terminology as a factor in coordination failures among responding agencies. The lesson institutionalized in NIMS is that interoperability is a language problem as much as an equipment problem.
The standard also recognizes a legitimate role for codes inside a single agency. NIMS does not forbid internal brevity; it forbids relying on it across organizational lines. The distinction is the boundary between a department's own tactical channel and any channel, meeting, or incident where outside cooperators are present.
Why "10-37" Means Four Different Things in Four Jurisdictions
Ten-code drift is documented and persistent. The classic illustration comes from associations of public safety communications officials, which have long noted that the same ten-code can carry contradictory meanings across agencies. "10-4" is widely understood as acknowledgment, but "10-37" and its neighbors vary wildly, and some agencies abandoned ten-codes entirely decades ago in favor of plain language.
A simple comparison shows the compliance problem concretely:
| Transmission element | What the sender means locally | What an outside cooperator may hear | NIMS-compliant alternative |
|---|---|---|---|
| "Unit 1" | First-due engine or supervisor unit | Any unit, no capability implied | "Engine 1" or "Battalion 1" with resource type stated |
| "10-37" | Wrecker requested (one common usage) | Operator available, juvenile involved, or unknown | "We need a tow truck" |
| "Code 2" | Urgent, no lights and siren (in some systems) | Unknown priority or "routine" | "Urgent response, no emergency lights" |
| Whole statement | Internal shorthand | Unusable without the local codebook | "Unit 1 requests a tow truck, urgent, no lights and siren" |
Radio system consultants and communications coordinators have pushed plain language for years partly because of this table's real-world consequences: a mutual-aid company arriving from two counties away can misread a priority code and stage when it should be moving. The failure isn't hypothetical. It's a predictable outcome of code drift.
Version matters too. Agencies that adopted the 2017 NIMS edition after earlier editions sometimes still carry legacy code traditions in their CAD systems and radio templates. A department can be nominally NIMS-compliant on paper while its default radio traffic remains code-heavy, which is one reason compliance audits look at actual transmissions, not just policy manuals.
Is Common Terminology a Radio Rule or a Management Characteristic?
This is the misconception worth correcting head-on: common terminology is not the same thing as a plain-language radio policy. It's one of fourteen management characteristics that NIMS lists as the foundation of incident command, and it applies to plans, briefings, forms, resource descriptions, and written products as much as to voice traffic. The fourteen characteristics include common terminology alongside unity of command, span of control, incident action planning, and integrated communications.
That breadth matters for the statement in question. Even if a department rewrote its radio traffic, it could still violate common terminology by describing resources inconsistently in its incident action plan, by using local zone names that mean nothing to assisting agencies, or by labeling positions with titles that don't match the NIMS command staff structure.
FEMA's National Incident Management System doctrine also ties common terminology to the Incident Command System's organizational language. When an incident commander establishes command, the positions — incident commander, operations section chief, planning section chief, logistics section chief, finance/administration section chief, public information officer, safety officer, liaison officer — are standardized terms. An agency that invents its own position titles for the same functions has stepped outside common terminology even if everyone on scene understands the local names.
Compliance, then, is a management posture measured in documents and transmissions together. A department can pass a radio audit and fail a planning audit, or the reverse. The statement "we have a 10-37 code 2" is a radio-level symptom of a broader habit of local shorthand.
Rewriting the Transmission in Plain Language: A Step-by-Step Method
Converting a code-based statement into NIMS-compliant plain language is mechanical once you know the elements. Use this sequence on the actual sentence.
1: Identify the unit by resource type and identifier — "Engine 1," "Battalion 1," "Medic 4" — rather than a bare "Unit 1" number that implies no capability. 2: Replace the ten-code with the literal need: "we need a tow truck," "we need a second ambulance," "operator is available." 3: Replace the priority code with plain urgency and response conditions: "urgent, no lights and siren," "emergency traffic, lights and siren," or "routine." 4: State the location or assignment precisely enough for an outside unit to act: street address, cross streets, or a named incident assignment. 5: Confirm the listener understood by having them repeat the request, not by exchanging another code.
Applied to the original statement, the compliant version reads: "Engine 1 is requesting a tow truck, urgent response, no lights and siren, at the intersection of Fifth and Main." Every element is now legible to a cooperator from another county.
If the rewritten transmission feels long, that's a feature, not a bug. Brevity codes save seconds inside a trained team and cost minutes of confusion across agencies. The NIMS trade is deliberate: a few extra syllables for a shared understanding. Failure handling is straightforward — if a listener responds with a code or a question you can't parse, restate in plain language rather than trading codes back, and if the exchange still fails, move to voice on a common channel or confirm by phone per your communications annex.
Where Codes Still Belong: Single-Agency Operations and the Boundary Line
None of this means a department must purge ten-codes from its own tactical channels. NIMS common terminology governs multi-agency, multi-jurisdiction communication; a single engine company talking to its own dispatcher on a dedicated channel can use whatever its standard operating procedures authorize. The characteristic becomes binding at the boundary — mutual aid, unified command, multi-discipline incidents, and any communication a cooperator might hear.
Practical departments handle this with discipline rather than prohibition. The usual pattern is a local codebook that pairs every code with a plain-language equivalent, radio templates that default to plain language on interoperability channels, and training that rehearses the switch. Some agencies have gone further and dropped ten-codes from their CAD and radio systems entirely, adopting the National Emergency Communications Plan's plain-language recommendations.
The boundary line is worth stating plainly for policy purposes: if the transmission could be heard by an agency that hasn't memorized your codebook, it must be understandable without one. That rule catches the original statement, mutual-aid requests, unified command traffic, and any incident where a liaison officer or assisting agency is on scene.
There's an operational cost to ignoring the line, and it's measurable in response time. A staged mutual-aid company waiting on a code clarification is not moving toward the incident. Communications coordinators who track after-action findings routinely cite terminology confusion among the top coordination failures in multi-agency events — a cost no department budgets for but every affected incident pays.
Training and Audit Checks That Catch Code Creep
Policies drift, and code creep creeps back in during high-tempo periods when shorthand feels faster. The countermeasure is periodic auditing of actual transmissions, not just policy review. Communications supervisors can sample recorded radio traffic on interoperability channels and score it against a plain-language checklist: was the resource described by type, was the need stated in words, was urgency expressed plainly, was confirmation requested.
The audit checklist maps cleanly to the statement at hand:
Unit identification by capability, not just number Literal statement of the need or condition Urgency expressed in plain words with response conditions Location specific enough for an outside unit Read-back confirmation from the receiving party
Training that rehearses the conversion works better than training that lectures about it. Scenario drills in which a dispatcher reads a code-based transmission and the trainee rewrites it in plain language build the habit. So do joint exercises with neighboring agencies, where the payoff — an outside crew understanding a request on first pass — is visible.
Version-specific compliance adds another check. Departments operating under the 2017 NIMS edition should confirm their communications annex, radio templates, and CAD pick-lists reflect plain-language defaults, because legacy templates are where code creep survives policy change. Auditors who check only the written policy will miss a CAD system that still offers "10-37" as a one-click disposition.
What Compliance Looks Like in an Incident Action Plan
Common terminology lives in written products too, and the incident action plan is the clearest test. A compliant plan describes resources by NIMS resource typing — category, kind, and type — so that "Engine 1" is accompanied by enough detail for an incoming agency to know what capability arrives. It uses standard ICS position titles, standard organizational terms, and plain-language descriptions of objectives.
Non-compliant plans smuggle local shorthand into the same document: local zone names without definitions, unit designators that only the home agency can decode, priority codes in the objectives section, and position titles that don't match ICS structure. The statement "we have a 10-37 code 2" written into a plan rather than spoken on a radio is the same violation in a different medium.
The fix follows the same rule as the radio fix. Define every local term on first use, pair codes with plain-language equivalents, and prefer the standardized term when one exists. A plan that a cooperating agency can execute without calling your dispatcher for a translation is a plan that satisfies the characteristic.
FEMA's NIMS training courses reinforce this in the planning sections, and the National Integration Center's routine updates to NIMS doctrine keep the language current. Departments that route their plans through a communications review before approval catch most of the drift.
FAQ
Does NIMS ban ten-codes entirely, or only across agencies?
NIMS discourages ten-codes and agency-specific codes in multi-agency communication and directs plain language where cooperators are involved; it does not abolish internal agency brevity. The practical rule is the boundary: if an outside agency might hear or act on the transmission, use common terminology. Departments that keep codes internally usually pair each one with a plain-language equivalent in their codebook.
What does a compliant version of the statement sound like?
"Engine 1 requests a tow truck, urgent, no lights and siren, at Fifth and Main" carries every element the original transmission intended. The unit is described by capability, the need is stated literally, and urgency is expressed in plain words. Any cooperator can act on it without a local code sheet. The confirmation step is a read-back, not a code exchange.
Is "Code 2" part of NIMS or a local convention?
"Code 2" is a local convention with meanings that vary by jurisdiction — commonly an urgent response without lights and siren in some systems, but not reliably so. NIMS does not define priority codes as common terminology. Compliant traffic states urgency in words along with response conditions, so a listener from another agency knows exactly what is being requested.
Does common terminology apply to written plans, or only to radio traffic?
It applies to written products as well: incident action plans, briefings, resource descriptions, and forms. A plan that uses undefined local zone names, unit designators only the home agency can decode, or non-standard position titles fails the same characteristic as a code-heavy radio transmission. Audits that check only radio traffic miss half the compliance picture.
How is the characteristic audited in practice?
Communications supervisors sample recorded transmissions on interoperability channels and score them against a plain-language checklist: capability-based unit identification, literal statement of need, plain urgency, actionable location, read-back confirmation. Plan reviews check the same elements in writing. Joint exercises with neighboring agencies provide the functional test — whether an outside crew understood the request on first pass.
Does calling the unit "Engine 1" satisfy common terminology by itself?
No — "Engine 1" fulfills NIMS resource typing only when it's accompanied by enough detail for a cooperator to know the capability that arrives, such as type and staffing. The identifier alone is better than "Unit 1" because it names the resource kind, but a compliant request still states the need, urgency, and location in plain words. Capability plus plain-language request is the full standard.
What happens if a cooperator still doesn't understand a plain-language transmission?
Restate more plainly rather than slipping back into codes, and if the exchange still fails, move to a common channel or confirm by phone per the communications annex. Escalating to voice or a landline is standard failure handling in multi-agency events. The goal is shared understanding, not speed of transmission.
Does the 2017 NIMS edition change the common terminology requirement?
The third edition, published in October 2017, retains common terminology among the management characteristics and keeps the plain-language direction for multi-agency communication. Departments that updated policy after that edition sometimes still run legacy code templates in CAD and radio systems, which is a common audit finding. Checking templates, not just the written policy, catches the gap.