Incident Report FAQ's

Incident Report FAQ's

Q. I attached some images to an incident report and I can't get the pdf to download. Am I doing something wrong?

This sometimes occurs when the images are uploaded at high resolution causing the system to time out while processing the IR for download. To prevent this, please run your high-res images through an online image optimizer before attaching to your IR. Doing so can result in file sizes 90% smaller than the original file for a faster download experience.


Q. I tried extracting a video from our CCTV system to attach to an incident report and SOVA would not allow me to attach it. What format video do I need?

SOVA only accepts MP4 as a video format, and that choice was made as that format allows the video to play directly in a web browser when clicked as opposed to having to download the video and then open it in a separate video player for viewing. You may want to discuss with your CCTV vendor to see if your system supports MP4 as an export format. Otherwise, there are free online video conversion websites that should be able to take care of changing formats for you.


Q. Recently I was working on an incident report and now it is missing from the list. Where did it go?

More than likely, someone mistakenly deleted the incident report. Fortunately with most things database related, nothing is ever truly deleted. Simply submit a ticket with the name of the reporting officer, incident date, IR classification and maybe the name of an involved person and with this information we should be able to find and restore the IR to an active state

Q. Why don't incident reports have a number when they are created?

If SOVA did that, and you decided to delete an incident report and re-create it, the result would a loss in your sequential numbering. For example, let's assume you had incident report numbers 1002, 1003, and 1004. If you decide to delete 1003, then your IR list would have gaps in the numbering. While this does not cause any issue directly, you might look back a few months, see an jump in your numbering and wonder if the system had a malfunction or there was some other issue. By not assigning IR numbers until after the incident report is accepted as the final, approved version, we keep things tidy. And, SOVA is very flexible in how you number your incident reports.


 




    • Related Articles

    • Incident Report Numbering

      SOVA offers flexibility in how you number your incident reports. While it might not be possible to create a numbering system that is exactly what you currently use, especially if you have a very complex system, you should be able to get pretty close. ...

    • Incident Report Listview

      The Incident Report listview in SOVA allows you to see all incident reporting from a single screen. From here, you can view and edit IR's, review media attached to IR's like images, audio and video files, PDF's and WORD documents. There are many ...

    • Changing Incident Report Status

      Incident reports (IR's) created in SOVA go through a lifecycle from inception to acceptance. At the various stages, authors of the IR may or may not have the ability to edit their reports, others can always send comments via email to the IR author to ...

    • Default, boilerplate IR narratives

      Maintaining consistency in your incident narratives is important for many reasons: Properly formatted narratives make reviewing quicker as admins know where to expect certain types of information Boilerplate narratives teach new officers how to write ...

    • Writing Incident Reports (video)

      This training video describes how to write incident reports in the SOVA platform, starting in SOVA Mobile and finishing the incident report in SOVA Web. SOVA remains flexible in this regard. You can begin the IR on the mobile device, collect basic ...