Contact

GlossaryFire and EMS reporting

Good intent call

Good intent call is a historical fire-reporting category. Learn why it does not mean a malicious false report or prove that a response was unnecessary.

A good intent call is a historical fire-reporting category covering certain responses where the reported emergency was not found as initially understood, along with specified related situations. It describes a classification in the reporting system. It should not be read as a judgment about whether someone should have requested help.

Where the label comes from

The National Fire Incident Reporting System, or NFIRS, placed good intent calls in its 600 series. The group included steam mistaken for smoke and some canceled responses. Its scope was broader than a single explanation such as “nothing happened.” NFIRS reference guide, Basic Module incident types.

The label remains useful when reading historical reports. NFIRS has retired, so a newer dataset using similar wording needs its own definition. A familiar phrase does not establish that two reporting systems include the same events. USFA documentation.

Example

Hypothetical: Someone sees a cloud rising near a building and reports possible smoke. Responders investigate and document steam rather than a fire. A historical NFIRS summary places that response in the relevant good intent category.

The response still involved a request, an assignment, and time spent investigating. The final classification explains what was found. It does not turn the caller's initial uncertainty into evidence of dishonesty or establish that dispatch could have known the outcome in advance.

Common confusion

Good intent and false alarm are separate historical reporting groups. Calling every nonfire response a “false alarm” can erase that distinction and give readers an inaccurate impression of the caller's conduct.

The category also differs from a confirmed hazardous condition without fire. A lack of flames does not, on its own, tell a reader which category fits. The source's completed incident classification matters more than a broad inference from the absence of a fire.

Interpreting a yearly count

List the included source codes when reporting a combined total. A change in how cancellations are grouped can shift the count even if the underlying response workload stays similar.

Keep incident totals separate from apparatus responses. Several vehicles can respond to one reported condition. If a historical chart spans a change in reporting systems, explain how the categories were mapped and whether a direct comparison remains possible.

Sources