"Is this site out of the floodplain, is it actually zoned for what we want to build, and can the environmental review get done before we file?"
What the screen looks like before you can even file
There is no separately named diligence phase in an Arkansas deal any more than there is in California's or Texas's. Reading the Arkansas Development Finance Authority's (ADFA) own Qualified Allocation Plan and its attached Multifamily Housing Application Guidelines makes clear how much of this phase's "screening" is threshold-requirement compliance work wearing a different hat. Over roughly two to six weeks, a developer or analyst works through the following before the Multifamily Housing Application (MFHA) can even be assembled.
| Step | What it involves |
|---|---|
| County assessor record | Pull the parcel's record from the county's own CAMA system, cross-checked against the Arkansas GIS Office's statewide Parcel Polygon layer |
| Zoning-or-not | Determine whether the site sits inside a municipality with an adopted zoning ordinance, inside a county that has established a planning board and zoning ordinance for its unincorporated area, or in neither — then get a signed zoning letter dated within six months of the deadline |
| Floodplain | Check FEMA flood — a 100-year floodplain or floodway is an outright bar for new construction, "no exceptions" |
| Environmental review | Commission and complete, not merely order, an EA or CEST-level review by a qualified environmental professional before the application is submitted |
| Site Selection distances | Measure driving distance by Google Maps to nine categories of amenity, and check for incompatible uses nearby, for up to 27 scoring points |
| Area of Opportunity Index | Look up the site's census tract score — unemployment, vacancy, population growth — on ADFA's own ArcGIS tool, worth up to 10 points |
| Income limits and rents | Pull HUD's own Multifamily Tax Subsidy Project (MTSP) limits directly; ADFA does not republish its own tables |
| Cost anchor | Check this year's per-unit federal credit limits and, for a 4% bond deal, the $300,000 total-development-cost-per-unit ceiling |
| Comparable awards | Read the current year's LIHTC-recipients PDF and prior years' rosters back to 2005 for nearby awards and rehabilitation-deduction exposure |
Roughly half of that list is arithmetic and lookups; the other half is paperwork with a clock attached to it.
As in California and Texas, two decisions come out of this phase: whether to pursue the site, and what goes into the option or contract. Arkansas's own twist on the second decision is date-shaped rather than price-shaped. The site control instrument has to run, without extension fees, to a fixed calendar date — not to expire prior to December 6 of the year of the MFHA (Application Guidelines § I(C)(4)) — tied to the following year's carryover cycle rather than a rolling term counted from signing.
One more timing fact worth building into an Arkansas calendar. This is a single-regulator program — ADFA alone, not California's three-way CTCAC/CDLAC/HCD split — but the QAP still moves on its own annual clock, and the clock is not always finished when the document is posted. The version on ADFA's site as of this research, the "2027 QAP" uploaded in September 2026, carries a blank Board-adoption signature block; the prior year's file is both named and signed as executed. Until ADFA republishes a signed version, its point values and thresholds are best treated as the working draft ADFA staff are using, not a locked document.
Zoning is permissive twice over, and the letter assumes it exists
Arkansas's zoning story splits differently from both California's — every one of 539 jurisdictions zones, vintage is the problem — and Texas's, where counties categorically cannot zone at all. In Arkansas, both municipal and county zoning are optional powers a governing body may choose to exercise, not a duty imposed on it. A municipality's governing body may adopt a zoning ordinance under Ark. Code Ann. § 14-56-416; nothing in that section compels it to. The same permissive structure runs one level up: under §§ 14-17-203 and 14-17-209, a county judge may appoint a county planning board, which may in turn prepare and adopt a zoning ordinance for all or part of the county's unincorporated area — but until a county actually does that, its unincorporated land carries no zoning classification to look up, by design, not by data gap.
| Municipal population | Jurisdictional distance beyond corporate limits |
|---|---|
| 8,000 or fewer | None — the municipality may not exercise zoning authority outside its corporate limits |
| 8,000 – 60,000 | 1 mile |
| 60,000 – 150,000 | 2 miles |
| Over 150,000 | 3 miles, and it cannot reach into a neighboring county without that county's and its cities' consent |
Ark. Code Ann. § 14-56-413.
A parcel a half mile outside a mid-size city's limits can sit inside that city's planning and zoning reach even though it reads as "unincorporated" on a plat. The reverse also holds: a parcel outside every municipality's reach, in a county that has never created a planning board, is genuinely unzoned. The QAP's own zoning-letter requirement doesn't spell out what satisfies it in that case. Unlike Texas's QAP, which names a specific "No Zoning Ordinance in Effect" letter type for exactly this scenario, Arkansas's Application Guidelines ask only for "a signed letter... from the appropriate zoning authority... stating... the property is properly zoned for such proposed use" (§ I(C)(5)) — text that assumes an authority and an affirmative zoning designation both exist to certify.
Arkansas has 75 counties and roughly 500 incorporated cities and towns as of the 2020 Census, each independently deciding whether to exercise the zoning power at all — a different failure mode from California's amendment-vintage problem, but the same practical result for a screening tool: the answer to "what does the code say" is sometimes "there is no code."
The parcel layer is one live service, with real seams
Arkansas's county assessors operate under the statewide oversight of the Arkansas Assessment Coordination Division, a division of the Department of Finance and Administration that supervises assessors and equalization boards and runs a statewide reappraisal-cycle and ratio-study program. What that buys a screening tool is closer to California's aspiration of one statewide layer than California itself has achieved: a single, live, statewide parcel service, published by the Arkansas GIS Office and built from the counties' own Computer Aided Mass Appraisal systems through the County Assessor Mapping Program (CAMP).
| Fact | Detail |
|---|---|
| Records | 2,117,780 parcel polygons, queried directly from the service's statistics endpoint, spanning all 75 counties |
| Product-page coverage claim | States "73 of 75" counties; a live groupBy query against the same service returns records for all 75 — a real discrepancy worth flagging rather than resolving silently |
| Coordinate system and paging | NAD83 UTM Zone 15N (EPSG:26915), not WGS84; maxRecordCount 200, so a full-county pull needs many sequential 200-record requests |
| Legal status | Carries the disclaimer that the data is "for real estate ad valorem tax valuation, research and assessment purposes only, and is not considered a legal boundary" |
| Attributes | 39 fields including owner name, mailing address, assessed/land/improvement value, subdivision, and Section-Township-Range — richer than California's stripped-down 2014 statewide snapshot, which carries essentially the parcel number alone |
Vintage tells the same story California's Riverside zoning layer tells, on a different layer. The whole service's own "last updated" metadata reads a single date, April 1, 2026 — but the underlying camadate field, each county's own CAMA extraction date, actually ranges from September 24, 2025 to March 17, 2026. A roughly six-month spread of real county-level currency sits hidden behind one republish stamp.
Floodplain is an absolute bar, and the environmental review comes before the filing, not after
Arkansas does not treat floodplain risk as a scoring factor or a mitigation queue the way California's SB 35 exclusion list or Texas's Undesirable Site Feature buffers do. It is a flat threshold requirement, stated without qualification: "No federally designated 100-year floodplain or floodway sites allowed. ADFA will not fund any project on a parcel that contains a 100 year floodplain or floodway... No exceptions" (Application Guidelines § I(C)(4)). An existing, operating affordable housing development already inside a floodplain can still apply for acquisition or rehabilitation, but only if it has not flooded since construction and carries flood insurance for the full affordability period — new construction has no comparable path. HOME- and NHTF-funded developments layer a second federal standard on top, the Federal Flood Risk Management Standard.
ADFA's own January 26, 2024 memorandum adds a timing requirement with no direct California or Texas analog: the environmental review itself — not merely an order for one — has to be complete, performed by a qualified environmental professional, before the MFHA is submitted. New construction of more than four units, or rehabilitation that doesn't meet the narrow categorical-exclusion criteria at 24 CFR § 58.35(a), needs a full Environmental Assessment; smaller or more limited rehabilitation needs the lighter Categorically-Excluded-Subject-to-§58.5 (CEST) review instead. Either way, the review has to be finished pre-submission, and the requirement applies to every Tax Credit applicant, not only ones layering in HOME or National Housing Trust Fund money.
| Layer | What was found |
|---|---|
| ADEQ Brownfields Program viewer | A public, unauthenticated ArcGIS REST feature service; a direct query returned 7 active and 54 completed sites |
| EnviroView (fuel storage tanks, solid waste, hazardous waste generators) | Published by ADEQ as an ArcGIS mapping app; not independently tested for open query access in this research |
| MethViewer (former methamphetamine-contaminated properties) | A distinctly Arkansas hazard layer with no counterpart in either California's or Texas's own guide; also not independently tested for open access |
| FEMA National Flood Hazard Layer | The same public, unauthenticated federal layer used in every state |
Absence of a hit on the layers actually queried here says nothing about the ones this research didn't have time to test — the same caution California's own screen draws about DTSC and SWRCB.
Site Selection is 27 points of measured distances, and Location is another 10
Unlike California's Opportunity Area designation or Texas's Neighborhood Risk Factor gates, Arkansas folds location quality into one self-contained scoring item. "Location" is worth up to 10 points, computed by ADFA itself for every census tract from three inputs — unemployment rate, vacancy rate, and population growth — published on ADFA's own ArcGIS Experience app and re-versioned annually (the current QAP calls this release "AOI 2027"). ADFA does the calculation; a developer only has to look the number up (Application Guidelines § II(A), Item 1).
| Component | Detail |
|---|---|
| Qualifying amenities, 3 points each, no stated cap on how many can be claimed | Grocery/supermarket, pharmacy, school/daycare (not for 100%-elderly developments), public park/green space, public library, senior center (elderly-only developments only), hospital/clinic/GP office, public transportation, pedestrian trail access |
| Distance rule | Within 3 miles for an urban site, 5 miles for a rural site; rural status is determined by USDA Rural Development's own eligibility tool, not an ADFA-specific definition |
| Distance measurement | Shortest driving distance by Google Maps, referenced in the market study's own map, each amenity backed by a named contact and phone number |
| Nearby occupied units | 3 more points if at least four residential units sit within 0.5 miles of the site boundary and are occupied as of the deadline |
| Incompatible-use deductions | -3 points for an adjacent incompatible use; -2 points for one within 0.3 miles measured "as the crow flies" — junkyard/dump/solid waste, pig or chicken farm, prison or jail, airport; "there is not a limit on the total number of points that can be deducted" |
A Qualified Census Tract location is worth exactly one Arkansas scoring point, and only if it's paired with a documented community revitalization plan that specifically addresses affordable housing (Application Guidelines § II(A), Item 12) — a far smaller in-QAP reward than California's opportunity-area mechanics. The number that actually matters for a QCT site sits outside ADFA's own point table entirely: the federal 130% eligible-basis increase under 26 U.S.C. § 42(d)(5)(B), which applies automatically regardless of anything ADFA scores. A QCT location also moves a project up Arkansas's own State LIHTC tie-breaker priority order, behind counties in the state's job-creation incentive Tiers 3 or 4 and ahead of counties without a recent federal LIHTC award (2027 QAP § IV).
None of this location math matters if the application can't clear ADFA's own floor: a minimum self-score of 75 points to apply for 9% credits, or 45 points for Bond Volume Cap/4% credits, stated flatly as "No exceptions" (Application Guidelines § I(C)(31)). The QAP's own scoring table leaves its "Total Points Possible" cell blank; summing each item's own stated maximum gives 99, but that is this guide's arithmetic on the published numbers, not an ADFA-stated ceiling — several point categories are mutually exclusive alternatives no single project could actually stack together.
Where the screen stops, and what it cannot tell you
| Item | Detail |
|---|---|
| 2027 per-unit 9% credit limit | $19,365 (0-1BR) to $23,100 (4BR) for new construction; $13,285 to $18,480 for acquisition/rehabilitation — recalculated annually (2026's figures were $18,700-$22,000 new construction and $12,650-$17,600 acquisition/rehabilitation, so the dollar level moves year to year) |
| 4% bond total development cost cap | $300,000 per unit, with ADFA retaining separate discretion to deny an application on cost reasonableness even under that ceiling |
| Total Development Costs Per Unit scoring | Up to 15 points below $210,000/unit, phasing down to 0 points above $260,000/unit for 2027 — up $10,000 at every threshold from the 2026 QAP's $200,000-$250,000 bands, so this scoring anchor also moves year to year |
None of these figures is a construction-cost estimate any more than California's Threshold Basis Limits are; they cap what ADFA will fund or reward, and say nothing about what a general contractor will actually quote for a given site.
ADFA's own award history is a real gap next to California's single combined List_of_Projects.xlsx or even Texas's per-round XLSX file. Each year since 2005 gets its own PDF roster — the 2026 9% round shows 12 developments awarded — with applicant, developer, county, congressional district, unit counts, and federal/HOME/NHTF dollar amounts, but no parcel identifier, no census tract field, and no spreadsheet to query across years. ADFA describes its annual 9% program as roughly $9 million in federal credit authority; the QAP itself caps any single 9% development at $1,300,000 of that annual ceiling (2027 QAP § III(C)).
One genuine simplification relative to California: ADFA does not publish its own income-and-rent-limit PDFs the way CTCAC does. Applicants read HUD's own Multifamily Tax Subsidy Project (MTSP) limits directly — a screening tool built for Arkansas doesn't need to solve CTCAC's three-vintage PDF problem at all, because there is no ADFA-specific layer standing between the site and HUD's own published numbers.
The honest limit is the same one California's and Texas's own guides draw. Whether the seller actually holds the option to December 6, whether a county that has never adopted a zoning ordinance will issue a letter ADFA will accept, whether a competing application is filing in the same round — none of that is a dataset, and none of it should be synthesized. What screening can and should do in Arkansas is make sure the arithmetic questions are answered before the phone call: floodplain status, the Site Selection and Location point math against the 75-point floor, and whether the environmental review can realistically finish before the deadline. EZFeasi has no Arkansas parcel, zoning, hazard, or award data loaded today — this entire phase is greenfield product work, not a refinement of an existing Arkansas feature.
Where this goes wrong
- Treating the QAP's zoning letter requirement as assuming the answer is yes. Item I(C)(5) asks for a letter stating the property "is properly zoned for such proposed use," but both municipal and county zoning are permissive under Arkansas law (§§ 14-56-416, 14-17-209) — a real share of Arkansas land, especially unincorporated county land, has no zoning ordinance to be properly zoned under, and the Guidelines never say what letter satisfies the requirement when that's the honest answer.
- Reading the site-control expiration date as flexible. Item I(C)(4) requires the option or contract to run, without extension fees, to a date not before December 6 of the MFHA year — a contract structured around a rolling term or a generic closing date rather than that specific calendar date will fail threshold.
- Ordering the environmental review after picking a site rather than before submitting the application. ADFA's January 26, 2024 memo requires the EA or CEST review to be complete, using a qualified environmental professional, before the MFHA is filed — not merely commissioned, and not deferred to post-award the way many states run it.
- Assuming the floodplain rule has a discretionary override. The QAP calls a site's 100-year floodplain or floodway status a bar for new construction and says "No exceptions" in the same sentence — there is no Executive-Director-style waiver in the text the way California's tiebreaker discount has one.
- Trusting the parcel service's product-page coverage claim over the live endpoint. The Parcel Polygon page reads "73 of 75 counties"; a direct groupBy query against the same FeatureServer returns records for all 75. Building an ingestion assumption on the page copy instead of testing the service would undercount counties that are actually present.
- Assuming a maxRecordCount of 200 on the statewide parcel service is a documentation footnote rather than an operational constraint. At roughly 2.1 million statewide records, a naive single-page pull for a populous county will silently return a fraction of its parcels, the same failure mode as California's SanGIS story on a different endpoint.
- Reading the parcel layer's single "last updated" stamp as one vintage for every county. The underlying CAMA extraction date actually ranges about six months across counties, hidden behind one republish date on the service's own metadata.
- Measuring Site Selection amenity distances as the crow flies. The QAP wants driving distance by Google Maps for the amenity side of the table; "as the crow flies" is reserved specifically for the incompatible-use deduction on the other side of the same item.
- Assuming the incompatible-use point deduction has a floor. The QAP states plainly that "there is not a limit on the total number of points that can be deducted" for site selection — a site near several flagged uses can lose more points than the site's amenities could ever earn back.
- Assuming a Qualified Census Tract location earns meaningful QAP points on its own. It earns exactly one point, and only paired with a documented community revitalization plan — the real value of a QCT site is the federal 130% eligible-basis increase under 26 U.S.C. § 42(d)(5)(B), which is independent of anything ADFA scores.
- Benchmarking a target score against a published maximum. The QAP's own points table leaves "Total Points Possible" blank in the current document, and several categories are mutually exclusive alternatives that can't be stacked — the number that actually gates an application is the stated 75-point minimum for 9% credits, not a computed ceiling.
- Treating the currently posted QAP as the Board's final, adopted document. As posted in September 2026, the 2027 QAP's adoption signature block is blank; the prior year's file is both named and signed as executed. Point values and thresholds in an unsigned QAP should be treated as a working draft.
- Using the annual LIHTC-recipients PDF as a queryable comps database the way California's or Texas's spreadsheet-based award files can be used. Each year is a separate PDF roster with no parcel identifier and no census tract field — closer to reading a printed list than querying a table.
- Assuming ADFA publishes its own income-and-rent-limit tables the way CTCAC does. It doesn't — applicants read HUD's own Multifamily Tax Subsidy Project limits directly, so a screening tool that expects an ADFA-branded PDF to parse will find nothing to parse.
- Assuming per-unit credit limits and Total Development Costs Per Unit scoring bands hold steady year to year. Both moved between the 2026 and 2027 QAPs -- the 9% per-unit credit ceilings rose (e.g. new-construction 4BR from $22,000 to $23,100), and every Total Development Costs Per Unit scoring threshold shifted $10,000 higher (the top band moved from under $200,000 to under $210,000) -- a tool that hardcodes either from one year's QAP will misscore the next round.
- HUD
- LIHTC
- State QAPs
- IRS § 42
- Housing Finance Agencies
