Incident Personnel and Call Credit

A tone drops at 2 a.m. Two members catch the engine, one drives straight to the scene in their own truck, and two more make it to the station just as the engine pulls out. They stay, stand by the second rig, and go home when the call clears. Every one of those five responded. Only three went to the scene.

Command Established records all five, and it keeps track of which is which — because "who responded" and "who was on scene" are different questions, and different parts of the system need different answers. This article explains the three ways a member can be attached to an incident, what each one counts toward, and why your CAD-imported response times reflect your own units.

Three ways a member can be on an incident

On an incident's Resources tab, personnel are recorded under one of three headings:

A member goes in exactly one of these for a given incident. If you try to add someone who is on a rig or in a POV as a station responder (or the reverse), Command Established refuses rather than counting them twice. The one exception is within the Apparatus section: a member may be listed on more than one rig for the same incident, for a call where they genuinely crewed both.

Apparatus and POV responders are covered in detail elsewhere; see How POVs Are Reported to NERIS for the POV side. The rest of this article focuses on station responders and on what each section counts toward.

Giving a member call credit for covering the station

The scenario: A member came to the station on the tone, the first-out rig had already left, and they stood by at the station for the rest of the call. They never rode out. You want their turnout to count.

That member is a station responder. To record them:

1. Open the incident and go to the Resources tab.
2. Click Add Station. If your department has one station, a Station Responders section appears for it immediately. If you have several, pick the station the member responded to from the list.
3. Use the Add crew member control in that section to search for the member and add them.

Station responders show up as name chips with no riding position — there is no role to assign, because they were not on a rig. Each station gets its own row, so a department with two houses can record who turned out to each.

Station responders appear on the incident's read-only view, on the printed run sheet under a Station Responders heading, and in the personnel count on the active-incident banner and responding view.

To remove a single member, remove their chip. To remove the entire section, use the section's remove control; you will be asked to confirm, since it removes every station responder on the incident.

What station responders count toward

This is the part that matters for your year-end numbers, so here is exactly what the system does.

Call credit and top responders — yes

Station responders earn one incident response, the same as a member who rode the engine. (A member listed on more than one apparatus for the same incident earns one response per assignment, so keep multi-rig assignments to cases where the member genuinely crewed both.) The Top responders list on the incident report counts them, and the per-member response totals that feed compliance evaluation include them.

LOSAP and compliance call counts — yes

Every Call count requirement in a compliance program is evaluated from the same per-member response records, and those records include apparatus crews, POV responders, and station responders alike. That means:

• A threshold-mode requirement such as "50 calls to stay active" or "50 calls for the annual stipend" counts a station response as a call.
• A points-mode (LOSAP) category such as "Alarms — 1 point per alarm, max 40" awards a point for a station response.
• A call-count requirement filtered by NERIS incident type still counts the station responder, as long as the incident's type matches.

If your department's bylaws or LOSAP plan say that only members who went to the scene earn credit, do not record the member as a station responder — Command Established does not have a separate "credit but do not count" option for this section.

See LOSAP Points Tracking and Compliance Programs for how to set those requirements up.

Personnel deployed — yes

The incident report's "personnel deployed" figures — total personnel deployed, firefighters per call, and the personnel-by-day breakdown — count station responders alongside apparatus crews and POV responders. A member who held down the station was committed to that call, so these figures treat them the same as the crew that rolled.

This changed in September 2026. Before then, station responders were left out of these particular figures. If you record station standby, your personnel-deployed numbers are higher than they used to be for the same calls — and because the incident report compares a period against the one before it, both sides of that comparison moved together, so your period-over-period trend is unaffected.

Note that these figures do not check whether a unit actually arrived: a crew on a rig that was cancelled en route still counts as deployed. A unit that was toned but never rolled at all does not.

Man-hours — yes

The incident report's man-hours figure multiplies each unit's crew by the time that unit was committed to the call. Station responders have no rig clock of their own, so they are credited the incident's duration, the same as POV responders. A unit that was cancelled en route stops counting at the cancellation, not when the call closed.

Incident personnel count — yes

The simple personnel count shown on an incident (in lists, the active-incident banner, and the responding view) includes station responders. It is a total of every crew assignment on the incident — apparatus seats, POV responders, and station responders added together — so a member listed on two rigs is counted twice.

How station responders are reported to NERIS

They aren't — and that is correct.

NERIS reports unit responses: an apparatus or a POV unit, with its staffing and its times. A member who stayed at the station was not part of any unit's response, so station responders:

• do not appear as a unit response in the NERIS submission,
• do not add to the staffing of any apparatus or the POV unit, and
• do not satisfy the NERIS requirement for at least one responding unit.

That last point catches people out. An incident whose only personnel are station responders is not ready for NERIS submission. It still needs at least one apparatus or POV responder — or, for a call where nobody responded, a no-action reason. Station responders are a Command Established record for your own credit and accountability; they are not something NERIS asks for.

Apparatus crews and POV responders are reported exactly as before. See How POVs Are Reported to NERIS for the POV unit rules.

Why your response times changed after a CAD import

The scenario: A chest-pain call came in, your engine arrived at 00:31, and the ambulance arrived at 00:38. After the CAD sheet was imported, the incident's on-scene time reads 00:38.

A dispatch sheet lists every agency on the call — the ambulance service, the sheriff, and mutual-aid companies as well as you. Command Established used to read an incident's en-route and on-scene times off whichever unit the CAD sheet happened to list first, which meant another agency's clock could set your department's response times.

Two things changed.

Times come from the earliest unit, not the first listed

For incidents created from a CAD run-sheet PDF, en-route and on-scene times are taken independently, each from the earliest unit that reported it. (Incidents created from text-only CAD emails with no PDF keep the times the email states.) The order units appear on the sheet no longer matters. One side effect: an incident whose arriving unit never logged an en-route time, but where another unit did, now records that en-route time where it previously had none. That is more accurate, but it does mean some older incidents will show an en-route time they did not have before when they are reparsed.

You can tell Command Established which units are yours

Under Settings > CAD Email, the Response Time Units setting lets you check which unit categories — FIRE, EMS, LAW — count as your department's own when recording response times. A fire department would typically check FIRE only. The same selection decides when an incident counts as completed: if the sheet has no formal closed time, the incident is marked complete once all of your selected units have cleared, even if other agencies' units are still on scene.

With the setting on:

• Only units in the checked categories set your en-route and on-scene times.
• If none of your units appear on a sheet (an EMS-only call, say), the incident records no response times rather than borrowing the ambulance's. Reparsing such an incident clears any times that came from another agency.
• If one of your units does appear but never logged a particular time (your engine has an on-scene time but no en-route time, say), reparsing leaves any previously stored value for that one time in place — it does not clear it. Check such incidents by hand after a reparse.
• If the CAD sheet does not label its units with a category at all, the filter is skipped and every unit counts, so an unlabelled sheet cannot wipe your times.

Leaving every box unchecked keeps the historical behaviour: every unit on the sheet counts. That is the default for every department, so nothing changes until you turn it on.

Once you set it, incidents already imported keep their old times until their CAD email is reparsed. In the Recent CAD Emails list on the same settings page, use the reparse control on an individual email, or Reparse All to reprocess stored emails. Emails are kept for seven days, and only the newest 100 are available to reparse (individually or with Reparse All); if you receive more than that in a week, older incidents keep their existing times and can be edited by hand on the Basic Info tab.

Common questions

Related

• How POVs Are Reported to NERIS
• LOSAP Points Tracking
• Compliance Programs
• CAD Email Integration
• Incident review workflow