IncidentAdmin Workflow

IncidentsThe IncidentAdmin workflow provides a comprehensive framework for reporting, tracking, and resolving security events on your property. Its primary purpose is to guide administrators through the complete lifecycle of an incident, from initial dispatch entry and task assignment to final resolution and statistical reporting. This article is intended for OPS-COM administrators and security personnel.

Setup and Configuration

Because this workflow encompasses the entire incident management module, there is no single setup step. Instead, administrators must ensure that all foundational elements—such as categories, flags, and physical locations—are properly established in the system prior to use.

Detailed setup instructions for these prerequisites can be reportedfound inon severalthe ways:

Configuring

Incidents
• CampusConfiguring SecurityIncidents maypage. observeAdditionally, violationsadministrators asmust theyhave occur
the
• Individualsappropriate mayroles contactand campuspermissions securityenabled to reportcreate, incidents
view,
• Staffedit, mayand report incidents on behalfincidents.
  of

  Using fellowthis staffFeature

  The incident workflow generally follows three main phases: initiation, investigation and tracking, and reporting.

  Initiating an Incident

  Security events are typically brought to the administration's attention through direct observation by patrol staff, phone calls from individuals, administrative requests, or students

• Requests to investigate may come from campus administration
• Incidents may be caught on surveillance camerascamera etc.

footage.

InitiatingEntering thethese entry of incidentsevents into the system is handled through two primary modules, which can be doneutilized in aany coupleorder ofdepending ways.on your organization's procedures:

• Access the Dispatch Logs page to quickly record incoming calls, alerts, and initial reports.

• Access the Incident Entry page to formally create and document a comprehensive case file.

TheseWhile itemsdispatch logs and incident entries can be generated inindependently, anydispatch order.logs can be directly linked and assigned to an incident report. This preserves the initial call data and integrates it seamlessly into the final investigative file.

Tracking and Managing Investigations

Once an incidentevent is recorded in the systemsystem, Securitysecurity Administratorsadministrators can track the progress of any resultingthe investigation orand manage follow-up eventsactivities. relatedThe core workflow highlights during this phase include:

• Searching, viewing, and editing active incident records as new details emerge.

• Creating and assigning actionable tasks directly to the incident.
  Tasks can be created and assigned tofield officers, primary investigators, case workersworkers, and securityadministrative administrationstaff.

  through

• Reviewing personal responsibilities by checking the incidentsMy tool.Tasks dashboard.

• InvestigatorsRecording canspecific trackprocedural their progress from initial discovery through to resolution.
  Stepssteps taken inand documenting the processfinal as well as the outcomeoutcomes for all individuals involved can be recorded, and in turn reported on through IncidentAdmin.
  
  The following subjects are the main highlights in the workflow process in IncidentAdmin.involved.

  1. Searching, viewing and editing incident records
  2. Working with

     Linking related occurrences and parking or moving violations to the main incident to build a complete case history.

  3. Viewing

"My Tasks" within IncidentAdmin

Generating reportsReports

from

The final phase of the workflow involves analyzing the collected data. IncidentAdmin provides a suite of reporting tools to help administrators review records storedand inoperational IncidentAdmin

efficiency:

A Word About Reports

• There are a number of reports that can be generated in IncidentAdmin.

  1. Recent Incidents Summary Report -Report: Lists all incident records logged within the last 30 daysdays.
     of incident records. 
     

  2. Search Repeat Offenders -Offenders: ReportGenerates a report on specific individuals involved in multiple incidents over a period of time.

  3. Weekly Stat Report -Report: Reports onCalculates the total number of allvarious incident types of incidents that happenedoccurred during a specified time spanspan.

  4. Calls for ServiceService: Summarizes service call metrics and dispatch responses.

  5. Summary SearchSearch: - Allows administrators to getRetrieves a summary of all incidents that have been recorded within a specified time frame.

  6. Summary Report -Report: Allows administrators to produceProduces a downloadable, spreadsheet-formatted list in a spreadsheet format of incident summaries based on a defined date range.range.

  7. Report by CategoryCategory: -Filters Searchand fordisplays incidents under defined categoriescategory classifications within a specific time frame.

  8. Sub Location ReportReport: -Filters Searchand displays incidents filteredbased byon subspecific location.physical zones or sub-locations on your property.

---

Best Practices and Considerations

• Standardize your reporting procedures: Organizations should develop a clear business rule outlining exactly when a situation warrants a simple dispatch log versus a full incident report. This ensures consistency in how daily activities are triaged and escalated.

• Utilize task assignments: Always use the built-in task assignment features for follow-ups. Assigning specific tasks to investigators or case workers ensures that the investigation maintains momentum and creates an auditable trail of accountability.