Common questions about incident cost recovery

Fire department billing is an administrative cost recovery process where a city, county, or fire department submits incident documentation to Onsite. Onsite reviews submitted incidents, organizes the supporting documentation, prepares insurer-ready claim packets, and sends those packets to insurance companies for review and possible payment. Not every incident or claim is payable; recovery depends on local policy, ordinance, state law, documentation, available coverage, whether an insurance claim exists, liability facts, policy limits, and carrier response.

Yes. Fire departments can bill for response cost recovery when local authority and documentation support it, but there are limitations and variables that determine whether a claim will be paid. For example, Onsite cannot file a claim on behalf of the at-fault party. The at-fault party must file their own insurance claim first; then Onsite can prepare and submit the department's recovery packet against that claim and track carrier follow-up.

Departments should review local authority before billing. A written ordinance, resolution, or policy can help define eligible services, approval paths, and how recovered funds are handled.

Onsite can help organize administrative materials and practical examples for local review, but it does not provide legal advice. Departments should work with municipal leadership and legal counsel on ordinances, resolutions, and policy language.

No. Emergency response decisions should remain based on life safety, incident command, and operational needs. Billing review happens after the incident using available documentation and approved local policy.

Onsite supports administrative recovery workflows for auto incidents, water rescue, backcountry rescue, landing zones, and structure fires when local authority and supporting documentation allow an insurer-ready packet to be prepared.

Auto incident billing organizes submitted auto incident response documentation, including incident reports, police reports, at-fault party information, auto insurer details, apparatus time, personnel time, extrication, cleanup materials, claim tracking, and monthly reporting.

Yes. Auto incidents can be submitted for insurance-company review when the department has local authority and supporting documentation. That does not mean every submitted claim will be paid; payment depends on available coverage, claim activity, policy limits, and carrier response. Onsite bills insurance companies only, not individuals.

Onsite does not determine legal fault. Administrative recovery may use available documents such as police reports, responsible-party information, claim details, and insurer responses to guide carrier follow-up.

Useful documentation can include the incident report, police report, responsible-party details, auto insurer information, apparatus time, personnel time, rescue tools, cleanup materials, claim status, denial notes, and carrier follow-up history.

Water rescue billing organizes submitted water incident documentation such as swiftwater, surface water, or ice rescue where applicable, including boat deployment, trained rescue staff, PPE, rope systems, command setup, mutual aid, equipment, materials, follow-up, and reporting.

Yes. Water rescue responses can be billed to insurance companies when local authority and documentation support the recovery packet. Payment is separate from billing and depends on claim activity, available coverage, policy limits, and carrier response.

The strongest water rescue submissions show the incident context, units assigned, trained rescue personnel, boat or watercraft deployment, PPE, rope systems, command activity, mutual aid, equipment, materials, and any responsible-party or insurance details available.

Yes. Mutual aid, specialty teams, watercraft, rescue equipment, and support units can be included when the department has documentation showing who responded, what was used, and how the response supported the incident.

Backcountry rescue billing supports submitted documentation for wilderness, trail, mountain, off-road, search and rescue, and technical rescue responses, including GPS coordinates, UTV/ATV use, rope rescue resources, personnel hours, vehicle hours, evacuation, incident documentation, and carrier follow-up.

Yes. Special rescue responses can be billed to insurance companies when the department has local authority and supporting documentation. Payment is not guaranteed; it depends on responsible-party information, available coverage, insurance claim activity, policy limits, and carrier response.

GPS coordinates help connect the rescue to the actual response environment. They can support trail, backcountry, off-road, mountain, wilderness, or remote-area context when Onsite organizes the recovery packet for insurance-company review.

No. Onsite does not replace the department's incident documentation. The department submits the available reports and response details, and Onsite organizes those materials for insurance-company billing and follow-up.

Landing zone billing focuses on submitted helicopter landing zone response documentation, including LZ setup, air medical coordination, command and control, scene safety, perimeter control, traffic control, hazard assessment, apparatus standby, mutual aid, and insurer-ready documentation.

Yes. Landing zone support can be billed to insurance companies when documentation and the related incident context support review. It is often tied to another incident, and payment depends on available coverage, claim activity, policy limits, and carrier response.

Not always. Landing zone support is often connected to the incident that created the need for air medical transport. Onsite keeps the LZ response tied to that incident context when preparing the packet and tracking carrier follow-up.

Helpful documentation includes LZ setup, perimeter control, hazard assessment, scene safety, apparatus standby, EMS coordination, air medical coordination, traffic control, mutual aid, timing, and the incident that created the landing zone response.

Structure fire billing organizes submitted documentation for building fires, residential fires, and commercial fires, including apparatus hours, personnel hours, suppression work, command, mutual aid, materials, fire reports, property insurance context, follow-up, and reporting.

Yes. Structure fires can be billed to insurance companies when the department submits the response for review. Billing does not guarantee payment; insurance-company payment depends on documentation, responsibility facts, available coverage, policy limits, and carrier response.

Property owner information, insurance carrier details, claim status, fire report context, cause and origin details when available, property damage information, responsible-party details, and carrier responses can all help Onsite manage billing and follow-up.

Structure fires can involve property coverage, responsibility questions, mutual aid, suppression resources, materials, and policy limits. Onsite organizes the documentation and tracks the insurance-company response without billing residents or individuals.

Useful documentation can include incident reports, fire reports, police reports, responsible-party information, insurer details, apparatus and personnel time, materials or equipment used, command notes, denial notes, and payment or recovery status.

Not always. Onsite can often work from submitted incident documentation and exported reports. Direct RMS or reporting-system access may help some workflows, but it should be reviewed with department leadership and local data-access requirements.

NFIRS and NERIS are incident reporting systems and data standards, not billing programs by themselves. They can help support documentation, but billing still depends on local authority, incident facts, and available insurance coverage.

Onsite bills the same rate everywhere using a national rate standard that insurers commonly accept for fire department response cost recovery. A large city and a small town are billed at the same amount for the same type of response. The goal is to stay within insurer-accepted ranges so claims are not priced too high to be paid, while also avoiding rates that are too low and reduce recovery for fire departments and municipalities.

Denials are tracked with the reason, date, follow-up notes, and next step when available. A denial does not mean every similar incident will be denied, and it does not guarantee a future payment either.

A stronger packet usually has complete incident documentation, police incident reports, clear service details, apparatus and personnel time, materials used, responsible-party or property information, insurer details, and organized follow-up notes.

No. Onsite does not bill individuals. Onsite only bills insurance companies, so recovery depends on available insurance coverage and an insurance claim the department can bill against.

No. Onsite does not bill residents or other individuals. Onsite only bills insurance companies when the applicable policy allows a fire department recovery claim to be submitted and reviewed.

Recovered funds may support department needs when local policy and budgeting rules allow. Cities and counties should decide how recovered dollars are received, allocated, and reported.

Onsite organizes documentation, prepares recovery packets, follows up with carriers, tracks statuses, documents denial notes, and prepares monthly reporting so crews and local staff are not running a billing process from scratch.

Leadership can receive reporting on submitted claims, recovered activity, pending and open claims, denials, follow-up status, incident types, and monthly trends.

Yes. The 90-day pilot is a limited recovery trial that lets a city, county, or fire department prove the workflow before continuing into an ongoing program. Departments still have access to every supported incident type from day one. During the pilot, Onsite reviews recent incident volume, sets up a documentation handoff, receives submitted incidents, reviews them for recovery potential, prepares insurer-ready packets, submits eligible packets to insurance companies, follows carrier responses, tracks denials or payments, and reports the results back to leadership. At the end of the pilot, the department can see what was submitted, what was pending, what was denied, what was recovered, and whether the process is working.

Departments have access to every supported incident type from day one, including during the pilot. The review is not about gaining access to more tools or services; it is about deciding whether the workflow is ready to keep running. Are incidents being submitted to Onsite consistently? Are the reports, police incident reports, responsible-party details, and insurance information complete enough for Onsite to prepare packets? Are insurance companies opening, reviewing, denying, or paying claims? Are leadership reports clearly showing submitted, pending, denied, and recovered activity? Those answers show whether the documentation handoff, carrier follow-up, and reporting process are working or need to be tightened.

EMS billing usually involves patient transport, medical coding, and health insurance workflows. Fire department billing is typically incident cost recovery tied to response resources, local policy, responsible-party information, and property or casualty insurance coverage.

The longer part is usually getting through local approval, legal review, policy readiness, and documentation access. Once a department is past that local red tape and ready to move forward, Onsite account setup takes minutes. Some departments still begin with a recovery review or 90-day pilot before continuing into an ongoing program.

Onsite gives departments a recovery process without forcing chiefs, finance teams, or municipal staff to run it internally. Departments submit incidents, and Onsite reviews the submitted documentation, identifies whether there is a viable insurance path, prepares insurer-ready packets, bills only insurance companies, follows carrier responses, tracks denials and payments, and reports the results in the Recovery Hub. The process is conservative by design: it shows leadership what is actually being submitted, pending, denied, and recovered before the department decides how to run the program long term.

A department can request a recovery review or estimate by sharing basic response volume, current policy status, incident types, documentation workflow, and leadership goals with Onsite.