Operations
How Associations Track HO-6 Compliance
Most condominium associations track unit-owner insurance one of four ways: not at all, in a spreadsheet, in a module of their management platform, or in dedicated software. A spreadsheet is genuinely fine for a small, stable, single-building association. It breaks at a predictable set of points — and knowing those points is more useful than a feature list.
The job to be done
Insurance compliance looks like a filing problem and is actually a calendar problem. Collecting a declaration page once is easy. The difficulty is that every unit's policy expires on its own date, those dates are scattered across all twelve months, and a unit that was compliant in March can be uninsured in April without anyone doing anything wrong.
The recurring work is therefore:
- Know which unit each owner corresponds to, as owners change
- Collect a current declaration page from each one
- Read it and check it against the association's requirements
- Know the expiration date and act before it passes
- Chase the ones that lapse, repeatedly, without giving up
- Be able to show the board and the carrier where things stand
Steps 4 and 5 are where every manual system fails. Not because anyone is careless — because tracking a few dozen independent renewal dates by memory and a reminder is not a thing humans do reliably for years at a stretch.
The four approaches
| Approach | Real cost | Works when | Fails when |
|---|---|---|---|
| No tracking | $0 until a claim | Never, really — though it is common | At the first uninsured loss, when the shortfall is assessed across every other owner |
| Spreadsheet | A few hours a month of somebody's time | One building, under ~50 units, a stable and engaged person maintaining it | Scale, multiple buildings, owner turnover, or that person leaving |
| Management platform module | Usually bundled | You already run the platform and the module actually stores expiration dates as dates | Many store documents but do not parse them, so nothing watches the calendar |
| Dedicated software | Typically per-unit, per-month | Multiple buildings, a portfolio, or when nobody has the hours | Very small associations where the minimum fee exceeds the value |
When a spreadsheet is genuinely good enough
One building. Fewer than about 50 units. Low owner turnover. A specific person who owns the task and is not going anywhere. In that situation a spreadsheet with a conditional-format rule on the expiration column works, and paying for software is hard to justify.
If that is your association, the things worth getting right in the sheet:
- Store the expiration as a real date, not text — otherwise nothing can sort or alert on it
- Key each row on street address + unit number, never unit number alone
- Add a column for the wind-only companion policy and its own expiration date
- Keep the PDF alongside the row, not in someone's inbox
- Put a standing calendar reminder on the person, not on the spreadsheet
The five points where manual tracking breaks
These are consistent enough to be a diagnostic. If two or more describe your association, the spreadsheet is already failing, whether or not it looks like it.
- 1. The unit-number collision
- Multi-building associations reuse unit numbers — there is a 101 in every building. Matching on unit number alone silently attaches the wrong policy to the wrong unit, and it looks correct. The dedup key has to be street address plus unit number.
- 2. The calendar exceeds working memory
- Somewhere around 40–60 units, the number of independent renewal dates passes the point where a person catches them reliably. Failures here are invisible: nothing happens, no alert fires, and the unit is simply uninsured.
- 3. The email that quietly bounces
- An owner changes their address. Reminders keep sending to the old one and keep bouncing. From inside the system it looks like an owner ignoring you; it is actually mail that never arrived. Without bounce visibility this can persist for years.
- 4. Ownership turnover
- A unit sells. The new owner was never invited, is not on the list, and does not know there is a requirement. The old owner's policy sits in the file looking current until it expires.
- 5. The maintainer leaves
- The board treasurer who ran the sheet resigns and it is not handed over — or is handed over without the context of which rows are stale. This is the most common single cause of an association discovering it has no idea who is insured.
Every one of these failures is silent. A missed renewal produces no error, no complaint and no symptom. The association finds out at the only moment it matters — a claim on an uninsured unit, where the shortfall usually lands on every other owner as a special assessment. That asymmetry, not the administrative burden, is the real argument for automating this.
What to look for, in any tool
Whether you evaluate us, a competitor such as Mackoul, or a module of the platform you already run, these are the questions that separate tools that work from tools that store files:
- Can owners submit without creating an account? Every login you require is a large drop in response rate. Forwarding an email should be enough.
- Is the document read, or just stored? If a human still types the expiration date into a field, you have bought filing, not tracking.
- Do reminders send themselves? On a schedule, before expiration, without anyone remembering to trigger them.
- How are units matched? Ask directly whether it matches on unit number alone. In a multi-building association that answer matters.
- Are bounced addresses surfaced? A tool that keeps mailing a dead address and reports it as "reminder sent" is reporting a fiction.
- Does it understand a wind-excluded pair? In Florida, a tool that flags every wind-excluded HO-6 as non-compliant will generate enough false alarms to be abandoned.
- Can the board see status without asking anyone? If producing the answer requires a person to prepare a report, the report will be out of date.
- What happens when a unit sells? New owners should be detectable and invitable, not silently missing.
If you manage multiple associations, the question changes. Per-association tools force you to log in separately for each book of business and give you no portfolio view. What matters is whether one login shows every association you manage, whether staff visibility can be scoped to the properties a given manager handles, and whether billing is consolidated or passed through to each association.
If you are starting from nothing
A workable first 30 days, regardless of what you use:
- Build the unit list first, from property records — not from memory or old email
- Attach whatever contact information you have; accept it will be incomplete
- Ask for declaration pages in one round, with a deadline and a one-step submission path
- Expect roughly half. Do not treat that as failure — it is the normal first pass
- Send a second and third round; most of the remainder arrives here
- Work the true holdouts individually, and note which addresses are bouncing
- Only then set the recurring reminder cadence — by that point the list is real
See where your association actually stands
condo.insure builds your unit list from property records, lets owners submit by forwarding an email, reads each declaration page automatically, and chases renewals on its own. Start free — no setup fee.
Start free Book a demo