To provide step-by-step instructions for completing the Response section of a First Due incident report. The Response section captures essential dispatch information and incident location details, forming the foundation of accurate incident documentation for Fire/EMS departments.
Background Information
The First Due incident report workflow is designed to follow a typical incident response structure. The Response section is the first step in documenting an incident and consists of two main areas: Dispatch information (unit times, incident type, notification details) and Location details (incident address, zone information, population density). This section establishes the basic incident parameters that other report sections will build upon.
The Response section has been streamlined in the current version, with Resources, Personnel, and other sections now appearing as separate tabs in the incident report interface.
If your agency has a CAD system integration configured with First Due, much of the dispatch and location information will automatically populate from your CAD data, reducing manual entry requirements.
Required Permissions
Incident Documentation Access: Permission to view and edit incident reports
Report Writing: Ability to create and modify NFIRS incident reports
Station Assignment: Access to view assigned stations and dispatch information
Video
Step-by-Step Guide
Completing the Dispatch Section
The Dispatch section captures critical timing and classification information. If your agency has CAD integration, most of this information will auto-populate from your CAD system:
Station and Incident Identification
Assigned Station: Verify the first due station for the incident location (auto-populated from CAD or system configuration)
Dispatch and Incident Numbers: Confirm the values determined by your agency and PSAP (typically populated from CAD integration)
Incident Type Classification
Incident Type Dispatched: Select the initial dispatch type (may auto-populate from CAD)
Actual Incident Type: May differ from dispatched type if conditions changed upon arrival (e.g., dispatched as 733, but found 111 upon arrival)
Using the Dispatch Incident Type Helper
If your agency has enabled the Dispatch Incident Type Helper feature, you can use the enhanced search functionality to find the correct incident type with additional detail and descriptions. This tool helps ensure accurate incident classification by providing more comprehensive information about each NFIRS incident type.
For detailed instructions on using this feature, see: [Link to Dispatch Incident Type Helper article]
Timing and Notification Details
PSAP (911 Center) Date and Times: Record when the call was received and dispatched (auto-populated from CAD when available)
Notification Type: Select how the agency was notified about the incident
Assigned Shift: Verify the on-duty shift at the incident date/time (auto-populated when applicable)
Alarm Assignment
Number of Alarms: Select the number of alarms assigned to the incident (when applicable)
Completing the Location Section
The Location section documents where the incident occurred. CAD integration will typically provide address and basic location data:
Address Verification
Location Discrepancy Slider: Toggle if the actual incident location differed from the dispatched location
Incident Address: Verify or update the incident address (usually pre-populated from CAD data)
Location Classification
Location Type: Select the appropriate NFIRS location type
Fire Zone: Confirm the agency fire zone (may auto-populate based on address)
Population Density: Select the appropriate NFIRS Population Density type
Mandatory Field Requirements
Fields marked with an asterisk (*) are mandatory and must be completed before the report can be finalized. Ensure all required fields in both Dispatch and Location sections are populated, even if CAD integration provides most information.
Best Practices
CAD Integration Benefits:
Verify auto-populated CAD data for accuracy before proceeding
Review timing information against your CAD records
Ensure incident numbers match between First Due and your CAD system
Incident Type Selection:
Use the Dispatch Incident Type Helper when available for more accurate classification
Consider both the dispatched and actual incident types carefully
Document rationale for any changes from dispatched to actual incident type
Data Accuracy:
Double-check dispatch times against CAD records
Verify incident addresses match actual response locations
Ensure incident types reflect what was actually found on scene
Dispatch vs. Actual Incident Types:
Use dispatched type for initial call classification (often from CAD)
Update actual type if conditions differ from initial dispatch
Document significant discrepancies in narrative sections
Location Details:
Confirm fire zone assignments for accurate response analysis
Select population density based on actual incident area, not just dispatch address
Use location discrepancy slider when response location differs from dispatch address
Time Management:
Complete Response section promptly after incident conclusion
Coordinate with dispatch center for accurate timing information
Verify shift assignments match actual on-duty personnel
Troubleshooting & FAQs
Q: My CAD data isn't appearing in First Due
A: Contact your system administrator to verify CAD integration is properly configured and functioning
Q: I don't see the Dispatch Incident Type Helper
A: This feature may not be enabled for your agency. Contact your system administrator about enabling this enhanced search functionality
Q: The assigned station doesn't match our response
A: Contact your system administrator - station assignments may need updating in the system configuration
Q: I can't find the correct incident type even with the helper
A: Use the closest matching NFIRS incident type available. Document specific details in the narrative sections of other report tabs
Q: Dispatch times don't match our CAD system
A: Verify with your dispatch center and use official CAD times. Contact support if there are systematic timing discrepancies
Q: What if we responded to a different address than dispatched?
A: Use the location discrepancy slider and update the incident address to reflect the actual response location
Q: I don't see Resources or Personnel sections
A: These sections are now separate tabs in the updated interface. Complete the Response section first, then navigate to other tabs
Q: Which incident type should I use if it changed during response?
A: Record the initial dispatch type in "Incident Type Dispatched" and the final determination in "Actual Incident Type"
Purpose Statement This feature enables multiple users to simultaneously work on different aspects of a fire incident report. While one user completes the main fire incident report, other users can access and document apparatus-specific information ...
Video New Features 1. NERIS - Update Stations and Add Attempts to Export List What - Enhanced update functionality for Station records within NERIS integration now ensures all update attempts, whether successful or failed, are consistently recorded ...
Purpose Statement The Incident Wrap-Up section enables emergency services personnel to document comprehensive incident narratives, designate the officer in charge, and finalize incident reports with proper attribution. This feature ensures complete ...
Purpose Statement The Size-up section of the Incident Report captures critical scene details, environmental conditions, and initial assessment information that occurred upon arrival at an incident. This section helps document the conditions first ...
Purpose Statement The Print or Email Fire Incident Reports feature enables users to generate professional PDF versions of fire incident documentation for printing, downloading, or distributing via email. This functionality streamlines the process of ...