Move-In Inspection Workflow That Holds

November 2, 20269 min read

Last reviewed: October 2026

Abstract editorial illustration for the article “Move-In Inspection Workflow That Holds”

A move-in inspection workflow ensures every required inspection is completed, documented, and approved before a resident moves in. The challenge isn't always a missed inspection. It's missing proof: an unsigned form, an incomplete date, or an inspection record uploaded weeks after the lease begins.

For compliance officers and asset managers, a reliable move-in inspection workflow prevents move-in approval until the inspection record is complete and properly filed. This article explains how to build that process and avoid compliance gaps. For program-specific requirements, see our companion post, Move-Ins Before Inspections: What Each Affordable Housing Program Requires.

What a move-in inspection workflow covers

It’s every step between “the unit is turned” and “this household is approved to move in.” It ties together four records: the unit inspection, the household’s eligibility file, the lease, and the program requirements attached to that unit. If any required piece is missing, the move-in stays pending. A text from maintenance saying the unit is ready doesn’t count.

For HUD-assisted multifamily properties, HUD Handbook 4350.3 requires a move-in inspection done with the tenant and kept in the tenant file, usually on form HUD-90106, and Management and Occupancy Reviews look for it. NSPIRE sets HUD’s physical inspection standards, with inspection requirements in 24 CFR 5.705. Public Housing, voucher, LIHTC and HOME units each have their own move-in rules on top of that, so check your program requirements and regulatory agreement.

Where the handoff breaks

Three teams are working toward three different deadlines. Leasing wants the move-in done on the scheduled date. Maintenance wants to close out the turn. Compliance wants a clean file. In most legacy setups they coordinate through email, paper forms and memory, and nobody owns the moment where all three have to line up.

Here’s how that plays out. It’s October 1 at a 120-unit property with a stack of turns due. A resident pulls in with a moving truck at 9:00 AM. The maintenance tech tells the site manager that Unit 204 is ready. Leasing hands over keys and finalizes the move-in. The signed inspection form is still sitting in the shop.

Six months later, the state agency or an MOR reviewer pulls the tenant file and there’s no pre-occupancy inspection in it. Now someone is digging through the shop, old emails and a shared drive. Even if they find the form, they may not be able to show it was completed before the resident moved in.

That timing question is what reviewers care about. They aren’t only asking whether an inspection exists. They’re asking whether it happened before occupancy. An undated form, or a scan uploaded after the lease start, doesn’t answer that.

What a complete inspection record includes

You can’t enforce “complete” until you define it. At minimum, the record should have:

Property and unit number, matched to the resident record
Inspection date
Name of the person who did the inspection
Condition of each room and major item, with notes on any existing damage
Dated photos of anything noted
Resident and staff signatures acknowledging the condition
Any deficiencies found, plus the work order and date each was resolved
A home in the resident and unit file, not a separate folder or someone’s inbox

The resident signature is the easiest piece to skip when a truck is waiting. It’s also the one you’ll want most at move-out, when you’re comparing condition and deciding on damage charges.

Layered properties: keep each check separate

One unit can carry LIHTC, Section 8 and HOME at the same time. That doesn’t change the inspection itself, but it does change how many things have to be true before approval. Treat them as separate checks that all have to pass. A single combined checklist makes it too easy for one green checkmark to make the whole file look done.

Inspection record: the unit was reviewed and accepted.
TIC or HUD-50059 and supporting documents: the household is eligible.
Lease: the agreement is signed.
Program record: which rules apply to this unit.
Final approval: all of the above were done before occupancy.

A finished TIC says nothing about the unit’s condition, and a passed inspection says nothing about income or assets. HOTMA added more work on the eligibility side, including asset limits and self-certification thresholds that HUD adjusts every year. That extra work can quietly pull compliance attention toward the income file and away from the inspection. Keep both in front of the reviewer, and pull current-year figures from HUD’s published table rather than hardcoding dollar amounts into your checklists.

If your properties submit to TRACS, send the move-in certification only after the full file is complete. TRACS shouldn’t be where you find out something was missed.

The approval gate: what should block a move-in

The fix is to make the inspection a hard stop instead of a reminder. A policy memo can’t stop someone from clicking “finalize.” A system can.

Staff set up the resident and unit records.
The inspector completes the inspection with the resident and attaches it to the unit record.
Compliance reviews the inspection alongside the eligibility file and program requirements.
The move-in stays pending while anything is missing, and the system shows exactly what’s missing.
Final approval happens only once every required record is attached and reviewed.

Decide ahead of time what happens when the inspection turns up problems. Which deficiencies block the move-in, and which can be documented with a work order and a target date? Write that rule down, so leasing isn’t making the call at 9:00 AM with a truck in the lot.

How ExactEstate handles it

ExactEstate builds the move-in inspection into the compliance workflow. Compliance checkpoints block move-ins until inspections are complete, so nobody can finalize occupancy on a verbal “it’s ready.” The same workflow automates TICs and recertifications for LIHTC and HUD Multifamily properties and supports HOTMA-ready processes, so the eligibility review and the inspection sit side by side at approval.

Staff complete the move-in inspection form in a median of 14 seconds once it’s open, measured across 252 real move-ins. The inspection also records the unit’s baseline condition, which gives you something concrete to compare against at move-out, instead of an argument about what the carpet looked like two years ago.

Compliance officers see the full file at approval, asset managers can confirm the workflow is being followed, and site staff get a specific next step instead of a vague warning. When staff aren’t sure why something is blocked, EEva Compliance Intelligence explains what’s missing and cites the rule behind it.

Test it before you roll it out

Test the failure path, not just the clean one.

Create a sample move-in with no inspection attached and try to finalize it. It should be blocked, and the screen should say why.
Attach an inspection that’s missing the resident signature. Does the system catch that, or does it only check that a file exists?
Complete the inspection and the review, then finalize. Confirm the timestamps show the inspection came before approval.
Repeat the whole test on a layered unit, such as LIHTC plus Section 8.

Then ask each team to walk through its part without mentioning email. Maintenance should know where the inspection ends. Compliance should know where approval starts. Leasing should know what “pending” means and what to tell a resident who’s waiting.

Last, open the finished resident file as if an auditor had just asked for it. The inspection, program review, lease and approval should read in order, with dates that make sense. If someone has to explain the sequence out loud, the workflow isn’t done. The Audit Readiness Checker is a quick way to spot other gaps while you’re at it.

Want to see it on your own portfolio? Book a 20-minute walkthrough and we’ll show you how the move-in checkpoint holds approval until the inspection, TIC and program records are complete.

Frequently asked questions

Is a move-in inspection required for LIHTC properties?

It depends on your state agency and regulatory agreement. Federal LIHTC rules focus on state agency inspections of a sample of units, but many state agencies and investors expect a documented move-in inspection in the tenant file. If the unit also has HUD assistance, the HUD requirements apply too.

Does the resident have to be there for the inspection?

For HUD-assisted multifamily and Public Housing properties, the inspection is done with the tenant. For other programs, it’s still the right practice. A signed inspection is far harder to dispute at move-out than one the resident never saw.

How close to move-in should the inspection happen?

As close as you can practically manage, ideally the same day or within a few days. The longer the gap, the more room there is for the unit’s condition to change. Whatever you do, date the record so the sequence is clear.

What if the inspection finds problems?

Follow a written rule you set ahead of time. Serious health and safety issues should be fixed before the resident moves in. Smaller items can be noted on the inspection the resident signs, with a work order and a target repair date attached to the file.

Is a move-in inspection the same as an NSPIRE inspection?

No. NSPIRE is HUD’s standard for physical inspections of covered housing. A move-in inspection is your property’s own record of the unit’s condition, done with the resident. Many teams build their move-in checklist around NSPIRE standards so the two line up. For voucher units, HUD has extended the NSPIRE compliance date to February 1, 2027, so many PHAs still inspect under HQS until then.

Is the make-ready checklist enough?
No. Make-ready is maintenance’s list for turning the unit. The move-in inspection is the documented condition record the resident signs. You need the make-ready done before the inspection, but one doesn’t replace the other.

Can we use digital inspections and e-signatures?

Generally yes, as long as the record is complete, dated, signed and kept in the resident file. For HUD Multifamily properties, HUD Notice H 2020-04 allows electronic signatures, as long as residents can choose paper if they ask. Confirm your state agency and any investors accept them too.