Choose a template
Or scan the QR code and report without an account.
Incident reporting
Easy to report. Hard to read.
Anyone can file a report in a minute. Only the people you name can open it.
Clearance · Kids' church leader
| Requirement | Detail | Status |
|---|---|---|
| Blue card | Expires 14 Nov 2026 | Current |
| Child-safe policy v4 | Acknowledged 2 Mar | Read |
| Volunteer form | Completed 2 Mar | Done |
| First aid certificate | Expires 19 Sep 2026 | Expiring |
| Leader's review | Not started | Blocked |
Application held — one item outstanding.
Why churches choose RiskEZI for incident reporting
Consistent reporting
Templates make sure the important details are never missed.
Appropriate access
Sensitive reports stay with the department handling them.
Accountability
Checklist items and tasks with someone responsible for each.
Complete records
Notes, witnesses, signatures and attachments on one record.
Adapt to your needs
Classes and templates in your own terminology.
Reporting
Filter by template, branch, department and date. Export to CSV.
Incident reporting
A QR code on the noticeboard
A volunteer scans it and reports what happened — no account, no login, no waiting until Monday. The report you actually want is the one that gets made.
- No account needed to report
- A QR code is enough
INC-0248 · Slip on wet floor in foyer
| Field | Value | Status |
|---|---|---|
| Reported by | Anonymous, via QR | Open |
| Class | Injury | Injury |
| Department | Facilities | Assigned |
| Witnesses | 2 statements, signed | Attached |
| Follow-up | Floor sign reordered | In progress |
Restricted to Facilities — 3 people can open this.
Incident reporting
Only the right people
Assign each incident to a department and restrict it to named users, so a sensitive report stays with the people handling it.
- Locked to the department handling it
- Named users only
Register · Sunday kids team
| Person | Detail | Status |
|---|---|---|
| Sarah M. | All items current | Cleared |
| James T. | All items current | Cleared |
| Priya N. | Blue card expires 12 Sep | Expiring |
| Dan W. | First aid expires 30 Sep | Expiring |
| Alex K. | Policy not acknowledged | Blocked |
4 of 6 cleared. 2 expiring within 30 days.
Incident reporting
A record of who looked
Every view of an incident is logged. When someone asks how you protect sensitive information about a child, that is the answer.
- Every view is logged
- Filter and export to CSV
Clearance · Kids' church leader
| Requirement | Detail | Status |
|---|---|---|
| Blue card | Expires 14 Nov 2026 | Current |
| Child-safe policy v4 | Acknowledged 2 Mar | Read |
| Volunteer form | Completed 2 Mar | Done |
| First aid certificate | Expires 19 Sep 2026 | Expiring |
| Leader's review | Not started | Blocked |
Application held — one item outstanding.
How incident reporting works
Record what happened
Who, what, when, where, and the first evidence.
Restrict access
Assign the department and name who may open it.
Document and submit
Notes, witnesses, signatures, attachments, action plans.
Follow up
Checklist items assigned to the people resolving it.
Review and report
Filter, review and export when compliance asks.
See it: The QR poster, an anonymous report arriving, and the access list showing exactly who can open it.
Replaces: A paper form, a photo of a paper form, and an email chain half the leadership team can read.
The rest of it
Risk assessments
Most systems give you a list of what could go wrong. RiskEZI shows what you did about it.
Event planning
Build the runsheet once, attach the risks to it, and reuse it every week.
Volunteer clearance
Blue card current, policies read, form completed, leader signed off — and RiskEZI tells you before any of it expires.
Handle incident reporting with clarity and confidence.
Twenty minutes with someone who knows churches, on your own examples.