Skip to main content

Managing Incident Flags

The Managing Incident Flags infeature OPSCOM allowallows administrators to create custom tags or labels that can be attached to incident reports. ThisIts featureprimary purpose is vital forto quickly categorizing,categorize, highlighting,highlight, or drawingdraw attention to specific characteristics of an incident, thereby improving reporting,reporting capabilities, search capabilities,efficiency, and internal communication. This article is intended for OPS-COM administrators responsible for managing incident configurations and workflows.

Setup and Configuration

This feature is a core administrative tool used to establish the descriptive labels available to enforcement officers and administrative staff when documenting incidents.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the incident configuration menus and manage the list of available flags.

Using this Feature

TheAdministrators Editcan Flagsuse pagethe allowsfollowing youinstructions to navigate the management interface to seamlessly add andor editdelete incident flags, as well as control their visibility in reports.

Accessing the Management Interface

  1. Hover over System Configuration,Configuration, click Incidents, then Incidents, and click Flags.

Adding Flags

  1. At the bottom of the list, click

    Click on the empty text box provided forat addingthe bottom of the active list.

  2. Enter a newdescriptive flag.

    3. name
  3. Fill ininto the nametext field (e.g., "High Priority," "Follow-Up Required," "or Safety Concern")Concern).

  4. Toggle

    Disable the Include In Reports checkbox if you do not want this flag to show upappear in generated reports.

  5. Click the Add button to append the new flag to the system.

By default, thisthe Include In Reports checkbox is on.automatically enabled for all new flags. Disabling this setting ensures the flag remains strictly for internal viewing and workflow management.

Deleting Flags

  1. Locate the specific flag you wish to remove from the list.

  2. Click Add. The new Flag entry will now appear in the list and is ready to be used when creating or editing incident reports.
Deleting Flags

1. Click the Delete button next to the flagflag.

and

  • Click the Confirm. button to finalize the removal.

    • Best Practices &and Considerations

    • ClearUse clear and Conciseconcise Namesnames:: Use short, descriptive names for your flags that clearly convey their purposeexact (e.g.,purpose. "Labels such as Critical," "Resolved," "or Requires Manager Review").Review are instantly understandable for anyone reviewing the incident data.

    • ReportCarefully Inclusionconsider report inclusion:: Carefully consider whether each individual flag should be Includedincluded Inin Reportsreports.. Flags used purely for internal workflowworkflows or temporary tracking might not need to appear in aggregated system reports.

    • StandardizationStandardize your list:: Develop a standardized list of flags to ensure consistency across all incident reporting. ThisA well-maintained and unified list makes it significantly easier to filter, search, and analyze large sets of historical incident data.

    • WorkflowIntegrate Integrationflags into workflows:: Think about how specific flags can integrate with your broader incident management workflow. For instance, applying a "Follow-Up Required"Required flag could become a standard operating procedure to officially trigger a management review process.

    Back to top