Texts at midnight, a voice message about the sink, an email with no unit number. Repairs vanish when requests arrive five ways. I would rather every request come in the same shape, so a manager can sort them in one place.
The problem. Area, type, urgency, a description and the date it began. These are the facts a repair person needs before they pick up a tool.
Getting in. Permission to enter, the hours the tenant is home, and a warning about a pet. They save a wasted visit.
Who and where. Name, unit and phone, so the right person is called.
Who fills it and who reads it
Tenants fill it in on a phone, or hand it to their own AI. It might ask "Which room is the problem in?" Then "How urgent is it?" Then "May we enter if you are out?" It shows everything and sends only after a yes. The manager reads the rows as JSON or CSV. See agent-fillable forms.
A tip
Sort by urgency first, then by problem area, so one trade can clear several jobs in a visit. Turn on the owner notice setting, notify_email, so you hear about each new request.
Find more in forms for landlords and forms for home services. A home inspection checklist finds problems before tenants report them. A tenant complaint form covers disputes between neighbours.
Questions
How do I handle emergencies?
Say in the form description that tenants should phone the emergency line first. A form is not a live alarm. The urgency answer helps you sort the day's list, not replace a call.
Can tenants add photos?
As a link only. Ask them to share a photo or video link in the last field. The form has no uploads, but the link arrives in the same row.
Can I pass requests to a contractor?
Yes, by CSV or by a signed webhook for every response. Filter by problem type first, so a plumber receives only plumbing rows.