Grants are not won with shopping lists. They are won with facts, mission alignment, and a clear case for why the funding matters.
The nerd in me really enjoys discussing technology, mission operations, drones, surveillance, covert systems, and all the things that help law enforcement do the job more safely and effectively. But sometimes we need to talk about the “how-to” for money — and in this case, grant money.
For agencies with a full-time grant writer, a dedicated city grant office, or a contracted specialist, this article may be a refresher. But if you are in a law enforcement agency, task force, sheriff’s office, public safety department, or special unit without access to that kind of support — and you still need to pursue funding — this article is definitely for you.
Submitting for a grant can feel daunting, especially if you are like me and prefer the mission and technical side of things. But in reality, preparing a strong grant submission is not as mysterious as it may seem. From a law enforcement perspective, think of it like preparing a case.
You collect facts. You understand the stakeholders. You establish the problem. You build the scenario. You connect intent, action, consequences, and evidence. Then you assemble everything into a complete and seamless mosaic that supports your conclusion.
A grant submission works the same way.
The data is different. The audience is different. The objective is different. But the basic workflow is familiar: build the case, prove the need, show the plan, justify the resources, and explain the outcome.
That is what we are going to walk through here.
And because we are living in a time where AI can help agencies organize information, draft language, and improve productivity, we will also talk about how to use AI responsibly in the grant-writing process — and where to be careful.
Finally, in keeping with the criminal justice theme, we will also discuss what happens after the award is made. That part matters. A lot.
For agencies actively looking for public safety funding opportunities, MAXSUR maintains a Public Safety Grants Resource Center to help identify grant programs and connect funding opportunities to real-world law enforcement missions.
Grants Are Not Shopping Lists
One of the biggest mistakes agencies make is treating a grant like a shopping list.
- “We need a drone.”
- “We need cameras.”
- “We need a surveillance trailer.”
- “We need license plate readers.”
- “We need better communications.”
Those may all be true. But from a grant reviewer’s perspective, the question is not simply whether the equipment would be useful. The question is whether the request is tied to a documented public safety need, an eligible grant purpose, a reasonable budget, and a measurable outcome.
A stronger grant argument does not say, “We want technology.” It says, “Here is the public safety problem, here is the operational gap, here is the mission impact, and here is how this funding will produce measurable value.”
A stronger grant argument sounds more like this:
Our agency is experiencing a documented increase in vehicle theft, narcotics activity, search-and-rescue incidents, special-event security requirements, and officer safety challenges. Current staffing and equipment limitations prevent us from responding with the speed, coverage, and intelligence required. Grant funding would allow us to implement a defined technology and training program that improves response, supports investigations, reduces risk, and creates measurable public safety outcomes.
That is a case.
And that is what grant reviewers need to see.
The goal is not to ask for “stuff.” The goal is to explain why a specific capability is necessary, how it supports the grant’s purpose, how the agency will use it, and how success will be measured.
Start With the Problem, Not the Product
Before you write about equipment, software, training, or technology, write about the problem.
A good grant narrative usually starts with a public safety challenge that is specific, local, and supported by data.
Examples may include:
- Rising property crime in specific neighborhoods
- Increased narcotics activity along a known corridor
- Growth in catalytic converter theft, copper theft, or infrastructure-related crime
- Large event security demands
- Long rural response times
- Search-and-rescue limitations
- Staffing shortages
- Officer safety risks during high-risk entries, barricades, pursuits, or surveillance operations
- Gaps in investigative capacity
- Critical infrastructure vulnerability
- Lack of real-time situational awareness
The more specific the problem, the easier it is to connect the proposed solution.
If the problem is vague, the request feels optional. If the problem is clear, documented, and mission-critical, the request starts to feel necessary.
That is the difference.
Build the Case With Local Data
A good grant application should include a mix of internal and external data.
Internal data is often the most powerful because it tells the local story. This may include:
- Calls for service
- Crime reports
- Arrest data
- Clearance rates
- Response times
- Staffing levels
- Overtime costs
- Mutual aid requests
- Special event deployments
- Officer safety incidents
- Search-and-rescue records
- Narcotics investigations
- Task force activity
- Repeat-location calls
- Geographic hot spots
- Known infrastructure vulnerabilities
External data helps validate the local argument. Useful sources may include the FBI Crime Data Explorer, state crime repositories, census data, county budgets, city budgets, school district data, public health data, transportation data, and emergency management plans.
The FBI’s Crime Data Explorer allows users to explore reported crime and law enforcement data from across the United States. Agencies using NIBRS data may also be able to build more detailed narratives because NIBRS captures incident-level information that can help explain offense type, property loss, arrests, weapon involvement, and other important details.
If you want to go deeper into making your agency more data-driven, we have a related article here: The Data-Driven Department: Internal and External Funding Cases.
Translate the Data Into an Operational Gap
Data by itself is not enough.
A grant reviewer does not just need to know that crime increased or that your agency is busy. They need to understand what that means operationally.
| Data Point | Operational Gap |
|---|---|
| Vehicle theft increased 28% over two years. | Patrol and investigative units lack mobile surveillance tools to monitor high-theft locations without tying up officers for long static deployments. |
| The agency covers 600 square miles with limited deputies on night shift. | Deputies face extended response times and limited situational awareness before arriving on scene. |
| Copper theft and utility vandalism have increased near substations and remote infrastructure. | The agency lacks persistent monitoring and rapid verification tools for critical infrastructure sites. |
| Special events require large security footprints. | The agency lacks mobile overwatch and real-time visibility across parking areas, entrances, perimeter zones, and crowd movement. |
This is where the grant argument starts to come together.
You are not just saying, “We want technology.” You are saying, “Here is the mission gap, here is why current resources are insufficient, and here is how the proposed solution closes that gap.”
For agencies facing infrastructure-related crime, remote site security, or public safety risks around utilities, transportation, or communications assets, MAXSUR’s Critical Infrastructure Protection Solutions page may help frame the mission need.
Match the Solution to the Grant Purpose
Every grant has a purpose. Your application needs to speak directly to that purpose.
If the grant is focused on officer safety, explain how the project reduces unnecessary exposure, improves standoff, gives officers better information before contact, or reduces the need to place personnel in dangerous positions.
If the grant is focused on crime reduction, explain how the project supports deterrence, interdiction, investigations, intelligence gathering, or evidence development.
If the grant is focused on emergency response, explain how the project improves response time, command awareness, search capability, disaster response, or coordination.
If the grant is focused on technology modernization, explain how the project improves operational efficiency, data sharing, accountability, reporting, and long-term capability.
Do not make the reviewer connect the dots. Connect them yourself.
The grant is intended to support [grant purpose]. Our agency’s documented problem is [problem]. Our current operational gap is [gap]. The proposed project addresses that gap by [solution]. The expected outcome is [measurable result].
That is clear. That is reviewer-friendly. And it keeps the application focused.
Build a Budget Reviewers Can Defend
A grant budget should not look like someone copied a quote into the application and hoped for the best.
Every major cost should have a reason.
For equipment, explain:
- What it is
- How many units are needed
- Where it will be used
- Who will use it
- Why the quantity is reasonable
- Why existing resources are insufficient
- Whether training, installation, software, warranty, support, or maintenance are included
- How it supports the project goals
For technology projects, do not forget the support items. Many agencies ask for the “main thing” but forget the pieces that make the main thing operational.
Depending on the project, that may include:
- Mounting hardware
- Installation
- Training
- Connectivity
- Software licenses
- Batteries
- Data plans
- Storage
- Policy development
- Integration support
- Maintenance
- Replacement parts
- Warranty coverage
- Project management
- Reporting support
A good budget narrative helps the reviewer say yes because it shows the request is thought through, reasonable, and tied to the mission.
Show Readiness
Grant reviewers like projects that can actually be implemented.
That means your application should explain who will manage the project, who will use the equipment, what policies are already in place, what training is required, and how quickly the agency can begin.
Readiness may include:
- Command support
- Assigned project lead
- Existing policy framework
- Existing trained personnel
- Procurement experience
- Vendor quotes
- Implementation timeline
- IT or communications support
- Evidence handling procedures
- Community engagement strategy
- Reporting capability
For example, if an agency is requesting surveillance technology, the application should discuss operational controls, deployment procedures, retention practices, and authorized use cases.
If the agency is requesting a UAS capability, the application should discuss pilot training, FAA compliance, policy, maintenance, data management, and mission approval workflows.
If the agency needs specialized mission equipment or covert surveillance capability, it should explain the operational need carefully and professionally. MAXSUR’s Custom Covert Solutions page can help agencies think through how specialized tools support investigations, surveillance, intelligence gathering, and public safety missions.
Define Success Before You Ask for Money
A strong grant application tells the reviewer how the agency will measure success.
This does not have to be complicated. But it does need to be specific.
Examples include:
- Reduction in response time to priority calls
- Number of missions supported
- Number of investigations assisted
- Number of deployments
- Number of officers trained
- Increase in area covered during special events
- Reduction in overtime for static surveillance
- Number of critical infrastructure sites monitored
- Increase in evidence quality or case support
- Improved recovery of stolen property
- Improved ability to locate missing persons
- Improved documentation for prosecution
Avoid vague outcomes like “improve safety” unless you also explain how safety will be measured.
The agency will measure project success by tracking the number of deployments, mission type, response time impact, officer exposure reduction, investigative assists, arrests supported, stolen property recoveries, and after-action findings.
That is much stronger.
How to Use AI to Help Build the Grant
AI can be a major help, especially for agencies without a grant writer. But it works best when you treat it like an assistant, not a decision-maker.
The best workflow is to break the project into small pieces.
Do not start by asking AI to “write a grant.”
Instead, build a working file with:
- The grant solicitation or NOFO
- Eligibility requirements
- Scoring criteria
- Budget rules
- Agency background
- Crime data
- Calls-for-service data
- Budget data
- Staffing information
- Maps or coverage areas
- Quotes
- Product descriptions
- Existing policy language
- Prior successful grants, if available
Then give AI small tasks.
Prompt 1: Summarize the grant requirements
Review this grant solicitation and summarize the eligibility requirements, deadline, funding purpose, scoring criteria, required attachments, budget restrictions, and anything that may make our project ineligible.
Prompt 2: Organize the data
Review the following crime and calls-for-service data. Identify the strongest trends that support a public safety technology grant request. Separate the findings into crime trends, officer safety issues, response challenges, and investigative gaps.
Prompt 3: Draft the problem statement
Using only the data provided, draft a grant problem statement for a law enforcement agency seeking funding for surveillance, response, and investigative technology. Do not invent facts. Flag any missing data that would make the argument stronger.
Prompt 4: Build the project narrative
Draft a project narrative that connects the documented problem to the proposed solution. Organize it into need, project design, implementation plan, training, expected outcomes, and sustainability.
Prompt 5: Act like a reviewer
Review this draft against the grant scoring criteria. Identify weak claims, unsupported statements, missing attachments, budget concerns, and areas where the narrative does not clearly match the grant purpose.
That is how you use AI well.
Small chunks. Clear instructions. Verified data. Human review.
Then, after the pieces are built, you can ask AI to help assemble them into a seamless final narrative.
AI Cautions for Law Enforcement
AI can be useful, but agencies need to be careful.
First, AI can be verbose. It may produce polished language that sounds good but does not actually say much. Grant reviewers do not need fluff. They need clarity, evidence, and alignment.
Second, AI can make mistakes. It may invent statistics, cite programs incorrectly, or assume eligibility that does not exist. Every factual claim should be checked.
Third, security matters. Agencies should be cautious about putting sensitive law enforcement information, Criminal Justice Information, personally identifiable information, investigative details, victim information, suspect information, or protected operational details into public AI tools.
The FBI’s CJIS Security Policy Resource Center provides guidance for protecting criminal justice information. Agencies should follow their own policies, IT guidance, legal requirements, and CJIS-related obligations when using any AI-enabled system.
Use AI for structure, organization, drafting, and review — but do not give it sensitive information unless your agency has authorized the tool and the use case.
When possible, use agency-approved systems, paid business tools with appropriate controls, redacted datasets, aggregated statistics, and non-sensitive summaries.
AI should help you build the grant package. It should not become a data leak, a policy violation, or the source of unsupported claims.
What Happens After the Award Matters Too
Winning the grant is not the finish line.
It is the beginning of the performance period.
After an award, the agency needs to manage procurement, documentation, reporting, inventory, training, deployment, performance tracking, and long-term sustainability.
That may include:
- Following procurement rules
- Keeping quotes and purchase records
- Tracking inventory
- Documenting training
- Maintaining equipment records
- Reporting outcomes
- Tracking grant-funded deployments
- Keeping financial records
- Following retention requirements
- Preparing for possible audit questions
- Ensuring the project is used for the approved purpose
This is another reason the grant application should be realistic. Do not promise outcomes the agency cannot track. Do not propose a project that cannot be sustained. Do not request equipment without thinking through maintenance, training, policy, and reporting.
A good grant is not just fundable.
It is executable.
A Simple Grant Narrative Template
1. Agency Background
Briefly describe the agency, jurisdiction, population served, geography, staffing, and mission.
2. Problem Statement
Describe the public safety problem using local data. Include crime trends, calls for service, response challenges, staffing constraints, geography, and mission risk.
3. Operational Gap
Explain why current resources are insufficient. Be specific about what the agency cannot currently do, cannot do safely, or cannot do efficiently.
4. Proposed Project
Describe the requested solution and how it addresses the problem. Keep the focus on mission outcomes, not product features.
5. Implementation Plan
Explain who will manage the project, how procurement will occur, who will be trained, how the equipment or capability will be deployed, and what policies or procedures will guide use.
6. Budget Justification
List the major cost categories and explain why each is necessary, reasonable, and tied to the project.
7. Outcomes and Evaluation
Define how success will be measured. Include activity metrics, operational metrics, and public safety outcomes.
8. Sustainability
Explain how the agency will maintain the capability after the grant period ends.
Final Thought
If you are in law enforcement, you already understand how to build a case.
A grant application is simply a different kind of case file.
You identify the problem. You collect the facts. You establish the operational gap. You connect the solution to the mission. You justify the resources. You explain the expected outcome. Then you present it in a way that allows the reviewer to understand it, defend it, and award it.
The agencies that do this well are not always the largest agencies. They are not always the agencies with the most polished writers. They are the agencies that clearly explain why the project matters, why the need is real, why the plan is executable, and why the funding will produce measurable public safety value.
Need Help Finding Public Safety Grant Opportunities?
For agencies looking for grant opportunities, public safety technology ideas, or help thinking through mission-driven solutions, visit MAXSUR’s Public Safety Grants Resource Center.