Submit an Incident Report (Web)

This guide covers the web incident-reporting flow. In the current product, the web flow opens as a modal titled Report New Incident.

When to Use the Web Form

Use the web form when the control room needs to log an incident directly, for example:

a guard phones the control room instead of submitting from mobile
an operator sees something on CCTV
you are backfilling an incident that happened earlier
you need to capture a report while already working in the dashboard

The web form is best for control-room logging. Guards in the field will often use the mobile app instead.

Opening the Form

Use the New Incident button at the top of the app shell. In the current UI, this opens a modal rather than a separate full page.

The Fields in the Current Form

The current web form includes these fields:

Field	Required	Notes
Incident Title	Yes	Short plain-English summary of what happened
Type	Yes	Searchable incident-type selector
Severity	Set it intentionally	Low, Medium, High, or Critical
Description	Yes	Factual narrative of what happened
Date & Time	Yes	Defaults to the current timestamp, but can be changed
Evidence	Optional	Add one or more photos
Location	Yes	Address search, map interaction, or current GPS

The Report Incident button stays disabled until the required information is present.

How to Fill It In Properly

1. Incident Title

Use a title that tells the next operator what happened and roughly where.

Good examples:

Unauthorized person at rear gate
Broken window at loading dock
Vehicle attempted entry without authorization

Bad examples:

Problem
Issue at site
Need help

2. Type

Choose the closest matching incident type from the search field. The platform supports the current incident-type set defined in the product, including theft, suspicious activity, emergency, medical emergency, fire, accident, maintenance, parking violation, and others.

3. Severity

Use the severity to reflect actual risk:

Level	Use it for
Low	Informational or minor operational issues
Medium	Requires attention, but not an emergency
High	Significant risk requiring prompt follow-up
Critical	Life-safety or major property-risk situations

4. Description

Write what was observed, what was done, and what risk remains.

Keep it factual:

what happened
who was involved
what action has already been taken
whether the threat is still active

5. Date & Time

Leave the current value if you are reporting the incident now. Change it if you are capturing a past event for the record.

6. Evidence

Attach photos when they add proof. The current web form supports photos, not video.

7. Location

The location is mandatory. You can set it by:

searching for an address
using the embedded map
clicking Use Current GPS Location

For desk-based reporting, address search is usually the fastest option.

Submitting the Report

Once the required fields are complete:

Review the title, description, and location one last time
Click Report Incident
Wait for the success toast

In the current UI, the success message is:

Incident reported successfully

What Happens After Submission

Once submitted, the incident becomes part of the live operational workflow:

it appears in Operations Board
it becomes visible in Incident Map
it affects dashboard counts and recent-incident views
it can be assigned, updated, resolved, or published later by admins

Newly submitted incidents enter the workflow at the left side of the board, in Incoming.

Practical Tips

Use a clear title first. The title is what operators scan under pressure.
Do not write a story in the title, put detail in the description.
Set the location carefully. A wrong pin wastes time during response.
Attach photos when the scene, damage, or suspect vehicle matters later.
If you are logging on behalf of someone else, say that in the description.

What This Form Does NOT Do

It does not support video upload
It does not auto-assign a guard
It does not auto-escalate severity into workflow status changes

Emergency Response - how incidents move from report to action
Control Room Dashboard - where operators monitor and triage these reports
Client Communication - how verified incidents are later published to clients