There is no shortage of HOTMA explainers. This is not another one. Your PMS vendor will ship the calculation changes, your state association will run the training, and NAHRO and PHADA have both covered the rule in more detail than we can here.
What nobody is covering well is the operational load — the work that sits between "the software supports it" and "our files are actually ready." That work is significant, it is mostly not software, and there are now under six months of processing time before it starts to matter.
The dates, precisely
From Notice PIH 2026-15, issued May 14, 2026:
- Starting January 1, 2027, HUD will enforce compliance with sections 102 and 104 of HOTMA for all PHAs.
- For PHAs subject to that deadline, all Form HUD-50058 transactions with an effective date of January 1, 2027 or later must be HOTMA-compliant.
- Exceptions: PHAs in the Moving to Work demonstration, and PHAs currently using only the HUD Family Reporting Software. For those, HUD will enforce once it completes certain systems modifications.
- The notice partially supersedes Notice PIH 2024-38. The July 1, 2025 compliance deadline for the provisions identified in that notice is not altered.
Note the phrasing on the main deadline: it is keyed to the effective date of the transaction, not the date you process it. That is the detail that determines your real timeline. An annual reexamination with a January 1, 2027 effective date is worked in the fall of 2026 — under HOTMA rules, with HOTMA data, months before the enforcement date itself.
If your recert cycle sends notices 90 to 120 days ahead, the households whose reexaminations must be HOTMA-compliant are being contacted this quarter.
What actually changes for your staff
Broadly, section 102 reshapes how income is reviewed — including the rules governing when an interim reexamination is required versus discretionary, safe harbor verification from other means-tested programs, and changes to deductions including the medical and disability expense threshold. Section 104 introduces asset limitations and changes when income from assets must be imputed rather than counted, along with self-certification below a threshold.
The mechanics are in HUD's guidance and we would rather point you there than paraphrase indexed dollar figures that change. What matters here is the shape of the operational consequence, and it comes down to three things:
- You will need data about households that your files do not currently contain, particularly around assets and real property interests.
- You will need written policy decisions in your administrative plan on the points HOTMA leaves to PHA discretion — including hardship exemptions and thresholds.
- Some households' rent will change, and some will be surprised by it. That lands on your phone line.
The data gap is the part to start on now
This is the item that takes longest and that nobody starts early enough.
Do this in the next two weeks: pull a sample of 50 active files across your programs. For each, check whether it currently contains the household-level information a HOTMA-compliant transaction will require — asset details at the level of specificity the new rules assume, real property interest, and the documentation supporting deductions under the revised thresholds.
Then count what is missing.
Whatever fraction that is, apply it to your total caseload. That number is your actual project: it is a household-by-household collection effort, and each one is an outreach, a document, a follow-up, and probably a phone call.
We have said elsewhere on this blog that PHA file data is worse than anyone's plan assumes — on one authority's imported applicant records we found zero out of 112 with a usable date of birth. Asset detail is scarcer than that. Assume you are collecting, not confirming.
The policy decisions need board time, and board calendars are slow
Where HOTMA gives the PHA discretion, someone has to decide and write it down. Count backward from the December board meeting and the deadlines are tighter than they look — a September or October adoption is realistic; a December one leaves no room for a revision cycle.
The decisions to get on an agenda:
- Hardship exemption policies and procedures — how a family requests one, what you require, how you document the determination, and how it is reviewed.
- Interim reexamination policy — the thresholds you adopt where HOTMA permits discretion, and how you handle income decreases versus increases.
- Asset verification and self-certification procedures — what you accept, when you require third-party verification, and how you document it.
- Your phase-in and transition approach for households affected by deduction changes.
- Notification language and timing for households whose calculation changes.
Each of these also needs staff procedure written under it, which is a separate piece of work from the policy language, and the one most likely to be skipped.
Budget for the phone line in Q1 2027
Here is the operational consequence nobody puts in a project plan: a meaningful share of your households will see a change in their calculation, and every one of those who does not understand the letter will call.
Think about what that looks like in January and February of 2027. Your specialists are working a normal recert cycle under a new ruleset, with new data requirements, while the phone line runs at multiples of normal volume because of notices they themselves sent. That is the crunch, and it is completely predictable today.
Three things reduce it materially, and all of them are cheap if done in advance:
- Rewrite the notice before you send thousands of them. Plain language, name the specific change, state what the household needs to do, and give a single clear next step. Have someone outside the housing field read it.
- Translate it properly into your top two non-English household languages — not machine-translated regulatory prose, which produces more calls than it prevents.
- Prepare the answers before the calls. Write out the five questions you know are coming, agree the answer to each, and make sure every person who might pick up the phone — including the AI agent, if you run one — gives the same answer.
That last point is not incidental. If a call system cannot answer "why did my rent change" from the household's own case file, every one of those calls becomes a specialist interruption during your busiest quarter in years.
A calendar that works backward
August–September 2026. Run the 50-file data gap sample. Size the collection effort. Draft admin plan revisions. Confirm with your PMS vendor, in writing, which HOTMA changes ship in which release and on what date.
October–November 2026. Board adoption of policies. Staff procedure written and trained. Start collecting missing asset and deduction data on households whose reexaminations fall early in 2027. Rewrite and translate the notices.
December 2026. Test a HOTMA-compliant 50058 transaction end to end through your system of record, before you need it to work. Confirm submissions are accepted. Identify who owns the submission error queue — by name.
January–March 2027. Protect specialist capacity. Anything you can take off the phone line in advance, take off it.
Where we fit
We are not a compliance consultancy and will not pretend to be. What we do is the collection and preparation load — the outreach, the document chasing, the income extraction and EIV reconciliation, and a prepared packet that your specialist reviews once and approves.
For HOTMA specifically, the relevant part is that when the required fields change, the collection workflow changes with them, and the AI does the chasing rather than your staff. Your specialists still make every determination. Nothing about eligibility, income, or rent is finalized by software — that is not just our compliance position, it is the reason the tool is usable in a HUD-regulated process at all.
If you want to see what your caseload looks like run through that workflow, with your files, before the deadline gets close, that is what a demo is for.
Nothing here is legal or compliance advice. Read Notice PIH 2026-15 and HUD's HOTMA guidance directly, and confirm your specifics with your field office.