Beginning in 2025, the Leonida Regional Police Service is moving to a standardized reporting model. This ensures that every interaction—whether it ends in a successful arrest or a suspect escape— is documented for the safety of all officers.
Step 1: The Initial Entry (CFS)
Every incident begins with a Call for Service (CFS). This should be created as soon as the scene is secure. The CFS acts as the "log" for your shift.
- Mandatory Info: Date, Time, Location, and Call Type.
- Summary: Use the "Comments" section for a quick "as it happened" description. This is often just general notes as best as you can do— no need to be professional per-se here, as this is visible internally only.
Step 2: The Incident Report
Once the CFS is logged, you must file a formal Incident Report and link it to that CFS. This is your primary legal narrative. It should be professional, objective, and detailed.
Example: "Officer observed subject [Name] firing an RPG into a crowd of people at a car show. Officer initiated a pursuit, and eventually the subject opened fire on department personnel by tossing grenades out their window."
Step 3: Choosing the Correct Conclusion
Depending on how the encounter ended, you will complete the paperwork in one of the two following ways:
Option A: The Suspect was Apprehended (Arrest)
If the suspect was successfully stopped or neutralized on-scene:
- Action: File an Arrest Record.
- Link: Attach the Arrest Record to the Incident Report.
- Status: Mark the Incident as Closed/Cleared.
Option B: The Suspect Cannot Be Arrested (Citation)
If the suspect was unable to be stopped or arrested for any reason, such as using cheats for example:
- Action: File an Citation Record.
- Link: Attach the Citation Record to the Incident Report.
- Status: Mark the Incident as Open.
Option 
The Suspect Escaped (Warrant)
If the suspect fled the area or "left the session" before an arrest could be made:
- Action: File a Warrant.
- Link: Attach the Warrant to the Incident Report.
- Status: Mark the Incident as Active/Wanted.
- Result: This flags the suspect in the system for all other officers to see.
Option 
Wanted Subject (Warrant Service)
If you perform a name check during a traffic stop or interaction and discover the subject has an Active Warrant, follow these steps to clear the system:
- The Arrest: Take the subject into custody (or neutralize the threat).
- The Supplemental Report: You do NOT need to create a new Incident Report. Instead, find the Original Incident Report linked to that warrant and file a Supplemental Report.
- The Update: In the narrative, state: "On [Date], the undersigned officer encountered the subject during a [Traffic Stop/Patrol]. Subject was taken into custody on Warrant #[Number]."
- Closure: Change the status of the Original Incident and the Warrant to "Cleared by Arrest"
Summary of Workflow Examples
| Scenario | Workflow Path | Final Outcome |
|---|---|---|
| Standard Arrest | CFS → Incident Report → Arrest Record | Case Closed |
| Cheater/Modder Flag | CFS → Incident Report → Citation | Warning Logged |
| Subject Flees/Logs Out | CFS → Incident Report → Warrant | Case Active (BOLO) |
| Warrant Catch | Supplemental Report (on Original Incident) | Warrant Cleared |
Note on System Integrity
The Leonida Regional Police Service utilizes a proprietary, high-level Records Management System (RMS) that far exceeds the capabilities of standard municipal departments. While this system provides us with a significant tactical advantage in the field, its effectiveness is entirely dependent on the diligence of our personnel.
While powerful, remember that it's only as useful as the data within it. By following these reporting procedures thoroughly, you are not just completing "paperwork"— you are building a comprehensive intelligence network that protects your fellow officers and ensures that no offender is overlooked. It is every officer's responsibility to maintain the accuracy and persistence of our records.