Skip to main content

Search

Knowledge Center

Fire Incident Setup (NERIS): Department Fields Management

Purpose Statement 

The Department Fields Management feature allows administrators to configure and maintain response zones for fire incident reporting. This centralized management ensures accurate incident documentation, proper jurisdictional tracking, and compliance with NERIS (National Emergency Response Information System) standards.

Background Information 

Response zones represent geographic or operational areas within a department's jurisdiction. Proper configuration of these fields is essential before beginning incident documentation, as they directly impact reporting accuracy and compliance with NERIS requirements. This feature is typically configured during initial system setup and updated as department boundaries or organizational structures change. Response zones help departments organize incidents by station areas, battalion districts, mutual aid regions, or other operational boundaries relevant to their organizational structure.
 

Required Permissions 

To manage department fields, users must have administrative access to Fire Incident Setup configurations. Based on the First Due permissions structure, the following permission is required:

  • Fire Incident Setup -Allows users to add, edit, delete, and configure items in Fire Incident Setup Section
     

Video 


 

Directions

 
1. From the Incident Documentation module navigate to the Fire Incident Setup and select the Department fields management.
 
 
From the Incident Documentation module navigate to the Fire Incident Setup and select the Department fields management.
 

List of Response Zones 

 
1. From the List of Response Zones you are able to add/remove or edit any existing zones. 
 
 

 
 
 
2. To create a new zone select on the + Add New Response Zone. 
 
 

 
 
 
3. Enter a name for the new zone. 
 
 
Enter a name for the new zone.
 
 
 
4. To remove a zone select on the x next to the zone. 
 
 
To remove a zone select on the x next to the zone.
 
 
 
5. Once you have completed creating / editing Zones or FDID's select Save. 
 
 
Once you have completed creating or editing Zones or FDID's select Save.
 
 

Best Practices 

Do's: 

  • Use clear, descriptive names for response zones that match your department's operational terminology and geographic boundaries
  • Review and update response zones when department boundaries change or operational areas are reorganized
  • Document any changes to response zones in your department's records management system for audit trail purposes
  • Coordinate response zone naming conventions with dispatch and field personnel to ensure consistency across all documentation
  • Maintain response zones that align with your NFIRS reporting requirements and state fire marshal expectations

Don'ts: 

  • Don't delete response zones that are associated with historical incident records, as this may impact data integrity or reporting
  • Don't create duplicate response zones with similar names, as this can cause confusion during incident documentation
  • Don't forget to save changes after editing or adding response zones, as unsaved work will be lost
  • Don't use abbreviations or codes in response zone names that are unclear to all personnel who document incidents

Tips & Recommendations: 

  • Consider organizing response zones by station areas, battalion districts, or mutual aid regions depending on your department's operational structure
  • Periodically audit your response zones to ensure they remain current with any organizational or jurisdictional changes
  • When restructuring response zones, communicate changes to all personnel involved in incident documentation to maintain consistency
  • Use naming conventions that include geographic identifiers or boundaries when helpful for clarity (e.g., "Station 1 Response Area - North District")

Troubleshooting & FAQs 

Q: What happens to existing incident records if I delete a response zone?
A: Deleting a response zone that's associated with historical incidents may cause data integrity issues or reporting gaps. Before deleting a response zone, verify it's not being used in any existing incident records. Consider creating a new response zone structure and updating future incidents rather than deleting zones with historical data.

Q: Can I rename an existing response zone without affecting historical records?
A: Yes, editing the name of a response zone by clicking in the box and modifying the text will update the zone name. However, check with your data manager or NERIS coordinator to understand how this might impact historical reporting or data exports before making significant name changes.

Q: How many response zones can I create?
A: There is no specified limit mentioned for the number of response zones you can create. However, it's recommended to create only the zones necessary for your operational structure to avoid confusion during incident documentation.

Q: Why can't I see the Save button after making changes?
A: Ensure you've scrolled to the bottom of the page or section where the Save button is typically located. Some screen resolutions or browser zoom levels may require scrolling to access the Save button. Always confirm your changes have been saved before navigating away from the page.

Q: What's the difference between response zones and station assignments?
A: Response zones represent geographic or operational areas within your jurisdiction used for incident classification and reporting. Station assignments typically refer to the specific fire station or unit responding to an incident. Response zones provide broader organizational categorization for NERIS compliance and operational planning.

Q: How should I organize response zones for a multi-station department?
A: Consider your department's operational structure and reporting needs. Common approaches include organizing by first-due areas, battalion districts, mutual aid zones, or geographic regions. Coordinate with your command staff and NERIS coordinator to determine the structure that best supports your department's operations and reporting requirements.