Frequently asked questions
Plain-English answers for managers, boards and homeowners.
The short version: Community Cover is a focused compliance-administration layer, not a replacement for your management software and not an insurance agency.
Community Cover runs the recurring workflow around homeowner insurance: requesting documents, reading the relevant policy information, tracking expiration dates, sending reminders, handling physical mail, organizing corrections and updates, preserving the history and producing clear reports. The goal is simple: routine work keeps moving without the manager having to chase every policy.
Yes. Community Cover collects condo owners’ HO-6 policy documents and other proof of insurance, records key policy details and expiration dates, follows up on missing or expiring records and preserves later policy updates. Managers review exceptions against the association’s configured requirements. This workflow focuses on individual unit-owner policies; it does not replace the association’s master policy.
Under Section 12(h) of the Illinois Condominium Property Act (765 ILCS 605/12), the board may, under the declaration and bylaws or by rule, require unit owners to carry insurance covering their personal liability and compensatory damages to another unit. The Act allows the requirement but does not apply it automatically, so whether owners must carry coverage depends on what the association has adopted. Community Cover helps management companies collect proof of that coverage, track renewals and show the board where things stand. For questions about your association’s documents, consult the association’s attorney. Read our Section 12(h) explainer →
Whatever the association’s requirement accepts. Commonly that is the declarations page of the owner’s HO-6 policy, or a certificate or evidence of insurance from the owner’s carrier or agent. Community Cover reads the details the association has configured, such as policy dates, carrier, policy number, insured name, property address and liability limit, and flags anything that needs a manager’s judgment. Receiving the document is the start of the review, not the end.
Insurance tracking shows which documents have arrived, what policy dates are recorded and which records need follow-up. Compliance review compares the recorded facts with the association’s configured requirements and records an approval, a correction request or an authorized exception. Receiving a PDF alone does not establish compliance.
It should be the opposite. Community Cover is designed so the routine process happens quietly in the background. Managers can work from exceptions and a digest rather than logging in every morning to see whether anything happened.
Usually, yes — which is the point. The work often exists already, but it is scattered across inboxes, spreadsheets, shared drives and individual follow-up. Community Cover turns that existing responsibility into one repeatable process across the portfolio.
No. The repetitive work — collection, extraction, reminders, recordkeeping and routine follow-up — should move away from the manager. If a management company wants even more of that work removed, the optional Concierge service can handle the repetitive administrative layer for $0.40 per unit per month.
Community Cover is not designed to turn managers into insurance professionals. The association, with its attorney and insurance advisers where appropriate, defines the objective requirement. Community Cover extracts and organizes the relevant facts and surfaces exceptions. Managers retain control over association decisions, but questions requiring insurance or legal interpretation should go to the appropriate professional.
Not every association starts in the same place. A management company can still create visibility around what has been requested and what has been received without pretending a violation exists where the association has not adopted an enforceable requirement. If the board later wants to move from information gathering to enforcement, it should confirm the appropriate authority and process with counsel.
That is exactly why Community Cover supports more than one route. Residents can use a secure upload link, email a document or mail a paper copy. They do not need to download an app or create a resident account.
The record is placed in the appropriate status, the issue is documented and the approved follow-up can continue. Managers can request a correction, approve an exception or take another association-authorized action. Community Cover keeps the history connected so the outcome does not disappear into an email thread.
A policy record can have more than one document over its life. A later endorsement, cancellation notice, revised declaration page or other update can be attached to the existing record, reviewed and used to update the relevant fields without erasing the earlier history.
No. Community Cover is a focused compliance-administration layer that works alongside the management company’s existing systems. A portfolio can begin with a straightforward data import rather than waiting for a deep integration.
Boards get visibility without another operational job. They can receive current compliance summaries, exception reporting and historical records showing what was requested, received, reviewed and decided. The board does not need to inspect every policy to know whether the process is working.
Start with a 60-day free trial: software, Concierge, standard mail and scanning are all free. After the trial, software stays free for the rest of your first year. From year two, software is $2.95 per unit per year. There is no implementation fee. Optional Concierge is $0.40 per unit per month. Printing, postage and scanning are charged separately based on actual usage.
Community Cover provides the workflow and billing infrastructure; the management company’s own agreement determines what it is entitled to charge the association. Depending on that agreement, the manager may be able to pass through Community Cover costs and apply permitted administrative or labor charges. Community Cover does not create that contractual authority.
Community Cover’s underlying charges can flow into a management-company billing view by association. The management company can then allocate the costs through its normal process and apply its own permitted fee structure before the association is billed.
This is a one-time rollout incentive, not part of Community Cover’s pricing. Management companies that implement Community Cover with Concierge across substantially all of their eligible associations may qualify for a one-time incentive of $2 per unit. It is paid once, after 90 days, and is subject to program terms.
Community Cover is not an insurance agency. Where enabled, a homeowner may be offered an optional path to browse alternatives through a licensed insurance partner. That route is separate from the compliance decision and should not change whether a document is approved or rejected. Any required disclosures or partner compensation would be handled separately.
Yes. The preferred approach is to prove the workflow on one or two associations first, learn what needs adjusting and then standardize the process across the eligible portfolio.
Where available, yes. A homeowner who needs coverage or wants to explore alternatives can be offered an optional path to a licensed insurance partner within the existing compliance workflow. Community Cover does not act as the insurance agency, and the insurance transaction remains separate from the association's compliance decision. Any revenue-sharing arrangement is subject to the applicable partner, licensing, regulatory and disclosure structure.
Still have a question?