A maintenance log is useful when it helps someone decide what happens next. A list containing only “AC problem,” “plumbing” and “done” leaves too many unanswered questions. The person following up needs to know which property, what was observed, who is responsible, what was approved and how closure was confirmed.
The method below is for organizing records. It is not a technical inspection, a repair instruction or a decision about legal responsibility for a cost.
Give each issue its own identity
Use one request reference per issue, such as M014. Keep the property or unit reference in a separate field. A property can have several open requests, and one contractor visit can address several issues. Mixing all of them into one row makes it difficult to see which defect remains unresolved.
A practical starting record contains the request reference, property reference, report date, observation, priority, responsible person, contractor, next action and target date. Add quote, approval, invoice, payment and evidence references as the case develops. Keep supporting documents in an appropriate controlled folder rather than embedding private details in a shared summary.
Describe the observation, not an unverified diagnosis
“Water drips below the kitchen sink after the tap runs” is a more useful observation than “replace all plumbing.” The first statement records what someone saw. The second assumes a cause and remedy that may not yet have been assessed.
Record the location, conditions and a photo reference when appropriate. Avoid taking photographs that expose residents’ documents or personal belongings. If the issue needs technical investigation, assign that question to a suitably qualified person. An immediate hazard needs the appropriate emergency or building response; it should not wait for the next spreadsheet review.
Separate the stages of the job
Reported, quoted, approved, completed and closed describe different stages. A quote is not approval to spend. A contractor saying the work is complete is not the same as the responsible reviewer confirming that the reported issue has been resolved.
Give every open request a next action and an owner. For example: “Request written scope and quote — assigned to coordinator — due Tuesday.” When the quote arrives, record its reference and move to the approval action. Keep earlier dates so the record explains how the case progressed.
Keep the cost fields distinct
Consider a fictional request with an approved spending limit of AED 500, an invoice for AED 450 and AED 200 already paid. These figures represent different things and belong in different fields.
The invoice balance is AED 450 − AED 200 = AED 250. Cost variance against the approved limit is AED 450 − AED 500 = −AED 50. The negative variance means the invoice is below that limit; it does not mean a payment of AED 50 is due. Payment status still depends on the AED 250 balance and the actual supporting records.
If an amount is unknown, leave it visibly unknown. Enter zero when you have confirmed a zero amount. Do not put an estimated quote into the invoice field simply to make a total appear complete. If the paid amount exceeds the invoice, investigate the allocation rather than hiding the difference.
Make closure evidence part of the record
Useful closure evidence can include a dated reinspection note, a completion photograph where appropriate, confirmation from the responsible person and the final invoice or payment reference. The evidence should relate to the original observation, not merely show that a contractor attended.
For M014, a closure note might state: “Sink tested after repair; no drip observed during the recorded check; photo M014-03; confirmed by the assigned reviewer.” This is a description of that check, not a certification of all plumbing in the property.
Run a short weekly review
Filter the log for open requests. Check overdue targets, cases waiting for approval, completed work awaiting confirmation and invoices with unexplained balances. Ask four questions for each remaining row: what is the next action, who owns it, when is it due and what evidence will close it?
Review the reasons for delay separately. “Waiting for access,” “quote not received” and “repair failed at recheck” require different follow-up. Keep a dated backup before reorganizing columns or formulas. If you sort or filter in a spreadsheet, keep the whole record together so an observation does not become detached from its property reference.
Start small and keep it usable
A shared log with ten reliable fields is more useful than a large dashboard that nobody updates. Begin with a few fictional requests, agree the status definitions and show the team how to record the next action. Add fields only when they help a real review decision.
Optional paid resource: the Property Maintenance Manager contains a prepared workbook. The process above can also be implemented in your own spreadsheet or approved record system.