Lessons 1 through 11 teach the standards. This lesson teaches what actually happens around them, which is where most PHA and owner frustration originates.
Preparation and inspection day set the record; everything after the report, including a technical review, is decided by the evidence gathered on that day, not by later argument.
Before the inspection. Properties receive advance notification of a scheduled inspection. The notice period, the scheduling mechanism, and the rules on rescheduling are set by HUD administrative guidance and have changed during the NSPIRE rollout, so confirm the current window against HUD's notices rather than relying on what was true under the old REAC protocol. Owners and PHAs must also notify residents of planned inspections (24 CFR 5.711(h)).
What matters more than the exact notice period is what a competent party does with it. Preparation work that genuinely changes outcomes:
Pull the prior inspection report and confirm every previously cited deficiency was actually corrected and documented. Repeat findings are the most avoidable points lost.
Walk the affirmative habitability items specifically, because they are pass or fail on presence and function rather than on condition. A missing smoke alarm is not a judgment call.
Verify unit access. Units the inspector cannot enter create problems that are procedural rather than physical, and the stakes are high: an owner or PHA that fails to provide the access HUD requires can be given a physical condition score of zero for the project (24 CFR 5.705(e)).
Confirm that fire-labeled doors still carry legible labels, that GFCI protection actually trips when tested rather than merely being a GFCI-shaped receptacle, and that heat is functional if the inspection falls in a heating season.
Assemble documentation: certificates for elevators, boilers, fire alarm and sprinkler testing, and any prior technical review outcomes.
Sampling. NSPIRE inspects a sample of units rather than every unit, drawn statistically, with the sample size scaling to property size. The practical consequence is that a defect repeated across many units is disproportionately damaging, because the sample is treated as representative. Fixing a systemic issue in five units and leaving it in fifty does not help if the sample lands in the fifty. This is why systemic defects deserve systemic correction rather than unit-by-unit patching.
On inspection day. The inspector works the three inspectable areas: Outside, Inside, and Unit. Deficiencies are recorded with severity, location, and evidence. The property representative should accompany the inspector, take their own parallel notes and photographs, and ask for the specific standard being cited when a call is unclear. Doing that in the moment is far more effective than disputing it weeks later from memory.
The representative's job is not to argue. It is to understand and document. A calm question of the form "which standard are you citing that under" produces a record; an argument produces friction and no record.
Life-threatening findings. When a life-threatening deficiency is identified, it triggers immediate obligations rather than waiting for the report. HUD gives notice of Life-Threatening and Severe items when the inspection ends, or at the end of each day of a multiple-day inspection. Life-Threatening items must be corrected within 24 hours of that notice unless HUD approves a variation, and the owner or PHA must certify electronically, with supporting evidence, within 2 business days after the deadline (24 CFR 5.711(c)). These are the findings that cannot be deferred to a correction plan.
After the inspection. Results are transmitted, deficiencies are listed with severities and correction deadlines, and a score is produced. From there the property either corrects and certifies, or challenges findings it believes are wrong.
Technical review and appeals. HUD provides a process for challenging inspection results. Broadly, challenges fall into two categories: objectively incorrect findings, such as a deficiency recorded in a unit that does not exist or a building attribute recorded wrongly, and disputes about the application of a standard to observed conditions.
Evidence is what decides these. Contemporaneous photographs with timestamps, maintenance records, work orders, invoices, and third-party certifications carry weight. Assertions do not.
Technical review, verified against HUD’s notice. Under Notice PIH 2023-16 / H 2023-07 (authority 24 CFR 5.711(d)), a request for technical review must be submitted electronically in the NSPIRE system, and REAC must receive it no later than the 45th calendar day following the day HUD provides the inspection report to the POA or PHA. A copy should go to NSPIRERegulations@hud.gov, with a courtesy copy to the HUD field office representative.
Grounds HUD will consider: HUD or inspector error, adverse conditions beyond the property’s control, modernization work in progress, and conflicts with state or local code. Requests must be accompanied by evidence.
What HUD will not review: “REAC will not conduct a technical review of the inspection results based on a PHA or POA’s correction of conditions after the inspection.” That is the rule behind the point below: the case is won or lost on the day of the inspection.
Threshold: only file where success would cross an administratively significant threshold per 24 CFR 5.711(d)(5), such as the score reaching 60 or changing inspection frequency under 24 CFR 5.705(c).
The operational lesson is simpler than the procedure: the case is won or lost on the day of the inspection, by whoever documented conditions properly, not later in the filing.
Practice Questions
1. During the notification period before an inspection, the highest-value preparation is generally:
Confirming past citations were corrected and documented
Asking HUD to reschedule the inspection to a later date
Repainting common areas
Reducing the unit sample by asking that fewer units be drawn
Answer: a. Repeat findings are the most avoidable points lost.
2. NSPIRE inspects a statistical sample of units. The practical consequence is:
A defect repeated across many units is disproportionately damaging
Sampling does not affect the score
Only the worst units are inspected
Systemic defects are less damaging than isolated ones because sampling averages them out
Answer: a. The sample is treated as representative of the whole property, so a defect repeated across many units is disproportionately damaging: fixing it in five units and leaving it in fifty does not help if the sample lands in the fifty.
3. An inspector cites a deficiency and the property representative disagrees. In the moment, the most useful action is:
Argue the point at length until the inspector relents and drops the citation
Refuse access to the remaining units
Ask which standard is cited and document conditions independently
Say nothing and file an appeal later
Answer: c. Understanding and documenting beats arguing, and it creates the record an appeal would need.
4. In a technical review, the evidence that carries weight is:
A letter from the owner
Contemporaneous timestamped photographs, work orders, invoices, and third-party certifications
A written assertion that the inspector was mistaken
The property's prior score
Answer: b. Evidence decides technical reviews: contemporaneous timestamped photographs, maintenance records, work orders, invoices and third-party certifications carry weight. Assertions do not.
5. A life-threatening deficiency identified during the inspection:
Is handled in the correction plan like any other finding, with no deadline
Can be deferred 30 days
Is scored but not cited
Triggers immediate obligations rather than waiting for the report
Answer: d. A life-threatening finding triggers immediate obligations rather than waiting for the report (24-hour correction, then electronic certification with evidence within 2 business days after the deadline, per 24 CFR 5.711(c)); these are the findings that cannot be deferred to a correction plan.
6. The notice period, scheduling mechanism, and rescheduling rules for NSPIRE inspections have changed during the rollout. Before GCHS tells a Texas PHA client how many days' notice to expect, it should:
Assume the old REAC/HQS notice period still applies
Ignore the notice period entirely
Ask the resident how much notice they received the last time around
Confirm the current window against HUD's current notices
Answer: d. The notice period, scheduling mechanism, and rescheduling rules are set by HUD administrative guidance and have changed during rollout, so the current window has to be confirmed against HUD's notices rather than assumed from the old REAC protocol.
7. Why does verifying unit access ahead of time matter as much as the physical condition of the unit?
A unit the inspector cannot enter creates a procedural problem
Access has no bearing on the inspection outcome
Only PHA-owned units require access verification
An inaccessible unit is simply skipped with no consequence for the property's score
Answer: a. A unit the inspector cannot enter creates a problem that is procedural rather than physical, which is exactly the kind of avoidable point loss good preparation prevents. Failing to provide access can even mean a physical condition score of zero for the project (24 CFR 5.705(e)).
8. During a GCHS pre-inspection walk, confirming GFCI protection means checking that the outlet:
Looks like a GFCI outlet, regardless of whether it trips
Actually trips when tested, not just looks GFCI-shaped
Is only checked if it sits in a bathroom
Needs testing only when the unit is vacant
Answer: b. The reading is specific: confirm GFCI protection actually trips when tested, rather than merely being a GFCI-shaped receptacle.
9. Which of the following are grounds HUD will consider in a technical review request?
A PHA simply disagreeing with the score
The property's general history of good relations with HUD
HUD or inspector error, adverse conditions beyond the property's control, modernization work in progress, and conflicts with state or local code
Any complaint filed by a resident, regardless of documentation
Answer: c. Under Notice PIH 2023-16 / H 2023-07, HUD will consider HUD or inspector error, adverse conditions beyond the property's control, modernization work in progress, and conflicts with state or local code, provided the request is accompanied by evidence.
10. What will REAC specifically decline to do in a technical review?
Consider evidence of inspector error
Consider adverse conditions beyond the property's control, such as a natural disaster
Consider conflicts with state or local code
Review results based on conditions corrected after the inspection
Answer: d. REAC will not conduct a technical review based on conditions the PHA or POA corrected after the inspection; the case is decided on conditions as they stood on inspection day.
11. Beyond having valid grounds, under 24 CFR 5.711(d)(5) a technical review is worth filing only when:
Success would cross an administratively significant score threshold
The PHA disagrees with the outcome at all, regardless of scoring impact or evidence
The property is Multifamily rather than Public Housing
The score is already above 90
Answer: a. Only file where success would cross an administratively significant threshold per 24 CFR 5.711(d)(5), such as the score reaching 60 or changing inspection frequency under 24 CFR 5.705(c).
12. How must a technical review request be submitted, and who should also receive a copy?
By certified mail only, with no electronic option
Electronically in the NSPIRE system, with a copy to NSPIRERegulations@hud.gov and a courtesy copy to the HUD field office representative
By phone call to REAC only
Directly and only to the individual inspector who conducted the visit
Answer: b. A request must be submitted electronically in the NSPIRE system, with a copy to NSPIRERegulations@hud.gov and a courtesy copy to the HUD field office representative. Source: Notice PIH 2023-16 / H 2023-07.
13. Which notice and regulatory citation govern the NSPIRE technical review process, and its 45-day filing deadline?
Notice PIH 2023-16 / H 2023-07, authority 24 CFR 5.711(d)
Notice PIH 2010-08, 24 CFR 5.705
Answer: c. The technical review process and its 45-day deadline run under Notice PIH 2023-16 / H 2023-07, authority 24 CFR 5.711(d).
14. What is the operational lesson behind the entire technical review process?
Corrections made after the inspection always restore lost points
Verbal explanations to the inspector are as effective as written documentation kept on file
The score stops mattering once a review is filed
The case is won or lost on inspection day, by who documented conditions
Answer: d. The operational lesson is simpler than the procedure: the case is won or lost on the day of the inspection, by whoever documented conditions properly, not later in the filing.
Micro-Assignment
Take a property you know. Build a pre-inspection preparation checklist you would actually hand to a site manager, sequenced by how many days before the inspection each item should happen. Include who is responsible for each line. Then mark the three items on your list that, if skipped, would cost the most points.
Glossary
Sample
The statistically drawn subset of units inspected, treated as representative of the property; scaled to property size.
Technical Review
HUD's process for challenging inspection findings, filed electronically in the NSPIRE system within 45 days of the report.
Repeat Finding
A deficiency cited in a prior inspection and found again, indicating correction failure; the most avoidable points lost.
Life-Threatening Finding
A deficiency that triggers immediate correction obligations rather than waiting for the inspection report.
Administratively Significant Threshold
The bar a technical review must clear to be worth filing, such as the score reaching 60 or changing inspection frequency, per 24 CFR 5.711(d)(5).
Notice PIH 2023-16 / H 2023-07
The HUD notice, under authority 24 CFR 5.711(d), governing how and when a technical review request must be filed.
Property Representative
The person accompanying the inspector on inspection day whose job is to understand and document, not to argue.
Contemporaneous Evidence
Timestamped photographs, maintenance records, work orders, invoices, and certifications created at the time; what a technical review is actually decided on.