Standard Operating Procedures

The standard we hold ourselves to

The SSPD operates under the Joint Department Operations — Standard Operating Procedures for Paradise State Roleplay. These procedures govern the conduct, tactics, and responsibilities of every sworn member.

All members are responsible for knowing and following these procedures. Ignorance of the SOP is not an excuse for violating it. The SOP may be updated and changed without notice, and all members are expected to regularly refresh themselves on it.

1.0

Introduction

This document outlines the standard procedures, expectations, and systems governing all law enforcement departments under the Joint Department Operations. It ensures coordination, fairness, and professionalism between all JDO departments.

  1. 1.0.1JDO SOP policies and rules apply to all departments.
  2. 1.0.2Departments can never create rules that infringe upon the JDO SOP.
  3. 1.0.3The JDO SOP may be updated and changed without notice; all JDO members are expected to regularly refresh themselves on this document.
2.0

Chain of Command

The Chain of Command ensures structure, accountability, and efficiency within JDO. It allows issues to be resolved at the proper level, prevents confusion, and maintains clear communication between ranks.

  1. 2.0.1Failing to follow the Chain of Command can lead to miscommunication and even disciplinary action.
3.0

Trainings

Training is how the department keeps every officer safe, competent, and consistent.

FTOs and FTAs

  1. 3.0.1Only FTOs or FTO Coordinators may host training for their designated department, and FTOs must be trained by the heads of that department.
  2. 3.0.2FTOs must give 100% to every training and complete everything on their department's training guide.
  3. 3.0.3Failure to properly teach cadets and prepare them for duty results in removal from the FTO position.
  4. 3.0.4FTOs may remove cadets acting disorderly or disrespectful, and must act professionally at all times as cadets' first role model.
  5. 3.0.5FTAs must assist FTOs with whatever the training requires, and attend a minimum of 2 trainings before being eligible for an FTO interview (departments may require more).
  6. 3.0.6FTOs must host a minimum of 3 trainings a month in order to stay at FTO.
  7. 3.0.7FTO is a requirement for any department Low Command and above.

Training Guides

  1. 3.0.8All departments are required to follow the JDO-wide Cadet Training Guide.
4.0

Uniform, Vehicle, and Loadout Policies

Uniforms, vehicles, and weapons follow strict standards across every JDO department.

Uniforms

  1. 4.0.1Wear the uniform designated to your rank unless special permission is granted through a reward.
  2. 4.0.2Department-bought EUP is used only in that department unless the department's heads give specific approval.
  3. 4.0.3Custom uniforms are not allowed unless you are Low Command or above.
  4. 4.0.4Uniforms under Pre Command must include at least 3 pieces of police EUP, and no civilian EUP — undercover subdivisions are excluded.
  5. 4.0.5All regular patrol uniforms remain professional no matter your rank.
  6. 4.0.6Tattoos above the neck and unnatural hair coloring are strictly prohibited.
  7. 4.0.7Departments are required to provide uniforms for all ranks and subdivisions.

Vehicles

  1. 4.0.8All LEO vehicles use realistic colors unless Department Coordination gives permission, and all department vehicle colors must be approved by Department Management.
  2. 4.0.9Officers must have their callsigns on their plates at all times.
  3. 4.0.10Use the vehicle assigned to you on your department structure unless you hold a department award, unless active as a subdivision.
  4. 4.0.11Driving into oncoming traffic is always strictly prohibited.
  5. 4.0.12Armored vehicles such as Bearcats are driven only by SWAT or other tactical team units when deployed as such.
  6. 4.0.13Tactical Patrol subdivisions are not allowed; creating one can result in a department strike.
  7. 4.0.14Vehicles unlocked through subdivisions are used only for that subdivision — never for patrol.
  8. 4.0.15Misuse or abuse of Code 2 or Code 3 results in a strike or more.
  9. 4.0.16No ramming or VDM except PIT. PIT: 120 mph limit, supervisor approval required, 60-second cooldown, and never on two-wheeled vehicles. Grappling authorization speed is 160 mph.
  10. 4.0.17Pursuits: 5-unit maximum on 10-80s with supervisors able to remove units, failure to disengage when ordered is a strike, no ramming to end a pursuit, and keep a safe distance.

Combat and Weapons

  1. 4.0.18All LEO units follow everything stated in the LEO Weapons Guidelines at all times.
  2. 4.0.19Lethal force is used only when a lethal threat has been posed to you — this does not include a fist fight.
  3. 4.0.20Pistols are used only at the gang blocks (postals 853, 826, and 794) unless there is a pre-planned scene.
  4. 4.0.21Bean bag shotguns are restricted to Supervisors and higher.
  5. 4.0.22Use only weapons provided in your LEO loadout or LEO-approved packs.
  6. 4.0.23Always abide by the Force Pyramid; mag dumping is allowed only if your life is in immediate danger.
  7. 4.0.24No combat rolling, no ghost or glitch peeking, and no confirm-killing.
  8. 4.0.25Units may shoot out of their vehicle if their life is in immediate danger, to a maximum of 50 mph.
5.0

Radio Traffic Operations

RTO is the foundation of communication between all active officers. Professional and efficient use of RTO ensures safety, coordination, and realism across patrols.

Professionalism

  1. 5.0.1Maintain a professional and respectful tone at all times.
  2. 5.0.2No profanity, sarcasm, or unnecessary chatter on the radio.
  3. 5.0.3Treat RTO as an in-character law enforcement communication channel.

Radio Procedure

  1. 5.0.4Always identify yourself using your correct callsign.
  2. 5.0.5Keep transmissions brief, clear, and relevant to current operations.
  3. 5.0.6Never interrupt ongoing transmissions.
  4. 5.0.7Units are required to respond to priority scenes if assigned by a Supervisor or higher.
  5. 5.0.8Priority transmissions are permitted in main RTOs for the initial notification only; all pursuit callouts move to priority channels.
  6. 5.0.9If you are dead, you are not allowed to speak in RTO.
  7. 5.0.10To speak with another officer outside RTO, say [Callsign | Name] direct and ask to go to a 10-1.
  8. 5.0.11Always call out in RTO when going 10-8, 10-7, or 10-6.

Radio Discipline

  1. 5.0.12Do not use RTO for off-topic or out-of-character conversations.
  2. 5.0.13Only active on-duty or recruiting LEOs should be present in RTO channels.
  3. 5.0.14Keep microphones clear of background noise, music, or echo.

Authority and Violations

  1. 5.0.15RTO authority scales with rank: Department Coordination and Department 01 hold full authority over cooldowns, punishing units, overruling dispatch, holding 10-3s, hosting briefings, and announcements, while patrol units hold none.
  2. 5.0.16Failure to follow RTO rules may result in verbal or written warnings, RTO suspension, or a strike or termination.
6.0

In-Game Rules

All LEO officers are required to stay in character at all times unless staff is required or a Department Head or above says otherwise. Reporting officers is always handled through the discord report system so roleplay and immersion are not broken.

General

  1. 6.0.1All LEO are required to be registered in the CAD at all times while on duty.
  2. 6.0.2Breaking any server rule while on duty results in a strike or removal.
  3. 6.0.3Corrupt cop RP is never allowed while patrolling; it is permitted only for pre-planned events approved by the 01.
  4. 6.0.4All LEO follow a 2-life rule and are required to value their life at all times.
  5. 6.0.5Going on duty during an active suspension results in removal or blacklist.
  6. 6.0.6High-speed pursuits are conducted with public safety in mind: call out location, speed, and direction, and terminate if it becomes unsafe.
  7. 6.0.7Log every traffic stop, arrest, and incident in the CAD.
  8. 6.0.8Jail times and charges follow the PSRP Penal Codes; officers may not charge suspects at their own discretion.
  9. 6.0.9No metagaming — all information must be gained through in-character means.
  10. 6.0.10If you disconnect or crash mid-scene, announce that your game has Code 0d and leave RTO.
  11. 6.0.11Identify yourself when prompted by a civilian or an officer, and never revive yourself.
  12. 6.0.12Hostage RP may be declined if it lacks realism, cannot be forced onto RTO or priority, and officers should avoid RDM/VDM hotspots.
  13. 6.0.13Miranda rights are required only when a suspect is in custody and you are questioning them for information to use against them.

Priority Cooldowns

  1. 6.0.14Priority cooldowns follow every priority to give LEO time to get ready for the next one.
  2. 6.0.15/cooldown sets an automatic 15-minute cooldown; /priomenu opens a prompt for a custom time, in progress, or hold.
  3. 6.0.16Hold means no roleplay should take place — DOD purposes or LEO briefings only.
  4. 6.0.17In progress means a priority is currently taking place in that AOP.
  5. 6.0.18Cooldown means no priorities should take place within the timeframe.

Kidnapping LEO

  1. 6.0.19Any LEO may be kidnapped as long as there is prior roleplay between you.
  2. 6.0.20Any kidnapping of LEO must be realistic and provide meaningful roleplay for all parties involved.

Breaching

  1. 6.0.21A breach may only occur under reasonable suspicion or probable cause that a suspect is inside or poses an immediate threat.
  2. 6.0.22A supervisor or higher-ranking officer must authorize the breach if present; in active shooter, hostage, or barricade scenarios officers may breach without prior approval if lives are in immediate danger.
  3. 6.0.23Breaches for misdemeanors are not permitted, and officers may only use a pistol while breaching with a shield.
  4. 6.0.24Before entry: establish a perimeter, contain the area, use negotiation or megaphones where available, and make sure every unit knows who is leading the breach.
  5. 6.0.25On entry: announce your presence (Dept Name, make yourself known, breaching), use flashbangs or breaching tools only in realistic and necessary situations, and avoid mass Rambo-style entries.
  6. 6.0.26After entry: clear all rooms methodically and communicate clear for each area, then detain, identify, and treat everyone involved.
  7. 6.0.27Unlawful breaches: no reason or RP context, failing to announce entry, excessive or unnecessary force, and breaching non-violent offenses without a warrant.
  8. 6.0.28Hostages are the number one priority in a negotiation; comply with demands while hostages are in immediate danger, and take lethal measures only if hostage safety can be ensured.

Jailing and Hospitalization

  1. 6.0.29Jailing is used when a suspect is lawfully detained and charged following an arrest; charges must be accurate, realistic, and roleplay-based, jail times reflect the severity of the offense, arrests are logged with the reason for detainment, and only involved officers may jail.
  2. 6.0.30Hospitalization is reserved for players who avoid arrest by dying or showing a clear lack of fear of life; it cannot be requested remotely, and misuse results in a strike or more.

Off-Duty Offenses

  1. 6.0.31LEO permissions (F5, third eye, cuffing, dragging, props, vehicles, weapons) may only be used in game, in uniform, and clocked on duty.
  2. 6.0.32Any use of LEO permissions off duty results in immediate removal or blacklist.
  3. 6.0.33Any server rule violation that impacts law enforcement roleplay results in disciplinary action within the member's department.

Ride Alongs

  1. 6.0.34Ride alongs for non-training purposes are permitted between any department at any rank.
  2. 6.0.35Ride alongs cannot exceed 2 people in each car unless permitted by Department Coordination.
  3. 6.0.36Put U(X) in your name while in an active ride along, taking the next number that is not in use.
7.0

Supervisors

A supervisor's goal is to correct officers and teach them. Becoming a supervisor is not just a role, it is also a responsibility.

Punishments

  1. 7.0.1All LEO supervisors are permitted to issue write-ups, suspensions, and send officers off duty.
  2. 7.0.2Follow the Write Up Guidelines at all times; supervisors may issue less harsh punishments at their discretion but are never permitted to punish higher than the guidelines state.
  3. 7.0.3Supervisor discretion may never override SOP rules, only apply judgment within them.
  4. 7.0.4You are required to have a clip whenever you issue a punishment.
  5. 7.0.5Supervisors cannot punish other supervisors.

Duties

  1. 7.0.6Maintain RTO efficiency at all times.
  2. 7.0.7Handle any misconduct you see with professionalism, maturity, and without bias.
  3. 7.0.8When a priority is active, drag units so they do not clog RTO.
  4. 7.0.9Regularly complete ride alongs.
  5. 7.0.10Log all disciplinary actions in the proper channels with full evidence attached; failure to document voids the punishment and may bring action against the supervisor.

Expectations

  1. 7.0.11Uphold the standards and rules of JDO and PSRP at all times; ignoring misconduct results in removal from your position.
  2. 7.0.12Lead by example, stay professional, and correct officers respectfully — mistakes are teaching moments.
  3. 7.0.13Do not abuse authority, punish out of bias or emotion, overstep rank, argue over RTO, or forget to clip and log punishments.
8.0

Reports, High Command Reports, and Appeals

Reports are never handled in game, and never leaked.

Reporting an Officer

  1. 8.0.1You always have the right to remain anonymous, but a clip that reveals your identity is used as evidence in punishment.
  2. 8.0.2Reports for Low Command and below go through the normal report process in the Officer Report Tickets of the main discord.
  3. 8.0.3You may correct an officer on misconduct in game only as long as it does not break RP.
  4. 8.0.4Reports are handled only by Department Heads and Pre-Command of that department, select Low Command of tier 3 departments, or Department Coordination.
  5. 8.0.5If a report includes officers from two different departments, Department Coordination is required to handle it.

High Command Reports

  1. 8.0.6High Command reports cover Pre-Command and higher and are filed through the High Command Report ticket in the department hub.
  2. 8.0.7They are handled by Department Coordination.
  3. 8.0.8Reports on Department Coordination go to Department Management or higher; reports on Department Management or higher go to a JDO Director, Community Managers, Co-Owner, or Owner.

Appeals

  1. 8.0.9Appeal through an appeal ticket in the department hub; warnings can be appealed.
  2. 8.0.10Appeals must be filed within 7 days of a punishment, and only once per scenario.

Evidence Requirements

  1. 8.0.11Clips must include context before the incident, include audio unless impossible, be untampered and uncut, and be less than 7 days old.
  2. 8.0.12POV priority runs accused first, then reporter, then third party.
9.0

Activity and Performance Expectations

Consistent activity keeps a department operational.

  1. 9.0.1All LEO are required to meet their department's activity requirements.
  2. 9.0.2Leave of Absence cannot exceed one month without special permission from a Department Head, and must include a reason and expected return date.
  3. 9.0.3The department reserves the right to remove you if your LOA exceeds one month.
  4. 9.0.4Participate in department operations, training, and community events when possible.
  5. 9.0.5Members who show exceptional activity and dedication may be considered for promotions or rewards.
10.0

Punishment Policies

All JDO personnel must follow punishment standards to ensure fairness, consistency, and accountability.

Standards

  1. 10.0.1All punishments must include valid clip evidence; screenshots alone are not sufficient.
  2. 10.0.2Punishments without proper evidence are void and may result in action against the issuer.
  3. 10.0.3All write-ups, suspensions, and removals must be logged properly in the designated channel.
  4. 10.0.4Punishments must be issued without bias — rank, friendship, or opinion cannot influence the outcome.
  5. 10.0.5If a punishment exceeds your authority, it must be escalated through the Chain of Command.
  6. 10.0.6Every member has the right to appeal respectfully (see 8.3); retaliation against anyone filing an appeal results in immediate disciplinary action.

Definitions

  1. 10.0.7Strike — remains active for 7 days; while active the member is ineligible for promotion during the next promotion period.
  2. 10.0.8Suspension — the member may not go on duty in any law enforcement capacity for its duration.
  3. 10.0.9Termination / Removal — complete removal from law enforcement; the member may reapply later but must restart as a cadet.
  4. 10.0.10Blacklist — full removal from law enforcement with no eligibility to serve until the blacklist period has expired.
11.0

Department Command

Department Command are expected to maintain consistent activity and actively foster the growth of their department.

  1. 11.0.1Strive to keep your department stable, strong, and well-organized.
  2. 11.0.2Department Heads always receive at least 1 week inactivity notice from Department Coordination or their 01 before removal.
  3. 11.0.3Department Head promotions must include an interview with a Department Director or higher.
  4. 11.0.4To reach Department Head you must be Pre-Command for at least 2 weeks unless given special permission by Department Management.
  5. 11.0.5Command members are expected to lead by example and demonstrate above-average activity.
  6. 11.0.6Communicate regularly with Department Coordination or Management about department performance, issues, or inactivity.
  7. 11.0.7Handle misconduct professionally and naturally.
  8. 11.0.8Department Heads may use any uniform using their own department's EUP, including probationary uniforms, while on duty.
  9. 11.0.9Department Heads may impersonate LEO off duty as long as the RP is in depth; low-effort RP or trolling while impersonating results in punishment.
12.0

Transfers, Resignation, and Removal

Moving between departments, or leaving law enforcement, follows fixed rules.

Transfers

  1. 12.0.1Members may request a transfer between departments with valid reasoning, approved by both the current and receiving Department Heads.
  2. 12.0.2Transfers are only permitted between similar department types — local to local is allowed, local to federal is not.
  3. 12.0.3Members may not transfer to avoid disciplinary action or activity requirements.
  4. 12.0.4Pre-transfer: no punishments within the past 14 days, no active inactivity warnings, minimum 1 month in LEO, above Probationary rank, and Heads and Pre-Command are not eligible.
  5. 12.0.5Post-transfer: 1-rank demotion, 1-week promotion hold, and a 1-month cooldown before the next transfer.

Resignation

  1. 12.0.6All LEO officers are free to resign at any time, though at least 1 week advance notice is appreciated.
  2. 12.0.7After resignation you have 14 days where you can rejoin LEO at 3 ranks below your previous rank.
13.0

LEO x Gang Rules

Criminal interaction is roleplay first and must stay realistic.

Drugs Transport

  1. 13.0.1LEO may raid drug sales and participate in full RP scenes related to criminal activity.
  2. 13.0.2LEO should not be taking transport trucks and unloading them at PD as if they were standard drug sale scenes.
  3. 13.0.3If criminal activity is discovered through a legitimate RP scenario or drug sale, LEO can take action as normal.

FINAL STATEMENT

The policies and expectations outlined in this document are designed to uphold professionalism, fairness, and integrity within JDO and PSRP. Every member, regardless of rank or position, plays a vital role in maintaining a strong and respectful community.

Leadership, accountability, and consistency are what define a successful LEO. All personnel are expected to follow these guidelines to ensure a safe, realistic, and enjoyable environment for everyone involved.

Together, we represent the standard of professionalism that defines PSRP.