The report form, field by field
What each question asks, why, and how the answers are used.
Last updated
Only the category, title and description are required. Everything else helps the case team but is optional.
| Field | Purpose |
|---|---|
| Category | Chooses the form and, together with your rules, where the case goes. |
| Short title | A neutral summary shown in lists. Reporters are warned not to include names, because many handlers can see titles. |
| What happened? | The narrative. It is encrypted at the field level. |
| When and where | Helps investigators place the events. |
| Department involved | Tells routing which department the report is about, so that department is kept away from the case. |
| Who is this about? | Level of the person concerned: colleague, manager, senior executive, compliance or ethics officer, or board member. Senior subjects make a case restricted automatically. |
| People involved or witnesses | Names or descriptions. Encrypted at the field level. |
| Estimated financial impact | Optional, for prioritisation. |
| Urgency | Standard, Urgent, or Critical when someone is at immediate risk. |
| Worried about retaliation | Raises the case's priority and confidentiality and alerts protection staff. |
| Reported before | Helps spot repeated concerns. |
| Category questions | Extra questions your organisation defines. Conditional ones appear only when a parent answer calls for them. |
| Identity | Anonymous by default. An identified reporter adds a name and a way to be contacted. |
Note. The form is validated twice: once in the browser for quick feedback and again on the server, which is the check that counts.
Related guides
Still stuck?
The SLEM Technologies team can help with set-up and questions.