Purpose Statement
The Response Section in a NERIS report is used to document key dispatch and location details related to an incident response.
This section helps agencies capture accurate incident classification, dispatch information, location use, occupancy details, response zones, and related reporting data. Completing the Response Section supports accurate documentation and helps ensure the incident report contains the information needed for agency, state, and federal reporting.
Background Information
The Response Section contains two primary areas:
- Dispatch
- Location
If the agency uses CAD integration, some fields may auto-populate in the report, including dispatch numbers, dispatch times, and dispatch incident type. Users should review all auto-populated information for accuracy before completing the report.
Required Permissions
Permissions may vary by agency configuration. Users typically need permission to:
- View NERIS reports
- Create or edit NERIS reports
- Update response, dispatch, and location details within a NERIS report
Confirm the exact permission names in Admin > Users & Roles or with your agency administrator before assigning access.
Video
Step-by-Step Guide
1. Open the Response Section
- Navigate to the appropriate incident report.
- Open the report.
- Select the Response section.
- Review the two available subsections:
- Dispatch
- Location
2. Complete the Dispatch Section
Use the Dispatch section to review and complete the incident classification and dispatch-related fields.
- Review the Incident Number and Dispatch Number fields.
- If your agency uses CAD integration, confirm that the following information populated correctly:
- Incident number
- Dispatch number
- Dispatch times
- Dispatch incident type
- Locate the Primary Incident Type field.
Select the appropriate primary incident type.
This field is required.
- Search for the incident type by using one of the following options:
- Scroll through the available list
- Type into the search field
- Select the pop-out icon to view the list on the side
- Add a Secondary Incident Type, if applicable.
Add a Tertiary Incident Type, if applicable.
Only one incident type is required, but up to three incident types may be documented.
Select any applicable Special Incident Modifiers.
This field supports multiple selections and may be used for federal, state, county, or local disaster or relief-related classifications.
- Complete or review the remaining Dispatch fields, as applicable:
- Fire conditions on dispatch
- Notification types
- Stations
- Shifts
- Alarms
3. Complete the Location Section
Use the Location section to document where the incident occurred, how the location was being used, and whether people were present or displaced.
- Select the Location subsection or scroll down to the Location area.
- Use the same dispatch location toggle to indicate whether the incident location is the same as the dispatched location.
- If the toggle is turned on, the location fields are locked and cannot be edited.
- If the toggle is turned off, update the location fields manually as needed.
- Select the appropriate Location Use.
- Select any applicable specific use details.
- Complete the Primary Nature of Fire Incident field, if applicable.
- Indicate whether people were present by selecting Yes or No.
- Enter the total number of people displaced, if applicable.
- Select all applicable Cause for Displacement options.
This field supports multiple selections.
- Indicate whether the location was in use.
- If the location was not in use, select the appropriate reason from the dropdown.
- Indicate whether the location was used as intended.
- Select the appropriate Response Zone, if response zones are configured for your agency.
- Select the applicable Population Density.
4. Review the Response Section
- Confirm that all required fields are complete.
- Review any CAD-populated information for accuracy.
- Confirm that the Dispatch and Location details accurately reflect the incident response.
- Continue to the next section of the incident report.
Best Practices
- Review CAD-populated fields before completing or submitting the report.
- Complete the required primary incident type before adding secondary or tertiary incident types.
- Use secondary and tertiary incident types only when they add meaningful detail to the incident record.
- Select all applicable special incident modifiers when documenting disaster or relief-related incidents.
- Confirm whether the dispatched location and actual incident location are the same before completing the Location section.
- Turn off the same dispatch location toggle before editing location fields.
- Avoid leaving required fields incomplete, especially fields marked with a red asterisk.
- Verify displacement details when people were displaced as a result of the incident.
- Use response zones consistently if your agency has them configured.
Troubleshooting & FAQs
Why are some location fields locked?
The location fields are locked when the same dispatch location toggle is turned on. This indicates that the incident location is the same as the dispatched location. Turn the toggle off to manually update the location fields.
Why did the Secondary Incident Type field appear?
The Secondary Incident Type field appears after a Primary Incident Type is selected. This allows users to document an additional incident classification when needed.
Is more than one incident type required?
No. Only the Primary Incident Type is required. Users may add secondary and tertiary incident types when the incident involved additional classifications.
Why are some fields already filled out?
If your agency uses CAD integration, certain dispatch details may automatically populate into the incident report. Users should still review these fields for accuracy.
What should I use Special Incident Modifiers for?
Special Incident Modifiers can be used to document applicable federal, state, county, or local disaster and relief-related classifications.
Why is the reason the location was not in use grayed out?
If the location is marked as being in use, the field for why it was not in use is disabled because it no longer applies.