Four Years, Ten Months, Eleven Days

The most expensive number in the life of a property management company is a date nobody has in their head. How a Kassel management office saved a warranty period that had almost expired — and why the story begins with a caretaker and a damp patch.

Scenario Story: Brehm & Kollegen is a fictional example company. The story shows the target build-out of Gewerkton; individual features are in beta or in development.

The Notice

The notice arrives on a Tuesday at 7:02 a.m., bundled with seven other reports, because Miriam Brehm no longer receives individual notifications, and never any in the evening.

Property Wilhelmshöher Allee 128, 34 units, handover four years and ten months ago. The warranty period for the waterproofing work expires in 62 days. The suggestion: an inspection of the underground garage and plinth area, now.

Deadlines like these are the industry’s sore spot. They arise from handover dates sitting in folders and expire while nobody is looking. Brehm manages 41 properties; she used to try with a spreadsheet and once missed a deadline by nine days. The repair cost the owners’ association 22,000 euros.

Today, the property file calculates deadlines from the actual handovers and proposes inspections early enough that a notice of defects is still possible. This is not legal advice and doesn’t pretend to be — it’s a calendar that knows where its data comes from.

The Caretaker and His Phone

Detlef Kranz has been a caretaker for 19 years and has never filled out a form he liked. His tool in this case is the same one a site foreman uses to document on a construction site: camera, microphone, one grip.

In the underground garage, axis 7, he finds what he has been seeing for months and never had a reason to report: a damp patch on the wall facing the ground, about a meter and a half wide, with efflorescence. He photographs and speaks: “Underground garage, axis seven, wall toward the embankment, damp, white edges, has been growing since spring.”

The record lands in the property file, with location, time, and image, stored unaltered. Kranz doesn’t have to enter anything, categorize anything, or decide anything. What he contributes is the one thing nobody else has: he was there.

What Brehm appreciates about it is the side effect. Kranz now reports things he used to consider “not that important” — because reporting takes twenty seconds, not twenty minutes.

Backwards Through Five Years

Now begins the part that would be impossible without an archive.

The Wilhelmshöher Allee construction project has been dormant for four years: no longer an active project, but an asset at rest — read access, chain of evidence intact, stored immutably, for a fraction of what a running project costs. The developer pays for it because retention obligations persist for years; Brehm, as the administrator, has read access to the part concerning the property.

She searches by location and building component, not by documents. The wall in axis 7 has a biography: the photo of the raw wall, the shots of the waterproofing before backfilling, the drainage protocol, the subcontractor’s completion notice, an item from the handover that was closed as remedied at the time.

The last entry is the interesting one. In the handover protocol from back then, there is a notice of defects concerning the execution of the plinth connection in exactly this area, closed with an after photo. The image shows a waterproofing membrane that, in one spot, was not carried up to the specified height.

Nobody noticed it at the time. The photo was still there anyway — for five years, unaltered, with a timestamp anchor.

The Chronology Nobody Had to Write at Night

For the notice of defects to the developer, Brehm needs three things: a description of the condition, a reference to the work, and a chronology.

She generates the chronology as a table — date, event, document link — from all the events attached to this building component. What law firms build by hand over days emerges here from what was documented anyway. Plus a package with an index and checksums, explicitly marked as evidence, without legal assessment — and with a viewer the other side can open offline and verify themselves.

That is exactly what shortened the case. The developer didn’t have to believe what Brehm claimed; he could verify it. The subcontractor, in turn, could hold up his own trail — he has one too, on equal footing, with his own photos and dictations — and demonstrated that he had executed the connection as shown in the approved detail. In the end, the fault lay in a drawing revision that two firms had read differently.

The remediation cost 47,000 euros. The owners’ association did not pay for it. The notice of defects went out eleven days before the deadline expired.

What the System Does Otherwise, When Nobody Is Disputing

Saving the deadline is the story Brehm tells at property management conferences. Everyday life looks different, and it is the reason the tool stays.

The systems. Elevators, ventilation, smoke extraction, fire suppression, gates — each with an identifier, location, product data, document reference, and recurring inspections. The deadlines don’t come from a list someone maintained, but from the handover dataset the installer delivered at completion. Maintenance records are attached to the system, not in a mail folder.

The residents. Tenants and owners report via a link, in their language, without an app and without an account — the same pattern buyers already know from the construction phase. Anyone who buys an apartment gets their reading package: fixtures, care instructions, maintenance intervals, reporting path. Brehm says it visibly saved her calls in the first year, and precisely the ones that benefit no one.

Visibility. An owner sees their apartment and the common property, not their neighbor’s apartment. The advisory board sees a curated status. Brehm controls what is visible, and every party involved can read on one page what they see and what they don’t.

The sale. When one unit changed owners in the spring, the documentation moved with it: the apartment file handed over to the new owner, as its own record, with an intact chain. For Brehm, that’s a service she charges for. For the buyer, it’s the difference between a folder of files and a history.

The portfolio without plans. Four of Brehm’s properties date from the seventies and have nothing but paper plans. For two of them, an engineering firm captured the floors in the browser as as-built geometry — walls, shafts, riser zones — so that reports have a location that isn’t “second floor, back left.”

The templates. Inspection protocols, handover checklists, and the maintenance catalog come as a coherent package and not from forty years of office tradition; Brehm has supplemented them with her own property terms.

Her own numbers. Once a quarter, Brehm reads across all 41 properties: Where are reports accumulating, which type of system fails most often, how long does it take from report to resolution. Not as an evaluation of people — individual performance cannot even be aggregated in this analysis — but as a basis for the next maintenance contract award.

The Sentence at the End

Kranz, the caretaker, made peace with the tool after two weeks, because he was allowed to try it out on a practice property for two weeks without being able to break anything.

His comment on the whole story is the best closing line you could get: “I’ve been seeing that patch since spring. The only new thing is that now someone has seen it who can do something with it.”

Transparency: Gewerkton is a product from the publisher of this publication.

Learn more about Gewerkton and its lines: Field, Studio and Cloud.