Load a scenario, then change the inspection time, program, responsibilities, or deficiencies. The clock board only calculates selected observations.
Non-life-threatening only; 0–30 days.
Observed deficiencies
Choose every observed condition and identify who is responsible for correction. A selected item makes the unit fail this modeled inspection.
Gate — pass before approval
24 CFR 982.305(f). Keep the existing date-order review separate from the deficiency clocks: the unit must pass inspection before tenancy approval, HAP execution, and lease start, subject to applicable exceptions.
Correction and follow-up timeline
Markers span the inspection through the furthest modeled deadline. Red markers are owner-responsibility HAP-abatement follow-up dates.
Rules this engine enforces
Life-threatening deficiencies use a 24-hour correction deadline under 24 CFR 982.404(a)(3).
Other owner-family defects use a 30-day correction period, with modeled PHA extension days applied only to non-life-threatening items, under 24 CFR 982.404(a)(2).
For an uncorrected owner-responsible item, the modeled HAP-abatement follow-up is no later than the first of the month after expiration under 24 CFR 982.404(a)(4).
The approval gate retains its date-order review from 24 CFR 982.305(f).
Checking this page's constants against the live governed rules register…
What this demo computes. It models deadlines from the entered local inspection time, selected deficiencies, extension days, and stated responsibility. It does not decide whether a condition meets NSPIRE/HQS, verify correction, apply an administrative plan or exception, issue notices, or take HAP action. The signed-in product records findings, evidence, responsibility, notices, approvals, and the actual workflow; if an input is absent, this demo does not guess.
National NSPIRE/REAC inspection-score statistics moved to the HUD BI Scorecards demo — the executive surface where national context belongs.