Batching small repairs when roof drainage may be involved

L

ledger.easy

Property investor
The people I’ve asked offline are split. A tenant in my Riyadh duplex has submitted several minor maintenance requests over the past few months. Each request is plausible and the rent is always on time, but separate call-out charges are adding up.

I want to stay responsive without sending someone for every non-urgent item. At the same time, I’m wondering whether the pattern could point to one larger roof-drainage problem. How would you decide what can be grouped, what needs prompt attention, and when to commission a broader inspection? If your answer depends on rules outside Saudi Arabia, please identify the difference.
 
Separate urgency from convenience. Anything suggesting active water entry, electrical exposure or worsening damage gets prompt attention. Cosmetic or low-impact items can be placed on an agreed visit list. Because roof drainage is a possibility, one focused inspection may cost less than repeated symptom-by-symptom call-outs. Keep the requests, photos, dates and work completed in one record.
 
Are the requests connected by location or timing? For example, do they concern the same side of the duplex or appear after rain, or are they unrelated things such as fittings and doors? Also, what does the maintenance history show? Frequency alone tells little; a cluster around one area is much more suggestive.
 
In Riyadh, arrange access according to the tenancy agreement and current Saudi requirements rather than copying a notice period from another country. For non-emergency visits, offer appointment windows in writing and get the tenant’s confirmation. That also makes grouping easier because both sides can agree which reported items will be covered during the visit.
 
A reliable payer who reports issues early may be protecting the property, not creating a problem. Compare the extra call-out costs with the possible cost of turnover, vacancy and preparing the duplex for a new tenant. If the rent is reasonably aligned with the market and communication is good, I would lean toward retention while improving the maintenance process.
 
I disagree with giving much weight to payment reliability when deciding whether a repair is necessary. Rent performance matters to the tenancy overall, but it does not establish whether a drain, seal or roof component is defective. The decision should rest on urgency, responsibility under the agreement and a competent diagnosis—not whether the tenant is otherwise easy to manage.
 
Those points can coexist. Payment history should not determine the technical response, but it does matter when choosing the tone and deciding whether this is really a tenant-management problem. Tell the tenant that non-urgent items will be consolidated into scheduled visits, while leaks or anything likely to worsen should still be reported immediately. That sets expectations without discouraging early reporting.
 
Another missing detail is whether the roof drainage serves only the rented unit or parts of both halves of the duplex. If components are shared, inspecting just the area nearest one reported symptom could miss the cause. Ask whoever attends to consider the drainage route and both affected and adjacent areas, rather than treating each request as isolated.
 
You can also reduce repeat charges through the scope given to the contractor. Send the full maintenance list before the appointment, identify which items may be related, and request findings on the suspected roof-drainage cause. That is different from simply asking someone to fix one visible symptom. Do not delay a potentially damaging leak merely to fill out the list.
 
A simple log would make the pattern clearer: date reported, location, description, photo received, urgency, attendance cost, work done and whether the issue returned. After a few entries you can distinguish repeat symptoms from unrelated wear. It also prevents arguments based on memory about how often someone attended or whether an earlier repair actually resolved the complaint.
 
One addition: keep deposit handling separate from this triage process. Frequent requests do not by themselves establish tenant-caused damage, and a deposit should not become a running maintenance account. Record evidence of cause and responsibility, then follow the tenancy terms and applicable Saudi rules if a deduction is ever considered.
 
For the drainage inspection, provide any photos or videos from when the symptom appears, especially if it is intermittent. Ask for the roof outlets, drainage path, visible connections and signs of moisture to be considered as one system. The useful outcome is not merely “cleared today,” but an explanation of whether there is a recurring obstruction, a defect or no connection between the requests.
 
From Doha, I would use a similar practical process but would not import Qatar’s contract or access assumptions into Riyadh. The rules that can change the answer are who is assigned maintenance responsibility, what notice is required for entry, and how deposits may be used. Those points need confirmation under the Saudi tenancy arrangement; the technical urgency of possible water damage is separate.
 
A workable next step is: acknowledge every request, ask for location and photos, classify anything potentially damaging for prompt attendance, and place genuinely minor items on one scheduled visit. Give the contractor the complete history and request a broader roof-drainage assessment. After that visit, compare the findings with the log. If one cause links the requests, repair it; if not, keep batching non-urgent work at an agreed interval.
 
You must log in or register to reply here.
Back
Top