Create the event
Date, place, branch, departments and the organiser team.
Event planning
Not an events calendar. The plan, and the proof it was followed.
Build the runsheet once, attach the risks to it, and reuse it every week.
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 event planning
Plan once
Templates and repeat rules generate the whole term.
Risks load in
Assessments for the location come with the event.
Tasks with owners
Turn a control into an action someone is responsible for.
Everyone informed
Comments, documents and email updates as plans change.
Approved before it runs
Submit for review and record the approval.
A record afterwards
Every change, comment and incident against the event.
Event planning
Templates that generate a term
Set up the Sunday service or the Friday youth night once, with its repeat pattern. The term builds itself.
- Repeat rules and school-holiday exclusions
- The term generates itself
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.
Event planning
The controls travel with the event
Each section of the runsheet carries its own risk assessment, and tasks go to named members of the organiser team. Whoever runs it sees what they're responsible for.
- Assessments load from the location
- Tasks go to named organisers
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.
Event planning
Closed loop
If an incident happens, it's recorded against the event it happened at. Next year's plan starts with what actually went wrong at this one.
- Incidents attach to the event
- Approval and comments kept together
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 event planning works
Load the risks
Assessments for that location, plus any the event adds.
Assign tasks
Controls become actions with an owner and a due date.
Approve it
An event manager reviews and records the approval.
Review and improve
Link any incidents back, and start next year from there.
See it: A Sunday service template generating the term, one section carrying its risk assessment, and an incident attached to last month.
Replaces: The runsheet in a spreadsheet, the risk assessment in a document, and no link between them.
The rest of it
Risk assessments
Most systems give you a list of what could go wrong. RiskEZI shows what you did about it.
Incident reporting
Anyone can file a report in a minute. Only the people you name can open it.
Volunteer clearance
Blue card current, policies read, form completed, leader signed off — and RiskEZI tells you before any of it expires.
Handle event planning with clarity and confidence.
Twenty minutes with someone who knows churches, on your own examples.