New Features

Checklist Schedule Management within Check Builder

• What - Checklist scheduling has been integrated directly into Check Builder, allowing administrators to view scheduling status, manage associated schedules, and identify scheduling issues without leaving the checklist. New scheduling indicators display whether a checklist is actively scheduled, has invalid schedules, or has not yet been scheduled.
• Why - Integrating schedule management into the checklist workflow provides better visibility into checklist readiness, simplifies schedule administration, and reduces the need to navigate between multiple areas of the application.
• How
  • Open a checklist within Check Builder.
  • Select Schedule to open the schedule management panel.
  • Review schedule counts and scheduling status.
  • Add or edit schedules directly from the schedule panel.
  • Changes automatically refresh the schedule summary and status after saving.
• Use Case - An administrator reviewing operational checklists can quickly identify unscheduled or invalid checklists, update recurring schedules from the same screen, and verify scheduling without leaving the checklist.

Configurable Checklist Availability Windows

• What - Scheduled checklists now support configurable availability windows that determine how long a checklist remains available after its scheduled due time. Instead of automatically expiring at midnight, checklist availability can now align with operational shift schedules.
• Why - Organizations operating overnight or extended shifts can keep scheduled checklists available for the duration of a shift, reducing missed inspections, minimizing manual corrections, and better aligning checklist availability with daily operations.
• How
  • Configure or edit a scheduled checklist.
  • Specify the desired availability duration for the schedule.
  • The checklist remains available until the configured availability period expires.
  • Overdue and expiration behavior automatically follows the configured availability window.
• Use Case - A checklist scheduled for a night shift can remain available until the end of the shift, allowing personnel to complete required inspections before the checklist expires.

Checklist Scheduler based on Due Time

Checklist Scheduler based on Available Duration (Start Time)

Required Pouch Completion for Kit Checks

• What - Kit checklists now include a Pouches Required option that requires all inventory and equipment contained within associated pouches to be completed before the checklist can be submitted. If required pouch items remain incomplete, the system automatically directs the user to the first incomplete item.
• Why - Requiring pouch completion helps ensure kit inspections are fully completed before submission, improving inventory accountability and creating a more consistent inspection experience.
• How
  • Create or edit a checklist that applies to a kit.
  • Enable the Pouches Required option.
  • Complete all required pouch inventory and equipment items before submitting the checklist.
  • If required items remain incomplete, the system automatically navigates to the first incomplete item.
• Use Case - Personnel performing a medical kit inspection are guided directly to any incomplete pouch items, ensuring every required pouch has been inspected before the checklist is submitted.

Minimum Kit Group Requirements for Compartments

• What - Compartments can now be configured with required kit groups and minimum quantity requirements. During apparatus inspections, the system automatically evaluates compartment contents, identifies missing or below-minimum kit groups, and records structured deficiencies before checklist submission.
• Why - Standardizing minimum kit requirements improves inspection consistency, increases operational readiness, and provides more reliable deficiency reporting across apparatus inspections.
• How
  • Open the compartment configuration.
  • Configure the required Kit Groups and minimum quantity requirements.
  • Complete apparatus inspections as normal.
  • If required kit groups are missing or below the configured minimum, provide the required deficiency information before submitting the checklist.
• Use Case - During an apparatus inspection, the system automatically identifies when required equipment kits are missing or below the required quantity, allowing inspectors to consistently document deficiencies and maintain accurate readiness records.

Medication Kit Association for Apparatus Compartments

• What - Agencies using the Medications module can now associate existing Medication Kits with apparatus compartments. This association provides greater visibility into where medication kits are assigned throughout the fleet by allowing Medication Kits to be linked directly to compartment records.
• Why - Associating Medication Kits with compartments improves apparatus organization and makes it easier to identify where medication kits are stored without requiring duplicate record management.
• How
  • Open the desired apparatus compartment.
  • Select Med Kit.
  • Search for and select the appropriate Medication Kit.
  • Click Save to associate the Medication Kit with the compartment.
  • Note: This association is informational only. Medication inventory, quantities, and checklist validation are not synchronized between the Assets and Medications modules.
• Use Case - An agency can associate an ALS medication kit with a specific apparatus compartment so personnel can easily identify its assigned location. During apparatus inspections, users can see where the Medication Kit is assigned; however, medication inventory and counts continue to be managed independently within the Medications module.

Enhancements

Configurable Field Update Thresholds

• What - Field Update questions within Checklist Builder now support configurable threshold warnings that help identify unusual numeric values before checklist submission. Administrators can configure percentage- or value-based thresholds for individual Field Update questions, allowing end users to receive warnings when entered values differ significantly from previously recorded values. End users can review and acknowledge these warnings before submitting the checklist while still allowing the submission to proceed.
• Why - Unexpected meter readings and other numeric field updates can lead to inaccurate asset history and preventive maintenance scheduling. Configurable thresholds help improve data accuracy by alerting end users to potential entry errors while maintaining a streamlined checklist workflow.
• How
  • Open a checklist in Checklist Builder.
  • Add or edit a Field Update checklist item.
  • Select Configure Thresholds.
  • Enable threshold warnings for the Field Update.
  • Select either a Percentage Increase or Absolute Delta (Fixed Value Increase) threshold.
  • Enter the maximum allowable threshold value and click Save.
  • During checklist completion, end users receive an inline warning when an entered value exceeds the configured threshold.
  • Before submitting the checklist, end users must acknowledge any warnings before continuing.
  • Note: Threshold warnings notify end users of unusual values but do not prevent checklist submission or modify preventive maintenance calculations.
• Use Case - An agency tracks engine hours using a Field Update question during apparatus checks. If an end user accidentally enters 12,500 engine hours instead of 1,250, the configured threshold immediately flags the value as unusual, allowing the entry to be verified before the checklist is submitted and helping maintain accurate asset records and preventive maintenance schedules.

Expanded Equipment Record Data Fields

• What - Equipment records have been enhanced with additional lifecycle, maintenance, testing, and ownership fields to provide more comprehensive asset management. Existing service date fields have been standardized as Last Service Date and Next Service Date across all equipment types, and new global and equipment-specific fields are now available throughout the application, including equipment records, list views, filters, Equipment Wizard imports, checklist field updates, field management, and system logs.
• Why - These additions provide greater flexibility for tracking equipment maintenance, testing, cleaning, compliance, and lifecycle information while improving reporting consistency and long-term asset management.
• How
  • Open an equipment record and navigate to the Specifications tab.
  • Review or update the newly available fields, including:
    • Global Fields: Purchase Date, Warranty Expiration Date, Calculated Expiration Date, Replacement Date, Surplus Date, Last Test Date, Next Test Date, Last Service Date, and Next Service Date.
    • Electronics/Communications: Last Update Date.
    • PPE: Last Cleaning Date, Next Cleaning Date, and Number of Times Cleaned.
    • SCBA: Last Fitment Testing Date and Next Fitment Testing Date.
  • Configure field labels and permissions through Field Management, if desired.
  • Use the new fields within Equipment Wizard imports, checklist Field Updates, list views, filters, and reports.
  • Review updates through the System Log for audit purposes.
• Use Case - Agencies can now maintain more complete equipment records by tracking lifecycle milestones, maintenance activities, testing schedules, cleaning history, and equipment-specific information, providing greater visibility for compliance reporting and replacement planning.

All Equipment Date Fields

PPE specific date fields

Electronics/Communications specific date field

SCBA specific date fields

Configurable Apparatus Type Field

• What - Apparatus records have been enhanced with a new configurable Apparatus Type dropdown that allows agencies to classify apparatus using their own terminology while preserving the existing NFIRS Apparatus Type field for reporting purposes. The new field appears before the NFIRS field on the apparatus record and supports field management, list views, filters, saved views, and the Import Wizard.
• Why - Many agencies use apparatus classifications that differ from NFIRS standards. This enhancement provides greater flexibility by allowing agencies to maintain their preferred naming conventions without affecting NFIRS reporting or existing system functionality.
• How
  • Open an apparatus record.
  • Select the appropriate value from the Apparatus Type dropdown.
  • Configure the field through Field Management to:
    • Rename the field label.
    • Add or modify dropdown options.
    • Configure edit permissions.
    • Mark the field as required.
  • Use Apparatus Type in apparatus list views, filters, saved views, criteria, and Import Wizard imports.
  • Note: The Apparatus Type field is independent of the existing NFIRS Apparatus Type field and does not impact NFIRS reporting or associated functionality.
• Use Case - An agency can classify apparatus using terminology that reflects its operational standards, such as "Heavy Rescue," "Utility," or "Ambulance - ALS," while continuing to maintain the appropriate NFIRS Apparatus Type for reporting requirements.