QuorumFile

The Clarksville Housing Authority (TN010)

The Clarksville Housing Authority (HUD participant code TN010, Clarksville, TN) runs low-rent housing across 504 units, so the HOTMA section 102 and 104 elections have to be recorded in its Admissions and Continued Occupancy Policy (ACOP). HUD enforces from January 1, 2027.

What HUD's record says

  • HUD participant code: TN010
  • Programs run: Low-Rent
  • Units on HUD's record: 504 (Medium High (300-999))
  • Fiscal year end: 9/30
  • Elections are recorded in: Admissions and Continued Occupancy Policy (ACOP)
  • HUD enforces HOTMA from: January 1, 2027
  • PHAS designation: High Performer

Every row above is read from HUD's Public_Housing_Authorities layer, the same source the free Decision Sheet reads. Nothing here is an assessment of this agency.

Which HOTMA elections this agency has to record

HOTMA sections 102 and 104 leave a set of decisions to the PHA rather than making them nationally, and a decision a PHA is allowed to make is one it has to write down. The Clarksville Housing Authority runs low-rent housing, so 17 of the catalogue's elections apply to it, 4 of which require a written policy rather than a choice recorded in passing. They belong in Admissions and Continued Occupancy Policy (ACOP). The full catalogue, each election with its CFR citation lists them with the regulation's own words beside each one.

The dates this agency is working back from

HUD enforces HOTMA from January 1, 2027. Adoption is not a single act on that date: the document has to be publicly available and noticed not later than 45 days before the public hearing that adopts it, the hearing has to happen, and the board has to adopt it at a meeting open to the public. The adoption procedure, in order sets out each step with the rule that fixes it.

This agency's fiscal year ends 9/30, so its next fiscal year begins October 1, 2026. An Annual Plan is due to HUD no later than 75 days before the start of the fiscal year (24 CFR 903.5(b)(3)), which puts that date at July 18, 2026. That is arithmetic on HUD's own fiscal-year-end field, not a date HUD publishes for this agency, and it applies only if this agency has to submit an Annual Plan at all.

Two things that could take this agency off that clock

PIH 2026-15 exempts MTW demonstration PHAs and PHAs filing exclusively through HUD's Family Reporting Software. HUD's layer does not list this agency as MTW, and that layer has been stale since 2018, so its silence is not proof either. FRS participation is not published in any filterable form at all, which is why no page on this site will tell you whether you are exempt. The Decision Sheet asks you both questions before it computes anything.

A second one worth checking: HUD's record puts this agency at 504 units, which is at or under the 550-unit line in the qualified-PHA definition. A qualified PHA is exempt from submitting an Annual Plan under 24 CFR 903.3(c), which removes the date above without removing the elections. The definition also requires that the agency is not designated troubled, and it counts public housing units and section 8(o) vouchers together, which is not what HUD's unit field on its own tells you. What changes for a qualified PHA works through it.

Run the free Decision Sheet for this agency

Open the Decision Sheet with TN010 already filled in. It asks the two exemption questions first, then lists every election scoped to the programs this agency runs, each with its citation and the regulation's own wording, and builds a backward timeline from a public hearing date you supply. It is free, needs no account, and is yours whether or not you buy anything.

Having the policy written

QuorumFile writes the HOTMA language into Admissions and Continued Occupancy Policy (ACOP) and hands back the adoption record that goes with it. For an agency in this configuration that is $99, charged once. One document, so the single-document price applies. What the pack contains shows the sections it writes, and where each one comes from names the regulation behind every clause.

Other TN agencies of about this size

Same state, comparable unit count. Size decides whether an agency is on the Annual Plan path at all, so agencies near each other on that axis are working to the same calendar.

Where these figures come from

The participant code, formal name, program type, unit count, size band, PHAS designation and fiscal year end are HUD's own Public_Housing_Authorities layer. The election catalogue and every citation on this page come from the regulations themselves and are the same records the paid pack is written from, so a citation cannot differ between the free page and the document. The Annual Plan date, where one is shown, is arithmetic on HUD's fiscal-year-end field and is labelled as derived rather than published.