> For the complete documentation index, see [llms.txt](https://www.blainecountysheriffoffice.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.blainecountysheriffoffice.org/sop/section-5-department-procedure/5.23-deputy-callsigns-and-badges.md).

# 5.23 - Deputy Callsigns & Badges

#### **1. Purpose**

This policy outlines the standardized system for issuing and using callsigns and badge numbers within the Blaine County Sheriff Office (BCSO). The goal is to maintain professionalism, ensure accountability, and facilitate effective communication across all BCSO operations.

***

#### **2. Definitions**

* **Callsign:** A unique alphanumeric identifier used over the radio and in documentation to represent a trooper or unit.
* **Badge Number:** A permanent identification number assigned to each trooper for administrative and identification purposes.

***

#### **3. Callsign Structure**

All Deputy callsigns shall follow this standardized format:

**#**#**-###**

***

#### **4. Badge Numbers**

* Badge numbers will be issued upon appointment to the BCSO.
* Badge numbers are unique, non-reusable, and assigned in sequential order.
* Example: Deputy John Smith is assigned Badge #30409.

Badge numbers will be used for internal records, promotion eligibility, disciplinary tracking, and commendation logging.

#### Badge Number system

* Heads: 3000-3010
* Command Staff: 3100-3150
* Supervisor: 3200-3220
* Supervisor in training: 3300-3310
* Patrol: 3320-3400
* Probationary: 3901-3950 <br>

**Training Rank Badge Number System**

Cadet: 3951-3999

#### **Division Leadership Badge Number**

* Motor Safety Division: 3700-3800
* K9 Division: 3635-3645
* CID/Gang & Narc: 3645-3655
* Special Response Team: 3851-3900
* Protective Service Division: 3800-3850&#x20;
* Marine: 3665-3675
* Helicopter Response Team: 3680-3685
* Training Officer: 3600-3625
* Public Information Office: 3401-3419

***

#### **5. Usage Guidelines**

* Deputy's must use their assigned callsign during all radio communications and patrol operations.
* Deputy's may not use or impersonate another Deputy's callsign or badge number under any circumstance.
* Lost or compromised badge numbers must be immediately reported to Command Staff.
* Callsigns may change upon assignment to specialized units; badge numbers will remain constant.

***

#### **6. Enforcement**

Any violations of this policy, including the misuse or unauthorized alteration of callsigns or badge numbers, may result in disciplinary action as deemed appropriate by BCSO Command Staff.

***

#### **7. Policy Review**

This policy will be reviewed bi-annually by Command Staff and updated as needed to reflect operational requirements or departmental changes.


---

# 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://www.blainecountysheriffoffice.org/sop/section-5-department-procedure/5.23-deputy-callsigns-and-badges.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.
