An eight week summer absence is the hardest thing a UAE garden faces, and what fails does so in a fixed order. This guide sets out that failure sequence week by week, identifies the one component that takes everything down at once, lists what to automate before you fly, covers the jobs no timer can handle, and explains when to arrange a person instead.
What fails first in an unattended garden
Failure follows an order. Small containers go in week one, new plantings in week two, the far ends of irrigation lines in week three, hedges and container trees in week four, emitters and filters through weeks five and six, and salt across the whole garden by week eight.
Week one takes the small pots. A 3 litre container in direct sun loses its water inside 36 hours at 45C, so anything off the dripline is finished before the second weekend.
Week two takes whatever went in over the previous six months. Those root balls sit in the top 20 cm of soil, which is the layer that dries fastest, with no deep roots to fall back on.
Week three exposes pressure problems. Plants at the end of a long lateral get the least water when supply pressure drops, and the shortfall only shows late.
Week four shows on hedges and container trees as scorch down the west facing side, which carries an afternoon load the plant cannot cool.
Weeks five and six are silent. Fine sand clogs the emitters, the filter loads up, flow drops, and nothing looks wrong from the gate.
By week eight, evaporation has concentrated salt in the top soil layer across every bed, which leaves a pale crust and root damage that outlasts the trip.
The component that takes everything down
The irrigation controller is the single point of failure. Every plant on the system depends on it, and three things stop it: a flat backup battery, a tripped circuit after a power cut, and a solenoid valve that sticks closed. Any one of them ends irrigation garden wide in a day.
Battery backed controllers hold their programme through a power cut, and the battery itself lasts months. Change it before travelling anyway, because the cost of being wrong is the whole garden.
A stuck solenoid is the harder failure to catch, since the controller still reports that it ran the cycle. Run every zone by hand and watch water arrive at the far end of each one.
Where a system has no pressure gauge, no filter or no zone separation, that's worth correcting before a long absence. Fitting a controller with zone valves, a filter and a pressure regulator is standard work under irrigation services, and it's the difference between one failure point and a garden that keeps running.
What to automate before you fly
Six tasks in the week before departure cover the automatable part. Reprogramme the controller for summer, flush the lines, clean the filter, extend drip to every container, mulch to 5 cm, and run a full manual test of each zone. Done in that order, each one verifies the last.
- Reprogramme for summer by shifting to daily cycles before sunrise. Increase the run time rather than adding a second daytime cycle, so the water reaches below 20 cm.
- Flush the lines by opening the end cap on each lateral and running it until the water leaving is clear of sand.
- Clean the filter by pulling the screen at the head, rinsing it and refitting it. A loaded filter starves the whole system.
- Extend drip to the containers with 4 mm microtube and one emitter per pot. Pots are the first casualties and the easiest thing to protect.
- Mulch to 5 cm with gravel or bark over open soil, which cuts surface evaporation and slows the salt crust that forms by week eight.
- Test every zone manually, walking each one while it runs to confirm water arrives at the last plant.
Move every pot that can be moved into afternoon shade before you go. A container that gets sun only until noon uses close to half the water of the same pot in full exposure.
What no timer can cover
Four jobs need a person on site: clearing drifted sand after a storm, spotting a failed zone, cutting back growth that blocks an emitter, and removing dead material before it spreads pests. None of them can be scheduled, because all four depend on events during the absence.
Pest outbreaks are the clearest case. Spider mites build up fast in hot dry air and spread from a few leaves to a whole hedge inside three weeks.
Lawns are the other. Turf on a summer schedule grows right through the absence, and the cut waiting on return takes off more than a third of the blade height, which damages the grass at the worst time of year.
Arranging cover instead
For an absence beyond four weeks, a visit every two weeks catches everything on the failure list before it turns terminal. The visit needs to check the controller, walk the zones, clear storm sand, cut the lawn and look under leaves for mites, every time.
Booking a fortnightly garden maintenance service before departure fixes the schedule while you are still around to explain the system. Hand over the controller programme, the location of the isolation valve and a note of which zone feeds which bed.
FAQ
Ahead of a long summer trip, 3 questions matter. What breaks first, what can be set up in advance, and whether a timer on its own is enough for eight weeks.
What fails first in a UAE garden while nobody is there?
Small containers in the first week, because a 3 litre pot in full sun exhausts its water inside 36 hours at 45C. Plantings under six months old follow in week two, then the far end of each irrigation line in week three.
What should be automated before travelling for the summer?
Reprogramme the controller to daily pre sunrise cycles with longer run times, flush the laterals, clean the filter, run microtube drip to every container, mulch open soil to 5 cm, and test each zone manually with water actually on the ground.
Can an irrigation timer cover an eight week absence on its own?
Only for the watering, and only if nothing breaks. A timer cannot clear sand after a storm, notice a clogged emitter, cut a lawn or catch a spider mite outbreak. That is why a fortnightly check is the practical limit on an absence this long.