Most repair disputes don't start with the repair. They start with the fortnight after it was reported, when nothing visible happened and nobody said why.
A contractor who can't come until Thursday is not a problem. A contract-holder who doesn't know a contractor has been booked is. The gap between those two situations is a single message, and it's the message that most often doesn't get sent.
This guide sets out a working process for handling a repair report from the moment it arrives to the moment it closes. It's about how to run the job, not about what you're legally obliged to do. For the obligations themselves, go to the official guidance linked at the end.
The First Hour
Three things, and none of them involve fixing anything.
-
Acknowledge it:
A reply confirming you've received the report, sent the same day, does more for the relationship than anything else you'll do on the job. It costs a minute. It also establishes, in writing, that you knew. -
Record it before you act on it:
Date received, how it came in, who from, what they said, in their words rather than your summary. Do this before you start chasing contractors, because that's the point at which the original report gets paraphrased into something more convenient. -
Ask the question that saves the wasted visit:
Most reports arrive underdescribed. "The boiler's making a noise" could be four different jobs. A photograph, a short video, or two clarifying questions will often tell you whether you need a plumber or an electrician, and whether it's urgent.
Triage: Three Questions
Before booking anything, work out which of these you're dealing with.
-
Is anyone at risk right now?
No heating in February, a suspected gas leak, an electrical fault, a security failure on a door or window. These get moved to the front regardless of what else is in the queue. -
Is the property deteriorating?
A slow leak isn't dangerous today and will be expensive in a month. Water damage compounds. So does damp. These deserve faster treatment than their inconvenience level suggests. -
Is it inconvenience only?
A dripping tap, a sticking window. Real, worth fixing, and it can be scheduled rather than dropped everything for.
The mistake is treating urgency as a function of how insistently it was reported. Some people apologise for reporting a genuine hazard. Others escalate a loose cupboard door. Assess the thing, not the tone.
Keeping the Contract-Holder Informed
This is the part that decides whether a slow repair becomes a complaint.
-
Tell them what's happening even when nothing is:
"The plumber can't get here until Thursday" is a satisfactory update. Silence for four days is not, and it's the same four days either way. -
Give a realistic date, not an optimistic one:
A date you meet is worth more than an early date you miss. If you're waiting on a part, say you're waiting on a part. -
Confirm access arrangements in writing:
Who is coming, roughly when, and whether the contract-holder needs to be there. Most access disputes are actually diary misunderstandings. -
Close the loop explicitly:
When the work is done, ask whether it's resolved. Their answer, in writing, is the single most useful line in the whole file. It also catches the jobs that were done badly, before they come back as a second report.
Working With Contractors
-
Brief them with the contract-holder's actual words:
A contractor told "check the damp in the bathroom" and one told "contract-holder reports black mould on the ceiling above the shower, worse after showering, appeared about six weeks ago" will do different quality work. -
Ask for a written outcome, not just an invoice:
What they found, what they did, and whether anything else needs attention. The invoice tells you what you paid. The outcome note tells you what's actually happening in the property, and it's what you'll want if the same issue returns. -
Notice repeat visits to the same property:
Three separate call-outs for related symptoms usually means the underlying cause was never found. Repeat visits are a signal, and they only look like a pattern if someone is holding the history in one place. Records kept alongside the property rather than scattered across inboxes and invoices make that pattern visible while it's still cheap to fix.
When It's Not Straightforward
-
When the contract-holder reports something you think isn't your responsibility:
Investigate anyway, and explain your reasoning in writing rather than just declining. A refusal with a reason is a conversation. A refusal without one is the start of a complaint. If you're unsure where responsibility sits, that's a question for the occupation contract and the official guidance, not for a judgement call in the moment. -
When you can't get access:
Log every attempt with dates and methods. Access problems are among the most common reasons a repair drags, and the only defence to "they did nothing for two months" is a record of the six times you tried. -
When the contract-holder is unhappy with the work:
Treat a complaint about quality as a new report rather than a continuation of the old one. Log it separately, with its own date. Merging the two is how a two-week job appears in the record as a four-month one. -
When there's an ongoing dispute:
Keep the tone of your written communications level. Anything you write may be read later by someone with no context and no stake in your side of it. Write it for that reader.
The Record You Want at the End
When a repair closes, the file should be able to answer six questions without anyone having to remember anything:
|
Question |
What answers it |
|---|---|
|
When was it reported? |
The dated inbound log entry |
|
What was reported? |
The contract-holder's own description |
|
What did you do first? |
Your acknowledgement and any clarifying exchange |
|
Who attended and when? |
The booking and the contractor's confirmation |
|
What was found and done? |
The contractor's written outcome |
|
Was it resolved? |
The contract-holder's confirmation |
If all six are there with dates, you have a complete account. If the first and last are missing, which is the usual pattern, you have a folder of invoices and a memory.
A system that timestamps entries as they happen removes the reliance on someone remembering to write it up afterwards, which is the step that reliably gets skipped when the job itself went fine.
Conclusion
The repairs that turn into problems are rarely the difficult ones. They're the ordinary ones that went quiet.
A process that acknowledges on the day, triages honestly, updates even when there's nothing to report, and closes the loop in writing will handle the vast majority of what comes in without anything escalating. It also produces the record you'd want if something did.
None of it is complicated. It's just the part that gets dropped when you're busy, which is exactly when it matters.
Frequently Asked Questions
1. What's the first thing to do when a repair is reported?
Acknowledge it in writing the same day and log it with the date, before you start arranging anything. Both take a minute and both matter later.
2. How quickly do I have to respond?
That depends on your obligations and circumstances, which is a question for the official guidance and your occupation contract rather than a blog. As a matter of practice, treat urgency as a function of risk to the occupier and to the property, not of how the report was phrased.
3. Should I use messages or email?
Whichever the contract-holder actually uses. What matters is that the substance ends up in your property records with a date, the same day, rather than staying on a phone.
4. What if I can't get access to do the work?
Log every attempt, with dates and how you tried. Access problems are a common cause of delay and the record is the only thing that distinguishes a delay from inaction.
5. Do I need to keep contractor reports as well as invoices?
It's worth it. The invoice records what you paid; the outcome note records what's happening in the property, and it's what tells you whether a recurring problem was ever properly diagnosed.
6. Where do I check what I'm actually required to do?
Welsh Government publishes guidance for landlords covering property condition and repair obligations, linked below. Check your occupation contract as well.
Important Notice
This article applies to Wales only, and it covers operational practice rather than legal requirements. Housing law is devolved, and Wales operates under the Renting Homes (Wales) Act 2016, using occupation contracts and contract-holders rather than tenancies and tenants. Guidance written for England does not apply here.
Nothing in this guide states what repairs you are responsible for, how quickly you must act, or what standard the property must meet. Those depend on your circumstances, your occupation contract and legislation that changes. Confirm your position using the Welsh Government's fitness for human habitation guidance for landlords and the Welsh Government's frequently asked questions for landlords, and take advice where it matters.
This content is general information only and does not constitute legal advice. RIOO is not a law firm.