Documenting No Response Calls

Documenting No Response Calls

Purpose Statement

This article explains how to configure and document "No Response" calls using custom Plus One Codes within the Fire Incident Report. This feature allows agencies to maintain internal records of non-response situations and meet documentation standards, even when NFIRS does not require an incident to be recorded.


Background Information

Some agencies prefer to document all calls, including those where no response occurred. While NFIRS does not require incident records for canceled calls prior to response, agencies may still choose to track these for internal audits, analysis, or historical accuracy.

NFIRS Guidance:

  • If an incident is canceled before units respond, there is no NFIRS incident to report
  • If units respond but are canceled en route, code as 611 – Dispatched & Canceled En-Route

Important for Validation: NFIRS validation rules currently require at least one person assigned to an apparatus. Agencies must have a fictional user (e.g., Test User or No Response Personnel) to meet this requirement. Under NERIS validation, a user will no longer be required.


Required Permissions

Users need administrative access to the Incident Documentation module to configure Plus One Codes. Specific permissions include access to:

  • Fire Incident Setup
  • Custom Field Management
  • Department Fields Management

Contact your system administrator if you cannot access these features.


Video



Step-by-Step Guide

Part 1: Fire Incident Setup – Creating Plus One Codes

Step 1: Navigate to Fire Incident Setup

  1. Go to Incident Documentation > Fire Incident Setup > Field Management




Step 2: Open Custom Field Management

  1. Select Custom Field Management
  2. Target the following fields:
    • Basic Module / Section C / Actual Incident Type Found
    • Basic Module / Section F / Actions Taken
  3. If these fields already have custom settings, use the pencil icon to edit them





Step 3: Configure "Incident Type Found" Field

  1. Use the dropdown to find
    Basic Module / Section C / Actual Incident Type Found


  2. Navigate to the Values tab
  3. Click
    Add Custom Option
    From the Values tab select Add Custom Option.



Step 4: Create Your Plus One Code for Incident Type

  1. Enter your custom Plus One Code and Description
  2. Click Create
    Now type in the new Plus One Code along with a Description to be displayed then select Create.




  3. From the Actions column:
    • Check the box to activate the code
    • Use the Incident Type Helper icon to define:
      • NFIRS or local definitions
      • Keywords or usage notes


Selecting on the Incident Type Helper icon you are able to add information such as NFIRS or Local Definitions and any Keywords.




Step 5: Configure "Actions Taken" Field

  1. Use the dropdown to find Basic Module / Section F / Actions Taken



  2. Navigate to the Values tab
  3. Click Add Custom Option
    Click on Add Custom Option



Step 6: Create Your Plus One Code for Actions Taken

  1. Enter your custom Plus One Code and Description
  2. Click Create/Update






Part 2: Documenting No Response Calls in a Report

Step 1: Select the Incident Type Found

  1. In the Response > Dispatch tab, locate the Incident Type Found field
  2. Begin typing your custom code or scroll to locate it
  3. Select the appropriate Plus One Code



Step 2: Select the Actions Taken

  1. In the Operations section, under Overall Departmental Actions Taken, use the multi-select dropdown
  2. Find and select your custom code
  3. Click outside the dropdown to apply selections



Step 3: Set Apparatus Status

  1. In Apparatus Details, use the Unit Canceled toggle
  2. Choose either:
    • Prior to Dispatch Acknowledgment
    • Prior to En Route
  3. If using CAD, times will auto-populate except for the Cancelled time





Best Practices

  • Label Clearly: Use descriptive Plus One Code names (e.g., "No Response - Call Logged Only") to avoid confusion
  • Maintain Consistency: Use identical descriptions across both Incident Type and Actions Taken fields
  • Create Fictional User: Establish a placeholder user (e.g., "Test User") to satisfy current validation requirements
  • Regular Audits: Review reports quarterly to ensure Plus One Codes are applied correctly and consistently
  • Documentation Standards: Maintain clear internal guidelines on when to use No Response codes versus standard NFIRS codes

Troubleshooting & FAQs

Q: Why doesn't my new code appear in the dropdown? A: Check if the field already has custom settings configured. If so, use the pencil icon in Custom Field Management to update the existing configuration rather than creating a new one.

Q: Can I skip assigning personnel if no one responded? A: Not under current NFIRS validation rules. A user must be attached to satisfy validation requirements. Use a fictional or placeholder user until NERIS validation is implemented, which will remove this requirement.

Q: Are these codes visible in NFIRS exports? A: Custom Plus One Codes may not be recognized in standard NFIRS exports. They are primarily designed for internal documentation and tracking purposes.

Q: What happens if I accidentally use a No Response code on an actual incident? A: Review and correct the incident report immediately. Plus One Codes should only be used for genuine non-response situations to maintain data integrity.


    • Related Articles

    • Fire Incident Setup - Size up and Operations

      Purpose Statement The Fire Incident Documentation Settings feature enables administrators to customize data collection fields and requirements for fire incident reports within First Due. This configuration ensures your department captures all ...
    • Fire Incident Setup (NFIRS): Department Fields Management

      Purpose Statement The Department Fields Management feature allows administrators to configure and maintain critical identifying information for fire incident reporting, including Federal Department ID (FDID) numbers and response zones. This ...
    • Fire Incident Setup - Narrative Template

      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 ...
    • Configuring Incident Number Format

      Purpose Statement The Incident Number Formatting feature allows fire and EMS departments to establish a standardized, consistent numbering system for all incidents. This automated configuration ensures that every incident receives a unique identifier ...
    • Fire Incident Setup - Custom Questions

      Purpose To explain how to create and manage a custom NFIRS report field. Video Directions 1. Navigate to Incident Documentation-> Fire Incident Setup -> Field Management. 2. Select on the New Custom Field. 3. Assign the custom field a label. This is ...