Inspection evidence organized before NSPIRE asks for it.
Photos, reports and corrective-action records for every unit, filed against the household as soon as the inspection happens, not weeks later when a reviewer requests them.
NSPIRE asks what happened at the unit, not just whether it passed.
An NSPIRE inspection produces more than a score. It generates photographs of specific deficiencies, a written report, a corrective-action plan, and eventually a re-inspection or work order confirming the fix. Loose photos on a phone and a PDF report saved to a shared drive make that trail hard to reconstruct months later. ETR files all of it against the unit and household as the inspection happens.
What the inspection file tracks
- Inspection reports and deficiency-level findings, by unit and standard
- Photo evidence attached to the specific deficiency it documents
- Corrective-action plans, work orders and completion confirmation
- A timestamped history across multiple inspection cycles for the same unit
Why the trail matters more than the score
When a HUD reviewer asks how a failed deficiency was resolved, the answer needs a date, a photo, and a work order, not a verbal description of what staff remember doing. ETR's full-text and metadata search means a compliance officer can pull a specific unit's inspection history, across every cycle, in a single search rather than opening separate folders for each inspection date.
ETR supports audit readiness around NSPIRE evidence. It does not perform inspections or score them; that stays with your inspection software or process. ETR is where the evidence generated by that process gets organized and kept retrievable.
Other household-file surfaces inside ETR.
Bring a redacted inspection file. See it organized in ETR.
A 30-minute session walking through your own NSPIRE documentation.