If the Incident can be deleted, a delete option will appear. [Refer to this wiki article for more details about Purging Incidents.](https://opscom.wiki/books/setup-configuration-for-admins/page/purging-incidents)
# Filling out the Incident Form (WIP) Here is a sample of what the Incident report looks like. Basic information describing what occurred can be registered here in the overview. This includes what one might consider the essential information about the incident. - Description - Status - Time - Place - Any related information or events [](https://opscom.wiki/uploads/images/gallery/2024-06/DQaimage.png) The incident report also allows the admin to record details: - Dispatch Logs - People Involved - Vehicles Involved - Missing Property if any - Tasks to be completed - Checklist (A Custom form that can be generated) - Related issues or incidents - External (Follow-Up Items) - Related Violations [](https://opscom.wiki/uploads/images/gallery/2024-06/dslimage.png) # Incident Checklist ### Accessing the Checklist To access the checklist go into any incident and click on the **Checklist tab**. To access the form click on **Open Checklist**. The checklist form will open. [](https://opscom.wiki/uploads/images/gallery/2024-06/xTTimage.png) # Checklist Fields Defined **CCTV Reviewed:** Indicate if the closed-circuit television cameras were reviewed. (Yes/No/Not Required) State the reason for what was selected or additional details. E.g. What was found in the footage? Why was the footage not reviewed? **Other Resources Reviewed:** Indicate if other resources were reviewed as a part of the incident. (Yes/No/Not Required) State all resources used or additional details. E.g. Social media, Canada 411 or OPSCOM. **Witness(es) Interviewed:** Indicate if witnesses were interviewed as a part of the incident. (Yes/No/Not Required) State all witnesses, and their contribution to the incident resolution or additional details. E.g. Mike Lawson - Saw the incident. **Suspect(s) / Person(s) of Interest Interviewed:** Indicate if the suspects were interviewed as a part of the incident. (Yes/No/Not Required) State all suspects involved, and their involvement with the incident or additional details. E.g. Sandra Morra - Admitted fault after evidence had been found. **Statements Obtained:** Indicate if statements were collected as a part of the incident. (Yes/No/Not Required) State all the statements provided in relation to the incident or additional details. E.g. No other people at the scene to make a statement. **Other Evidence Collected:** Indicate if other physical or virtual evidence was reviewed as a part of the incident. (Yes/No/Not Required) State all the evidence collected, where it is stored and important information about it, or additional details. E.g. Beer bottle - given to the police - had fingerprints of the suspect. **Safe Plan and Community Resources Discussed with Complainant:** Indicate if a safe plan and community resources were discussed with the complainant. (Yes/No/Not Required) State what specifically was discussed, or additional details. E.g. Complainant was informed that the police were updated on the case and that the complainant's information was given to them. **Other Departments / Agencies Consulted or Notified:** Indicate if other departments were notified as a part of the incident. (Yes/No/Not Required) State all departments notified and the reason why, or additional details. E.g. Housing - Students need to be moved to separate buildings. **Community Notified:** Indicate if the community was notified as a part of the incident. (Yes/No/Not Required) State how and why the community was notified, or additional details. E.g. Flyers put up on west residence building to inform other students of the case, due to its nature and school policy. **Security / CPTED Audit Conducted:** Indicate if security and/or CPTED (Crime Prevention Through Environmental Design) audit was conducted as a part of the incident. (Yes/No/Not Required) State what was audited, any problems found, and steps taken to resolve them, or additional details. E.g. Audit of residence building security shows blind spots in lobby cameras by front desks. Additional cameras were added. **Recommendations Made to Prevent a Re-occurrence:** Indicate if recommendations to prevent future incidents were made. (Yes/No/Not Required) State all recommendations, or additional details. E.g. An employee will be posted at the front desk of the residence building at all times, to ensure the safety of all in the main lobby. **Complainant Notified of Outcome:** Indicate if the complainant was notified of the outcome. (Yes/No/Not Required) State what the complainant was told, or additional details. E.g. Bob Gant was informed that there would be an employee posted at the front desk, who could help prevent future incidents. **Documentation Updated & Filed:** Indicate if documentation was updated and filed for the incident. (Yes/No/Not Required) State what documentation was updated, or additional details. E.g Security audit has been saved to the security network drive and camera layout has been updated for all buildings. **Status at time of Closing:** Indicate the status of the incident at the time the case is closed. (Solved/Unsolved/Unfounded) **Reason For Report Being Closed:** Indicate the reasons for the report being closed. (Drop down box) E.g Reason beyond the control of service **Closing Comments:** Indicate any final comments or details of the case. E.g. Case has been closed, recommendations have been implemented for security and staffing. This type of incident should no longer be possible on the lobby floors of all residence buildings across campus. # My Incident Tasks ## Accessing your Tasks To access your tasks, click on **Incidents**, then click **My Tasks** [](https://opscom.wiki/uploads/images/gallery/2024-06/Epbimage.png) To view tasks, click on the *blue drop-down menu*, select your **name**. [](https://opscom.wiki/uploads/images/gallery/2024-06/AsKimage.png) Click on the **Incident Number** to display the **Incident information** page for more information. [](https://opscom.wiki/uploads/images/gallery/2024-06/lhLimage.png) # View Cameras 1. To view the cameras, go to Incidents icon, and click on View Camera [](https://opscom.wiki/uploads/images/gallery/2024-06/04timage.png) 2\. Next, you will see a page that has a button that says "**Launch Cameras**". Click on it [](https://opscom.wiki/uploads/images/gallery/2024-06/as1image.png) 3. A new window will open so you can see the Cameras [](https://opscom.wiki/uploads/images/gallery/2024-06/HY3image.png) # Related Occurrences 1. Click the **'Incidents Menu'** select '**Search Incidents**'. [](https://opscom.wiki/uploads/images/gallery/2024-06/Rt6image.png) 2. In the Occurrence# field enter the **Incident Number** you wish to relate to another. [](https://opscom.wiki/uploads/images/gallery/2024-06/PoDimage.png) 3. The **Incident Information** screen displays. *Note: the tabs along the top of the form,* they provide a quick summary of information. Under the **'Related'** tab we currently see the numeral 0 indicating that there are no incidents related at this time. When you select the **Related** tab, the button to **Track Related Occurrences** will appear. [](https://opscom.wiki/uploads/images/gallery/2024-06/0QAimage.png) 4. Click the **'Track Related Occurrences**' button to display the **'Track Related Occurrences'** screen. The buttons across the top allow different options to search for. The '**Add Related Occurrences**' form is now available, by selecting **New Related List**. [](https://opscom.wiki/uploads/images/gallery/2024-06/GOYimage.png) 5. The first step is to **Name** and **Create** the list. In our example, we are naming the list "***Suspicious Activity March 20***". In the notes field, you can add a description of what the purpose of the list is. Click '**Save**' to save the list name and information. The screen will refresh with a **Search** box now showing at the bottom. [](https://opscom.wiki/uploads/images/gallery/2024-06/foFimage.png) 6. Enter the **Current Incident Number** you are working with. For this example we are using16-0004. Click **'Search.'** [](https://opscom.wiki/uploads/images/gallery/2024-06/iaaimage.png) 7. Click '**Add**' to add this incident to the list entitled ***'Suspicious Activity March 20th'***. 8. Repeat the search process by entering the *Incident number* you would like to relate to the first incident. For example, Incident 16-0004 as 16-0006 and click **'Search'**. Add this incident to the list. The resulting screen will look like this: Note both 16-0004 and 16-0005 are listed. [](https://opscom.wiki/uploads/images/gallery/2024-06/qREimage.png) 9. To see the result of this process, search once again for the original Incident 16-0004 from the **Search Incidents** menu. Note the change in the Related Tab now indicates 1 related occurrence. [](https://opscom.wiki/uploads/images/gallery/2024-06/ptRimage.png) 10. Click on **Related** to see the **Related Incident Information**. Note: the related incident is now listed. This information will show up on the incident information for both incidents in question. [](https://opscom.wiki/uploads/images/gallery/2024-06/dEQimage.png) # Dispatch Logs ## Reviewing Dispatch Logs Hover over the **Incidents** icon, **Dispatch**, and select **Dispatch Logs**. [](https://opscom.wiki/uploads/images/gallery/2024-06/zl2image.png) This will bring up the **View/Edit Dispatch Log Records** page. Here administrators/dispatchers can view all open logs that still need to be followed-up on. [](https://opscom.wiki/uploads/images/gallery/2024-06/UzYimage.png) ## Printing a Dispatch Log To print the currently selected dispatch logs, select the appropriate source in the list of current dispatch logs followed by **Print Selected** to get a printed list of these logs. [](https://opscom.wiki/uploads/images/gallery/2024-06/DwJimage.png) ## Creating new Dispatch Log Records To create a new log record select one of the options from the **Create New Log Record** [](https://opscom.wiki/uploads/images/gallery/2024-06/SuDimage.png) Once the source contact for the new log has been selected, this will bring up the **Add New Log Record** screen. [](https://opscom.wiki/uploads/images/gallery/2024-06/qg1image.png) Select the appropriate **Category** from the drop-down menu and type in any details that need to go with the log in the ***Note section.*** Select the **Add New** button at the bottom of the screen to save the information. Once the information has been saved, the log will show at the top of the listing of Dispatch Log Records. ## Adding Additional Log Notes If dispatchers want to add a separate log that is attached to the first log, select the **Add link** in the **Add column**. This will bring up an **Add Log Note** screen where dispatchers can include the source of the information, the category and any notes that need to be included. To save the log select the **Add** button at the bottom. To save the log and to also close the log, if it is completed, select the **Add & Close** button at the bottom. [](https://opscom.wiki/uploads/images/gallery/2024-06/8CXimage.png) If dispatchers want to assign an admin user to act on the log or if they want to attach an incident report, select the **Assign** link at the far right of the log. When an assignment is made, the incident number will appear in the listing of Dispatch Log Records. This link can be selected to gain access to view/edit the incident report. ## Viewing Additional Notes / Rolled-Up Alerts We can view all of the available log records associated with the dispatch log In the **View/Edit Dispatch Log Records**, by selecting the **+** symbol to the left of the log. [](https://opscom.wiki/uploads/images/gallery/2024-06/a3Fimage.png) Dispatchers can add additional information to the initial log by selecting the link for the dispatch number. To close a log once it has been dealt with, select the **"C"** in the Status column to change the status to closed. ## Bulk Closing of Dispatch Logs It is also possible to close multiple Dispatch Logs in bulk. Select the logs you wish to close by selecting the checkbox associated with the log in question. Once you have selected all the log records you wish to close, click on Close Selected. [](https://opscom.wiki/uploads/images/gallery/2024-06/RcjxFhimage.png) # Incident Distribution FeatureThis article describes the Incident Distribution feature, which allows dispatchers to email incident details directly to pre-configured user groups. Its primary purpose is to streamline communication and enable faster response times by eliminating the need to manually copy information to external email clients. This guide is intended for OPSCOM administrators and dispatch personnel.
### Setup & Configuration Before this feature can be used, an administrator must create distribution *departments*. These *departments* define the recipients for incident emails. - Go to **System Configuration**, then **Distribution**, and click on **Departments and Users** ##### Creating a New Distribution Department - On the Distribution **Department Dashboard** page, click the **List All** button beside for *Departments*. Then click the plus button. - Enter a descriptive name in the **Department Name** field (e.g., **Patrol Group A**, **Security Supervisors**). This name will be visible to dispatchers. - Click **Save Changes**. ##### Adding a Contact to a Distribution Department - On the Distribution **Department Dashboard** page, click the **List All** button, but this time for the *Users* menu. Then click the plus button, again. - Select the *Department* you want this contact to belong to, and then add the contact information, including **email address.** - Click **Save & Send Invite**Once you click the button to *save and send*, this email address will receive an invitation with a link inviting them to view internal incident reports. This is why the email address is required. Contacts who are invited to view distributions are not the same as ***parkers***, or ***admin users***. They can only access the incident distribution module.
##### Managing Existing Distribution Groups From the **Distribution Group Admin** page, you can perform the following actions for any existing group: - Click the **Edit** button to modify the **Group Name** or the list of **Email Addresses**. - Click the **Delete** button to permanently remove a group. ### Using this Feature Once distribution groups are configured, dispatchers can send incident details directly from an incident's information page. ##### Sending an Incident Email 1. Go to the **Incident Information** page for the relevant incident. 2. Click the **Email Incident** button. A pop-up window will appear. 3. Click the **Select Recipient** drop-down menu and choose the appropriate distribution group. 4. Optionally, add any relevant comments or instructions in the **Comments** text box. 5. Click the **Send Email** button to distribute the information. **Key Information in Email** The email sent to the distribution group automatically includes the following key details from the incident report: - Incident Number - Location - Time of Incident - Description of Incident - Any optional comments added by the dispatcher The invitation email looks like this: [](https://opscom.wiki/uploads/images/gallery/2025-08/Ztiimage.png) --- ### Best Practices & Considerations - **Regularly audit your Distribution Groups to ensure the email lists are up-to-date.** Outdated information can lead to delayed or missed incident notifications. - **Use clear and intuitive Group Names.** Names like **Day Shift Patrol** or **Weekend Supervisors** are more effective for dispatchers than generic names like **Group 1**. - **Remember** the send invited *Department Contacts/Users* a message letting them know about the system, so they do not delete your message, or loose it in the spam folder. # View Open Incidents 1\. Hover over the **Incidents** icon and select **View Open Incidents.** [](https://opscom.wiki/uploads/images/gallery/2024-06/NDbimage.png) 2\. This will take administrators to the **Open Incidents Report Page**. Administrators can select the specific ***Incident Number link*** to view/edit that particular incident. [](https://opscom.wiki/uploads/images/gallery/2024-06/SToimage.png) # Incident Summary Report by Sub-Location 1\. Hover over the **Incidents icon**, click **Reports** and select **Sub-Location Report**. [](https://opscom.wiki/uploads/images/gallery/2024-06/vREimage.png) 2\. This will bring up the **Search Incidents** page. Select the specific dates that they want to search as well as the specific sub-location that they want to search. Select the **"Search"** button when all criteria have been entered. [](https://opscom.wiki/uploads/images/gallery/2024-06/drHimage.png) 3\. This will bring up a table at the top of the page that provides an overview of the incidents that have occurred in each sub-location based on the time frame specified (sample below). Administrators can also select the **Details link** to the right of a particular incident to view/edit that particular incident. [](https://opscom.wiki/uploads/images/gallery/2024-06/kevimage.png) # Incidents Summary Report by Category 1\. Hover over the **Incidents** icon, click **Reports** and select **Report by Category** [](https://opscom.wiki/uploads/images/gallery/2024-06/Hocimage.png) 2\. This will take you to the **Incidents Summary by Category** screen. Select the selection boxes beside the categories that you want to include in your report, select the dates that you want the report to include, select location and/or select the sub-location. Select the Search Incidents button at the bottom once you have selected all of the criteria that you want to search by. Note, you do not need to select an option in all sections, only the ones that you specifically want information on. [](https://opscom.wiki/uploads/images/gallery/2024-06/iPeimage.png) 3.This will bring up a table at the bottom of the page that provides an overview of the incidents that have occurred in each category based off of your search criteria (sample below). From here you can select any of the links listed as a sub-category to get a **Sub-Category Report.** [](https://opscom.wiki/uploads/images/gallery/2024-06/lE4image.png) 4\. In the **Sub-Category Report,** administrators can sort the table by selecting the column headings. Administrators can select the Details link beside a particular incident to view/edit details within that incident. [](https://opscom.wiki/uploads/images/gallery/2024-06/R9Himage.png) # Incidents Summary Report Hover over the **Incidents** icon, click **Reports** then select **Summary Report.** [](https://opscom.wiki/uploads/images/gallery/2024-06/0fTimage.png) This will take you to the **Incident Summary Report** page. Here you can get a summary of all incidents that have been recorded within a specified time frame. [](https://opscom.wiki/uploads/images/gallery/2024-06/twIimage.png) Enter the ***start date*** and ***end date*** for the report that you want to create and select the button at the bottom for **"Search Incidents**". If you wish to include incidents that do not have a summary in the results, uncheck the **Show only Items with Summaries** checkbox. This will bring up the **Incident Summary Report** at the bottom of the screen. You can export this information to an Excel file by selecting the **"Export to Excel"** button. You can also get the details of an individual incident by selecting the **"Details"** button to the right of the particular incident that you want to review. [](https://opscom.wiki/uploads/images/gallery/2024-06/zhQimage.png) # Recent Incidents Summary Report (Last 30 Days) 1\. Hover over the **Incidents** icon and select **Recent Incidents**. [](https://opscom.wiki/uploads/images/gallery/2024-06/GNsimage.png) 2\. This will bring up a table of all incidents that have been recorded in the previous 30 days. You can get the details of an individual incident by selecting the "**View Incidents**" button to the right of the particular incident that you want to review. You can also sort the table by selecting the column heading to sort by. [](https://opscom.wiki/uploads/images/gallery/2024-06/iEKimage.png) Note: The ability to export this report to excel is now a permission that can be given to admins. [](https://opscom.wiki/uploads/images/gallery/2024-06/3KCimage.png) # Incident Reports - [Recent Incidents Summary Report (Last 30 Days)](https://opscom.wiki/books/the-opscom-admin-portal/page/recent-incidents-summary-report-last-30-days) - [Incidents Summary Report](https://opscom.wiki/books/the-opscom-admin-portal/page/incidents-summary-report) - [Incidents Summary Report by Category](https://opscom.wiki/books/the-opscom-admin-portal/page/incidents-summary-report-by-category) - [Incident Summary Report by Sub-Location](https://opscom.wiki/books/the-opscom-admin-portal/page/incident-summary-report-by-sub-location) # Editing Incidents 1. From the **Incident Information** page, select the '**Edit Incident**' button [](https://opscom.wiki/uploads/images/gallery/2024-06/XZuimage.png) 2. Enter or change any new information, then select '**Update Incident Details**' [](https://opscom.wiki/uploads/images/gallery/2024-06/v4Cimage.png) 3. Select '**View Incident**' to return to the **Incident Information** page [](https://opscom.wiki/uploads/images/gallery/2024-06/fiqimage.png) 4. There are other options listed down the side bar. An explanation for each button is below: [](https://opscom.wiki/uploads/images/gallery/2024-06/hOXimage.png) Close Incident - Select this button to toggle the incident between Closed and Open. Edit Incident - Select this button to toggle between viewing and editing the incident. Distribute Incident - Select this button to create a distribution report. This locks the incident from being edited. Email Incident - Select this button to generate an email about the incident. Download Incident - Select this button to download a PDF copy of the incident. This locks the incident from being further edited. Toggle Read Status - Select this button to toggle the read status from '**unread**' to '**read**' or '**read**' to '**unread**' # Incident Entry 1\. Hover over the **Incidents** icon and select **Incident Entry.** [](https://opscom.wiki/uploads/images/gallery/2024-06/ab7image.png) 2\. This will take you to the **Opened Incidents** page. Here you can select the link for a particular ***Incident Number*** to view the details of that particular incident or you can select the ***Create a*** ***New** **Incident*** **button**. [](https://opscom.wiki/uploads/images/gallery/2024-06/QnXimage.png) 3\. When you select the link to **Enter New Incidents**, this will take you to STEP 1: Finding individuals and vehicles related to an incident. Select the appropriate link to search by Users, Vehicles or Missing Property. If the incident is not associated with a particular user, vehicle or missing property, select the "**Enter Specific Incident Details**" button. [](https://opscom.wiki/uploads/images/gallery/2024-06/TgAimage.png) 4\. Once you find the user that you are looking for, select the "**Add User to Incident"** button at the bottom right. If there is no user found with the information you are searching, you can select the "**Add a New Individual to the Database**" button at the very bottom, in the center. This will take you to the STEP 1: Quick Registration Form where you can enter all the details that you have on the individual. [](https://opscom.wiki/uploads/images/gallery/2024-06/PdSimage.png) 5\. Once the user is selected or added you will be taken to a page where you can identify specifics about the individuals involved in the incident. Fill in all the details that you have. You must fill in the **Relation** field which identifies person's relationship to the incident (e.g. victim, witness, prime suspect, etc.) Select the "**Save User Details"** button to save the details. Select the "**Search for Additional Individuals**" button to add other individuals involved in the incident. You can also add vehicle details and property details by selecting the appropriate link. You can also select the **"Enter Specific Incident Details"** button at the bottom right if there are no other details to add related to people, vehicles, and property. [](https://opscom.wiki/uploads/images/gallery/2024-06/NgJimage.png) Sample Vehicle Search [](https://opscom.wiki/uploads/images/gallery/2024-06/V3Rimage.png) Sample Missing Property Search [](https://opscom.wiki/uploads/images/gallery/2024-06/sHyimage.png) 6\. Once you select the **"Enter Specific Incident Details"** button you will be taken to STEP 2: Entering Incident Information. A summary of the people involved, vehicles involved and/or the missing property involved will appear at the top of the page. Next, you will find the **Incident Information** section where you will fill in all information that you have on the incident. (**OPS Number** is an abbreviation for ***Other Police Services Number*** used for tracking the incident. **PON Summons** is an abbreviation for ***Provincial Offences Notice Summons.***) To attach images, select the **"Choose File"** button beside the line for Attach Image, find and select the file that you want to attach and select the **"Open"** button. This will upload the file and attach it to the incident. When all information is submitted in the Incident Information section, select **"Save Incident"** at the bottom of the page. [](https://opscom.wiki/uploads/images/gallery/2024-06/e1eimage.png) 7\. Once the incident has been saved you will be taken to the **"Incidents - Last 30 Days"** summary screen. If you need to edit any details, select the **"View Incident"** link to the right of the incident that you want to reopen. [](https://opscom.wiki/uploads/images/gallery/2024-06/P2Vimage.png) # Search Incidents 1\. Hover over the **Incidents** icon and select **Search Incidents**. [](https://opscom.wiki/uploads/images/gallery/2024-06/RWtimage.png) 2\. This will take you to the **Search Incidents** screen. Here you can do an Incident Search, People Search or a Vehicle Search. Fill in the information you want to search by and select the "**Search**" button at the bottom of that particular section. ## Search Criteria **Occurrence #:** When an incident is created in the system a unique ID number is designated to the incident that can be referenced in this search module. **Police Occurrence #:** If you partner with a police force they may have a reference number that can be assigned and searched. **Reported by (Officer):** This search filter will narrow your search to incidents reported by specific officers selected from a drop down pick list. **Reported Dates**: Enter the date on which the incident was reported. **Status:** Select from a drop down pick list incidents that have a status of **Open, Closed,** or **Close Requested** **Summary:** Enter a short description of the incident in question. **Between Dates: **Enter a date range in which the incident occurred. **Location** and **Sub-Location:** Select areas where the incident occurred. **Room Number:** If the incident occurred in a specific room on campus, enter the room number here. **Category:** Select the general type of incident being searched from a drop down pick list. **Sub Category:** Select the specific type of incident in relation to the general type being searched from a drop down pick list. The list changes based on which general category is chosen. **PON/Summons Issued:** Select whether or not a PON (Provincial Offence Notice) or Summons has been issued. **Arrest/Apprehension Made:** Select whether or not an arrest or apprehension of an individual was made. **Violence Involved:** Select whether or not violence was involved in the incident. **Weapons Involved:** Select whether or not weapons of any kind were involved in the incident. **Text:** Use this field to enter related key words, descriptions, locations etc. This search field searches both the narrative, and location description. **Last Updated Between Dates: **Select a date range of when an update to the incident information might have occurred. **Has Been Read:** Select yes, no or either. This will select incidents that have been previously reviewed or those that have not. **Case Manager**: Select from a drop down pick list to filter on specific case managers assigned to the incident in question. **Primary Investigator:** Select from a drop down pick list to filter on specific primary investigator assigned to the incident in question. **Task Assignments:** Select from a drop down pick list to filter on a specific assignee who has been tasked with investigating the incident in question. **Requires a Checklist:** Select whether or not the incident has a related checklist. **Include Checklist Details: **If the item above it checked as yes or either, check this box if you wish to have the checklist details appear in your search results. [](https://opscom.wiki/uploads/images/gallery/2024-06/lbUimage.png) **People Search:** In this section you can enter typical details about a specific person to perform an incident search on. **Vehicle Search:** In this section you can enter typical details about vehicles that are involved in the incident being searched. [](https://opscom.wiki/uploads/images/gallery/2024-06/K5Vimage.png) # Configuring Incidents Here is the list of items that would have to be set up in the system prior to using the incident module. [](https://opscom.wiki/uploads/images/gallery/2024-06/cNbimage.png) 1. **Categories**: Incident Categories are a listings of the types of Incidents that occur. Each **Category** can have multiple **sub categories**. Here's an example of a category and it's sub-category items. In this case the category is **Break and Enter**. The subcategories appear on the right. [](https://opscom.wiki/uploads/images/gallery/2024-06/pbPimage.png) 2. **Flags**: Incidents may be **flagged** for information, and/or importance. An example would be: "Was violence involved?" or "Were there weapons involved?" For more information Refer to this Article. 3. **Ethnicity**: Within incident reporting you have the ability to enter a description of people associated with the incident, whether it be the victim, a related person, the suspect or person who committed the incident. Ethnicity is one of the descriptors typically used in identifying a person related to an incident. 4. **Relations**: In this area you can define the relationship/involvement the individual has with the particular incident. Examples could be: Complainant, Witness, Victim etc. 5. **Ext. User Profile Options**: These items are **extended values** used in describing an individual within incident reporting. Examples could be: Physical descriptors such as hair colour, hair style, Body Build Type, Clothing Style etc. (**Note:** These descriptions will only be seen in the incidents module and not in the user's profile.) 6. **Missing Property Types**: An incident may include theft or damage to property. This item allows you to create **pick lists** that can describe property involved in an incident. Examples could be: Vehicles, personal property such as jewelry, computers, electronic devices, money, etc. 7. **Cameras**: In this section admins can configure input from surveillance cameras that may have captured the incident. # IncidentAdmin Workflow Incidents can be reported in several ways: - Campus Security may observe violations as they occur - Individuals may contact campus security to report incidents - Staff may report incidents on behalf of fellow staff or students - Requests to investigate may come from campus administration - Incidents may be caught on surveillance cameras etc. Initiating the entry of incidents into the system can be done in a couple of ways. - Dispatch Logs - Incident Entry These items can be generated in any order. Once an incident is recorded in the system **Security Administrators** can track the progress of any resulting investigation or follow-up events related to the incident. Tasks can be created and assigned to officers, primary investigators, case workers and security administration through the incidents tool. Investigators can track their progress from initial discovery through to resolution. Steps taken in the process as well as the outcome for 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**. 1. Searching, viewing and editing incident records 2. Working with related occurrences and violations 3. Viewing "**My Tasks**" within **IncidentAdmin** 4. Generating reports from records stored in **IncidentAdmin** ## A Word About Reports There are a number of reports that can be generated in **IncidentAdmin.** 1. **Recent Incidents Summary Report -** Lists the last 30 days of incident records. 2. **Search Repeat Offenders -** Report on individuals involved in multiple incidents 3. **Weekly Stat Report -** Reports on the number of all types of incidents that happened during a specified time span 4. **Calls for Service** 5. **Summary Search -** Allows administrators to get a summary of all incidents that have been recorded within a specified time frame. 6. **Summary Report -** Allows administrators to produce a list in a spreadsheet format of incident summaries based on a date range**.** 7. **Report by Category** - Search for incidents under defined categories within a specific time frame. 8. **Sub Location Report** - Search incidents filtered by sub location.