Skip to main content

Search

Knowledge Center

Completing an Incident Report (NERIS) - Wrap Up

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 incident documentation that meets NERIS reporting standards while maintaining clear accountability for report completion and incident command responsibilities.

Background Information

The Wrap-Up section represents the final phase of incident documentation, where personnel document detailed narratives describing the incident, actions taken, and outcomes. This section is critical for creating comprehensive incident records that support after-action reviews, regulatory compliance, legal documentation, and quality improvement initiatives.

Proper narrative documentation provides context that raw data fields cannot capture, including decision-making rationale, unusual circumstances, collaborative efforts with other agencies, and lessons learned. The system's auto-save functionality protects against data loss during report completion, while the officer designation fields ensure proper accountability and chain of command documentation.

Required Permissions 

To complete the Incident Wrap-Up section, users need:

  • Incidents - View fire incident reports
  • Update Incident Reporting - Edit existing incident reports
  • Create Incident Report - Create new fire incident reports
  • Complete - Mark incidents as complete
  • Authorize - Authorize completed incident reports

Video 


 

Step-by-Step Guide

 

Accessing the Wrap-Up Section

  1. Navigate to Incident Documentation > Fire Incident List from the main navigation menu
     
 

 
  1. Locate and open the incident requiring wrap-up documentation
     

 
  1. Ensure the Information section is fully completed before proceeding
  2. Select the Wrap-up section from the incident menu on the left side of the screen
     

 

 

Entering Incident Narratives

  1. Click Use Template to utilize a department template
     

 
  1. Click the Expand Icon to see what the narrative template will put into the narrative field
     

 
  1. You can also type a Narrative without using a template. Click into the narrative text box to begin documentation
     
 
  1. Begin typing your incident narrative - the system will automatically save your work as you type
  2. Document comprehensive incident details including:
    • Initial conditions and situation found upon arrival
    • Actions taken by each unit/crew
    • Patient care provided (for EMS incidents)
    • Fire suppression or mitigation tactics employed
    • Hazards encountered and safety measures implemented
    • Collaboration with other agencies or resources
    • Incident outcomes and final disposition
    • Any unusual circumstances or deviations from standard procedures
       
  3. Review Apparatus Narratives, and go to them if necessary, by clicking Apparatus Narrative.
     
 
  1. You can also document Incident Impediments. 
     
    1. Incident Impediment - refers to factors that hinder or obstruct the effective investigation, reporting, or response to incidents.
       
You can document any Incident Impediments utilizing the same features as the Department narrative.
 
 
ℹ️

Info:

The auto-save feature activates as you type, eliminating the need to manually save your progress. However, maintain an active internet connection to ensure auto-save functions properly.

 

Designating the Officer in Charge

  1. Click Edit next to Officer in Charge
     

 
  1. Select the appropriate officer from the dropdown list to populate their information automatically
     

 
  1. Verify the Member Completing Report field - this will auto-populate with the profile information of the currently signed-in user
  2. Confirm all information is accurate before proceeding to submit or finalize the incident report
     

Best Practices

Narrative Documentation Best Practices:

  • Write narratives in clear, professional language using past tense
  • Include specific times for key incident milestones (arrival, patient contact, departure)
  • Document objective observations rather than assumptions or opinions
  • Use standard fire/EMS terminology and abbreviations consistently
  • Include relevant unit numbers, personnel names, and apparatus identifiers
  • Document any deviations from standard operating procedures and rationale
  • Address all aspects of the incident chronologically for clarity

Officer Designation Best Practices:

  • Designate the Officer in Charge immediately upon completing narratives
  • Verify the correct officer is selected - this determines official incident command documentation
  • Ensure the Officer in Charge reviews and approves the incident narrative
  • For incidents with command transfers, document all commanding officers in the narrative
  • Coordinate with the designated officer before finalizing the report

System Usage Best Practices:

  • Configure narrative settings before agency-wide implementation (reference NERIS Setup - Wrap-up)
  • Complete narratives as soon as practical after incident conclusion while details are fresh
  • Maintain active internet connectivity to leverage auto-save functionality
  • Review auto-populated Member Completing Report information for accuracy
  • Use consistent narrative structure across all incidents for easier review and analysis

Common Mistakes to Avoid:

  • Do not leave narrative sections blank - minimal documentation is better than none
  • Avoid using jargon or abbreviations that external reviewers may not understand
  • Do not rely solely on auto-save - verify your narrative saves before closing the browser
  • Do not designate an incorrect Officer in Charge - this affects official incident records
  • Avoid completing wrap-up before finishing the Information section
  • Do not include protected health information (PHI) beyond what is necessary for incident documentation

Troubleshooting & FAQs

Q: My narrative text isn't saving automatically. What should I check?

A: Verify your internet connection is active and stable. Auto-save requires continuous connectivity. If connection is confirmed, try refreshing the page (your work should be saved to the last auto-save point). Clear your browser cache if the issue persists, or contact your system administrator to verify narrative settings are properly configured.

Q: The Officer in Charge dropdown is empty or missing personnel. How do I fix this?

A: This typically indicates the desired officer doesn't have an active user profile in First Due, or they lack the proper permissions/rank designation. Contact your system administrator to verify the officer's profile exists, is active, and has the appropriate rank/role assigned. The dropdown only displays personnel meeting officer-level criteria as configured in your agency settings.

Q: Can I edit the "Member Completing Report" field if it auto-populated incorrectly?

A: The Member Completing Report field is typically locked and auto-populates based on the logged-in user's profile to maintain accountability. If it displays incorrectly, this usually indicates a profile issue or someone else is logged into the system. Log out and log back in with the correct credentials. If the problem persists, contact your system administrator to verify your user profile is correctly configured.

Q: What should I do if I need to complete wrap-up for an incident someone else started?

A: You can complete the wrap-up section even if another user created the initial incident report. Your profile will appear as the Member Completing Report. In the narrative, clearly document your role and explain why you're completing the report (e.g., "Report completed by FF Smith based on information provided by IC Johnson"). Ensure the correct Officer in Charge is designated regardless of who completes the documentation.

Q: The system isn't allowing me to access the Wrap-Up section. What's wrong?

A: First, verify the incident Information section is fully completed - the system requires this before allowing wrap-up access. If Information is complete, check your user permissions with your administrator. You may lack incident documentation editing rights or specific wrap-up access. Additionally, some agencies configure workflow requirements that must be met before wrap-up becomes available.

Q: How detailed should incident narratives be?

A: Narratives should be comprehensive enough that someone unfamiliar with the incident can understand what occurred, what actions were taken, and why. Include all relevant details about conditions, actions, decisions, and outcomes. Generally, 2-4 paragraphs for routine incidents and more extensive documentation for complex, unusual, or significant incidents. Follow your agency's narrative policies and NERIS requirements.

Q: Can I see previous narratives from the same incident as a reference?

A: Yes, if multiple units responded and completed separate narratives, you can typically view other narratives within the same incident report. This helps ensure consistency and comprehensive documentation across all responding units. Check with your administrator about your agency's specific workflow for multi-unit incident documentation.

Q: What happens if I lose internet connection while typing a narrative?

A: Auto-save functions only work with active internet connectivity. If connection is lost, your most recent auto-saved content should be preserved, but anything typed after the connection dropped may be lost. When connection is restored, refresh the page to see the last saved version. As a best practice, consider drafting complex narratives in a text document first, then copying them into the system when ready.

Before implementing incident documentation across your agency, ensure proper narrative settings are configured by reviewing the NERIS Setup - Wrap-up article. This configuration determines narrative field requirements, templates, and agency-specific documentation standards that affect how the Wrap-Up section functions for all users.