The Station Closure Hearing

The department should not rely on a single average. First, validate the CAD extract: determine whether the missing 14% is random or clustered by time, call type, or geography, and state that limitation in the summary. Second, calculate response-time distributions by census tract and call priority, not just the department-wide average, and overlay the schools, nursing home, and unsprinklered apartments. Third, model the closure scenario against alternatives such as a brownout, relocation of a reserve engine, or an automatic-aid agreement. Fourth, present the trade-off plainly: the closure saves $2.3 million but adds 2.4 minutes to 61% of Station 2 calls and removes the closest unit from several vulnerable occupancies. Avoid claiming that the data prove a death will occur; that overstates the evidence and invites attack. The reasoning is that credible analysis acknowledges uncertainty while still showing the risk concentration. The one-page summary should distinguish verified findings, estimated impacts, and data gaps.

The assistant chief should respect the chain of command while ensuring accurate information reaches decision-makers. He should brief the fire chief and city manager with the validated analysis and ask them to transmit it to council. He should prepare a public-facing summary that states the data limitations and the operational trade-offs, then route it through the city's public information process. He should meet with the neighborhood coalition and the nursing home administrator to hear concerns and correct misinformation, but he should not organize petition drives or partisan campaigns. He should brief the union and the school district so their questions are answered consistently. If a council member requests information directly, he should refer the request to the city manager's office and document it. The reasoning is that the department's credibility depends on being technically honest and politically neutral. Direct lobbying against the city manager's proposal could cost the chief access and influence, while silence could allow false claims to dominate.

The department should respond with transparency, not defensiveness. It should release the methodology, the CAD query parameters, the counts of included and excluded calls, and the identity of the person who performed the analysis. It should invite the council member or an independent analyst to review the extract, and it should correct any errors promptly. It should avoid personal attacks and avoid repeating the charge in public statements. If the 14% missing data could bias the result, the department should say so and show a sensitivity analysis under best-case and worst-case assumptions. The reasoning is that an accusation of cooked data is best answered by reproducibility. A neutral, technical response also protects the department if the council later requests an audit. The department should not ask the union to defend the data; that would make a technical question look political.