Maintenance request form
A maintenance request form closes the gap between a tenant noticing a problem and a manager knowing about it. Instead of a phone call or a lost email, a tenant picks the issue category, states the unit number, and attaches a photo if one helps. Urgency is a self-reported field at submission time — routine fixes can queue, emergencies get flagged — so a repair crew knows what to act on first.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
A photo attaches directly to the request
A tenant can photograph a leak or a broken fixture from their phone and attach it to the same submission. It is stored with that response, not sent as a separate email, so it stays linked to the request permanently.
Webhook delivery notifies your team instantly
Each request posts to Slack or a webhook the moment it is submitted, so your team reacts to the unit number in a channel rather than checking an inbox.
This one uses file uploads, which is a paid feature — you can build and edit it on the free plan, but saving it needs an upgrade.
No card required.
Maintenance Request
Live previewHow to build this form
5 steps in the editor.
- Add a text field for the tenant name and an email field so you can acknowledge the request or ask a clarifying question.
- Add a required text field for the unit or apartment number, so you know exactly where the problem is.
- Add a dropdown with your issue categories — plumbing, electrical, appliance, HVAC, other — so requests route without you reading each description first.
- Add a textarea for the issue description and an optional file field for a photo of the problem.
- Add a radio group for urgency — routine, urgent, emergency — and connect the form to Slack or a webhook so your team is notified the moment it arrives.
Fields in this form
8 fields, using 7 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Your name | Short text | Yes |
| Unit or apartment number | Short text | Yes |
| Email address | Yes | |
| Phone number | Phone | Optional |
| Issue category | Dropdown | Yes |
| Describe the issue | Long text | Yes |
| How urgent is this? | Radio buttons | Yes |
| Upload a photo (optional) | File upload | Optional |
What goes wrong with this form
Specific to a maintenance request form, not general advice about forms.
Leaving the unit number optional
A request with no unit number cannot be acted on. Make it required — a tenant will not skip a required field, and you cannot receive a request you have no way to locate.
Using a text field instead of a dropdown for issue type
Free text returns "plumbing leak", "plumbing", "water" and "leak in bathroom" for the same problem. A dropdown of your actual categories keeps every response sortable from submission.
Not capturing urgency at all
Without a structured urgency field, every request reads the same until someone opens it. A radio group with clear options sets expectations at submission, so routine and emergency requests are distinguishable in the export, not just in someone's memory.
Questions about this form
Can tenants attach a photo of the problem?
Yes — an optional file field lets them photograph a leak, a broken appliance or damage from their phone. The photo is stored with that response permanently, visible to your whole team without a separate email.
How do I get notified of a new request?
Add a webhook destination pointing at your own system, or turn on Slack delivery in Settings. Each request posts the moment it is submitted, so your team can respond from the channel directly.
Can I sort requests by urgency or type?
Yes. A dropdown for issue category and a radio group for urgency are both structured fields, so the CSV export can be filtered or sorted by either column without reading every description first.
This one uses file uploads, which is a paid feature — you can build and edit it on the free plan, but saving it needs an upgrade.