Immediate acknowledgment
Return the reference, location, summary, recorded access choice, and what happens during triage. Repeat how to escalate a worsening or emergency condition.
Give residents a short mobile path to identify the property and unit, describe what they see, flag visible danger, choose contact and access preferences, and add useful evidence.
Publish emergency instructions beside the form. Staff—not the tenant—should apply the formal priority, responsibility, trade, and repair decision.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Explore the sample records before you copy the app. Add real tenant, access, vendor, and property information only in your own secured workspace.
Every field must either identify the place, explain the symptom, support safe access, or make communication easier.
Pre-fill what the signed-in tenant is already entitled to use where possible. For assisted intake, confirm the exact building, floor, unit, room, common area, or visible location so the team does not dispatch to the wrong place.
Use familiar categories plus a concise summary and description. Ask what is happening, where it appears, when it started, and whether the condition changes—not what component failed or which trade should attend.
Let the tenant explain whether a room, appliance, water, heat, power, access, or normal use is affected and whether they observe smoke, gas odor, flooding, sparks, heat, structural movement, or another immediate concern. Show the emergency route prominently.
Capture preferred contact, permission to enter or appointment need, useful service windows, pets or known access considerations where appropriate, and optional photos or files. Do not encourage unsafe inspection or unnecessary personal information.
The form must connect to a team, a response expectation, and a visible repair history.
Return the reference, location, summary, recorded access choice, and what happens during triage. Repeat how to escalate a worsening or emergency condition.
A coordinator checks location, symptom, impact, photos, safety signals, responsibility context, and access. If something is missing, ask one specific question rather than returning a generic incomplete status.
Connect the accepted request to the internal technician or vendor work, service window, access plan, blocker, and meaningful tenant update. Preserve the request even when several work orders are needed.
Explain what was done and any follow-up in plain language. Let the tenant confirm, report the issue unresolved, or reopen when the symptom returns.
Use conditional fields so the default path stays short.
| Field group | Ask the tenant | Leave to staff |
|---|---|---|
| Location | Property/unit and exact affected area | Portfolio coding or asset classification |
| Issue | Category, observable symptom, when it started and photos | Diagnosis, trade and repair scope |
| Impact | What cannot be used and visible safety concern | Formal priority, responsibility and emergency class |
| Access | Permission, appointment, contact and useful times | Technician/vendor assignment and route |
| Outcome | Whether the original issue is resolved | Cost approval, internal evidence review and supplier assessment |
A convenient digital form cannot be the only service path or a reason to collect unnecessary data.
Use readable labels, clear required fields, keyboard and mobile support, language assistance, and an alternative phone or staff-assisted route.
Avoid unrelated identity, household, payment, medical, or lease data. Control who can see contact, access, photos, internal notes, cost, and other resident records.
Explain which conditions require local emergency services, an emergency maintenance number, security, or another immediate channel. Do not imply that submitting the web form guarantees real-time monitoring.
Test the form with tenants and coordinators. Replace terms such as triage code, SLA class, disposition, or closure evidence with a clear next step and an understandable result.
Business administrators can shorten the mobile path and improve routing without rebuilding the downstream maintenance records.
A useful tenant request form can be built in hours and a focused field, condition, message, or route can often be improved in tens of minutes.Show property-specific access or front-desk questions only when relevant.
Add an issue-specific prompt that helps without asking for diagnosis.
Change acknowledgments and routing when response ownership changes.
Create a queue for unacknowledged, missing-information, no-access, or reopened requests.
Jodoo can connect mobile intake to internal triage, work orders, updates, evidence, and confirmation.
The tenant reports a need. Staff decide scope, priority, responsibility, service owner, cost, and whether a work order is appropriate.
A focused external or portal view should reveal only the request and communication needed for that user. Test actual permissions before using live tenant data.
Access, notice, habitability, emergency service, disability, language, charges, retention, and privacy obligations vary. Configure the form with accountable local review.
Include exact location, issue category, plain-language symptom, when it started, occupant impact, visible safety concern, preferred contact, access permission or appointment need, useful service times, and optional photos. Keep formal priority and technical diagnosis with staff.
It should display emergency instructions and collect visible warning signs, but do not rely on a normal web submission as the emergency response channel unless your organization truly monitors and guarantees it. Publish the correct immediate phone or local emergency route.
Yes. Photos can help clarify location and visible condition. Make them optional when possible, explain what is useful, protect privacy, and never ask a tenant to touch, open, climb to, or approach an unsafe condition.
The team acknowledges, checks completeness and safety, decides responsibility and priority, coordinates access, creates or links work, sends meaningful updates, records the outcome, and asks whether the original problem is resolved.
Yes, but prefer one governed model with conditional property-specific questions where practical. Too many disconnected copies make wording, routing, emergency instructions, and reporting harder to maintain.
Inspect the tenant-facing fields, then follow sample requests through status updates, triage, assignment, work, evidence, and confirmation.
Open the tenant request form