> For the complete documentation index, see [llms.txt](https://docs.mrmylo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mrmylo.xyz/standard-operating-procedures-department-of-corrections/s1/1.4-10-codes.md).

# 1.4 - 10 Codes

The Department of Corrections operates on frequency 3.00. 10-codes are used to provide fast and clear communications over radio to ensure operations are as efficient as possible, especially under high-stress situations. These codes are used by multiple agencies, however may vary slightly. 

When relaying information, the following formula should be used:

{% hint style="danger" icon="walkie-talkie" %}
\[CALLSIGN] > \[10-CODE] > \[TRANSMISSION]
{% endhint %}

For example, “100, 10-77 in the yard, two aggressive unarmed inmates”.

When relaying information make sure you’re not talking over someone else. If it is very important to say “Break Break” to interrupt, then continue.

‘Tac Comms’ is an abbreviation of 'tactical communication’, most often heard during active riot situations, or high risk transports with PD. This means that the radio should be silent unless the information being transmitted is critical to the active situation. Any other transmission can be done via /dispatch, or can wait until the situation is clear. 

<table data-header-hidden data-search="false"><thead><tr><th>Code 0: Game Crash</th><th></th></tr></thead><tbody><tr><td>Code 0: Game Crash</td><td>Code 4: All Clear</td></tr><tr><td>10-1: Unable to Copy</td><td>10-23: Arrived on Scene</td></tr><tr><td>10-2: Loud and Clear</td><td>10-25: Report in person</td></tr><tr><td>10-3: Tactical Communication</td><td>10-41: On Duty</td></tr><tr><td>10-4: Acknowledgement</td><td>10-42: Off Duty</td></tr><tr><td>10-5: Relay</td><td>10-43: Mental Patient</td></tr><tr><td>10-6: Busy, Unless Urgent</td><td>10-47: Injured Person</td></tr><tr><td>10-7: Out of Service</td><td>10-50: Vehicle Accident/Collision</td></tr><tr><td>10-8: In Service</td><td>10-52: Police Required</td></tr><tr><td>10-9: Repeat</td><td>10-71: Active Shooting</td></tr><tr><td>10-10: Negative</td><td>10-72: Hostage Situation</td></tr><tr><td>10-13: Shots Fired</td><td>10-76: Enroute</td></tr><tr><td>10-14: Officer or Medic Injured</td><td>10-77: Need Backup (Non-Emergency)</td></tr><tr><td>10-15: Inmate</td><td>10-78: Need Backup (Emergency)</td></tr><tr><td>10-19: Enroute to Station/Prison</td><td>10-79: ETA</td></tr><tr><td>10-20: Location</td><td>10-91: Transport Unit</td></tr><tr><td>10-22: Disregard</td><td>10-99: Officer in Distress</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mrmylo.xyz/standard-operating-procedures-department-of-corrections/s1/1.4-10-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.