Can Tenants Do Their Own Move-In and Move-Out Inspections?

What the law actually says

Start with what a move-in or move-out inspection legally is, because the question usually hides a wrong assumption. A rental condition report is not a code inspection, a habitability inspection, or an appraisal. It is a document between the two parties to the lease that fixes the unit's condition at a point in time so that, months or years later, damage can be separated from what was already there. No state statute requires that document to be produced by a licensed professional, and none requires it to be produced by the landlord personally. Where statutes speak at all, they assign the work to the landlord, the tenant, or both together, and a surprising number put the pen in the tenant's hand.

The clearest example is Michigan. According to the Michigan Legislature's published text of the state landlord-tenant act (legislature.mi.gov), MCL 554.608 requires the landlord to furnish two blank copies of a commencement inventory checklist, after which "the tenant shall review the checklist, note the condition of the property and return 1 copy of the checklist to the landlord within 7 days after receiving possession." The statute even dictates the notice that must appear at the top of the form in 12-point boldface: "You should complete this checklist, noting the condition of the rental property, and return it to the landlord within 7 days." In Michigan, the tenant-completed move-in inspection is not a workaround. It is the statutory design.

Virginia goes one step further and answers the property manager's version of the question directly. Under Va. Code 55.1-1214 (law.lis.virginia.gov), the default is a landlord-prepared move-in report within 5 days of occupancy, but the statute adds that the landlord "may adopt a written policy allowing the tenant to prepare the written report of the move-in inspection," in which case the report is deemed correct unless the landlord objects in writing within 5 days of receiving it. That is a state legislature codifying tenant self-completion as an approved way to build the official condition record, with the review-and-object window as the quality control.

Eleven statutes, three patterns

Condition-report statutes sort into three patterns: states that hand the record to the tenant, states that require both parties to acknowledge it, and states that keep the duty on the landlord. The table below covers eleven states whose statutes speak directly to who makes or verifies the move-in and move-out record. It is about who completes the inspection; for what each state requires when you later deduct from a deposit, see the separate state-by-state documentation table.

Read down that middle column and the pattern is hard to miss. Legislatures did not treat tenant participation as a threat to the record. They treated it as the thing that makes the record binding. According to the Kentucky Revised Statutes (apps.legislature.ky.gov), the signatures of both parties on the damage listing "shall be conclusive evidence of the accuracy of such listing." Georgia's statute uses the same conclusive-evidence language, and adds that a tenant who neither signs nor dissents in writing forfeits the ability to contest those items later. The strongest condition documentation in American landlord-tenant law is not the report a manager wrote alone. It is the one the tenant touched.

What makes a tenant-performed inspection hold up

So the legal question is settled: tenants can do their own inspections, and in several states the statute expects them to. The operational question is the one property managers actually mean when they ask: if my tenant does the inspection, can I rely on it when the deposit dispute lands in small claims court? The statutes above, read together, give a concrete answer. They never test who captured the record. They test four properties of the record itself.

Modern tenant-guided inspection software is engineered against that list, which is why the category exists at all. The standard mechanics, described in our explainer on tenant-guided inspections, map one-to-one onto the statutory tests: the app schedules the inspection inside the legal window, walks the tenant room by room so coverage is complete, timestamps each capture at the moment it happens, and routes the finished report to the manager for review or objection. According to RentCheck's published comparison documentation (getrentcheck.com), resident inspections in its platform require every photo to be captured inside the app, with no uploads from the camera roll, so a photo's timestamp and its subject cannot be separated. That in-app capture rule is the software equivalent of a notarized date, and it answers the fraud objection better than an unaccompanied staff walkthrough does: a manager's own undated phone photos carry no such guarantee.

There is also a quieter argument for the tenant's version of events, and California's legislature recently made it explicit. Under the photograph requirements added to Cal. Civ. Code 1950.5 (leginfo.legislature.ca.gov), landlords must photograph units at move-out and, for tenancies beginning on or after July 1, 2025, "immediately before, or at the inception of, the tenancy." The direction of regulation is toward more photographic condition evidence, captured closer to the moment of transition, by whoever is actually there. At move-in, the person actually there is the tenant.

Where tenant self-completion is not enough

An honest page has to draw the boundary, because tenant-performed does not mean landlord-absent. Four situations keep a duty on the management side no matter how good the tenant's capture is:

None of these boundaries cut against tenant-performed inspections; they define the workflow around them. In a both-signature state, the tenant's guided capture becomes the list both parties sign. In a landlord-duty state, it becomes the second, independent record that corroborates the landlord's own. The one configuration no state endorses is also the most common one in practice: no timely record from anybody, and a dispute argued from memory.

The real objection is review, not capture

Push on the "can tenants really do this" objection and it usually is not legal at all. It is about trust in the work product: a tenant is not a trained inspector, some submissions will be incomplete or careless, and at move-in the tenant has every incentive to document generously, since each preexisting scratch they record is a deduction they cannot be charged for. That incentive is exactly why the move-in side of the record is safe to hand over: the tenant's self-interest points at thoroughness, and an overly thorough baseline costs the manager nothing. The exposure sits at move-out, where the incentive flips, and where somebody on the management side still has to judge what the submission actually shows.

That is the honest limit of tenant-performed inspections as the category ships today: the tenant does the capture, and a person on the management side still opens every submission and decides what is damage, what is wear, and what was already in the baseline. At portfolio scale that review is the bottleneck, and it is also where mistakes get expensive, because a missed change at move-out is a deduction never taken. This is the layer RapidEye was built for: the tenant records a guided video walkthrough, and the review is done by AI against that unit's own move-in baseline, so the manager receives findings with timestamped evidence attached instead of a queue of photos to adjudicate. The capture question this page answers has a settled legal yes. The review question is where the operational leverage is, and pairing tenant capture with automated baseline comparison is how both ends of the record get made and checked without a site visit.

Quick FAQ