From Report to Close: Running Maintenance Requests

From Report to Close: Running Maintenance Requests

Part three moved the money cycle out of memory and into a process with dates, owners and defined paths. Now we move to the second cycle that runs daily in any property portfolio, and the only one your tenant starts rather than you: maintenance.

The difference between the two cycles is that money has dates known in advance, while maintenance arrives without an appointment. An air conditioner dies on a Friday, a leak appears at night, a lift stops in a building housing six families. That randomness is exactly why maintenance needs a fixed process, because anything that arrives suddenly and finds no ready path goes to the easiest place available: a private chat on an employee's phone.

Where accountability dies

Send me a photo on my WhatsApp looks like fast service for the tenant. In practice it is the point where accountability evaporates. When a report lives in a private chat, five things happen at once:

• The report becomes owned by a person, not the office. If that employee travels, leaves or changes phone, everything not yet done leaves with them, and nobody even knows what was lost.
• Nobody knows how many reports are open right now. The simple question of how many requests are live today has no answer, because they sit scattered across conversations that no single list gathers.
• Priority goes to whoever pushed hardest. The tenant who sends five messages gets served before the one who sent a single message, even when the second report is the more dangerous one for the building.
• Cost disappears. The technician does the work and is paid in cash or by transfer, and that amount never attaches to the unit it was spent on. The year ends and you cannot say which unit cost you more than it brought in.
• There is no close. A report ends when the tenant stops asking, not when they confirm the fault was actually fixed. The difference between those two shows up a month later when the same fault returns.

None of these five is a negligence problem. The employee wants to help and the technician does the work. The problem is that the report was never recorded against the unit, so it stayed an event in someone's memory — and people's memories are not a record for an asset you own or manage.

A report is a small work order

The easiest way to bring maintenance under control is to stop treating a request as a message and start treating it as a small work order. And a work order is not one unless it carries six elements:

• The source. Who reported it, when, and through which channel. A tenant report is different from an observation on a routine inspection or from a technician who was in the building for another job, and recording the source is what makes the unit's history readable later.
• The unit. The specific unit and building, not the tenant's name — because the asset the fault recurs on is the unit, and tenants change above it.
• Description and evidence. A short text and one or more photos. The photo taken at report time is what later settles the question of whether the fault existed before or after move-in.
• Priority. From a closed list, set by a written rule rather than a judgement made in the moment.
• Assignee and target date. A named person or contractor, and an expected date the tenant is told about.
• Cost and close. The actual amount charged against the unit, and a confirmation from the tenant that the fault was resolved.

These six are not extra bureaucracy. Each one answers a question you will need answered later: who is following it, which asset failed, is the complaint documented, why was this served before that, who did the work, what did it cost, and did it actually end.

Priority is a written rule, not a feeling

Nothing consumes more of an office's time than internal negotiation over what gets done first. The fix is not a daily meeting but a rule written once and published to the team. A practical rule classifies reports with three questions in order: is there a safety risk, does it prevent use of the unit, and does it get worse if delayed.

• Urgent. Anything touching safety, disabling an essential utility, or widening the damage with every hour: a water leak, an electrical fault, a stopped lift, a door that will not lock. Responded to immediately, even temporarily, to stop the damage.
• Important. Anything that disables part of the unit without spreading fast: an air conditioner in one room, a water heater, a kitchen appliance. It gets a near date, announced to the tenant.
• Routine. Improvements, appearance and defects that do not affect habitability. Batched and executed together on a scheduled visit — which on its own saves repeated technician trips to the same building.

What matters in this classification is not its precision but its consistency. When the rule is written, an employee can explain to a tenant why their request happens tomorrow and not today, and the owner can review the decision a month later. A rule that is never written defaults automatically to a single rule: whoever shouts loudest.

From assignment to close

After classification the execution loop begins — four steps, each leaving a written trace:

• Assignment. The request goes to a named technician or contractor with the description, the photos and a date. An assignment recorded without an explicit name reverts to being everyone's responsibility, which means nobody's.
• Coordinating with the tenant. An agreed and pre-announced access time. The most common reason a technician visits without doing the work is arriving to find nobody in the unit, and that is a paid visit with no result.
• Execution and documentation. What was actually done, any parts used, an after photo and the amount. That amount is charged to the unit rather than to general expenses, and it is this link that later lets you know maintenance cost per unit.
• Close with tenant confirmation. The office does not close the request alone; it closes on confirmation from whoever reported it that the problem is over. If no confirmation arrives within a reasonable window, it closes with that fact explicitly recorded.

There is a fifth step almost everyone skips: warranty and recurrence. When the same fault returns in the same unit within a short period, the problem is not the fault but the repair or the person who did it. Linking the new request to the previous one on the same unit is what makes that pattern visible instead of paying for it twice.

Documentation protects both sides

Some owners assume that documenting maintenance is a procedure that protects the tenant at the owner's expense. In fact it protects both, in different ways.

The owner or the office gets a record proving they responded, when, and at what cost — exactly what is needed in any dispute over obligations, or when deducting from a deposit at the end of a contract. They also get a technical history of the asset: how often this lift failed, which contractor's work keeps coming back a month later, and which unit consumes more of its own income than it appears to.

The tenant gets something simpler: knowing the report was registered, that it has a number and a date, and that they do not have to resend it every two days to keep it alive. That point connects directly to renewal from the previous part, because what pushes a good tenant not to renew is usually not the price but the feeling that their requests disappear.

In short-stay hospitality units the effect is sharper still, because the gap between a ready unit and one with a small unfixed fault surfaces in a public rating that every future guest reads. Readiness there is not good intentions but the result of a checklist run between every two guests and logged like any other maintenance request.

The Origami view

Real estate and hotels is one of our specialisation sectors, and we treat a maintenance request as a work order tied to a unit, not as an incoming message to an employee. The practical difference is that a work order has a measurable state, a response time you can compare, and a cost that accumulates against a specific asset — while a message leaves nothing behind but an impression.

The order we recommend: open one announced intake channel for tenants instead of personal numbers, then link every report to its unit the moment it arrives, then write the priority rule and adopt it, then close the loop with tenant confirmation and cost. We apply this order in real estate and hotels projects because measuring response time or cost per unit before intake is under control produces numbers that do not reflect what is actually happening.

What you can do this week

These steps need no new tool, and they size the problem before any purchase decision:

• Collect every open report today onto one sheet from all the team's phones and WhatsApp groups. The count alone will surprise you, and it is the first number you have ever owned in this area.
• Write the unit and arrival date against each report and calculate how many days have passed. Anything older than two weeks is your immediate priority list.
• Define one intake channel and tell every tenant about it in writing, then stop accepting reports on personal numbers.
• Write the priority rule on one page with three levels and examples of each, and adopt it for the team without exception.
• Calculate two numbers: the average days from report to close over the last two months, and how many faults recurred in the same unit. Those are the baseline you will measure every later improvement against.

Coming next

We have fixed status, then money, then maintenance. The next part goes down to the layer all three lean on the moment a dispute starts: documents. The contract and its annexes, tenant identity, the handover record with photos, payment receipts and maintenance reports — attached to the unit rather than to a folder named after an employee, and what a dispute actually needs as evidence.

Sources

• Real Estate General Authority — regulation of the Saudi real estate sector and its platforms and services.
• Ejar Network — registration of lease contracts and the data of their parties and terms.
• Ministry of Municipal and Rural Affairs and Housing — policies governing the municipal and housing sectors.
• Ministry of Tourism — regulation and licensing of tourist accommodation facilities in the Kingdom.
• Zakat, Tax and Customs Authority — e-invoicing requirements relevant to documenting expenses and services.
• Saudi Vision 2030 — the national direction for the housing sector and service quality.