Ask any caseworker why a household's rent changed and they will open Elite, OnSpring, or SACS. The screen displays an income figure, an effective date, and a calculated rent. Case closed. Then somebody, perhaps a hearing officer, legal aid, or a HUD reviewer, says "show me," and the agency learns that the screen is a witness, not the record.

PHA software is good at formal coherence. It catches broken date sequences, blank required fields, and transactions that do not fit the workflow the vendor imagined. It is much worse at detecting a thin file, stale verifications, an unsigned 9886, or income that was countable on paper but not in fact. A 50058 that passes HUD's data edits proves only that the record was internally consistent. It does not prove the documents in the cabinet supported the entry. "Our system indicates" is a weak sentence because it summarizes nothing more than what the agency wrote down for its own convenience.

The hierarchy that staff and software both forget is that the tenant file is the proof layer and the software is the production layer. The signed 9886, pay stubs from the correct period, SSA letters, EIV reports, and the rest of the documentary record are what support the judgment. The software stores the abstraction that follows the judgment. When that order reverses, and the screen is consulted as if it were evidence, neat entries start receiving the respect that belongs to sound casework. Scanning weak files into a document management system does not fix this. It produces searchable weak files.

The remedy is dull and durable. Define what each file must prove. Build SOPs that say what evidence must be present before a transaction moves. Run QC on a sample before HUD or a tenant's attorney does. Train staff to reach the judgment before they touch the keyboard. None of this is exciting, which is partly why vendors prefer to sell storage. Our operational assessments, SOP development and file digitization work all begin in the same place: when somebody says, "show me," what can the file actually prove?

Ask any housing professional whether a public housing resident may simultaneously hold a second federal housing subsidy and you will get an immediate, confident no. Ask for the regulation and the conversation stalls. That is because, for the LIPH program, no such regulation exists. Part 960 does not prohibit it. Part 966 does not prohibit it. The US Housing Act of 1937 does not prohibit it. The HCV program has an express regulatory ban at 24 CFR § 982.352(c), but HUD never wrote a corresponding rule for public housing. It simply never got around to it. 

What LIPH has instead is an enforcement architecture that assumes the prohibition without stating it. The EIV mandate at § 5.233(a)(2) requires PHAs to search for duplicative records. Notice PIH 2018-18 operationalizes that search. The new Public Housing Occupancy Guidebook titles the relevant section "Avoiding Duplicate Subsidy," but describes only the search procedure, not the rule it is meant to enforce. HUD's Multifamily Handbook (4350.3) comes closer, declaring that the assisted unit "must be the family's only residence," but it governs a different program entirely and cites no authority for the claim. Everybody knows the rule. It's implied in a PHA's duty as a fiduciary of HUD funding. But HUD didn't write it down.

None of this means a PHA should test the theory. HUD enforces rules it never codified with the same conviction as those it did; no family will successfully carry two subsidies, codified prohibition or not. But the gap matters where precision counts: in an ACOP that attempts to answer every requirement the program imposes, and in the termination hearing where a resident's attorney will ask which regulation the family actually violated. The answer: a Notice, a Guidebook heading, and the structural logic of the program…is defensible but uncomfortable.

At ProjectLogic we find this sort of thing interesting, perhaps more than HUD does. If you would rather have that instinct working for you than against you, we should talk.