Skip to Content
AdminOperational Reports

Operational Reports

Operational Reports are your weekend and event report builder. After each service or event, you build a report that captures what happened, who served, and what needs attention. Reports follow an approval workflow that ensures accountability and creates a permanent record of your ministry’s operations.

🛡️

Admin & Oversight: Both Organization Admins and Oversight leadership can create and view reports. Coordinators and above can approve or reject submitted reports.

What Are Operational Reports?

An Operational Report is a structured summary of a service or event. It captures:

  • Who served and where
  • Checklist completion status
  • Incidents or observations
  • Leadership notes

Reports serve as your ministry’s operational record — the documentation that shows faithful stewardship of your Safety Team’s work.

Accessing Operational Reports

  1. Navigate to Admin in the sidebar.
  2. Click on Reports or Operational Reports.
  3. The list displays all reports for your organization.

Creating a Report

  1. Click New Report (or the + button).
  2. Fill in the report details:
FieldRequiredDescription
TitleYesDescriptive title (e.g., “Sunday March 23 Weekend Report”)
TypeYesCategory of report
Reporting PeriodYesDate range the report covers
SquadYesWhich squad served
LeadYesThe Safety Team Member who led the service
CampusYesWhich campus or location
Linked EventsOptionalThe specific events this report covers
  1. Click Save to create the report in DRAFT status.

Report Workflow

Reports follow a three-stage approval workflow:

StatusMeaningWhat You Can Do
DRAFTWork in progressEdit, delete, or submit
SUBMITTEDSent for approvalView only — locked for editing
APPROVEDAccepted by leadershipArchived with encrypted PDF

The Workflow in Detail

DRAFT — You build and refine the report. Add details, link events, write your notes. Only DRAFT reports can be edited or deleted.

SUBMITTED — When you submit a report, the platform captures a snapshot of live event data at that moment. This includes:

  • Current assignments (who served where)
  • Checklist completion status
  • Any linked event data

Once submitted, the report is locked. No further edits are possible in this state.

APPROVED — A Coordinator or above reviews the submitted report and either approves or requests changes:

  • Approve — The report is finalized and an encrypted PDF archive is generated for permanent record-keeping.
  • Request Changes — The report returns to DRAFT status with coordinator notes explaining what needs to be revised. You can then edit and resubmit.

Once submitted, a report locks. You cannot edit a submitted report. If changes are needed, a Coordinator must use “Request Changes” to return the report to DRAFT status. This is by design — it ensures the integrity of the submitted snapshot.

Best Practices

  • Submit Promptly — Build and submit reports within 24 hours of the event while details are fresh.
  • Link All Relevant Events — Connecting the report to specific events ensures the snapshot captures complete data.
  • Be Thorough in DRAFT — Since submissions lock the report, make sure everything is complete before submitting.
  • Use Clear Titles — Include the date and service type for easy identification in the report list.
  • Review Coordinator Notes — When a report is returned to DRAFT, read the coordinator’s notes carefully before revising.

Next Steps

Last updated on

Need More Help?

If you can't find what you're looking for, our mission support team is standing by.

© 2026 N4 Safety. All rights reserved.