Running In-Game Patrols and Events

These two formats have different purposes and require different preparation:

• Patrols: Regular operational sessions. Members go on duty, respond to calls, and carry out standard department functions. The focus is routine operations and activity maintenance.
• Events: Planned scenarios or operations with a specific purpose — a pursuit drill, a multi-department response, a civilian interaction scenario. Events typically require advance coordination and a designated coordinator.

Most departments run weekly or bi-weekly patrols as their standard activity and hold events as supplementary, less frequent sessions.

Irregular patrols produce irregular attendance. Establish a schedule your members can plan around:

• Set patrol days and times based on when your member base is most active — use Discord's member activity data or a scheduling poll.
• Post the patrol schedule at least 48 hours in advance in a dedicated channel.
• Assign a patrol lead for each session — someone responsible for opening the server, managing CAD, and running debrief.
• Require members to confirm attendance or flag conflicts in advance if your server uses attendance tracking.

A patrol should have a defined start, execution, and end. Avoid free-form sessions with no coordination:

• Briefing (5 minutes): Patrol lead covers current objectives, active calls, and any special operational notes.
• Active patrol: Units sign into CAD, go on duty, and respond to calls via dispatch. Patrol lead monitors and coordinates.
• Debrief (5–10 minutes): Brief review of the session — notable calls, conduct observations, and any procedural notes.

Events require more preparation than patrols. Assign a coordinator who handles logistics:

• Define the event objective — what is this event designed to accomplish or practice?
• Assign roles in advance — who is handling dispatch, who is on scene, which departments are involved?
• Brief participants before the event starts. Everyone should know what to expect before the scenario begins.
• Run the event at a consistent pace — do not let it drag or end abruptly. The coordinator manages the timeline.

Tracking patrols and events produces data that improves future sessions:

• Log attendance for every session — member name, rank, duration on duty.
• Note any significant incidents, conduct issues, or operational highlights in a patrol report.
• Review attendance trends monthly. Members who are consistently absent without notice should be contacted directly.

Debrief is not a formality — it is where operational improvement happens:

• Keep debrief factual and brief. Limit to three to five observations per session.
• Separate conduct issues from operational issues. Conduct is addressed privately, not in group debrief.
• Ask for input from participants — what went well, what needs adjustment?
• Follow up on any procedural changes that were identified in debrief. If nothing changes from debrief to debrief, members will stop participating in them.