You email a tenant a move-out form. It’s a PDF with thirty-six fields, fourteen yes/no questions, and a signature line. They open it on their phone in the parking lot of the moving truck.
They don’t complete it.
You send a reminder. You send another. Three weeks later, the deposit deadline is approaching and you still don’t have it. You guess at the answers and move on.
This is a writing problem, not a tenant problem. The form was the obstacle.
Why most move-out forms don’t get completed
The default tenant experience with a move-out form looks like this: a 14-page PDF designed for a desktop printer, full of legalese, asking for information they don’t have on hand, with a wet-signature line at the end.
It fails on four counts:
- Wrong device. They’re filling it out on a phone, in a car, between trips.
- Wrong order. It asks for hard things (signatures, dates, attestations) before easy things (their forwarding address).
- Wrong tone. It reads like a contract, which puts them in a defensive posture.
- No progress signal. They can’t tell if they’re 10% or 80% through.
The form is asking for cooperative effort, but the design is adversarial. Tenants stop.
Treat the move-out form the way product designers treat a checkout flow. The goal is not to ask everything you might want, the goal is to complete.
Start with what they want to give you
The first question on every move-out form should be the easiest one to answer and the one the tenant most wants to give: their forwarding address.
Why this works: the tenant has a self-interest in this question. They want their deposit. Asking for the address first puts them in a “give to receive” mindset for the rest of the form.
It also establishes momentum. Forms that open with hard questions feel like work. Forms that open with easy questions feel like progress.
Other low-friction openers:
- New email address (if it’s changed).
- New phone number (if it’s changed).
- Move-out date confirmation.
- Last day of utility transfer.
None of these require thought. All of them produce dopamine when answered. By the time you get to the harder questions, the tenant is already 30% through.
Group fields by mental context
Most move-out forms are organized by what the landlord cares about, sections like “Damages,” “Cleaning,” “Keys Returned.” That’s an internal taxonomy.
The tenant’s mental model is room-by-room. Their brain is walking through the apartment as they fill out the form. The form should match that walk.
A working section structure:
- You and your forwarding info. (Easy openers.)
- Move-out logistics. (Date, time, key return method, utility transfer.)
- Walkthrough by room. (Kitchen, bathrooms, bedrooms, living areas, outdoor space, in the order someone would physically walk through.)
- Things to flag. (Items left behind, repairs the tenant did themselves, anything they want to call out.)
- Attestation and signature. (Saved for last.)
Within each room, group questions tightly: “Any issues with the kitchen?” → conditional follow-up if yes → photo upload → next room. Don’t make them think about kitchens, then bathrooms, then back to kitchens.
For the room-level checklist itself, the 47-item move-in walkthrough covers what to ask about. The move-out form is the same questions in reverse, with a different framing.
Mobile-first phrasing
Roughly 80% of tenants will open the move-out form on a phone. Design every line of copy for a 4-inch screen.
Concrete rules:
- Question stems under 12 words. “Did you remove all your belongings from the unit?” not “Have you completed the removal of all personal belongings, including those in storage areas, closets, and the garage?”
- Answer options that don’t wrap. “Yes” / “No” / “Not sure” beats “Yes, completely” / “No, items remain” / “Partial, see notes.”
- One question per screen for hard ones. Photo uploads, sign-offs, anything that requires looking up information.
- Help text below, not above. Tenants read top to bottom. Put the question first, the explanation second.
The clearest test of mobile phrasing: read the form aloud. If a sentence makes you stop for breath, it’s too long for a phone screen.
Conditional logic over long forms
The single biggest gain in completion rate comes from conditional logic, only showing questions that apply.
A non-conditional form asks every tenant every question, including “If you had any pets, were they registered with management?” That question is irrelevant to the 60% of tenants who didn’t have pets. They have to read it, parse it, and skip it. Three seconds of friction, multiplied by twenty similar questions, is the difference between completion and abandonment.
A conditional form has a single question early: “Did you have any pets in the unit?” If no, all pet-related questions disappear. If yes, the relevant pet questions appear inline.
Apply this aggressively:
- Pets, only if pets.
- Storage unit, only if rented.
- Parking, only if assigned.
- Guest access, only if used.
- Damages, only if any reported.
A form with 40 possible fields and good conditional logic feels like a 12-field form to the average tenant. Same data, much better completion.
Photos: ask, don’t require
The instinct is to make photo uploads required. “Tenant must upload three photos per room before submitting.” This kills completion rates more than any other choice.
Why: photos are for you. The tenant doesn’t benefit from them. Requiring them as a blocker triggers abandonment when storage is tight on their phone, when the lighting is bad, when they’re in a hurry.
A better pattern: photo uploads are optional and encouraged, with a clear note that they help process the deposit faster and protect against disputes. “Upload a photo of any area you want to call out, speeds up your refund.”
Tenants who care about their deposit will upload photos. Tenants who don’t would have given you bad photos anyway. The completed form without photos is more valuable than the abandoned form that demanded them.
If you must require photos, require them only for specific flagged issues, “you said the kitchen has damage, please attach one photo.” Conditional photo requirements work. Universal ones don’t.
For more on what good photo documentation looks like (and what your own photos should capture either way), see move-in and move-out photos.
Phrase the hard questions as observations, not accusations
The single biggest tonal mistake on move-out forms is treating every question as an interrogation.
Compare:
- “Did you damage the carpet?”, defensive trigger.
- “Anything to flag about the carpet condition?”, collaborative.
Or:
- “Were any items broken during your tenancy?”, bad.
- “Is there anything you’d like to call out about the unit?”, good.
The collaborative phrasing isn’t softer because you’re going easier on the tenant. It’s softer because it produces more honest answers. A tenant in a defensive posture under-reports. A tenant in a collaborative posture over-reports, which is what you want for the documentation.
A good test: does the question read like a deposition or like a checkout conversation? If it’s a deposition, rewrite it.
Signature placement and friction
Save the signature for last. Always.
A signature near the top of the form (or even in the middle) creates a commitment moment too early. Tenants who haven’t decided yet whether to engage fully will balk. They’ll close the form and come back to it “later”, which means never.
A signature at the end is a capstone, not a gate. The tenant has already done the work. Signing feels like finishing, not committing.
The signature mechanics themselves matter:
- Typed name + checkbox is universally usable. Acceptable in most jurisdictions for non-notarized purposes.
- Drawn signature on touchscreen is fine but adds friction. Tenants who hand off the form to a spouse to sign create gaps.
- Wet-signature only kills mobile completion entirely. Avoid unless legally required.
If your jurisdiction requires a wet signature for any reason (some lease-related documents do), structure the form so the tenant submits the data first, with a separate “print, sign, and return” step for the legal piece. Don’t combine them.
Progress signals: the cheapest win
A tenant filling out a form needs to know how far they are. A 30-field form with no progress bar feels infinite. The same form with a progress indicator feels finite.
Cheap implementations:
- A percentage bar at the top.
- “Section 3 of 5” at each section break.
- “About 2 minutes remaining” estimates at the start of each section.
Slightly better implementations:
- A multi-step form with explicit “Next” buttons, where each step feels small.
- Auto-save indicators (“Saved, you can close this and come back”).
- Section completion checkmarks.
The best implementation: a form that breaks into 4-6 obvious sub-sections, each of which feels like an accomplishment to finish. The tenant gets to feel productive halfway through.
The 25-field rule
A working move-out form has fewer than 25 visible fields for the average tenant. Beyond that, completion rates collapse.
This sounds restrictive. It isn’t, with conditional logic. You can have 60 possible fields in the form and only show 18 to the median tenant.
When you draft the form, count fields by tenant journey, not by total. A tenant with no pets, no storage unit, standard parking, and no damages should see fewer than 15 fields. A tenant with multiple flagged issues should see more, but they’re already engaged.
If your form requires more than 25 fields for the simple case, something is being asked that doesn’t need to be asked. Audit each question:
- Is this information you already have?
- Is this information you’ll get from the walkthrough anyway?
- Does this question have ever changed a decision?
If the answer to any of those is “no,” cut the question.
What a good form actually feels like
Below is a working example. It’s the same form, organized the way this article describes. Click through it. Notice the order, the section grouping, the way each click feels like progress. This is what a tenant should see.
As you click, notice that the progress bar moves the whole time — the tenant always knows where they are, and every check feels like a step closer to done.
What to send after they submit
The form ending is as important as the form opening. A “thanks, we’ll be in touch” message is bad UX.
A good submission flow:
- Immediate on-screen confirmation: “Got it. Here’s what happens next.”
- Email confirmation with a PDF copy of their answers attached.
- A timeline: “We’ll do the walkthrough on [date]. You’ll receive the deposit refund or itemized deductions by [date].”
- A way to reach you with corrections within 72 hours.
The PDF copy is important. It tells the tenant they have a record too. This single artifact reduces dispute frequency more than almost any other intervention. A tenant who feels they have parallel documentation is less likely to suspect manipulation later.
The DiscoveryMark Move-Out Checkout flow produces this PDF automatically, delivered to both parties via email. $15 per record. The form itself, the photos, and the timestamped record all bundled.
When the form is part of a bigger system
A great move-out form on its own is worth a lot. A great move-out form that connects to the original move-in record is worth significantly more.
The two documents, side by side, are the difference between a defensible deposit decision and a contested one. Move-in says “this is the unit we gave you.” Move-out says “this is the unit we got back.” Any deviation is the documented basis for a deduction.
If your move-in record is loose phone photos and a checklist nobody signed, even a perfect move-out form has nothing to compare to. Build both. Make them match.
For the tenant-facing side of move-out, a move-out checklist for tenants covers what they should be doing before they reach the form.
The closing thought
A move-out form that gets completed is worth a lot more than a comprehensive one that doesn’t.
Design the form like a product, not a contract. Lead with easy questions, group by room, use conditional logic, phrase collaboratively, save signatures for last. Keep total visible fields under 25. Confirm submission with a PDF copy.
The Move-Out Checkout flow on DiscoveryMark applies these patterns by default, and produces the signed, dated, court-ready PDF that turns a completed form into a defensible record.
