Tenant repair reporting with photos: one visit, right trade

This post in 30 seconds.

• The problem: a repair raised as "leak in bathroom" sends a plumber to what turns out to be a roof, and the Housing Ombudsman investigated 43% more repairs complaints in 2024-25 than the year before.
• The fix: let the tenant show you. A guided photo and video capture on their own phone, step by step, no app, arriving as a dated case your repairs team can diagnose from the desk.
• The clock: under Awaab's Law, the day you become aware of a damp and mould hazard is day zero. A dated, structured report is your record of that day.
• Who this is for: repairs and maintenance managers, customer-service leads and digital leads at housing associations, council housing teams and large landlords in the UK and Ireland.

Every repairs manager has a version of this job. The call handler logs "damp patch, bedroom ceiling". A plasterer attends, looks up, and says it's a roof.

The roofer comes a week later without the right flashing. Third visit, the tenant is at work, and the job closes as no access.

Nothing in that chain was anyone's fault. The report was just too thin to diagnose from. Martin Crossland, Head of Customer Repair Contact at Southern Housing, puts it plainly in a piece on getting repairs right first time: "we need multiple visits to identify the issue, which delays repairs and can be frustrating for residents."

This guide is about fixing that at the point of report. What a good tenant repair reporting flow asks for, in what order, why a single attached photo isn't enough, how the submission lands in your repairs system, and how you'd measure whether first-time fix actually moved.

Repairs managers at housing associations and council housing teams know the job that gets raised as "damp patch, bedroom" and turns into three visits and a stage-one complaint. We build Venta Capture, VentaVid's guided capture product, so that the tenant can show you the fault properly before anyone is dispatched. See how it handles a repair report, then decide whether it fits your repairs process.

In this post:

• Why the second visit happens
• The clock is now regulated
• Why "attach a photo" in a portal fails
• What a good repair reporting flow asks for, step by step
• How the submission feeds the repairs system
• How to measure first-time fix on photo-reported jobs

Why the second visit happens

The repair report is the diagnosis input, and most of them are written by someone who has never seen the fault. A tenant describes what they can see, a call handler picks a trade from a script, and an operative finds out what the job really is when they open the front door.

The Regulator of Social Housing's Tenant Satisfaction Measures for 2024/25 put the scale on it. Landlords completed just under 15.1 million responsive repairs in the year, over 11 million of them non-emergency. Sector-wide, 79% of those non-emergency repairs were finished within target, and the median landlord had 69.5% of tenants satisfied with the time the last repair took.

So roughly one non-emergency repair in five misses its target. Not all of that is diagnosis, but a lot of it is.

I read the Housing Ombudsman's repairs casework for this piece, and the pattern that kept coming back was not exotic. The Ombudsman's Repairing Trust spotlight report (June 2025) says it directly: "it can be basic failings we see repeatedly, and that sit behind 1 in 4 repairs not being done on time." One case in the report had a diagnosis that identified 19 separate repair jobs and no plan to carry them out, which produced "excessive delays, multiple repeat contractor visits, and a finding of maladministration."

The same report has two lines every repairs manager should pin above the desk. Operatives told the Ombudsman about "the value of being able to upload photos or additional information to help diagnose issues correctly." And external contractors reported "receiving outdated or incomplete information" from landlords.

Both point at the same fix. Get the picture before the van moves.

The cost unit, by the way, is the visit, not the repair. Housemark's first look at 2024/25 year-end results has landlords completing an average of 3.3 repairs per property. If a meaningful share of those need a second attendance because the first one was a diagnosis trip, the waste is in the fleet, the operative's day and the tenant's patience, long before it shows up as a complaint.

The clock is now regulated

In England, the day you become aware of a potential damp and mould hazard is day zero, and every deadline that follows counts from it. That is the part of Awaab's Law that changes how a repair report has to work.

The government's guidance on Awaab's Law timescales, in force for social landlords in England since 27 October 2025, sets these out:

• Emergency hazards: investigate and make safe within 24 hours.
• Significant damp and mould hazards: investigate within 10 working days of becoming aware.
• Written summary of findings: to the tenant within 3 working days of the investigation concluding.
• Safety work: begin within 5 working days of the investigation ending. Where preventative work can't start straight away, physical work within 12 weeks.
• Records: the guidance expects "clear records of all engagement, investigations and communications with tenants."
• What's next: in 2026 the regulations extend to excess cold and heat, falls, structural collapse, fire and electrical hazards, and in 2027 to all remaining HHSRS hazards.

Read "becoming aware" against how most reports arrive today. A phone call with no photo. An email with a blurry attachment that sits in a shared inbox.

A note in the tenant portal that nobody assigns. In each case the clock has started and the landlord may not know it.

The complaints data shows what that costs. In its Annual Complaints Review 2024-25, the Housing Ombudsman investigated 43% more complaints about repairs than the previous year, upheld 73% of them, and reports that over 40% of all compensation ordered was for failures in handling leaks, damp and mould. Repairs featured in 45% of the cases assessed as high risk.

The money is going in. The Regulator's Global Accounts show the sector spent £10bn on repairs and maintenance in 2024/25, up 13% on the year, partly driven by the management of damp and mould.

Spend is not the constraint. Information at the point of report is.

Ireland: a different statute, the same problem

Ireland has no Awaab's Law equivalent, but the obligation is there. The Housing (Standards for Rented Houses) Regulations 2019 apply to dwellings rented from private landlords, local authorities and approved housing bodies, and require a home to be kept "in a proper state of structural repair" and "not defective due to dampness or otherwise", according to an Oireachtas Library and Research Service spotlight from June 2024.

Redress splits by provider: local authority tenants use the council's complaints procedure, while AHB tenants can also go to the Residential Tenancies Board. The same spotlight notes the European Committee of Social Rights found the State had "failed to collect complete statistics on the condition of Local Authority housing since 2002". If you run repairs for a council or an AHB, a dated visual record per report is the cheapest stock-condition evidence you will ever gather.

Why "attach a photo" in a portal fails

Most portals already have an "add a photo" button. It's optional, unguided, and it produces one image. A single tenant photo usually answers the wrong question: it shows that something is wrong, not what it is or where it comes from.

The failure modes are predictable:

• Wrong angle. A close-up of black mould with no wall, ceiling or window in frame. The surveyor can't tell condensation from a leak.
• No scale. A stain that could be the size of a coin or a dinner plate. The operative brings the wrong quantity of everything.
• No context. No shot of the room, the radiator, the extractor fan, the window. The things that explain the fault are exactly the things the tenant didn't think to photograph.
• No source. A water mark on a ceiling with no photo of the bathroom above it or the gutter outside.
• No words. The tenant knows it's worse after rain, or only when the shower runs. None of that is in the picture.
• No provenance. A gallery upload with a phone-clock date proves little. The best gallery photo in the world doesn't tell you when it was taken or whether it was edited.

That last one matters more now that Awaab's Law asks when you became aware, and it's why the tenant-advice pages tell residents to "keep evidence". Evidence for the tenant is not the same thing as diagnosis for you.

Guided capture flips who decides what gets photographed. Your organisation writes the sequence: what to show, in what order, with an example photo and a one-line instruction per step, and a short video with the tenant talking over it.

The tenant follows the steps on their own phone. If a step is missing, the reviewer asks for a retake of that step, not a whole new report. We wrote up the general case in guided photo capture: what it is and why uploads fail.

The effect on dispatch is the whole point. In customer-support use, Venta Capture reports that 23% of customer problems are solved without dispatching a technician at all, and the ones that do need a visit arrive with the technician already briefed.

If you'd like to see what a guided repair report looks like from the tenant's side and from the desk, take a look at Venta Capture.

What a good repair reporting flow asks for, step by step

Start with the operating model, because it decides everything else. The capture is asynchronous: you send the link now, the tenant records when they're home, your team reviews when it's ready. No video call to schedule, no operative on the other end of a camera, no appointment for something that only needed a look.

That matters in housing more than almost anywhere. Tenants work shifts. Your planners are already juggling 3.3 repairs a property.

Fifteen million responsive repairs a year cannot each get a scheduled call. Send now, capture later, review when ready.

Here's a general repair reporting flow that works as a first standard flow. Adjust the wording to your own trades.

1. Identify the tenancy or job. The link already carries your reference if you sent it from the repairs system; if the tenant came in from a QR code on a rent statement or a landing page, ask for the address and postcode first.
2. Where in the home? A single-choice list: kitchen, bathroom, bedroom, living room, hallway, outside. This alone steers the trade.
3. The whole room. One wide photo from the doorway. This is the context shot nobody sends unprompted.
4. The fault from about a metre away. Close enough to see it, far enough to see what it's attached to.
5. A close-up. The detail: the crack, the corrosion, the mould edge, the drip.
6. Something for scale. A hand, a coin, a tape measure if they have one. Sounds trivial; it's the difference between one tube of sealant and a skip.
7. The surroundings or the likely source. The window and its seals for damp, the stopcock and pipework under a sink for a leak, the fuse board for an electrical fault, the room above a ceiling stain.
8. A 20-second video with the tenant talking. "Walk from the door to the problem and tell us when it started and when it's worst." Spoken explanations get transcribed and become searchable text on the case.
9. Yes/no questions that steer the next step. Is water still coming in right now? Is there electricity near it? Does anyone in the household have a health condition that this affects? A "yes" on the first two routes the case to emergency handling; a "yes" on the third is exactly the vulnerability information the Ombudsman keeps finding missing.
10. Access and contact. Best days and times, a phone number, whether there's a dog. Asked at the end, not the start, so the tenant has already done the useful part.
11. Declaration and submit. A configurable checkbox, then a thank-you page with a copyable reference number the tenant can quote when they ring.

The damp and mould variant follows the sequence we use for property flows: room overview, ceiling, affected wall, floor, suspected source, close-up, spoken explanation. Add three questions: is the extractor fan working, is the heating on in that room, and is anyone in the household under five, elderly or living with a respiratory condition. Those three are the first things a damp surveyor asks, so ask them before the surveyor is booked.

What the tenant actually sees

A text, WhatsApp message or email with a personal link, or a QR code on screen or on paper. It opens in the phone's browser in their own language (15 are available), with your logo and a card that says the whole thing takes a few minutes and needs no app and no account.

Each step shows an example photo and one plain instruction. A progress bar counts down the required items. If they open it on a laptop, they get a QR code to continue on the phone, because the recording has to come from the device in the room.

What not to do

• Don't ask for 15 photos. Six well-chosen shots and one short video beat a gallery dump. Required steps should be the minimum a surveyor needs.
• Don't ask the tenant to diagnose. "What's causing it?" is your job. "Show us the window seals" is theirs.
• Don't close the phone line. Some tenants will always ring. The call handler can send the link during the call and stay on while the tenant takes the first photo. Others need an operative to attend regardless; the flow is for the majority, not the exceptions.
• Don't build the branching yourself on day one. Standard flows come ready-made and your own team adjusts the steps, slots and wording. Flows with if-this-then-that routing, escalation rules and integrations are set up around your process by VentaVid, scoped on a call.

The guided video capture and request video by link pages cover the mechanics of the capture flow and the conditional logic behind the yes/no questions.

How the submission feeds the repairs system

A folder of JPEGs in an inbox is not a repair report. What should arrive is a case: your reference number, every answer the tenant gave, the transcript of what they said, the media, and a server-recorded receipt time, in a shape your repairs system can route.

In Venta Capture that case carries:

• A reference in your own format (prefix, digits, year), plus a separate "your reference" field for the works order number your housing management system already issued.
• Structured answers. The room, the yes/no answers, the free text, each stored as a field, not buried in a description box.
• The transcript. What the tenant said over the video, as searchable text.
• A receipt timestamp verified on the server, plus device context for each photo and video.
• A digital seal. A SHA-256 fingerprint per submission, a signed seal, and a session timeline showing when the link was created, opened, and submitted. The sealed submission is what lets you show, later, that the file you're looking at is the file you received.

One honest line about that timestamp, because it gets oversold elsewhere. The receipt time proves when you received the report, not when the damp started. For Awaab's Law that is exactly the useful fact: it is your dated record of the day you became aware, and the answers and photos beside it are the start of the "clear records" the guidance asks for.

Gallery uploads are accepted where you allow them, but they're labelled as unverified provenance so a reviewer knows the difference.

From there it behaves like a ticket:

• Routing and ownership. Statuses you define, assign to a surveyor or planner, escalate to a manager with a reason, an SLA in hours on the route, notifications on submission, assignment and status change.
• Contractors without logins. A view link puts the whole case in front of the operative or the subcontractor on their phone. No account to create for them either.
• Into the repairs system. Copy the case for the CRM, or let webhooks and the API push it to your housing management or scheduling system so the works order carries the evidence with it. Workflow automation forwards cases by status.
• Retakes. If step 7 is missing, a retake request goes out in one click, names the gap, and the new material attaches to the same case. The review and retake loop is what turns an incomplete report into one more step instead of a failed one.
• The audit trail. Who opened what, when, and on whose account, for the day a complaint reaches stage two.

Two related flows sit on the same infrastructure and get their own posts. Using the submission for remote triage and contractor proof of work is covered in our remote property inspection guide, and tenant self-inspection at check-in and check-out has its own piece. This post stays on the reactive repair.

How to measure first-time fix on photo-reported jobs

If you can't compare photo-reported jobs against phone-reported jobs of the same trade, you won't know whether any of this worked. Set the measurement up before the first link goes out.

Use the definition your benchmarking already uses. A first-time fix is a repair diagnosed and completed on the first attendance with what the operative carried. Then:

1. Tag every job with its reporting channel (phone, portal text, guided capture) and, for captured jobs, the case reference. This is one extra field on the works order.
2. Pick two or three trades to start. Plumbing leaks, damp and mould, and electrical faults are the ones where the first visit is most often a look rather than a fix.
3. Run it for 90 days. Enough volume to see a difference, short enough that nothing else changed.
4. Compare four numbers per trade: first-time fix rate, average attendances per job, days from report to completion, and the no-access rate. Guided reports carry access preferences, so the last one usually moves too.
5. Read the retakes. Every retake request is a step the flow got wrong. Fix the instruction or the example photo, not the tenant.

Here's the shape of the maths, with example numbers. Swap in your own.

Nobody knows your cost per visit better than your own finance team, so multiply it out yourself. The 20% and the quarter are placeholders to show the shape. What isn't a placeholder is that the visit avoided is a visit avoided for the operative, the planner and the tenant at the same time, and that the Ombudsman's 1 in 4 repairs not done on time starts to look reachable when the first attendance is the right one.

Want to run one repair type through this on your own stock? Have a look at Venta Capture and build a damp and mould flow first.

Frequently asked questions

Do tenants need an app to report a repair with photos?

No. The link or QR code opens the guided flow in the phone's browser, with no app to install and no account to create. Install screens are where tenants give up and ring instead, which is the outcome you're trying to avoid.

What about tenants who can't or won't use a smartphone?

Keep the phone line open and let the call handler send the link during the call for those who can manage the first photo with help. For the rest, an operative attends as before, or a staff member can start a capture themselves on a visit. The flow is for the majority of reports, and it frees attendance capacity for the tenants who need it most.

Does the photo timestamp prove when the damp started?

No, and be wary of anyone who says it does. A server-verified receipt time proves when you received the report, which under Awaab's Law is your dated record of the day you became aware. What happened before that is what the photos, the tenant's account and your investigation establish.

How long do social landlords in England have to deal with damp and mould under Awaab's Law?

For a significant damp and mould hazard, the investigation must happen within 10 working days of becoming aware, the tenant gets a written summary within 3 working days of it concluding, and safety work starts within 5 working days of the investigation ending. Emergency hazards must be made safe within 24 hours. The guidance is on gov.uk and it is worth reading in full.

Does this replace the inspection or the operative visit?

It's remote-first, not remote-only. Some reports can be resolved or closed from the desk, some become a correctly briefed first visit, and some still need a surveyor. The aim is that nobody attends to find out what the job is.

How does a photo repair report get into our housing management system?

Each case carries your reference format and a field for the works order number, and the answers are structured fields rather than a description box. From there you can copy the case for the CRM, share a view link with a contractor, or use webhooks and the API to push it to your repairs or scheduling system. Complex routing and integrations are set up around your process on a scoping call.

Does this apply in Ireland?

The regulatory clock is different, but the obligation to keep a home "in a proper state of structural repair" and free of dampness sits in the Housing (Standards for Rented Houses) Regulations 2019, which cover local authorities and approved housing bodies. A dated visual record per repair report is also the simplest way to build the stock-condition evidence Irish local authorities have been criticised for lacking.

Start with one repair type

If your operatives are still walking into repairs blind, the fix starts at the report, not at the depot. Pick the trade that generates the most second visits, write down the six shots and one video a surveyor would want, and put that flow in front of the next hundred tenants who report it.

What it takes to start.

• Free plan, no credit card. Build the flow, send it to yourself, then to a tenant.
• Live in 10 minutes for a first standard flow. Stuck? Book a free setup call and we build it together.
• Everything goes out in your own branding, in the tenant's language, with no app to install.

The VentaVid team builds Venta Capture and runs the free setup call on your own repair types.

See Venta Capture on your repair types

Or start for free and build a damp and mould flow this afternoon. If you'd rather see it against your own repairs process first, book a demo and bring your worst repair type.