LogoLogo
Sunbelt Home
  • Sunbelt Roleplay - Welcome Notice
  • 🌍SUNBELT CORE
    • Community Terms of Entry
    • Community Rules and Regulations
    • Community Structure
  • 👮PUBLIC SAFETY CORE
    • Radio Communication Handbook
    • CAD/MDT Handbook
    • State Statutes
  • 👨‍💼CIVILIAN CORE
    • Civilian Guidelines
    • Restricted Weapons, Vehicles, and Peds
Powered by GitBook
LogoLogo

© 2025 Sunbelt Roleplay

On this page
  • Welcome to the CAD/MDT Handbook
  • SECTION 1 - CAD/MDT GUIDELINES
  • 1.01 General Utilization
  • 1.02 Report Generation
  • 1.03 Supervisor Expectations

Was this helpful?

  1. PUBLIC SAFETY CORE

CAD/MDT Handbook

PreviousRadio Communication HandbookNextState Statutes

Last updated 2 months ago

Was this helpful?



Welcome to the CAD/MDT Handbook

The CAD/MDT Handbook is a multi-phase handbook that outlines the proper utilization of the Sunbelt Roleplay CAD system. These guidelines are applicable to all Community Members and are enforced by Department Supervisors. Community Members with questions or concerns should reach out to their Department Supervisors.


SECTION 1 - CAD/MDT GUIDELINES

1.01 General Utilization

  1. Personnel are expected to be logged into CAD during the entirety of their patrol. At the end of their patrol, personnel should remove themselves from any calls they were on and log out.

  2. Personnel are expected to keep their status updated within the CAD system.

  3. Personnel are expected to run and attach their own names, license plates, and any other queried data.

  4. If self-dispatch is active, personnel shall enter their own officer initiated activity into the CAD system.

  5. If self-dispatch is active and a call is received, personnel are expected to attach to the calls received and clear themselves from the call upon completion.

    1. The last unit on the call should close the call out.

  6. Personnel shall add a narrative to every call they are attached to. It should be a short summary of what they did, action taken, and their final disposition.

1.02 Report Generation

  1. When generating reports, all reasonable fields should be filled out completely and will appropriate detail.

  2. Report Numbers assigned to reports issued should use the Report # from the call generated regarding the incident.

    1. If multiple are created, add a - and go from 1-9. So for example, 10101010-1.

  3. Report narratives shall be complete and detailed for all report entries. No narrative/summary entries shall be blank.

1.03 Supervisor Expectations

  1. Supervisors are expected to review all pending reports and ensure compliance with department procedures, ensure the report was properly filled out, and ensure the charges are appropriate and the narrative/summary includes all the needed information.

  2. Supervisors should send all complaints back for corrections that do not meet community or department standards.

👮