Purpose Statement
First Due Reports (FDRs) are a library of pre-built reports available within the Ad-Hoc Reporting module. These reports are created and maintained by the First Due Reporting & Platform Team.
FDRs provide standardized analytics and operational insights for Fire and EMS agencies, including incident response times, ePCR metrics, inspection compliance, personnel administration, apparatus activity, and training records. They allow agencies to access commonly requested reports without building complex report configurations from scratch.
Background Information
First Due Reports are designed to address common Fire and EMS reporting needs that may extend beyond the standard reports available within individual First Due modules.
The FDR library includes more than 213 reports across major operational areas. It contains both:
- Summary Reports, which display grouped or aggregated results.
- Tabular Reports, which display detailed, record-level information.
FDRs are located in the Ad-Hoc Reporting area but are created and maintained by First Due. They cannot be edited directly. However, many FDRs can be cloned and customized as agency-owned Ad-Hoc Reports.
How FDRs Are Identified
Each First Due Report follows this naming convention:
FDR-[PREFIX]: Report Name
The prefix identifies the module or data domain associated with the report.
| Prefix | Module or Data Domain | Example |
|---|---|---|
| NFIRS | NFIRS Incident Reporting | FDR-NFIRS: Incident Count by Month & Year |
| IR | Incident Reports and NERIS | FDR-IR: Structure Fires with Property Loss Greater Than or Equal to $5,000 |
| EPCR | ePCR and EMS Documentation | FDR-EPCR: Total Patients by Patient Disposition |
| TRNG | Training | FDR-TRNG: Training Class Hours by Objective (YTD) |
| INSP | Inspections | FDR-INSP: All Open Violations |
| OCC | Occupancies | FDR-OCC: All Inspectable Occupancies |
| PERM | Permits | FDR-PERM: All Active Permits |
| HYD | Hydrants | FDR-HYD: Completed Hydrant Services by Assigned User YTD |
| AI | Assets, Inventory, and Apparatus | FDR-AI: Apparatus Details |
| PERS | Personnel | FDR-PERS: Active Personnel Roster |
| ADMIN | Administration and User Management | FDR-ADMIN: Last Login by Department Users |
| SCH | Scheduling | FDR-SCH: Today’s Time Off (Detailed) by Type |
| EVENT | Events and Activities | FDR-EVENT: Events Detail |
| INV | Invoices | FDR-INV: Invoice Details – Previous 30 Days |
| MED | Medications | FDR-MED: Medications Nearing Expiration |
| PS | Payroll Summary | FDR-PS: Incidents, Trainings, & Events Attendance Percentage |
For a full list please see First Due Reports Directory.
Automatic Deployment and Locked Folders
FDRs are globally deployed to agency Ad-Hoc Reporting environments. When the First Due Reporting & Platform Team releases a new FDR, it is automatically delivered to the appropriate FDR folder without requiring action from the agency.
FDR folders are locked because their structure must remain consistent across agency environments. This ensures that:
- New FDRs are delivered to the correct location.
- Folder organization remains consistent.
- Agencies do not accidentally interrupt the report deployment process.
- First Due Reports remain easy to identify and locate.
Although FDR folders cannot be renamed, moved, or deleted, agencies can create separate folders for their own reports and cloned FDRs.
Recommended: Create an agency-owned folder named FDR Clones. Save customized copies of First Due Reports in this folder so users can distinguish agency-owned reports from the original First Due versions.
FDRs cannot be removed or hidden. Use search, filters, and browser bookmarks to quickly access frequently used reports.
Some FDRs are built with native Ad-Hoc Reporting functionality and can be cloned. Other FDRs use custom backend development or custom SQL and cannot be cloned or modified.
Required Permissions
Users must have permission to access the Reports Module and view Ad-Hoc Reports.
Users must also have permission to access the data modules and Data Sources used by the selected FDR. For example, a user may need access to ePCR data before they can view an FDR-EPCR report.
Additional permission may be required to clone an FDR and save the copy as an agency-owned Ad-Hoc Report.
If an expected FDR, Data Source, or action is unavailable, contact a system administrator to review the user’s assigned role and permissions.
Video
Step-by-Step Guide
Access a First Due Report
- Navigate to Reports Module → Ad-Hoc Reports.
- Review the Report Folders for reports beginning with the FDR- prefix.
- Locate the appropriate report manually or use the available search and filter options.
- Review the report description to confirm its purpose, included data, default date range, and any identified limitations.
- Select the hyperlinked report name to run the report.
Search for First Due Reports
- Navigate to Reports Module → Ad-Hoc Reports.
- Select the Search field.
- Enter FDR to display First Due Reports.
- To narrow the results, enter a specific report prefix or search term. Examples include:
- FDR-NFIRS for NFIRS reports.
- FDR-EPCR for ePCR and EMS reports.
- FDR-INSP for inspection reports.
- Response Time for reports containing that phrase.
- Use the available filter options to narrow the list by module or report type.
- Select Apply to apply the filters.
- Select Reset to remove the filters and return to the full report list.
Run and Filter a First Due Report
- Locate the desired FDR.
- Select the hyperlinked report name.
- Allow the report to load and display its results.
- Review the applied filters, including the date range, station, shift, apparatus, or other criteria.
- When an editable filter is available, select Edit on the filter box.
- Adjust the filter values as needed.
- Apply the changes and review the updated results.
Many FDRs use default date ranges such as:
- This Year to Date.
- Last Calendar Month.
- Last 30 Days.
Always confirm the active date range before using the report results.
Create an FDR Clones Folder
Before cloning reports, create an agency-owned folder to keep customized FDRs organized.
- Navigate to Reports Module → Ad-Hoc Reports.
- Create a new folder using the available folder-management option.
- Enter FDR Clones as the folder name.
- Save the folder.
- Use this folder for customized copies of First Due Reports.
Creating a dedicated folder helps users distinguish customized reports from the locked, automatically deployed FDR library.
Clone and Customize a First Due Report
When an FDR is close to the desired report but requires modifications:
- Navigate to Reports Module → Ad-Hoc Reports.
- Locate the FDR you want to customize.
- In the Actions column, select the Clone icon.
- Enter a new name for the customized report.
- Use a name that clearly distinguishes the clone from the original FDR. For example:
- CUSTOM – Response Times by Station – A Shift
- CLONE – Open Violations – Station 2
- Select Copy to create the cloned report.
- Open the cloned report.
- Modify its columns, criteria, grouping, sort order, calculations, or other available settings.
- Save the report in the FDR Clones folder and/or any additional folders.
- Run the cloned report and verify that the results are correct.
Not all FDRs can be cloned. When an FDR relies on custom backend development, the Clone option may not be available. Contact the First Due Reporting Team when a modification is needed for a non-cloneable FDR.
Example FDR Reports by Use Case
For a full list please see First Due Reports Directory.
Response Time Analysis
| Report Name | Type | Purpose |
|---|---|---|
| FDR-NFIRS: 90th Percentile Response Summary by Unit – YTD | Summary | Displays 90th-percentile response time from dispatch to arrival, grouped by unit. |
| FDR-NFIRS: 90th Percentile Response Summary by Incident Type – YTD | Summary | Displays 90th-percentile response time grouped by incident type. |
| FDR-NFIRS: Apparatus Call Time and Percent Utilization | Tabular | Displays the total time each apparatus spent on calls as hours and as a percentage of the year. |
Incident Volume and Trends
| Report Name | Type | Purpose |
|---|---|---|
| FDR-NFIRS: Incident Count by Month & Year (Variable Dates) | Summary | Displays incident totals by month and year. |
| FDR-NFIRS: Incident Count by Day of Week and Time of Day – YTD | Summary | Displays call-volume patterns by day and time for staffing analysis. |
| FDR-NFIRS: Count of Incidents by Apparatus | Tabular | Displays a monthly count of incidents assigned to each apparatus. |
| FDR-IR: Incident Count by Primary Incident Group | Summary | Displays the incident count and percentage of the total by NERIS primary incident group. |
EMS and ePCR
| Report Name | Type | Purpose |
|---|---|---|
| FDR-EPCR: Total Patients by Patient Disposition | Summary | Displays patient totals and percentages by disposition. |
| FDR-EPCR: EMS High Utilizers | Tabular | Identifies repeat patients with five or more ePCRs within the previous 365 days. |
| FDR-EPCR: Medications Given Detail | Tabular | Displays detailed medication administration records. |
| FDR-EPCR: Procedure Success Summary by Crew Member | Summary | Displays procedure totals and success or failure rates by crew member. |
Fire Prevention and Inspections
| Report Name | Type | Purpose |
|---|---|---|
| FDR-INSP: All Open Violations | Tabular | Displays open violations for occupancies within the jurisdiction. |
| FDR-INSP: All “In Progress” Inspections | Tabular | Displays inspections that remain in progress. |
| FDR-INSP: Completed Inspection Count by Inspector | Summary | Displays year-to-date inspection totals by inspector. |
| FDR-OCC: All Inspectable Occupancies | Tabular | Displays active occupancies identified as inspectable. |
| FDR-PERM: Recently Expired Permits | Tabular | Displays permits that expired within the previous 90 days. |
Personnel and Administration
| Report Name | Type | Purpose |
|---|---|---|
| FDR-PERS: Active Personnel Roster | Tabular | Displays active personnel with associated shift, station, and rank information. |
| FDR-ADMIN: Last Login by Department Users | Tabular | Displays the most recent login attempt for each user, including failed attempts. |
| FDR-ADMIN: Users, Roles and Authentication Methods | Tabular | Displays users, roles, and authentication methods. |
| FDR-ADMIN: Total User Logins by Day | Summary | Displays daily login volume for the previous 30 days. |
Apparatus and Assets
| Report Name | Type | Purpose |
|---|---|---|
| FDR-AI: Apparatus Details | Tabular | Displays apparatus inventory and specification information. |
| FDR-AI: Apparatus Currently Out of Service (OOS) | Tabular | Displays equipment currently out of service and the associated time calculation. |
| FDR-AI: Apparatus Work Order Costs (Summary) | Summary | Displays total work-order costs by apparatus. |
| FDR-AI: Apparatus Fluid Costs & Volumes | Summary | Displays fluid costs and volumes by apparatus. |
Training
| Report Name | Type | Purpose |
|---|---|---|
| FDR-TRNG: Completed Trainings and Sum of Hours Per Personnel and Category – YTD | Summary | Displays training hours by person and category. |
| FDR-TRNG: Training Class Hours by Objective (YTD) | Summary | Displays training hours by objective for compliance and ISO tracking. |
| FDR-PS: Incidents, Trainings, & Events Attendance Percentage | Summary | Displays personnel attendance percentages across incidents, training, and events. |
Grants and Compliance
| Report Name | Type | Purpose |
|---|---|---|
| FDR-NFIRS: FY2024 FEMA Assistance for Firefighters Grant (AFG) | Tabular | Provides pre-calculated metrics for page 6 of the FY2024 AFG application. |
| FDR-NFIRS: Structure Fires, Property Loss and Contents Loss | Summary | Displays structure fire totals and associated property and contents loss. |
Best Practices
- Review the report description before running an FDR. Descriptions may identify the report’s scope, default date range, assumptions, and treatment of imported records.
- Confirm the report’s active filters before relying on the results.
- Clone an existing FDR when it closely matches the agency’s reporting need instead of rebuilding the report from scratch.
- Create an agency-owned folder named FDR Clones and save customized FDR copies in that folder.
- Do not attempt to move or rename the locked FDR folders.
- Use clear naming conventions for cloned reports so users can distinguish them from First Due-maintained reports.
- Consider adding CUSTOM or CLONE to the beginning of a cloned report’s name.
- Test cloned reports after changing criteria, columns, grouping, joins, or summary calculations.
- Make changes incrementally and run the report after each major modification.
- Use browser bookmarks for FDRs that are accessed frequently.
- Schedule recurring delivery when users need the same FDR on a regular basis.
- Periodically review the FDR library for newly deployed reports.
- Confirm whether imported or legacy records are included before using an FDR for compliance, grant, or operational reporting.
Troubleshooting & FAQs
Why can’t I see all First Due Reports?
FDR visibility depends on the user’s permissions for the underlying modules and data. For example, a user without ePCR access may not see FDR-EPCR reports. Contact a system administrator to review the user’s assigned access.
Can I edit an FDR directly?
No. FDRs are created and maintained by the First Due Reporting & Platform Team and cannot be edited directly. Clone the report to create an agency-owned, editable copy.
Why can’t I clone a specific FDR?
Some FDRs use custom backend development or custom SQL that cannot be represented in the Ad-Hoc Report Builder. These reports cannot be cloned. Contact the First Due Reporting Team when a modification is needed.
Where should I save a cloned FDR?
Create an agency-owned folder named FDR Clones and save cloned reports in that folder. This keeps customized reports separate from the locked FDR library and makes them easier to locate.
Why are the FDR folders locked?
FDR folders are locked because new reports are automatically deployed to agencies. The folder structure must remain consistent so each report is delivered to the correct location.
Can I reorganize the original FDR folders?
No. Original FDR folders cannot be renamed, moved, or deleted. Use search, filters, bookmarks, and an agency-owned FDR Clones folder to organize the reports your agency uses.
How often are new FDRs added?
The First Due Reporting & Platform Team develops and deploys new reports based on agency needs, platform updates, and reporting requirements. Newly released FDRs are automatically delivered to agency environments.
Can I schedule an FDR for automated delivery?
Yes. FDRs support available scheduling and delivery options, including recurring schedules, email delivery, and SFTP delivery.
What is the difference between an FDR and a Canned Report?
Canned Reports are located within module-specific sections of the Reports Module and generally provide limited parameter controls. FDRs are located within Ad-Hoc Reports, are identified by the FDR- prefix, and may contain more complex reporting logic.
Can I remove FDRs for modules my agency does not use?
No. FDRs cannot be removed or hidden. Use search and filter options to focus on reports relevant to the agency.
Why is my cloned FDR returning unexpected results?
Changes to criteria, columns, joins, grouping, or summary calculations may alter the report’s logic. Create a fresh clone and make smaller changes, testing the report after each modification.
Do FDRs include imported or legacy records?
This varies by report. Review the report description for information about whether imported records are included or excluded.
Can FDRs be used for grant applications or compliance reporting?
Some FDRs are designed to support grant and compliance requirements. Confirm that the report applies to the current reporting period and review its description before using the results.