Automated Permitting Systems Demonstration NOFO
This cooperative agreement funds jurisdictions to deploy automated building code permitting systems and evaluate their real-world performance, costs, and effects in government permitting environments.
RESTRICTED TO: STATE LOCAL GOV
⚑ Eligibility is limited to jurisdictions; individuals, foreign entities, and sole proprietorships are ineligible. · Funds deployment plus evaluation in real operating conditions, not general research. · Cooperative agreement implies HUD substantial involvement.
Unit fits — one characterization, each unit's own rules
| IPPRA | 15 none | university cannot apply directly (ineligible) |
| Tom Love Innovation Hub | 15 none | deep-tech content; no commercialization signal |
| Physical Sciences & Engineering (demo) | 15 none | university cannot apply directly (ineligible) |
Description
The Automated Permitting Systems Demonstration NOFO is intended to support jurisdictions that will deploy automated building code permitting systems and partner with HUD to evaluate their applicability and effectiveness within real-world operating conditions. This demonstration will test the real-world deployment of an automated permitting platform within a government permitting environment to evaluate its effects on processing timelines, workflow efficiency, staff roles, and applicant experience. The demonstration will generate empirical evidence on operational performance, costs, governance needs, and potential cost savings to inform broader adoption by state and local jurisdictions.
Eligibility
Individuals, foreign entities, and sole proprietorship organizations are not eligible to compete for, or receive, awards made under this announcement.
Apply
View on Grants.gov → CONTACT: Department of Housing and Urban Development <researchpartnerships@hud.gov >
Proposal brief SEE AN EXAMPLE →
A one-page internal memo: fit assessment, submission requirements, document scaffold, and next steps dated back from the deadline — tailored to your project idea if you add one.
Proposal shell · Federal (generic) conventions SEE A FEDERAL EXAMPLE →
Funder-faithful document skeletons — Federal (generic)'s document set with section headings, page limits, reviewer guidance, and writing prompts; add a project idea to get [DRAFT] starter bullets. Download as .md for Word or Overleaf.
Legacy IPPRA LLM assessment (v2.0, for comparison)
55/100 · gpt-5.4-mini · 2026-07-06
This is a public-sector demonstration/evaluation opportunity focused on permitting systems, governance, costs, and applicant experience, so it has a real research/evidence-generation component rather than pure service delivery. The topical fit is only partial for IPPRA: it touches environmental/building policy and public administration, but it is not centered on one of IPPRA’s core human-behavior domains or a primary portfolio area. Public jurisdictions and likely public research partners can participate, so eligibility is not a barrier, but the opportunity is more technical/operational than a strong social-science fit.
Legacy scoring history
| 2026-07-06 | 55 | gpt-5.4-mini | This is a public-sector demonstration/evaluation opportunity focused on permitting systems, governance, costs, and applicant experience, so it has a real research/evidence-generation component rather than pure service delivery. The topical fit is only partial for IPPRA: it touches environmental/building policy and public administration, but it is not centered on one of IPPRA’s core human-behavior domains or a primary portfolio area. Public jurisdictions and likely public research partners can participate, so eligibility is not a barrier, but the opportunity is more technical/operational than a strong social-science fit. |
| 2026-07-06 | 55 | gpt-5.4-mini | This is primarily a public-sector operations and policy evaluation opportunity around automated building-code permitting, with a strong social/behavioral component in applicant experience, staff roles, governance, and adoption impacts. IPPRA could contribute to the human-systems and program-evaluation aspects, but the topic is only indirectly connected to its core portfolio areas rather than a direct technical match. Public universities are eligible as non-excluded entities, so there is no eligibility cap issue. |