Ask any property manager what takes up most of their hours and most of their peace of mind, and few will say «the owners’ meetings» or «the accounts». They will say insurance claims. A leak in the car park, a storm that lifts part of the roof, a blockage that floods two ground-floor flats. The physical damage is fixed in days; the claim file can drag on for months.
The reason is almost never the insurer. It is that the claim file does not live anywhere. It lives scattered across an email with the claim notification, a WhatsApp message with the resident’s photos, a call to the loss adjuster that nobody wrote down, a quote in PDF that somebody forwarded, and a spreadsheet where the property manager tries to remember where each of the thirty open claims in their portfolio had got to.
This article explains how a homeowners’ association claim can be handled when there is just one claim file and everyone involved works on it at the same time.
Why control of a claim gets lost
A homeowners’ association claim has one feature that makes it especially hard to follow: at least four parties are involved, each with different interests and timetables.
- The property manager, who files the claim and answers to the owners’ meeting.
- The insurance brokerage or the insurer, which opens the claim file and decides.
- The loss adjuster, who visits, measures and assesses.
- The contractor, who carries out the repair once given the green light.
Each of them uses their own tools. The result is predictable: nobody has the full picture, everyone asks by email «how is this going?», and the property manager becomes a switchboard for forwarded messages. When a resident asks at the owners’ meeting why the leak on the fourth floor has gone five months without being repaired, the honest answer is usually «I am waiting for a reply», without being able to say from whom or since when.
One claim file, four doors
The alternative is to stop moving documents around and start sharing the claim file. In FixrOS a claim is not an email: it is a case with its own status that each party enters through its own door, seeing exactly what concerns it.
The property manager works from their dashboard. The insurer, the insurance brokerage and the loss adjuster enter a separate portal, with their own logins and their own view. The claim file is not sent: access to it is granted. That is why, when the brokerage updates a piece of data, the property manager sees it straight away, without anyone having to notify anyone.
The initial submission is the simplest part of all: from the issue that is already open, the property manager sends the claim to their brokerage’s portal in a single action. From then on the claim file no longer belongs to them alone: it is a shared workspace.
Eleven statuses, each with its owner
What really prevents things from getting out of hand is not shared access, but the fact that the claim file can only move forward in one order, and each step can only be taken by the party responsible for it. This is the full journey:
- Draft: the property manager prepares the claim.
- Notified: they send it to the portal. This is where the clock starts ticking.
- Acknowledged: the insurer or the brokerage confirms receipt and opens a claim file.
- Adjuster assigned: the professional who will carry out the assessment is appointed.
- Adjuster visited: the loss adjuster confirms the visit.
- Report received: they submit their assessment.
- Approved: the insurer accepts the settlement.
- Repair scheduled: the property manager hires the contractor and sets a date.
- Repaired: the contractor finishes.
- Paid: the insurer pays out.
- Closed: the property manager marks the claim file as complete.
There is a twelfth status, Rejected, which can be reached from any point after notification. And it comes with an important condition: rejecting requires the reason to be written down. There is no silent rejection. If the insurer decides the damage is not covered, that reason is recorded in the claim file, with date and author, and the property manager can take it to the owners’ meeting or challenge it with arguments.
The division of responsibilities is just as strict. The property manager can send the claim, schedule the repair and close. The insurer and the brokerage acknowledge, assign a loss adjuster, approve and pay. The loss adjuster can only do two things: mark that they have visited and submit their report. Nobody can skip a step or sign on behalf of someone else.
The loss adjuster’s report stops being a PDF
The piece that most delays a claim file is usually the loss assessment, and almost always for the same reason: the report arrives as a free-form document that has to be read from start to finish to extract four pieces of data.
In FixrOS the loss adjuster does not write a document: they fill in a guided report of six steps, which they can complete from their mobile during the visit itself.
- Cause and mechanism of the damage.
- Measurements taken on site.
- Damage per unit, identifying which home or element is affected and which asset it is.
- Itemised valuation, with taxable base, VAT and excess.
- Proposal and technical recommendations.
- Completion and submission.
Because the information comes in structured, there is nothing to interpret at the end: the claim file already knows which units are affected, which assets have been damaged, how much each item adds up to and what the total is. The work saves itself as the loss adjuster progresses, so an interrupted visit does not mean starting from scratch.
The claim and the issue, in sync
There is a design detail that solves a very specific day-to-day problem. In FixrOS a claim is not a standalone entity: it is the insurer’s track on an issue that already exists. The leak reported by the resident on the fourth floor is the same leak that travels to the brokerage.
That means that, as the insurance claim file progresses, the issue reflects that progress: when a loss adjuster is assigned it moves to pending assessment, when the report arrives it moves to quote sent, when the insurer approves it moves to quote approved. The property manager no longer sees an «open» issue from four months ago that has in fact been assessed and approved.
With one important safeguard: the issue never moves backwards. If the property manager has already marked it as resolved on their own initiative, the insurance claim file does not reopen it. The judgement of whoever manages the community takes precedence over the automation.
What each party gains
The property manager stops being a switchboard. They can open their portfolio and see, at a glance, what status each claim is in and who has the ball. When a resident asks, the answer has a date and a name.
The insurance brokerage receives complete claim files from the very first moment, instead of emails missing the policy reference or the photos. And it updates the status just once, in one place, without having to write an email afterwards to explain it.
The loss adjuster works with a script, not a blank template, and submits from the site.
And the homeowners’ association gets what carries most weight at an owners’ meeting: traceability. Who did what, when, and why the decision that was made was made.
Frequently asked questions about claims management in homeowners’ associations
Who files the insurance claim, the property manager or the resident?
Usually the resident reports the damage and the property manager, as secretary of the homeowners’ association, files the claim with the community’s insurer. In FixrOS the resident’s report and the claim are the same file at two different moments: the resident opens the issue from the app and the property manager sends it to the brokerage’s portal when they decide it should go to the insurer.
Can the homeowners’ association and an individual owner claim separately?
Yes, and it is the norm when the same event damages common elements and the interior of a home. The homeowners’ association claims under its policy for the damage to common elements, and each owner claims under their own for the damage to their private property. They are separate claim files even though the origin is the same.
What happens if the insurer rejects the claim?
The claim file moves to Rejected status and the reason is recorded in writing, with date and author. That record is the basis for requesting a review, going to the insurer’s policyholder ombudsman or, where appropriate, considering other routes. Without a written reason there is no rejection.
Can the loss adjuster fill in the report with no signal in the car park?
The report is completed step by step and progress is saved as it is filled in, so an interrupted visit does not mean repeating the work.
Does the brokerage see community data that does not concern it?
No. Each party enters its own portal and sees the claim file and the data needed to process it, not the firm’s portfolio or the rest of its communities.
How long does a claim handled this way take?
It depends on the insurer and the type of damage, and no tool changes a company’s timescales. What does change is dead time: the time lost between one party doing something and the next one finding out. That time, in a shared claim file, tends towards zero.
You may also be interested in
- FixrOS for property managers
- How to claim damages from the Consorcio de Compensación de Seguros
- FixrOS for insurance loss adjusters
- FixrOS for insurers and insurance brokerages
Claims are only one of the fronts a firm handles at the same time. If you are considering switching tools, this guide to choosing property management software sets out the questions worth asking in any demo.
Conclusion
Claims do not get out of hand through lack of diligence, but because the claim file does not exist as such: what exists are fragments scattered across four inboxes. Bringing them together in a single case, with defined statuses, role-based permissions and a structured loss adjuster’s report, turns the claim from a black hole of hours into a process that can be followed, explained and closed.