Feature Requests

We need professional-looking PDF exports that we can send to our insurance company. The export should include the incident details, all follow-ups, amendments, attachments, and a complete audit trail. Different presets for different audiences would be ideal.

We need a way for congregation members to submit incident reports without needing a Steward account. A public-facing form with CAPTCHA protection would let anyone report safety concerns while preventing spam.

We need different permission levels. Not everyone should see all incidents. Volunteers should only see their own reports, while safety directors need full access. And some incidents are sensitive enough that only select leaders should have visibility.

We need better reporting and analytics. Specifically: incident trends over time, average resolution time, incidents by category/location, and the ability to generate charts for board presentations. The current dashboard shows counts but we need deeper insights.

When our attorney tells us to preserve records related to a potential claim, we need a way to lock those incidents so they can't be modified or deleted, even by administrators. This is a legal compliance requirement for us.

I want more granular control over which email notifications I receive. Right now it's all or nothing. I'd like to choose: notify me for urgent incidents only, or only when I'm assigned, or only for status changes on my reports.

Email notifications are fine but sometimes I miss urgent incidents because I don't check email frequently. Push notifications on my phone would help me respond faster to urgent situations, especially on Sundays when I'm already at the building.

Our church serves a diverse community with members who speak Spanish and Korean. Being able to switch the interface language would make it much more accessible for our bilingual volunteers who file reports.

The current file upload works but it's clunky — you have to click the button and browse. Drag-and-drop from the desktop would be much faster, especially when attaching photos from an incident scene.

Our church uses Planning Center for volunteer management. It would be amazing if Steward could pull in volunteer info so we don't have to manually enter names and roles when filing incidents. Even a basic directory sync would be helpful.

The current PDF export presets are good but we'd like to customize what sections appear and in what order. Our insurance company has specific formatting requirements that don't quite match the built-in presets.

Our team communicates via Slack. Having incident notifications posted to a dedicated Slack channel would improve our response time significantly.

It would be great to have a dark mode option for the app. Many of us work late at night after services and the bright white screen is hard on the eyes. A system-level toggle in profile settings would be ideal.

For security-sensitive incident data, we'd like the option to require 2FA for all users, or at least for administrators and privileged reviewers. This would add an important layer of protection for our sensitive records.

Power users would benefit from keyboard shortcuts for frequent actions like creating a new incident, navigating between sections, and submitting forms. A cheat sheet accessible via a shortcut key would be great too.

We can view the audit trail in the app but can't export it separately. For our annual insurance review, we need to provide audit logs as standalone documents. An export option for the audit trail would be very helpful.

Currently we can only export one incident at a time as a PDF. When we need to send a batch to our insurance company, it takes forever. Would love to select multiple incidents and export them all in one go — either as separate PDFs in a zip or as one combined document.

I'd love to receive a weekly or monthly summary email with incident statistics — number of new incidents, resolution times, trends, etc. This would save me from having to log in just to check if everything is on track.

We want low/medium/high/critical priority levels instead of just an urgent flag. This would help us triage more effectively when multiple incidents come in at once.

We'd like the ability to create our own custom incident categories beyond the default ones. Our church has specific ministry areas that don't fit neatly into the existing categories. Being able to add, rename, and organize categories would help us track things better.

A calendar view showing when incidents occurred would help us spot patterns like recurring issues on specific days of the week or during particular events.

Sometimes we make typos or realize we forgot important details after submitting. It would be helpful to edit the original incident report even after submission.

Some types of incidents happen regularly (e.g., monthly fire drill reports, quarterly safety inspections). It would save time to have templates that pre-fill common fields so we don't have to re-enter the same information every time.

A dark theme would reduce eye strain when working in low-light environments. Toggle in user settings.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

This is an automated feature request from Playwright E2E tests. It verifies the submit modal works correctly.

Build custom reports with flexible date ranges, saved report templates, and exportable charts for board presentations, insurance reviews, and compliance audits.

When uploading photos of incidents, it would be helpful to annotate them — circle areas of concern, add arrows, add text labels. This would make photo evidence much more useful.

Please add a dark mode option. The white background is too bright for evening use.

We'd like the ability to permanently delete incidents from the system, especially old ones that are no longer relevant. This would help keep our records clean.

Track team certifications, background checks, and clearance expirations. Assign requirements with links to external training, set expiration reminders, and maintain a clear record of who is current.

Track maintenance requests, schedule inspections, manage facility assets, and keep your campus running smoothly.

Enable real-time incident notifications to be sent directly to Slack channels or Microsoft Teams, allowing safety teams to respond faster without needing to check the Steward dashboard constantly.

Automatically sync member and volunteer data from popular church management systems like Planning Center and Breeze to streamline incident reporting and reduce duplicate data entry.

tadahfgafdadsfaafafafa

Beyond categories, it would be helpful to tag incidents with custom labels like "children's ministry", "parking lot", "Sunday service", etc. This would make filtering and searching much more powerful.

Allow people to vote on feature requests without being logged in. This would lower the barrier to participation and get more community input.

Plan mission trips, manage fundraising campaigns, track donor contributions, coordinate team logistics, and keep your congregation connected to your outreach efforts.

Complete incident & safety reporting system with role-based access, immutable records, legal exports, public intake forms, audit trails, and team workflows.

A native mobile application for iOS and Android that enables staff and volunteers to quickly report incidents from anywhere on campus, with offline support and camera integration for attaching photos.

A centralized activity feed that shows all recent actions across the organization with powerful filtering by incident type, user, date range, and action type for quick oversight.

Import historical incident records from CSV or Excel spreadsheets to migrate existing data into Steward, with field mapping, validation, and duplicate detection during the import process.

Add internationalization support so that the Steward interface and incident forms can be used in multiple languages, making it accessible to diverse congregations and multilingual staff.

Plan events, coordinate volunteer schedules, manage background checks, and streamline communication across your teams.