Most tenant complaints about building management are not about the repair itself. They are about not knowing whether anyone received the request, who is coming, or when. A service request portal fixes that only if it is built around three things: capturing enough detail the first time, sending each request to the party that is actually responsible for it, and telling the tenant what is happening without them having to chase. This guide covers what the portal should capture, who is responsible for what under Dubai tenancy and jointly owned property law, how a request becomes a work order, what status updates to show, how to collect satisfaction scores, and a worked example.
Key takeaways
- Route by responsibility, not by building. In a Dubai tower the unit is the landlord's duty and the common parts belong to the management entity. The portal has to know which is which.
- Ask questions, set priority centrally. Tenants describe the fault; the help desk sets the priority that starts the SLA clock.
- One request, one record. Requests by phone, email or WhatsApp should land in the same queue as portal requests, or the reports will undercount.
- Close the loop with the tenant. Confirmation and a rating at closure tell you whether the job was really fixed.
Who is responsible for which request
A portal that sends every request to one inbox pushes the hard question, whose job is this, onto a coordinator who may not know the answer. In Dubai two laws decide most of it. The landlord and tenant law (Law No. 26 of 2007) sets the duties inside a leased property, and the jointly owned property law (Law No. 6 of 2019) sets who looks after the shared parts of a building with several owners.
| Rule | What it says | What it means for the portal |
|---|---|---|
| Law 26 of 2007, Art. 15 | The landlord hands over the property in good condition for the use stated in the lease. | Move-in defects are the landlord's to fix. Tag requests raised in the first weeks of a lease as handover snags. |
| Law 26 of 2007, Art. 16 | Unless agreed otherwise, the landlord is responsible for maintenance and for repairing defects or damage that affect the tenant's intended use. | Default route for in-unit faults is the landlord or the landlord's property manager. The lease can change this, so store the lease's maintenance terms against the unit. |
| Law 26 of 2007, Art. 17 | The landlord is responsible for defects and wear and tear not caused by the tenant. | Record the cause the technician finds. Wear and tear and tenant damage are charged differently. |
| Law 26 of 2007, Art. 19 | The tenant must maintain the property as an ordinary person would, and may not make changes or carry out maintenance works without the landlord's permission and the required licences. | Tenant-caused damage can be recharged. Fit-out and alteration requests need an approval step before any work order. |
| Law 6 of 2019, Art. 2 and 18 | Common parts are those designated for common use. The developer, a hotel project management company or a RERA-appointed management company is responsible for their management, operation, maintenance and repair, depending on the project category. | Lobby, lifts, corridors, risers, car parks and shared plant go to the management entity's help desk, not the unit landlord. |
| Law 6 of 2019, Art. 24 | The owners committee checks that the management entity carries out the management, operation, maintenance and repair of the common parts. | Common-area request history and response times are the evidence the owners committee will ask for. |
| Law 6 of 2019, Art. 40 | The developer stays liable for structural defects for 10 years from the completion certificate, and for defective installations for 1 year from handover of the unit. | In a new building, tag installation faults raised in the first year so they can be claimed from the developer. |
Other emirates and GCC countries have their own tenancy and strata rules, so the table is a Dubai example. The design point holds everywhere: each unit and each area of a building needs a responsible party recorded against it, so the portal can route a request the moment the tenant picks the location.
What the request form should capture
Every field the help desk has to phone the tenant back for adds a day. Every field the tenant does not understand gets skipped or filled in wrongly. Keep the form short, and make most answers a pick from a list rather than free text.
- Location from a list. Building, floor, unit, then room or area. For common areas, a short list such as lobby, lift, car park, pool or corridor. This is what drives routing.
- Category from a list. Air conditioning, plumbing, electrical, lifts, pest control, cleaning, access and security, other. Around ten categories is enough for a tenant; the help desk can refine it.
- Two or three urgency questions. Is water still leaking? Is anyone trapped? Is there smoke, a burning smell or sparking? The answers set the priority, not a “how urgent is this” slider.
- Photos or a short video. One photo often tells the technician which parts and which trade to bring.
- Access. Times the unit can be entered, whether someone will be home, and permission to enter with building security if not.
- Preferred contact. App notification, SMS, WhatsApp or email, and the language the tenant prefers for messages.
- A plain description. One free-text box, last, for anything the lists did not cover.
Fit-out, alteration and move-in or move-out requests are different. Under Article 19 the tenant needs the landlord's permission and the licences for works, so these should open an approval workflow with document uploads rather than a maintenance job.
From request to work order
The portal is the front door of the FM help desk, and it should feed the same queue as phone calls, emails and WhatsApp messages. If a request arrives outside the portal, the help desk logs it in the same system so it gets a reference number and appears in the reports.
Triage rules worth writing down
- The help desk confirms or changes the category and sets the priority using the definitions in the FM contract. The priority starts the response and resolution clocks agreed in the SLA.
- Duplicates are merged, not closed. Five tenants reporting the same broken lift should become one work order with five requesters, all of whom get the updates.
- Requests that belong to another party, such as a common-area fault raised through a landlord's portal, are passed on with the original timestamp and photos, and the tenant is told who has it.
- Anything the tenant must pay for, such as damage they caused or work outside the lease, gets a quote and the tenant's approval before the job is scheduled.
Status updates the tenant should see
Internal job statuses are usually more detailed than a tenant needs. Map them to a handful the tenant can understand, and send a message only when something changes that matters to them.
| Tenant sees | Triggered when | Message should include |
|---|---|---|
| Received | The request is logged | Reference number and what happens next |
| Accepted | The help desk confirms the category and priority | Who is responsible, and if it was passed to another party, which one |
| Scheduled | A visit is booked | Date and time window, and any access needed |
| On the way | The technician starts travelling | Technician name and the trade |
| Waiting | Parts, a quote approval or access are pending | What it is waiting for and who needs to act |
| Completed | The technician closes the job on site | What was done, before and after photos, and a confirm or reopen option |
| Closed | The tenant confirms, or the confirmation period passes | A one-question rating |
The photos at completion are the same field evidence owners use to check the contractor, which is covered in our guide to technician proof of work. Showing them to the tenant as well cuts down on “nobody came” disputes.
Satisfaction scoring that means something
Long surveys after every job get ignored. A single question at closure gets answered, and the option to reopen tells you more than the score does.
- One rating, one optional comment. Ask how satisfied the tenant is with the job on a five-point scale, with a comment box that opens for low scores.
- A reopen button. A job reopened within a set period counts against the first-time fix, whatever the rating says.
- Score the job, not the building. Attach each rating to the work order, so it can be reported by contractor, trade and building.
- Set a minimum count. A contractor's monthly average from three responses is noise. State in the scorecard how many responses are needed before the rating counts.
Used this way, satisfaction and reopen rates can sit next to SLA compliance on the monthly contractor scorecard.
Worked example: a leak in a Dubai Marina tower
A tenant in a leased apartment in a jointly owned residential tower reports water dripping from the ceiling of the bathroom. The tower is managed by a management company on behalf of the developer; the apartment is let by an individual owner through a property manager. This is an illustrative scenario.
- The tenant picks the building, floor, unit and “bathroom”, chooses plumbing, answers “yes” to “is water still leaking” and adds two photos. The portal gives a reference number at once.
- The unit is recorded against the landlord's property manager, so the request goes to their help desk. The leak answer sets an urgent priority under their contract with their maintenance contractor.
- The technician finds the leak comes from a shared drainage stack in the riser above the ceiling. That stack is a common part under Article 2 of Law 6 of 2019, so its repair falls to the management company under Article 18.
- The property manager's help desk passes the request to the management company's help desk with the original time, photos and the technician's note. The tenant sees “Passed to the building management company” and the new reference.
- The management company repairs the stack. The landlord's contractor returns to repair the ceiling, which is damage inside the unit affecting the tenant's use, a landlord duty under Article 16 unless the lease says otherwise.
- Both jobs close with photos. The tenant confirms and rates the fix. The owners committee can later see the stack repair in the common-area history.
Without location-based routing and a hand-off step, this request usually turns into two phone calls, a WhatsApp thread and a dispute about who caused the ceiling damage.
Common mistakes
- A free-text location field, so requests cannot be routed or reported by building and floor.
- Letting tenants choose the priority, so every request is urgent and the SLA figures stop meaning anything.
- Closing a request when it is passed to another party, so the tenant loses track and the hand-off is never measured.
- Separate systems for the portal and the help desk, so phone and WhatsApp requests never appear in the portal history.
- No record of lease maintenance terms against the unit, so the help desk cannot tell landlord work from tenant work.
- A satisfaction survey with ten questions, sent days after the job.
Where Reflexion fits
Planning a tenant portal for your buildings?
We can show how requests are routed by unit and common area, how tenants see each status change, and how ratings feed the contractor scorecard.
Frequently Asked Questions
What is a tenant service request portal?
It is a web page or app where tenants and residents report faults and request services, such as a leaking air conditioning unit, a blocked drain or an access card. Each request is logged with its location, category and photos, passed to the help desk as a work order, and tracked until it is closed, with the tenant able to see its status at every step.
Who is responsible for maintenance requests in a rented property in Dubai?
Under Article 16 of Dubai Law No. 26 of 2007, the landlord is responsible for maintenance and for repairing any defect or damage that affects the tenant's intended use of the property, unless the lease says otherwise. The tenant must look after the property as an ordinary person would (Article 19). In a jointly owned building, the common parts are the responsibility of the management entity under Article 18 of Law No. 6 of 2019, not the landlord of an individual unit.
Should tenants set the priority of their own requests?
No. Tenants should answer a few plain questions, such as whether water is still leaking or whether anyone is stuck in a lift, and the help desk should set the priority from those answers. Priority starts the SLA clock in the FM contract, so it has to follow the contract's definitions, not how urgent the request feels to the person raising it.
What should a tenant see after raising a request?
A reference number straight away, then a short update at each change of status: accepted, scheduled with a visit time, technician on the way, completed, and a request to confirm the fix and rate the service. If the request is passed to someone else, such as the building's management company for a common-area fault, the tenant should be told who now has it.
How do satisfaction ratings from a portal feed into contractor performance?
Ask one rating question when the job is closed and allow the tenant to reopen it if the fault is not fixed. The share of jobs reopened and the average rating per contractor and trade can then sit on the monthly contractor scorecard next to SLA compliance, as long as the scorecard states the minimum number of responses needed for the score to count.
Related reading
What Is an FM Help Desk?
The channels a help desk handles and how requests become work orders.
Technician Proof of Work
The field evidence that closes a job and settles disputes.
FM Contractor Performance Evaluation
Putting SLA, reopen and satisfaction figures on a monthly scorecard.
Work Order KPIs
The 12 measures FM teams track once requests become jobs.
