HSGP and EMPG: What These Grants Will Actually Pay For in EM Software

Two federal preparedness grants are obligating to states right now, and both will pay for emergency management software. The Homeland Security Grant Program (HSGP) is open at the federal level. Most state-level Emergency Management Performance Grant (EMPG) sub-application windows have closed; allocations and awards are landing in the Q2–Q3 spend window. The money is there. The reason agencies leave it on the table is almost never eligibility — it is how the purchase gets described in the application.

HSGP: SaaS Is Already on the Authorized Equipment List

HSGP funds the 21-category Authorized Equipment List (AEL). That list is not a generic shopping catalog — it is the controlling document for what State Homeland Security Program (SHSP) and Urban Areas Security Initiative (UASI) dollars can buy. Inside Category 04, AEL 04AP-11-SAAS — Applications, Software as a Service — makes cloud-delivered software an explicitly authorized line item. There is no gray area to argue.

The decision turns somewhere else: whether the software supports a National Priority Area or a recognized Core Capability. SHSP narratives that anchor in "Operational Coordination," "Planning," or "Public Information and Warning" — and tie back to gaps identified in the agency's THIRA — score. Narratives that describe a vendor's feature list do not.

Then 2 CFR 200 takes over. Costs must be allowable, allocable, reasonable, and necessary, and the supporting documentation has to prove it. The 2025 Preparedness Grants Manual (FM-207-23-001) is the procedural reference; the AEL is the eligibility reference. Read both before drafting an investment justification.

EMPG: POETE, and Why Software Crosses Three of Its Five Buckets

EMPG is the all-hazards capability grant, and its allowable costs sit in five categories — Planning, Organization, Equipment, Training, Exercises — known by EM grants administrators as POETE. Incident management software does not live in one POETE bucket. It lives in three.

• Planning. The platform that hosts your IAP development, ICS 215 work-analysis worksheets, and operational period planning is a Planning cost.
• Organization. Personnel-adjacent tooling — staff augmentation through digital workflows, ICS 203 organizational structure, ICS 211 check-in — supports Organization.
• Equipment. SaaS subscriptions and devices used for response coordination are Equipment.

The narrative writer's job is to break the line item down across POETE so the SAA reviewer sees exactly which capability gap each dollar closes. A single procurement that rolls up under "incident management software" gets scored once. The same procurement, decomposed across three POETE categories with citations to specific Core Capabilities, gets scored three times.

EMPG also requires a 50% non-federal match — cash or in-kind. Director salary, EMA staff time, and exercise hours all count toward in-kind. For most local agencies this is the easiest match in the federal portfolio.

National funding ran $319.5M in FY25, and FY26 is prioritizing an additional $250M for the 11 FIFA World Cup host states. State sub-allocations are being awarded now. Period of performance ends sooner than agencies expect — agencies that wait until Q4 to encumber funds end up returning them.

Where the Application Goes Wrong

The single most common mistake in HSGP and EMPG investment justifications: describing software in vendor language instead of doctrine language.

Software that mirrors the ICS data model — organizational hierarchy through ICS 203/204, work assignments by Operational Period, resource lifecycle from check-in to demobilization — maps cleanly to Core Capabilities the SAA already scores against. Operational Coordination is the strongest hook for a digital ICS platform, because the Core Capability target language in the National Preparedness Goal is essentially a description of what an Operational Period architecture does.

There is a second-order argument worth threading in: a platform that produces ICS 214s, 211s, and 204s as a natural output of operations also produces the cost-tracking artifacts a future Public Assistance claim needs. This is the documentation-as-byproduct framing — it lets the same procurement close two gaps at once, which strengthens both the EMPG narrative and the agency's PA reimbursement posture. Platforms like NIMS Logic are built on exactly this premise, but the framing matters even if the agency goes a different direction on the buy: any software that the agency selects should answer the doctrine question, not just the feature question.

Your Move in the Next 60 Days

Three concrete steps for any EM director or administrator looking at this funding window:

1. Pull last year's award letter and find the unspent obligation balance. Most agencies discover they had room and never used it.
2. Map the line item to an AEL or POETE category before the conversation goes to procurement. If you cannot place the cost on the AEL or in a POETE bucket, the investment justification will not survive review.
3. Write the narrative against Core Capability gaps in your THIRA, not against vendor feature comparisons. SAA reviewers score capability outcomes, not product specs.

Q2–Q3 2026 is the obligation window. Agencies that move now — with a defensible AEL or POETE classification and a Core Capability narrative — convert grant dollars into digital ICS infrastructure before period of performance closes. Agencies that wait return the money.

See how NIMS Logic approaches the operational-period and documentation-byproduct architecture →