Quick answer
The short version.
Fire dispatch data is an evolving operational record. The first version reflects what was reported, not necessarily the final cause or damage. Incident type, address, time, units, department, and status can change, remain incomplete, or use local terminology. A reliable business system preserves the original report, applies later updates to the same incident, and leaves unknown fields visibly unknown.
01
Incident type is a dispatch classification
Labels such as structure fire, residential fire, commercial fire, alarm, smoke investigation, or outside fire help responders and downstream systems organize a call. They are not a final fire-investigation finding or restoration scope.
Local agencies use different codes and naming conventions. A normalization layer can make lists easier to read, but it should retain the original source label for traceability.
02
Dispatched and last updated are different times
The dispatch time records when the incident first entered the source workflow. The last-updated time records the newest source change Lossline has processed. Keeping both prevents a later update from making an old incident look newly dispatched.
Updates may add or remove units, change the address, refine the incident type, or mark an event inactive. A large fire may remain active through quiet periods, while some source systems may never publish a clean closure.
03
Responding units add context, not a severity score
Unit identifiers can represent engines, ladders, rescues, chiefs, special units, or mutual aid. The same number of units can mean different things across departments. Some feeds expose the full assignment; others show a partial or delayed list.
Use units to understand the response record, not to promise a particular damage level. A zero or missing unit count means the field is unavailable or empty in the processed source, not that nobody responded.
04
Departments and territories can be missing
An incident may arrive without a clean agency label even when it can still be matched to a watched feed or geography. The interface should omit awkward punctuation and show a neutral unknown state rather than invent a department.
Territory subscriptions are routing rules. They do not prove which agency ultimately controlled the scene, especially when mutual aid or multi-agency response is involved.
05
Addresses can evolve
Initial dispatch locations may be intersections, approximate blocks, landmarks, apartment complexes, or addresses entered with inconsistent formatting. Later updates can refine the location. Property enrichment should use the best normalized address while preserving the source value.
If an address changes materially, the system should prevent an old owner match from being silently attached to the new property. Cached enrichment is valuable only when the normalized property identity is genuinely the same.
06
A reliable system has aging and duplicate rules
Live sources can repeat records, omit closures, or publish delayed updates. A production system needs stable incident identifiers, deduplication, an update window, a stale-state policy, and a way to stop polling records that never close.
The business-facing record should remain understandable after monitoring ends. Preserve the dispatch time, last processed update, final known status, source label, and any limitations instead of deleting history.
FAQ
Common questions.
Does a structure-fire label confirm structural damage?
No. It is a dispatch classification. The final cause and damage scope require later verification and, where appropriate, a site assessment.
Why can responding units change after the first alert?
Assignments evolve as dispatchers and responders add, clear, stage, or transfer resources. Source feeds may also publish updates at different times.
What does an unknown department mean?
It means the processed incident did not include a reliable department label. It should not be treated as evidence that no department responded.
Primary sources
Research behind this guide.
Lossline publishes educational business content. It is not legal, safety, insurance, claims, or restoration advice. Verify material information and consult qualified professionals for your circumstances.