Resident files that hold up under a HUD review.
Move-in, unit transfer, and move-out are three separate transactions with three separate document sets. ETR keeps them attached to the same LIPH household file instead of scattered across a resident's tenancy.
A resident's tenancy is not one event. The file should not treat it that way.
A public housing resident's tenancy runs through several distinct transactions: the original move-in inspection and lease-signing, any unit transfer requested for accessibility or household-size reasons, and eventually a move-out inspection and account settlement. Each of these carries its own forms, inspection reports and approvals. ETR attaches every one of them to the same resident household file, in the order the events actually happened.
What the resident file tracks
- Move-in inspection reports, lease documents and unit-condition photos
- Transfer requests, approvals and updated lease paperwork
- Grievance and reasonable-accommodation records, access-restricted by role
- Move-out inspection findings and final account documentation
Why this matters at review time
When a HUD reviewer or an internal auditor pulls a resident's file, the question is rarely about a single document. It is about the sequence: did the move-in inspection happen before occupancy, was the transfer properly approved, does the move-out paperwork match the unit's condition report. Because ETR keeps every transaction inside the same household file in order, staff can answer that sequence question by opening one record instead of searching three shared drives and a filing cabinet.
ETR is not a property management or accounting system. It holds the resident documentation and evidence layer alongside whatever system your authority already uses to track rent and unit assignments.
Other household-file surfaces inside ETR.
Bring a redacted resident file. See it organized in ETR.
A 30-minute session walking through your own LIPH documentation.