Skip to main content
Book a demo

Move-In Inspection Checklist for Compliant Moves

Abstract editorial illustration for the article “Move-In Inspection Checklist for Compliant Moves”

A move-in inspection checklist only helps if it can actually stop a move-in. A PDF that staff fill out after the keys are handed over records what happened. It doesn’t prevent anything. On layered affordable housing properties that combine LIHTC, Section 8 and HOME, the checklist has to cover the unit, the household file, the lease and each program’s rules, and the move-in should wait until every item is done.

Below is a working checklist you can adapt, the most common reasons move-ins happen too early, and the numbers to track so you know your checkpoint is working.

Why move-ins happen before inspections

The pressure is predictable. A family has movers booked for 9:00 AM and utilities transferring that day. Leasing wants the unit off the vacancy report. Maintenance finished the turn and moved on. Compliance is still waiting on an inspection report or a signature.

When the inspection lives in a maintenance queue, income documents sit in a separate compliance folder, and the move-in screen doesn’t know about either, nothing stops the site manager from clicking “finalize.” The resident is active before the file is ready, and the compliance officer inherits the problem. A missing pre-occupancy inspection can’t be fixed after the fact, because reviewers look at the order of the dates.

The move-in checklist

Use this as a starting point and adjust it to your programs, regulatory agreements and company policy.

The unit

  • Make-ready complete and work orders closed
  • Move-in inspection completed and dated, before occupancy
  • Inspection done with the resident and signed by both the resident and staff (required for HUD Multifamily and Public Housing; best practice everywhere else)
  • Any deficiencies either fixed before move-in or documented with a work order and target date, according to your written policy
  • For voucher units: the PHA’s inspection passed, or was approved under the PHA’s non-life-threatening or alternative inspection option under 24 CFR 982.305, and the Request for Tenancy Approval is approved
  • Inspection record attached to the unit and resident file, not a separate folder

The household file

  • Income certification complete: TIC for LIHTC, HUD-50059 for project-based Section 8, or the program’s equivalent
  • Certification signed by everyone the program, form or state agency requires
  • Third-party verifications in the file and less than 120 days old at certification, ideally uploaded straight to the household record through the resident portal
  • Net assets reviewed. For HUD programs, households can self-certify assets up to 52,787in2026(54,898 in 2027), and the asset limit is 105,574(109,797 in 2027), under 24 CFR 5.618. These limits don’t apply to LIHTC-only households. The HOTMA Compliance Assessment can show whether your process is ready.
  • Income checked against the current income limit for every program on the unit
  • Social Security number and citizenship or eligible immigration status documents collected where the program requires them

The lease

  • Correct lease form for the program (for example, the HUD model lease for project-based Section 8, or the tenancy addendum for vouchers)
  • All required addenda attached, including lead-based paint disclosure where it applies
  • Signed by the household and owner, on paper or with e-signatures included in ExactEstate Core

Program-specific items

  • LIHTC: unit designation and set-aside confirmed, and state agency forms complete
  • HOME: unit meets HOME property standards and the income determination is in the file
  • Vouchers: rent reasonableness determined, and the family’s share no more than 40% of adjusted income at initial lease-up
  • Layered units: every program’s requirements met, not just one

Final approval

  • Every item above complete and reviewed by compliance
  • Approval date recorded, and after the inspection and certification dates
  • Any exception approved in writing by an authorized person, with the reason

How the checklist should work in your software

On paper, a checklist is only as strong as the person filling it out. In software, it can enforce the order:

  1. The site manager starts the move-in.
  2. The system checks the unit’s programs and the file against the required items.
  3. If anything is missing, the move-in is blocked, and the screen says exactly what’s missing and who needs to act.
  4. Staff resolve the item, whether that’s maintenance clearing an inspection finding or leasing collecting a signature.
  5. The move-in goes through once every required item is complete.

If your policy allows exceptions, limit them to authorized compliance staff and record who approved each one and why. An exception that isn’t documented looks the same as a mistake to an auditor. If you’re comparing systems on how well they enforce this, our guide on how to evaluate property management software for affordable housing lists the questions to ask.

How to tell if your checkpoint is working

Track a few numbers at the move-in decision point every month. Business intelligence dashboards make this easier than pulling it together by hand.

MetricWhat it tells you
Move-ins blockedHow often files reach move-in day incomplete
Blocks by item (inspection, certification, lease, other)Where the process breaks down most
Time to resolve a blockWhether blocks cause real delays for residents
Exceptions approvedWhether the rules are too strict, or being worked around
Findings on move-in files at reviewWhether the checkpoint is actually preventing findings

Read them together. Frequent inspection blocks usually point to turn scheduling. Frequent certification blocks point to document collection. Lots of exceptions mean either the policy needs clarifying or the checkpoint is set too broadly. The goal isn’t zero blocks. It’s catching problems at move-in instead of at audit.

How ExactEstate handles it

ExactEstate builds these checks into the move-in workflow. Compliance checkpoints block move-ins until inspections are complete, and the same platform automates TICs and recertifications and supports HOTMA-ready workflows.

  • Rules set per property. Each property’s programs, set-asides and income limits live on its compliance profile, so the checkpoint applies the right items to LIHTC, HUD Multifamily, Section 8 and layered units. Our team configures this with you during implementation.
  • Fast inspections. Staff complete the move-in inspection form in a median of 14 seconds once it’s open, measured across 252 real move-ins.
  • A readiness check before certification. The TIC or HUD-50059 is built from the household record, and the system shows what’s missing before it goes out. For HUD properties, certifications then flow to TRACS from the same record. PHAs get the same readiness check on the HUD-50058 with our software for public housing agencies.
  • Answers with the source. EEva Compliance Intelligence explains what’s blocking a certification and cites the rule behind it.

Operators who’ve made the switch see the difference: NuRock cut compliance time by about 70%, with move-ins taking 5 minutes instead of 15.

Related reading

Check where your current files stand with the Audit Readiness Checker.

See it on your portfolio. Book a 20-minute walkthrough and we’ll show you how move-in checkpoints, inspections and TIC validation work across your layered LIHTC, Section 8 and HOME properties.

Frequently asked questions

What should a move-in inspection checklist include?

 At minimum: a dated inspection signed by the resident and staff, a completed and signed income certification, current verifications, a signed lease with the right addenda, and any program-specific items. On layered units, include every program’s requirements.

Can a resident move in if the inspection found minor problems?

It depends on the program and your policy. Many operators allow minor items to be documented with a work order and target date. For voucher units, a PHA that has adopted the non-life-threatening deficiencies option can approve a unit with only minor deficiencies.

Who should be able to override a blocked move-in?

Only authorized compliance staff, and only when your written policy allows it. Every exception should record who approved it and why.

Is NSPIRE required for move-in inspections?

NSPIRE sets HUD’s physical inspection standards, and many teams build their checklists around it. For voucher units, HUD extended the NSPIRE compliance date to February 1, 2027, so many PHAs still inspect under HQS until then.

Do the HOTMA asset limits apply to LIHTC?

No. The asset limit and self-certification threshold are HUD program rules. LIHTC asset treatment follows Section 42 and your state agency’s guidance.

How do I know if our move-in process is working?
Track blocked move-ins, the reason for each, time to resolution and exceptions approved. Compare them with findings on move-in files at your next review. The Audit Readiness Checker is a good baseline before you start.

Sources

  1. Inspection requirements for HUD-assisted housing — ecfr.gov
  2. NSPIRE inspection standards and procedures — HUD Real Estate Assessment Center
  3. LIHTC compliance monitoring requirements — Electronic Code of Federal Regulations
  4. HOTMA income and asset definitions — Electronic Code of Federal Regulations (eCFR)

What changed

  • — 1 cited figure(s) match the current regulation text
  • — 1 cited figure(s) match the current regulation text
  • — 1 cited figure(s) match the current regulation text
  • — 1 cited figure(s) match the current regulation text
← Back to Blog