A tenant texts, "The sink is broken." You ask which sink. They answer that evening. The next morning you ask whether it is leaking or clogged. By the time a plumber gets the details, the request has spent a day moving through questions that could have been answered at the start.
A maintenance intake should collect enough information to choose the next action without asking the tenant to diagnose the repair. Ask for the exact location, observed symptom, timing, current condition, useful photos, and a reliable contact. Then tell the tenant what happens next.
Name the room, fixture, and exact spot
Start with the property and unit, then narrow the location. "Upstairs hall bathroom, sink cabinet, left supply line" gives the person reviewing the request a place to inspect. "Bathroom problem" does not. In a building with shared equipment or common areas, ask whether the issue is inside the unit, in a hallway, outside, or in a utility space.
Use familiar labels. Tenants may not know a plumbing or electrical term, and they should not have to. A form can ask for the room first and the item second. Leave a plain text field for anything that does not fit the list.
Confirm the unit on the request page instead of asking the tenant to type the whole address every time. That avoids routing a good description to the wrong property because somebody entered an old address or a similar unit number.
Ask for the symptom, not a diagnosis
Prompt the tenant to describe what they see, hear, smell, or cannot use. "Water appears under the cabinet when the cold tap runs" is more useful than "bad valve." The first statement can be checked. The second may be a guess that sends the wrong part or vendor.
A good description includes what changed and what still works. Ask whether the issue is constant or intermittent, whether one fixture or several are affected, and whether a switch, control, or appliance shows an error. Keep troubleshooting requests within safe, ordinary observations. Do not ask a tenant to remove a panel, touch wiring, climb, move a heavy appliance, or test equipment beyond their competence.
Preserve the tenant's original wording. You can add a later diagnosis after somebody qualified examines the condition, but do not overwrite the first report. The difference between what was reported and what was found is useful when the same symptom returns.
Capture timing and the condition right now
Ask when the tenant first noticed the problem and what was happening when it appeared. A leak that occurs only while the upstairs shower runs needs different scheduling than a pipe that is leaking continuously. A breaker that trips when one appliance starts is different from an entire unit without power.
The current condition matters more than a generic urgent checkbox. Ask whether water is still flowing, the unit is secure, a required service is unavailable, smoke or sparking is present, or the condition is getting worse. Give tenants a separate, plainly written instruction for immediate danger so they do not assume submitting a web form is an emergency response.
Do not promise a response time the operation cannot support. State how requests are reviewed, how urgent reports should be made outside normal monitoring, and when the tenant can expect an acknowledgment or scheduling update. Keep emergency contacts and utility instructions specific to the property and current.
Request photos that answer a question
Ask for one wider photo that shows the location and one closer photo that shows the condition when photographs are safe and useful. A tight picture of a puddle proves there is water. A second image showing the puddle under the kitchen sink tells the reviewer where to look.
Tell the tenant what not to include. Faces, personal papers, medicine, computer screens, valuables, account numbers, and unrelated rooms do not belong in a maintenance record. A photo should document the repair area without collecting the rest of somebody's home.
Photos are supporting evidence, not a gate. A tenant may be unable to take one safely, the problem may not be visible, or the camera may not capture an odor or intermittent sound. Let the request proceed and ask a focused follow-up if an image would change the next action.
Get a contact plan without treating it as entry permission
Collect the tenant's name and the best phone or email for this request. Ask for practical scheduling limits, pets, accessibility needs, or another fact that affects the appointment. Keep permanent access codes, alarm credentials, and key locations out of the open description field.
A contact preference does not by itself authorize entry. Record scheduling messages, consent, and any required notice through the process that applies to the lease and property. Share tenant contact details with a vendor only when there is a valid need and an appropriate basis.
This article provides general operating information, not legal or safety advice. Repair duties, emergency response, notice, entry, privacy, accessibility, and required response times depend on the condition, lease, and current state and local requirements. Use qualified local professionals for work and decisions outside your competence.
Turn the submission into one owned next action
Review the request once, then assign a concrete next step. That may be calling the tenant, sending immediate safety instructions, scheduling an inspection, dispatching a qualified vendor, checking warranty coverage, or asking one specific follow-up question. Give that action an owner and due time.
Separate intake from triage. Intake records what the tenant reported. Triage decides priority and response. Keeping those stages distinct prevents a vague category such as "plumbing" from replacing the facts that support the decision.
LetsGoLandlord gives each unit a copyable no-login maintenance request link. The form collects a title, description, tenant name, and optional contact details, then creates a ticket for that unit. Use the description prompt to request the location, symptom, timing, current condition, and photo context your operation needs. The ticket can preserve the updates that follow, but the landlord still decides the proper response.
Close the intake loop with a useful acknowledgment
Confirm that the request was received and repeat the next known step. A useful message says who will review it, whether somebody will contact the tenant, and when the next update is expected. Avoid writing "submitted successfully" and leaving the tenant to guess whether anyone saw it.
If information is missing, ask one narrow question tied to the decision. "Is water still flowing when both taps are off?" is easier to answer than "Can you send more details?" Add the answer to the same ticket instead of starting a separate text thread with no link back to the request.
Review repeat follow-ups each month. If landlords and vendors keep asking which room, when the issue started, or whether the condition is active, add that prompt to the intake. The best form is not the longest one. It is the one that removes the questions your operation asks every time while still letting a tenant report an unusual problem in their own words.