Every organization has different incidents to track, with different fields and notification requirements. Incident types let Managers define the categories that appear in the IR form.
Configuring incident types is web-only and Manager-only.
What an incident type controls
For each incident type, you can configure:
-
Name — what staff pick from the dropdown (e.g. Fall, Aggression, Medication Error).
-
Description / definition — guidance for staff about when to use it.
-
Severity scale — the options shown (Minor / Moderate / Serious / Severe, or custom).
-
Notification rules — who must be notified when this type of IR is submitted.
-
Required fields — which fields are mandatory (description, witnesses, follow-up, etc.).
-
Custom fields — your own questions specific to this incident type.
The right configuration makes IR filing faster and prevents missing information.
Where to configure
-
Sign in at
app.behca.com(US) orau.behca.com(Australia) as a Manager. -
Open Incident Reports → Configuration (or Manage → Incident Types, depending on UI version).
-
You'll see the list of types currently set up.
Adding a new incident type
-
Click New Type.
-
Fill in the name and description.
-
Configure required fields, severity, and notifications.
-
Save.
The new type appears in the IR creation form for all team members immediately.
Suggested incident types
Most organizations have at least these:
-
Fall — accidental, with or without injury.
-
Behavioral Incident — aggression, self-injury, property damage.
-
Medication Error — wrong dose, wrong med, missed dose.
-
Allegation — abuse / neglect / complaints.
-
Near Miss — almost happened, was averted.
-
Property Damage — significant damage to belongings or facility.
-
Restrictive Practice — restraint or restriction used.
-
Elopement — person left the premises unauthorized.
-
Death — sometimes called "Critical Incident".
-
Other — catch-all for anything that doesn't fit.
Your industry and regulator may require additional types — check your local guidance.
Editing an existing type
-
Click the type's name in the list.
-
Edit fields.
-
Save.
Changes affect new IRs going forward. Existing IRs of that type retain their original configuration — you don't retroactively change history.
Removing a type
You can usually deactivate a type so it no longer appears in the dropdown for new IRs, while keeping existing IRs intact. Outright deletion is risky — past IRs would lose their type — and is usually disabled.
Custom fields
For specialized tracking, you can add custom fields to a type — text, number, dropdown, checkbox. Examples:
-
Fall: Did the person hit their head? (Yes/No)
-
Behavior: Was a restraint used? (Yes/No, with details)
-
Medication Error: Was the GP notified? (Yes/No, with notification time)
Custom fields are powerful but can overwhelm staff. Aim for the smallest set that captures what's needed.
Notifications by type
Different types may need different notifications:
-
Falls / Injuries — notify family + GP.
-
Behavioral — notify behavior clinician + family.
-
Critical / Serious — notify regulator + senior management.
-
Medication errors — notify prescriber + pharmacy.
Configure these per type so staff don't have to remember each rule.
Tips
-
Start with the standard types above and customize from experience.
-
Don't proliferate types. 5–10 well-designed types is better than 30 niche ones — staff have to remember which to use.
-
Review annually. As your service evolves and regulations change, refresh the configuration.
-
Pilot a new type before rolling it out to the whole team. Make a few sample IRs to test the form.
Common questions
-
Can a Staff member request a new type? — Yes — they should ask a Manager. Only Managers can add or edit types.
-
Will old IRs migrate to a new type definition? — No. They keep the configuration that existed when they were created.
-
Is there a global library of incident types? — Not currently. Each organization configures its own.
-
Can I bulk-import types from another organization? — Not currently. Set up types manually.