Saved Views allow users to create and apply pre-configured filter sets to the Fire Incident List, enabling quick access to commonly used search criteria without manually recreating filters each time. This feature streamlines incident documentation review, reporting workflows, and data analysis by providing one-click access to customized incident lists.
Background Information
When working with the Fire Incident List in the Incident Documentation module, users often need to filter incidents by specific criteria such as date ranges, incident types, apparatus, personnel, or station assignments. Rather than manually configuring these filters repeatedly, Saved Views allow users to create, save, and share filter configurations across the entire department.
Key Benefits:
Time Efficiency: Apply complex filter combinations with a single click
Consistency: Ensure all users can access standardized views for reporting and analysis
Departmental Collaboration: Share useful filter configurations with all authorized users
Workflow Optimization: Create views for daily routines, compliance reviews, or specific reporting needs
Common Use Cases:
Daily incident review by shift or battalion
Monthly NERIS reporting preparation
Specific incident type analysis (structure fires, EMS assists, etc.)
Apparatus-specific incident history
Training incident reviews
Quality assurance workflows
Required Permissions
Users must have specific permissions enabled by their agency administrator to interact with Saved Views. The following permissions control access levels:
Incident Report Saved View Permissions:
Create Permission: Allows users to create new Saved Views and displays the save button. New views are immediately available department-wide.
Read Permission: Allows users to view and apply any Saved Views created by others, but not modify or delete them.
Update Permission: Allows users to edit existing Saved Views, including modifying filters or renaming views.
Delete Permission: Allows users to remove Saved Views from the system.
Warning: Saved Views are system-wide for the entire department, not personal to individual users. Any Saved View created or modified will affect all users with Read permission.
Video
Step-by-Step Guide
Accessing the Fire Incident List and Saved Views
Navigate to Incident Documentation > Fire Incident List from the main menu.
On the Fire Incident List page, you will see existing Saved Views displayed at the top of the list (if any have been created and you have Read permission).
If you have Create permission, you will also see a Save button (represented by a save icon) available in the interface.
Applying an Existing Saved View
To apply a pre-configured Saved View, simply select the desired view name from the Saved Views section.
The Fire Incident List will automatically update to display only incidents matching the saved filter criteria.
Even after applying a Saved View, you can still adjust filters manually:
Remove individual filter criteria by clicking the X button next to a specific criterion
Clear all filters by selecting the Reset button
Creating a New Saved View
Configure the filters you want to save by selecting your desired criteria from the Filters section (date range, incident type, station, apparatus, personnel, etc.).
Select the Down arrow to view all Filters.
Once you have set all desired filters, select the Save button.
A pop-up window will appear with two options:
Override Current: Select this to replace the currently applied Saved View with your new filter configuration
Save New: Select this to create a brand new Saved View without affecting existing views
Type in a descriptive name for your Saved View (e.g., "Last 30 Days - Structure Fires" or "Battalion 1 - Current Month").
Select Save to confirm.
Your new Saved View will immediately appear in the Saved Views section and will be available to all users with Read permission.
Updating an Existing Saved View
Apply the Saved View you wish to update.
Modify the filter criteria as needed.
Select the Save button and choose Override Current to update the existing view with your new configuration.
Deleting a Saved View
If you have Delete permission, you can remove unwanted Saved Views by selecting the delete option associated with the view.
Best Practices
Do:
Use clear, descriptive names for Saved Views that indicate the filter criteria (e.g., "Last Month - All Incidents" rather than "View 1")
Create Saved Views for frequently used filter combinations to save time
Coordinate with your department on naming conventions for consistency
Review and clean up unused Saved Views periodically to avoid clutter
Test a Saved View after creating it to ensure it displays the expected results
Consider creating views for common reporting periods (monthly, quarterly, annual)
Don't:
Create duplicate Saved Views with similar filter criteria
Use vague or cryptic names that other users won't understand
Override existing Saved Views without communicating with your team if others rely on them
Forget that Saved Views are department-wide—your changes affect all users
Tips:
Create specialized views for different workflows (daily operations, monthly reporting, training review)
Use date-relative filters when possible so views remain relevant over time
Document your department's Saved Views and their intended purposes
Assign responsibility for maintaining Saved Views to specific roles (e.g., data managers, supervisors)
Troubleshooting & FAQs
Q: I don't see the Save button. Why not? A: You need the "Create" permission for Incident Report Saved Views. Contact your agency administrator to request this permission.
Q: Can I create a personal Saved View that only I can see? A: No, all Saved Views are department-wide and visible to any user with Read permission. This ensures consistency in reporting and data analysis across the department.
Q: I accidentally deleted a Saved View. Can I recover it? A: Deleted Saved Views cannot be recovered. You will need to recreate the view with the same filter configuration. Consider limiting Delete permissions to administrators only.
Q: How many Saved Views can we create? A: While there is no hard limit, it's best practice to keep the number of Saved Views manageable (typically 10-15) to avoid overwhelming users with too many options.
Q: Can I modify a Saved View created by another user? A: Yes, if you have Update permission. Remember that any changes you make will affect all users who use that Saved View.
Q: The Saved View isn't showing the incidents I expected. What's wrong? A: First, verify the filter criteria in the Saved View match your expectations. The view may have been modified by another user with Update permission. You can adjust the filters manually or create a new Saved View with the correct configuration.
Q: Can Saved Views include custom field filters? A: Yes, any filter available in the Fire Incident List can be included in a Saved View, including custom fields configured by your agency.
Purpose Statement Filters allow you to temporarily modify the data displayed in your Ad-Hoc Reports without permanently adjusting your report criteria. This feature enables dynamic data exploration and customized views of your report information, ...
Purpose Statement Personnel custom list views allow administrators and supervisors to create tailored views of personnel data that meet specific organizational needs. This feature enables users to customize which personnel information is displayed, ...
Purpose Statement Narrative templates in First Due streamline fire incident documentation by providing pre-formatted text blocks that crews can quickly insert into incident reports. This feature reduces documentation time, ensures consistent report ...
Purpose Statement This article provides answers to commonly asked questions about fire incident documentation in First Due. Whether you're navigating setup configurations, managing documentation requirements, or troubleshooting submission issues, ...
Purpose Statement The purpose of this article is to explain how to view, link, or unlink EMS records using the Associated Records section within a Fire Incident Report. This feature enables seamless integration between Fire and EMS documentation, ...