Move-In Before Inspection: The Audit Risk

Move-in before inspection ends audits — not vacancies

What is the real villain here?

A move-in before inspection creates audit risk because the file cannot prove that the unit cleared the required compliance checkpoint before occupancy. The safest control is a hard stop that withholds approval until the inspection is complete, documented, and attached to the tenant record.

An on-site PM carries two pressures at once. The first is vacancy cost: every day a unit sits empty is revenue the property does not collect. The second is compliance: every move-in without a completed inspection is a potential REAC finding or IRS Form 8823 event. When the software does not intervene, the PM resolves this tension the fastest way available — move them in, chase the paperwork later.

This pattern shows up constantly in compliance officer conversations and in PHA audit prep discussions. The inspection was "verbally confirmed." The unit was "turned in 24 hours ago." The TIC was "going to be signed next week." These are not bad-faith decisions. They are what happens when policy is the only guardrail and the software imposes none.

On a layered portfolio — LIHTC plus Section 8 PBRA plus HOME on the same unit — the exposure compounds. Each program has its own inspection threshold. Satisfying one does not satisfy the others. A system that does not track program-specific gate status creates gaps that auditors find 18 months later.

What does a skipped inspection actually cost?

The cost shows up in three places.

REAC findings. The Real Estate Assessment Center scores properties on physical condition and management practices. A pre-occupancy inspection skipped and documented after the fact is a management finding. Enough management findings lower the REAC score. A low REAC score goes to the board. The board asks questions the compliance officer does not want to answer in public.

Section 8 HAP exposure. 24 CFR 982.405 states that a PHA must inspect a unit before approving a tenancy. voucherready.com summarizes the practical outcome clearly: a unit that fails inspection or was not inspected before move-in is not eligible for a Housing Assistance Payment until it passes. That means the operator may have collected no HAP for a period when the unit was occupied — and may owe that period back if audited.

For operators with units serving families whose net assets exceed $100,000 (the HOTMA threshold stated in 24 CFR 5.618), an incomplete asset test at move-in adds a second finding layer on top of the inspection gap.

How does a compliance checkpoint actually block the move-in?

ExactEstate enforces a configurable compliance checkpoint at the move-in finalization step. When a PM clicks "Finalize Move-In," the system runs a gate evaluation before anything is written to the tenant record.

If any gate is red, the move-in does not finalize. The PM sees which gate is blocking and what action is needed. The audit log records the attempt, the blocking gate, and the timestamp. Nothing moves until the condition is resolved.

The default gates cover the most common audit failure modes:

Program-specific add-on gates apply automatically based on the unit's program designation. A Section 8 PBRA unit requires HAP contract documentation. An HCV unit requires a voucher portability confirmation and an RFTA on file. A HOME unit mid-cycle requires an eligibility recertification. The system reads the program flags on the unit and applies the right gate set — the compliance officer does not have to configure each case manually.

The override path exists for edge cases. A compliance officer with the appropriate role can override a blocked gate, but the override itself is an audit row: who approved it, when, and why. That row is visible to the next auditor who opens the file.

This is the workflow described in ExactEstate's battlecard: "Compliance checkpoints that block move-ins until inspections are complete." The checkpoint is not a reminder. It is a hard stop.

Does the checkpoint slow down leasing?

The checkpoint does not slow down leasing. It moves the compliance work earlier in the leasing timeline, where it belongs.

In a standard compliant workflow, the pre-occupancy inspection happens before the lease is offered. The TIC is completed before the applicant is approved. Income documentation is collected during screening, not after move-in. When those steps are done in sequence, the move-in finalization is fast — all gates are already green.

The checkpoint only creates friction when the process is out of order. That friction is the point. An on-site PM who cannot finalize a move-in because the inspection is missing will call to schedule the inspection. That is a better outcome than a compliance officer who discovers the gap during a HUD audit review.

For more on how AI-assisted workflows are closing the compliance audit gap for affordable-housing operators, see AI for Affordable Housing Compliance: Closing the Audit Gap. For operators evaluating platforms side by side, the Entrata vs. ExactEstate comparison covers how compliance enforcement depth differs across platforms. And for TRACS-specific workflows, ExactEstate Now With Online TRACS Integration shows how submission sequencing connects to the same compliance gate logic.

What about NSPIRE's new inspection standards?

NSPIRE — the National Standards for the Physical Inspection of Real Estate — replaces UPCS as HUD's inspection framework for public housing and multifamily assisted properties. HUD's Real Estate Assessment Center has been phasing NSPIRE in across program types.

For operators who have already moved to NSPIRE, the pre-occupancy inspection standard changes what the inspection must document. The unit condition criteria under NSPIRE differ from UPCS in scope and scoring weight. An operator running pre-NSPIRE checklists on a property now subject to NSPIRE standards is creating a documentation gap that the move-in checkpoint will catch — because the gate requires an inspection on file that meets current standards, not a legacy form.

The HUD Real Estate Assessment Center's NSPIRE guidance is the governing source for what a valid pre-occupancy inspection must include. Operators preparing for NSPIRE reviews should confirm that their inspection documentation format aligns with current REAC expectations before the next scheduled inspection cycle.

Run the compliance checkpoint on your own portfolio

See the move-in blocking workflow in a 20-minute walkthrough on your own portfolio's program mix — LIHTC, Section 8, HOME, or layered — and watch the gate evaluation run in real time.

Which eligibility figures should the same checkpoint verify?

The checkpoint should also confirm that the household file uses the applicable federal eligibility figures. Section 24 CFR 5.603 states: “A family whose annual income does not exceed 80 percent of the median income for the area, as determined by HUD with adjustments for smaller and larger families, except that HUD may establish income ceilings higher or lower than 80 percent of the median income for the area on the basis of HUD's findings that such variations are necessary because of unusually high or low family incomes.” (https://www.ecfr.gov/current/title-24/section-5.603) Section 24 CFR 5.618 states: “(i) The family's net assets (as defined in § 5.603) exceed $100,000, which amount will be adjusted annually by HUD in accordance with the Consumer Price Index for Urban Wage Earners and Clerical Workers;” (https://www.ecfr.gov/current/title-24/section-5.618) Section 24 CFR 5.611 states: “(1) $480 for each dependent, which amount will be adjusted by HUD annually in accordance with the Consumer Price Index for Urban Wage Earners and Clerical Workers, rounded to the next lowest multiple of $25;” (https://www.ecfr.gov/current/title-24/section-5.611)