Washington Nonprofit Security Grant Program for Churches: Two-Agency Guide

A Washington church researching security funding usually finds two different programs and assumes they're the same thing. They aren't. The Washington State Department of Commerce runs a state-funded Religious and Nonprofit Security Grant, paid for through the state budget, while the Washington Military Department's Emergency Management Division is the separate agency that reviews and forwards applications to FEMA for the federal Nonprofit Security Grant Program (NSGP). Different money, different agency, different application — and, unlike states such as New Jersey where one office runs both tracks, Washington splits the work across two.

That split matters for planning purposes. For background on the federal program itself — the Investment Justification format, funding tiers, and national deadlines — see our 2026 NSGP complete guide and our NSGP eligible expenses breakdown.

Two Agencies, Two Different Grant Tracks

Most other states with a dual-track setup — New Jersey and Illinois, for example — route both the state and federal money through a single homeland security office. Washington doesn't. Commerce, the state's economic and community development agency, owns the state grant, while the Military Department's Emergency Management Division — the state's emergency management authority — owns the federal NSGP relationship with FEMA. A congregation pursuing both tracks in Washington is, in practice, managing two separate points of contact rather than one.

What the State Religious and Nonprofit Security Grant Covers

Commerce's program funds security equipment, training, and other physical safety needs for faith-based organizations and nonprofits that have been targeted, or are at risk of being targeted, because of their mission, ideology, or beliefs. In the 2023 award cycle, Commerce distributed close to $500,000 across 20 faith-based organizations and nonprofits statewide, with individual awards of up to $25,000 per grantee. The Washington Legislature revisited the program and added funding in winter 2024, which is a useful signal that lawmakers treat this as an ongoing commitment rather than a one-time appropriation — but it also means the exact award ceiling and total pool can shift from cycle to cycle.

Eligible uses under the state program have included physical security enhancements such as reinforced doors, fencing, exterior lighting, security camera and access-control systems, and target-hardening measures like cement barriers placed in front of a building's entrances.

The Federal NSGP Track Through the Military Department

Washington nonprofits — including churches, synagogues, mosques, and temples — can't apply to FEMA directly for the federal NSGP. The Washington Military Department's Emergency Management Division reviews subapplications from nonprofits located in the state, scores them, and forwards a ranked list to FEMA for final funding decisions, which is the same structural role every state's administering agency plays. Applicants use the federal Investment Justification (IJ) format, following FEMA's Nonprofit Security Grant Program Subapplicant Quick Start Guide, rather than a state-specific form.

Because the Emergency Management Division can only forward applications from organizations physically located in Washington, and because NSGP splits funding between an Urban Area track (NSGP-UA) for congregations inside a federally designated high-risk urban area and a State track (NSGP-S) for everyone else, it's worth confirming with the division early which track your location falls under — it affects both your competition pool and, in some cycles, your award ceiling.

Who's Eligible

Both tracks share a similar baseline: 501(c)(3) nonprofits, including houses of worship, that can show an elevated risk of a terrorist attack or hate crime tied to their ideology, beliefs, or mission. Neither program requires a congregation to prove a past attack — a documented pattern of threats, vandalism, or comparable incidents targeting similar organizations in the area can support eligibility, and a security consultant or local law enforcement liaison can help frame that case.

Churches that haven't formalized 501(c)(3) recognition should review our 501(c)(3) grants for churches guide first. Most churches qualify for tax-exempt treatment automatically under IRS rules without filing for it, but having a clean determination letter, group exemption documentation, or EIN on file still smooths review for either Washington track — see our guide on church group exemption and grant eligibility if your congregation is part of a denomination rather than independently incorporated.

Registrations and Documentation

• SAM.gov registration and a Unique Entity ID (UEI) — required for the federal NSGP track only, since that money flows through FEMA. Not required for Commerce's state program on its own.
• Vulnerability assessment — a documented, site-specific description of your facility's security gaps, expected for both tracks and central to how each agency scores applications.
• Budget narrative or investment justification — tying each requested expense to a documented vulnerability, required for a Commerce application, a Military Department application, or both.

SAM.gov registration takes longer than most congregations expect. Our SAM.gov and Grants.gov registration guide covers the realistic timeline — worth starting even if you plan to apply to Commerce's state grant first, since most congregations that pursue one track eventually apply to the other.

How to Apply

1. Check both agencies' current program pages — commerce.wa.gov for the state grant, mil.wa.gov for federal NSGP details — to confirm open application windows and current-cycle deadlines.
2. Register in SAM.gov and obtain a UEI if you intend to pursue the federal NSGP track through the Military Department.
3. Complete a site-specific vulnerability assessment, ideally with input from a security professional or local law enforcement.
4. Decide which categories fit your need — equipment, training, personnel-adjacent costs where eligible — and draft a budget narrative tied to that assessment for each program you're applying to.
5. Submit separately to each agency — Commerce's application and the Military Department's IJ subapplication are two distinct processes, even when a congregation pursues both in the same year.

Running Both Programs Without Double-Funding

The rule that carries across every state and federal security grant is the same: you can't fund the identical line item from two different sources. A Washington congregation could, for example, use Commerce's state grant to fund exterior lighting and fencing while using federal NSGP funds for a separate camera and access-control project — as long as the two budgets are documented separately and don't overlap on the same specific cost.

Because Washington's two tracks run through entirely separate agencies with no shared application portal, keeping clean, separate documentation for each request isn't just good practice — it's the only way either agency can verify you're not double-billing the same expense.

Common Mistakes Washington Applicants Make

• Assuming one application covers both programs. Commerce and the Military Department don't share an intake system — you'll need to apply to each separately, with separate documentation.
• Skipping SAM.gov because the state grant doesn't require it. True only if you never apply federally. Most congregations eventually do, and starting registration late is a common, avoidable delay.
• Treating the vulnerability assessment as boilerplate. Given that Commerce received 116 applications for one recent cycle against a limited pool, a generic paragraph about houses of worship facing risk in general scores worse than a site-specific assessment documenting your building's actual entry points and any prior incidents.
• Not confirming NSGP-UA vs. NSGP-S status. Confirm with the Emergency Management Division which track applies to your location — it affects your competition pool and, in some cycles, your award ceiling.
• Budgeting against last year's award figures. Both the state pool size and award caps have moved across recent cycles; verify current numbers directly with each agency before finalizing a project budget.

Security funding is often just one piece of what a Washington congregation is pursuing — see our church security grants guide for the broader landscape, and our 50-state security grants breakdown for how Washington's approach compares to other states running their own state-funded programs.

Frequently Asked Questions