Tactic Timestamps Capture for NERIS Incident Reporting (New Feature)

What – A new Tactic Timestamps section has been added to the incident report and Setup for agencies reporting to NERIS. This section provides nine dedicated timestamp fields that capture key tactical milestones directly on the incident report.

Why – Accurate tactic timing data is critical for NERIS reporting, and relying on inferred or background data can introduce errors. This feature ensures that timestamp values submitted to NERIS reflect actual, user-entered entries from the incident report.

How
- This feature is available exclusively for NERIS clients and must be enabled through Setup before it appears on incident reports
- Navigate to Setup > Operations > Module Interoperability
- Locate the Tactic Timestamps setting and enable it for your agency
- Once enabled, the Tactic Timestamps section will appear within the Operations section of the incident report
- Enter timestamps for any applicable tactic fields: Command Established, Completed Sizeup, Suppression Complete, Primary Search Begin, Primary Search Complete, Water on Fire, Fire Under Control, Fire Knocked Down, and Extrication Complete
- These fields are also available in Field Management (including a Read Only option) and Workflows
- Only values entered in this section will be transmitted to NERIS — no inferred or background timestamp data will be used

Use Case
- A fire agency submitting NERIS reports can now record the exact time primary search began and completed, ensuring their submitted data reflects true on-scene activity.
- An administrator can configure which tactic timestamp fields are visible or editable on the incident report using Field Management controls.
- A supervisor reviewing completed incidents can use Workflows to incorporate tactic timestamp data into automated processes or quality review steps.
 

Field Customization Inheritance from Parent Agencies (New Feature)

• What - Agencies can now inherit field customizations and Plus One codes (for NERIS clients) from their parent agency, following the same inheritance model already in place for workflows. These inherited settings are visible in a read-only list under NERIS Settings → Parent Settings.

• Why - Managing field customizations across multiple agencies can be time-consuming and inconsistent. This change allows child agencies to automatically reflect their parent agency's configurations, reducing manual setup and improving standardization across agency hierarchies.

• How

  • Navigate to NERIS Settings in the application
  • Select Parent Settings
  • Under the parent workflows section, locate the Parent Custom Field Customizations and Plus One Codes list
  • This list is read-only and reflects the configurations inherited from the parent agency
  • No edits can be made to inherited settings at the child agency level; changes must be made at the parent agency level

• Use Case

  • A child agency onboarding to the system automatically reflects the field customizations already configured at the parent agency level, reducing duplicate setup work.
  • A NERIS client agency inherits Plus One codes from their parent, ensuring consistent data entry options across all connected agencies.

  • An administrator reviewing a child agency's settings can quickly confirm which field customizations are inherited versus locally configured.

     

CAD Priority Field Added to NERIS Incident Reporting (Feature Enhancement)

What – The CAD Priority field has been added to NERIS incident reports, positioned in the same location it occupies within NFIRS reporting.

Why – As agencies transition from NFIRS to NERIS, maintaining a consistent field layout reduces confusion and helps ensure data entry workflows remain familiar and efficient.

How –
- The CAD Priority field is now available within the NERIS incident report structure
- Navigate to a NERIS incident report
- Locate the CAD Priority field in the same relative section where it appears in NFIRS
- Enter or update the CAD Priority value as part of your normal incident reporting workflow
- This change applies to NERIS reporting only — no changes have been made to NFIRS field placement or structure

Use Case –
- An agency transitioning from NFIRS to NERIS can locate and complete the CAD Priority field without relearning report layouts.
- A dispatcher completing a NERIS incident report can enter CAD Priority in the expected location, reducing data entry errors.
- A system administrator reviewing incident records across both standards can expect consistent field placement, supporting smoother audits and reporting.