The Repair Request Black Hole: Why Property Maintenance Work Orders Vanish
The tap in apartment 14 started dripping in early September. I know the exact week because the tenant sent me a photo of a coffee cup under it, with a note: "third cup today". By the time someone actually fixed it, the cup had been replaced by a bucket and the building had paid for a new kitchen cabinet base.
Eleven weeks. Not because anybody was lazy. The caretaker told the board. The board chair emailed the management company. The management company called a plumber, who said he needed a part, then went on holiday. Somewhere in that chain the work order stopped being a task and became a rumour.
If you manage buildings — a German Hausverwaltung, a Swedish BRF, a Dutch VvE, an OSMD in Riga — you have a version of this story. Probably several.
What actually happens to a repair request
A resident notices something. A radiator valve hisses. The stairwell light flickers. Water appears where water should not be.
Now trace the message. It arrives by phone call, or a WhatsApp message to the board chair, or a note in the letterbox, or a form on a website nobody checks. The chair mentions it at the next board meeting, which is in three weeks. Someone writes it in a notebook. The notebook goes into a drawer.
Meanwhile the resident asks again. Politely the first time. Less politely the second.
This is the black hole. Not one dramatic failure, but a chain of small handovers with no owner and no timestamp. In buildings I have looked at, a single non-urgent repair routinely passes through four or five people before anyone writes down who is doing what by when.
Three places work orders go to die
The shared inbox. A management company handles 30 buildings and one info@ address. By Friday there are 200 unread messages, half of them invoices, and the plumber request from Tuesday is somewhere on page three. Email is excellent at receiving and terrible at remembering.
The WhatsApp group. Fast, friendly, completely unauditable. The message that says "the boiler is making a noise again" scrolls away in two hours. Nobody can prove later whether it was reported, who replied, or what was agreed. Try reconstructing that during an insurance claim.
The paper notebook. Still alive in more buildings than anyone admits. It works fine until the caretaker is on holiday, or leaves, and takes the institutional memory with him.
The German version is not crazy
Germany gets a bad reputation for bureaucracy, but the WEG system has one genuinely useful feature: it forces a decision about who may act. Since the 2020 reform (WEMoG), section 27 of the Wohnungseigentumsgesetz lets the manager decide on urgent repairs without waiting for an owners' resolution. That is a good rule. A burst pipe does not respect meeting schedules.
The problem starts above that threshold. A new intercom system, a facade repair, a lift modernisation — those need a resolution, quotes, sometimes a special levy. In the gap between "the board agrees something must be done" and "the owners vote", requests sit in a folder. In Munich or Hamburg I have seen emergency call-outs billed at 180 to 260 euros before the first hour of work, and normal electrician rates around 70 to 95 euros per hour. Expensive, yes. But the real cost is usually the damage that happened while three people exchanged emails about whether the call-out was justified.
Austria is similar in spirit, with its own vocabulary: the Hausverwaltung, the Eigentümergemeinschaft, the MRG for rented flats. Vienna's older stock adds another layer — the same repair may involve a listed facade, a chimney sweep and a district heating provider.
The Nordics went the other way
In Sweden, a bostadsrättsförening usually has a felanmälan — a fault reporting function, often a form or an app, often with a promised response time. The board does not have to be in the loop for a leaking radiator; the property manager or the contracted maintenance firm handles it and reports back.
Finland does something similar with the huoltoyhtiö, the maintenance company that looks after the building day to day. The isännöitsijä, the property manager, oversees contracts and money; the huoltoyhtiö handles the dripping tap. When something happens at 2am, there is a päivystys number — an on-call line — and everyone knows it exists.
What both countries get right is not technology. It is the default: one channel, one responsible party, one expected response time. The software is just where that agreement lives.
Compare that with the UK, where major works in blocks often trigger a Section 20 consultation if any leaseholder would pay more than 250 pounds. Perfectly sensible protection, and also a reason work orders can sit for months while notices are served. Different problem, same underlying issue: nobody can see the queue.
One queue, one owner, one timestamp
Here is the unglamorous fix. Every request gets a number, a channel, an owner and a date. That is it. A spreadsheet can do it. A decent maintenance module does it better, but the tool is not the point.
The rules I would put on the wall:
- Every request enters at one door. Not five. Residents get one address, one form, one phone number, and they are told what happens next.
- Every request has a named owner, not a team. "Facilities" is not a person. "Marta, until Thursday" is.
- Every request gets a triage decision within one working day: emergency, planned, or rejected with a reason.
- Every status change is written down. Not in a chat, in the record.
None of this is exciting. That is the point. Excitement in maintenance means water where water should not be.
Approval thresholds that do not freeze the building
Boards often ask me for a spending limit. My usual suggestion: let the manager approve emergency work up to a clearly written number, with the contractor list agreed in advance. In Germany that might be 500 or 1,000 euros depending on the building. In Sweden the board might set 10,000 SEK. The number matters less than the agreement.
The other half is the contractor list. Three plumbers, two electricians, one lift company, each with rates, insurance and an out-of-hours number. When the boiler dies on Friday evening, nobody should be searching Google. A pre-agreed list is boring administration that saves a fortune at exactly the wrong moment.
Photos, GDPR and the argument about the stairwell
Photos are the single biggest improvement in repair handling in the last decade, and also a quiet compliance trap. A caretaker photographing a damaged door is fine. A caretaker photographing a damaged door with a resident's nameplate, post and a child in the frame is a different conversation.
The GDPR line is not complicated: photograph the fault, not the person. Store the image with the work order, limit access to people who need it, and delete it when the insurance claim or warranty period ends. German works councils tend to ask about this before the owners do, so it is worth having an answer ready.
What I would fix this month
If you run a portfolio and recognise the dripping tap story, do not start with software. Start with a list: every open request right now, its owner and its age. You will find at least three that everyone assumed someone else had handled.
Then pick one door for new requests and tell residents, in plain language, what response to expect. Then give the caretaker permission to close small things without a meeting.
The tap in apartment 14 would have cost about 90 euros to fix in September. It cost several hundred by November, plus a cabinet, plus a tenant who now photographs everything. Black holes are expensive. A shared list is not.