Article9 min read
Washington Fire Department Annual Reporting Requirements: RCW Guide and Checklist
Which Washington fire departments must issue an annual performance report, what RCW 35.103, 35A.92, 52.33 and 53.56 require, and a checklist for preparing one.
Which Washington fire departments need annual performance reports, what do RCW 35.103, 35A.92, and 52.33 require, and how can departments prepare them more efficiently?
Washington law requires covered, substantially career fire departments to evaluate their service levels, deployment, and response-time objectives every year and issue a written report. The report must identify where adopted performance standards are not being met, explain the consequences of those deficiencies, and address the steps needed to achieve compliance.
The requirements are similar whether an agency operates as a municipal fire department, fire protection district, regional fire authority, or port district fire department. The governing statute depends on the jurisdiction.
This guide explains the reporting rules, the data departments need, and a practical process for producing a useful annual performance report.
Which Washington RCWs require annual fire department reports?
Washington's fire service performance-reporting requirements appear in four chapters of the Revised Code of Washington:
- City or town fire department: annual evaluation and report in RCW 35.103.040; written service objectives in RCW 35.103.030.
- Code city fire department: annual evaluation and report in RCW 35A.92.040; written service objectives in RCW 35A.92.030.
- Fire protection district or regional fire protection service authority: annual evaluation and report in RCW 52.33.040; written service objectives in RCW 52.33.030.
- Port district fire department: annual evaluation and report in RCW 53.56.040; written service objectives in RCW 53.56.030.
Each chapter pairs a written service-delivery policy with annual evaluation and reporting. For port district fire departments, RCW 53.56.040 also provides that an annual FAA Part 139 inspection and certification satisfies that section's requirements.
Which fire departments must comply?
A critical qualification is that these chapters define a covered fire department as a substantially career agency, not a substantially volunteer agency.
A combination department should not assume that the presence of a few paid positions either automatically includes or excludes it. The relevant questions include who routinely responds to incidents, the agency's minimum career staffing, and the operational roles of career and volunteer members. The Washington State Association of Fire Chiefs and Washington State Council of Fire Fighters have recommended documenting the basis for that determination.
If your department is uncertain about coverage, review its staffing and service arrangement with its governing body and legal counsel. Volunteer agencies may also choose to use the same performance measures even when the statutory requirement does not apply.
What service objectives must a covered department establish?
Before an annual report can evaluate performance, the jurisdiction needs a written policy identifying its services and objectives.
The policy must identify the department's existence, services, basic organizational structure, expected number of employees, and employee functions. It also establishes service-delivery objectives for applicable operations, including fire suppression, EMS, special operations, aircraft rescue and firefighting, marine rescue and firefighting, and wildland firefighting.
The statutes specify response-time objectives for key measures:
- Turnout time: from the crew's notification of the emergency until the unit is en route.
- First-arriving engine: travel/response time to a fire suppression incident.
- Full first-alarm assignment: response time for the complete initial fire suppression assignment.
- First EMS responder: response time for a first-responder-capable or higher-level unit to an EMS incident.
- Advanced life support: response time for an ALS unit when the department provides that service.
The governing body must establish a performance objective of at least 90% achievement for the specified time objectives. That does not mean Washington sets a single statewide four-, six-, or eight-minute response-time target for every jurisdiction. Departments establish their own applicable time objectives and then measure performance against them.
One detail matters when calculating the numbers: these RCWs define response time as the interval from en route to arrival, after turnout time. A dispatch-to-arrival figure may be valuable, but it is not interchangeable with the statute's response-time definition. Label every metric clearly.
What must the annual performance report include?
Under the annual-report sections, covered jurisdictions must evaluate service level, deployment, and achievement of each response-time objective in each geographic area of their jurisdiction.
The written report must also:
- Identify the geographic areas and circumstances in which the adopted standards are not being met.
- Explain the predictable consequences of those deficiencies.
- Address the steps necessary to achieve compliance with the adopted standards.
In practice, a report designed to support those requirements should make the following information easy to review:
- Adopted objectives: the applicable service and response-time goals, including the stated achievement threshold.
- Response performance: observed results and the share of eligible incidents meeting each objective.
- Geographic differences: results by first-due area, station area, district, or other relevant service geography.
- Exceptions and deficiencies: where performance did not meet objectives, with clear counts, definitions, and operational context.
- Department assessment and next steps: leadership's explanation of likely effects, improvement priorities, and any necessary corrective actions.
Additional material such as call-volume trends, workload, concurrency, apparatus utilization, or maps can make the report far more useful. Those are helpful management analyses, not a substitute for the required comparison with adopted objectives and discussion of deficiencies.
Why report the 90th percentile instead of just the average?
Averages can hide the slower calls that matter when measuring reliability. The 90th-percentile time identifies the point at or below which 90% of included responses occurred. For example, a 90th-percentile response time of six minutes means nine in ten measured responses took six minutes or less.
Departments should also calculate the percentage of eligible responses that met their adopted objective, because that directly answers whether the performance target was achieved. Define which incidents qualify, distinguish turnout from travel time, and review incorrect or missing timestamps according to a documented data-quality policy. Do not quietly remove legitimate slow responses as “outliers.”
Is there a specific deadline or state filing requirement?
The fire-performance RCWs require an annual written report, but the provisions cited above do not specify one universal calendar-day deadline or a statewide upload portal for that particular report. Departments should follow applicable local policies, board schedules, and legal guidance for issuance and publication.
Do not confuse the operational performance report with a local government's annual financial report. Under RCW 43.09.230, local governments file financial reports with the Washington State Auditor within 150 days after their fiscal year closes. That is a separate reporting obligation.
A practical annual reporting checklist
A dependable process begins well before the report is due:
- Confirm applicability and adopted objectives. Identify the governing RCW, verify whether your agency is substantially career, and locate the current approved service-delivery policy.
- Define measures and service areas. Establish incident categories, geographic boundaries, qualifying units, response phases, and the definition of a full first-alarm assignment.
- Collect the operational records. Gather appropriate CAD and dispatch incident records, unit-level timestamps, apparatus identifiers, incident classifications, and location or first-due-area fields.
- Validate the data. Check for duplicates, missing timestamps, corrected incidents, cross-boundary responses, and mapping changes. Record any exclusions and their reasons.
- Evaluate each objective. Calculate performance by service category and relevant geography. Compare results against adopted times and at-least-90% achievement objectives.
- Document deficiencies and actions. Have leadership explain where objectives are not met, the predictable consequences, and the steps needed to improve performance.
- Review, issue, and preserve the report. Obtain the appropriate internal review, publish or distribute the annual written report under your agency's procedures, and retain a consistent record for comparisons in future years.
The calculations can be automated. The agency's interpretation of the results, decisions about service levels, and approval of corrective actions remain leadership responsibilities.
What about monthly reports to fire commissioners?
Many Washington fire districts produce monthly operational reports for their boards. Under RCW 52.14.090, boards of fire commissioners hold regular monthly meetings, but that statute does not establish a universal monthly operational-report template.
A useful commissioner report might include call counts, staffing, response times, unit workload, overlapping incidents, and significant operational trends. Because these measures overlap with annual performance reporting, agencies can benefit from using one consistent data process for both.
Example: Bellingham Fire Department's 2025 Annual Report
The Bellingham Fire Department's 2025 Annual Report, prepared in partnership with Civic Informer, shows what a modern operational report can make accessible.
It brings together 24,249 calls, 39,613 apparatus responses, and 18,903 calls within eight first-due areas, alongside call trends, apparatus utilization, response-time analysis, and interactive geographic coverage.
The distinction between calls and apparatus responses is important: one incident may require several units, so workload analysis should not confuse the number of incidents with the number of responding apparatus.
The report is an example of the analysis and presentation that dispatch data can support. It should not be assumed that any public dashboard or statistical report, by itself, satisfies every requirement of a jurisdiction's adopted performance policy and annual statutory evaluation.
Explore Bellingham Fire's interactive annual report.
Frequently asked questions
Do volunteer fire departments have to prepare these RCW performance reports?
The performance-measurement chapters are framed around substantially career fire departments. A department's classification depends on its actual staffing and response arrangements, not just whether it has any paid positions. Other financial, administrative, and records obligations may still apply to volunteer agencies.
Does Washington require every department to meet a four-minute response time?
No. The statutes require jurisdictions to establish applicable response-time objectives and set at least a 90% achievement target for the specified measures. They do not impose a uniform four-minute time objective on every department.
Can a CAD export be used to prepare the annual report?
Often, yes. CAD and dispatch records commonly contain incident types, unit assignments, event timestamps, and geographic identifiers. The available fields and their quality determine which measures can be calculated reliably. Department-specific policies and leadership input are still needed to evaluate performance against adopted objectives.
Is an annual operational report the same as the State Auditor's financial report?
No. Fire-performance evaluations under RCW 35.103, 35A.92, 52.33, and 53.56 are distinct from annual local-government financial reporting under RCW 43.09.230.
Spend less time assembling reports and more time using them
Departments already generate much of the operational information they need during everyday dispatch and response activity. The challenge is turning those records into accurate, repeatable analysis without rebuilding the same spreadsheets and charts each year.
Civic Informer prepares reporting figures, visualizations, and report drafts from existing dispatch exports, with department leadership supplying adopted objectives, reviewing findings, adding operational context, and approving what is shared. The same data foundation can support annual performance reporting, commissioner or council updates, and ongoing operational analysis.
See Civic Informer's Fire & EMS reporting solutions or contact our team to discuss your department's reporting workflow.
This guide is general information, not legal advice. Jurisdictions should verify current statutory requirements and their own applicability, policies, and reporting procedures.
Further reading: MRSC's Washington fire services guidance · RCW Chapter 35.103 · RCW Chapter 35A.92 · RCW Chapter 52.33 · RCW Chapter 53.56
About the author

Civic Informer
Published Nov 18, 2026. Articles are not edited after publishing; any correction is added here with its date.