Incident Checklist

The Incident Checklist provides a standardized form for administrators and investigators to ensure all critical investigative steps are completed before closing an incident. Its primary purpose is to help maintain comprehensive, consistent, and legally sound records for audits and internal reviews. This article is intended for OPS-COM administrators and security personnel responsible for managing and closing incident reports.

Setup and Configuration

The Incident Checklist is a core component of the IncidentAdmin module and requires no additional system setup. However, administrators must have the appropriate permissions to view and edit incidents to access and complete this form.

Using this Feature

Administrators must navigate to an active incident report to access and fill out the checklist. The form requires users to select standard responses (e.g., Yes, No, Not Required) and provide clarifying remarks for each step of the investigation.

Accessing the Checklist

1. ToNavigate accessto and open the checklist go into anyspecific incident andyou clickwish onto update.

2. Click the Checklist tab. To accesswithin the formincident clickrecord.

   on

3. Click the Open Checklist. button to launch the form.

TheDepending on your organization's specific subcategory configurations, filling out this checklist formmay willbe open.a mandatory system requirement before an administrator is permitted to close the incident report.

Checklist Fields Defined

When filling out the checklist, provide specific details in the remarks fields to justify your selections.

• CCTV Reviewed: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?footage Whyor wasexplain why the footage was not reviewed?reviewed.

• Other Resources Reviewed:Reviewed

  :

  Indicate if otherexternal resources were reviewedutilized, such as asocial partmedia, ofpublic the incident.  (Yes/No/Not Required) State all resources useddirectories, or additionalOPS-COM details.records.

  E.g.
Social media, Canada 411 or OPSCOM.

• Witness(es) Interviewed:Interviewed

  :

  IndicateNote if witnesses were interviewedspoken as a part of the incident.  (Yes/No/Not Required) State all witnesses,to and summarize their contributionspecific contributions to the incident resolutionresolution.

  or
additional details. E.g. Mike Lawson - Saw the incident.

• Suspect(s) / Person(s) of Interest Interviewed:Interviewed

  :

  IndicateDocument ifany thesuspect suspectsinterviews, were interviewed as a part of the incident.  (Yes/No/Not Required) State all suspects involved, andnoting their involvement with the incident or additionalstatements.

  details.
E.g. Sandra Morra - Admitted fault after evidence had been found.

• Statements Obtained:Obtained

  :

  IndicateConfirm if formal, written statements were collected asfrom aany partinvolved ofparties.

  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:Collected

  :

  IndicateDetail if otherany physical or virtual evidence was reviewed as a part of the incident.gathered (Yes/No/Note.g., Required)photos, Statephysical all the evidence collected, where it is storeditems) and importantnote informationits aboutsecure it,storage orlocation.

  additional
details. E.g. Beer bottle - given to the police - had fingerprints of the suspect.

• Safe Plan and Community Resources Discussed with Complainant:Complainant

  :

  IndicateNote if the complainant was provided with a safesafety 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 givenreferred to them.external support resources.

• Other Departments / Agencies Consulted or Notified:Notified

  :

  IndicateList ifany otherinternal departments (e.g., Student Housing) or external agencies (e.g., local police) that were notifiedbriefed as a part ofon 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:Notified

  :

  IndicateState if and how the broader community was notifiedalerted as a part ofto the incident.incident (Yes/No/Note.g., Required)safety Statebulletins, howcampus andemails).

  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:Conducted

  :

  Indicate if securitya and/or CPTED (Crime Prevention Through Environmental Design)Design (CPTED) or general security audit was conductedperformed. as a part of the incident.  (Yes/No/Not Required) State what was audited,Note any problemsvulnerabilities found,discovered and the steps taken to resolve them,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:occurrence

  :

  IndicateDetail ifany recommendationsoperational or security changes suggested to prevent future incidentssimilar wereincidents.

  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:Outcome

  :

  IndicateConfirm ifthat the complainantreporting party was notifiedupdated on the final resolution of the outcome.case.

  (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:Filed

  :

  IndicateNote ifexactly documentationwhere wasrelated updatedfiles, and filed for the incident. (Yes/No/Not Required) State what documentation was updated,audits, or additionalhard details.copies E.gwere Securitysaved.

  audit
has been saved to the security network drive and camera layout has been updated for all buildings.

• Status at time of Closing:Closing

  :

  IndicateSelect the statusfinal state of the incident at the time the case is(Solved, closed.Unsolved, (Solved/Unsolved/or Unfounded).

  
  
  

• Reason For Report Being Closed:Closed

  :

  IndicateClick the reasonsdrop-down menu and choose the primary reason for the report being closed. (Drop down box) E.g Reason beyondclosing the controlreport.

• Closing Comments: Provide a final narrative summarizing the resolution and confirming any implemented recommendations.

---

Best Practices and Considerations

• Standardize Remarks: Organizations should develop a business rule outlining the minimum level of service
  
  Closingdetail Comments:required in the remarks section.

  IndicateSimple any final comments"Yes" or details"No" ofanswers without context can lead to poorly documented investigations.

• Complete Before Closing: Ensure all relevant checklist fields are thoroughly completed before attempting to change the case. E.g. Case has been closed, recommendations have been implemented for security and staffing. This type ofoverall incident shouldstatus noto longerclosed.

  be
possible on the lobby floors of all residence buildings across campus.