HOA Insurance Claims Guide for Contractors

• →Residential claims typically involve one dwelling, one homeowner decision-maker, and a photo set that maps to a single sketch — HOA claims multiply that footprint across buildings, common elements, and unit owners under association control.
• →Authorization is governance-driven: boards, property managers, and management companies — not a homeowner handshake — control emergency scope, access, and reconstruction approvals.
• →Coverage splits between association master policies and unit-owner (often HO-6) policies; contractors must index evidence so desk reviewers can attribute common-element versus unit scope.
• →Common elements create association-scale scope that does not exist on single-family files: roofs, exteriors, corridors, amenities, and shared systems must be documented separately from unit interiors.
• →Carrier scrutiny scales with invoice total and association complexity: specialist adjusters reconcile evidence by building, common-element zone, and unit — not as a blended residential dump.
• →Operational difference: same craft fundamentals, higher evidence volume, stricter Community → Building → Common Element / Unit indexing, and continuous board/manager coordination.

See the Commercial Insurance Claims Documentation Guide for the parent commercial framework; see the Multifamily & Apartment Insurance Claims Guide when the property is rental multifamily without association governance focus.

• →Identify the association type and governing documents in play at intake: CC&Rs, bylaws, rules, and any emergency repair provisions the manager can confirm.
• →Map the decision path: who can authorize emergency mitigation today versus who must approve reconstruction, roof replacement, or change orders later.
• →Expect phased decisions — day-one stop-loss may be manager-authorized while board votes, reserve reviews, or special assessments control later phases.
• →Document written approvals with date, name, role, and scope; verbal board hallway agreements fail association audits and carrier reinspection.
• →Align documentation packages to how boards review files: building summaries, common-element indexes, and unit lists they can forward to carriers and counsel.
• →Do not opine on coverage, reserves, or special assessments in field notes — document conditions and authorization sources only.

Governing documents and responsibility matrices vary by state and association; capture what the association confirms and photograph conditions that support the work performed.

• →Establish a single contractor liaison and a primary association contact (often the property manager) for documentation packages — dual channels create conflicting unit lists and missed notices.
• →Record board president/claims liaison separately from day-to-day management when both exist; know who receives weekly status packets versus who signs emergency authorizations.
• →Request official building directories, unit numbering, common-element labels, and access protocols from management — every claim artifact must use those IDs.
• →Log every manager or board authorization (emergency work, after-hours access, unit entry, temporary relocation, change orders) with date, name, role, and scope.
• →Coordinate carrier walkthroughs through management so unit access, common-path staging, and board observers are scheduled — not improvised on inspection day.
• →Treat management company reporting cadence as claim evidence: area-indexed packets support large-loss scrutiny and association timeline questions.

• →At intake, note whether the loss is being handled primarily as an association master-policy claim, a unit-owner claim, or a dual-policy coordination file — as confirmed by the association or unit owner, not as contractor coverage advice.
• →Index common-element damage under association claim identifiers and unit interior damage under unit IDs so carriers can reconcile master versus HO-6 (or similar) boundaries.
• →Photograph and label finishes and assemblies that sit on responsibility boundaries (e.g., exterior sheathing vs interior drywall, roof vs attic, corridor vs unit entry door) without declaring coverage.
• →When unit owners retain separate contractors, keep association-authorized common-element packs distinct from unit-owner packs to avoid blended evidence disputes.
• →Record who authorized each scope segment — association, manager, or unit owner — so supplements and change orders map to the correct decision path.
• →Never merge master-policy common-element galleries with unlabeled unit interiors; dual-policy underpayment often starts with inseparable photos.

Policy forms and responsibility charts vary; contractors document conditions and authorization, while coverage determinations belong to the insured, association, and carrier.

• →Build a working responsibility matrix from association guidance: association common elements, limited common elements, and individually owned unit property.
• →Document common elements (roofs, exteriors, structural components, corridors, amenities, grounds, shared systems) in dedicated folders and estimate sections.
• →Document individually owned interiors, fixtures, and contents separately when in contractor scope — label to unit numbers matching association records.
• →Treat limited common elements (balconies, patios, assigned storage) as their own index entries when association records identify them separately.
• →Cross-reference causation paths: roof or stack damage on common elements that drives unit interior damage must appear in both packs with reciprocal IDs.
• →Do not bury common-element scope inside a representative unit folder — carriers cut association lines when evidence is inseparable from unit dumps.

• →Publish Community → Building → Common Element / Unit → Room naming within 24 hours and enforce it on every crew.
• →Pre-inspect with site map and building list from management; photograph elevations, roofs when accessible, and common paths before opening units.
• →Work building by building: complete common-element and exterior packs for a building before or in parallel with its unit block — never leave building IDs ambiguous.
• →On multi-building associations, keep per-building indexes so carriers can approve or reinspect one building without reopening the entire community file.
• →Same-day office sync: upload and label all building and common-element sets before the next shift; backlog labeling destroys association attribution.
• →For multi-building roof campuses, apply the Multi-Building Roofing Claims Guide under this association indexing framework.

This building-wide workflow is the operational backbone for water, fire, mold, and roofing HOA losses — peril field standards live in the corresponding commercial and specialty guides.

• →Treat each affected unit as its own documentation chamber with a dedicated photo folder, note set, and estimate section when unit interiors are in scope.
• →Use fixed naming: Building_Unit_Room_Stage aligned to association unit numbers (e.g., Bldg4_Unit412_Bath_Before_001).
• →Capture entry overview, each affected room overview, damage detail with scale, and undamaged adjacent rooms that define scope boundaries.
• →Inspect adjacent and stacked units for migration on water and smoke losses; update the unit inventory the same day discoveries appear.
• →Coordinate unit entry through management: notice timing, entry windows, and access denials keyed to unit IDs become claim evidence.
• →Never merge Unit 412 and Unit 414 into one gallery — mixed unit dumps are a primary association underpayment driver.

For apartment-style unit chamber depth on rental multifamily, see the Multifamily & Apartment Insurance Claims Guide; keep association governance and common-element separation from this guide.

• →Capture arrival conditions before extraction, drying, or board-up alters the scene — association baselines establish what carriers and boards compare to later production.
• →Confirm who authorized emergency stop-loss (manager emergency authority, board directive, or written emergency rule) and log that authorization with scope and date.
• →Index emergency work by common-element and unit ID: extraction volumes, equipment set, temporary protection, and safety actions.
• →Photograph equipment placement per chamber with asset tags visible; community-level equipment photos do not defend per-unit or per-zone lines.
• →Separate emergency mitigation packages from reconstruction estimates so associations can approve emergency scope while boards deliberate rebuild decisions.
• →On water, fire, and mold emergencies, apply Commercial Water, Fire, and Mold indexing while keeping this guide’s common-element/unit structure intact.

• →Index roofs by building and elevation with labels that match association site maps — community-wide unlabeled roof galleries fail multi-building review.
• →Document matching, slope transitions, and undamaged comparison elevations when partial replacement is disputed across a campus.
• →Tie roof findings to interior top-floor and corridor stains with reciprocal IDs in common-element and unit packs.
• →Coordinate board and manager roof walkthroughs with photo indexes ready — association decision-makers need building-level summaries, not raw dumps.
• →Estimate roof scope by building section; do not bury multi-building roofs inside a single residential roof block.
• →Follow the HOA Roofing Claims Guide and Multi-Building Roofing Claims Guide for roof specialty procedures under this association framework.

• →Water: start chamber-level moisture maps and dry logs on day one; separate common-path drying from unit drying; see Commercial Water Loss Documentation Guide.
• →Fire: index soot/smoke by common element and unit; document corridors, HVAC, and life-safety impairments as association-scale systems; see Commercial Fire Claims Guide.
• →Mold: separate source, amplification, and migration zones; keep containment and clearance evidence labeled to association location IDs; see Commercial Mold Claims Guide.
• →Cross-peril: never drop Community → Building → Common Element / Unit indexing when the loss phases from mitigation into reconstruction or from water into mold.
• →Link shared-system causation (roof, stack, HVAC) to both association common-element packs and affected unit packs.
• →Apply peril specialty photo and log standards under this HOA indexing framework — do not revert to single-family templates mid-claim.

• →Identify AHJ jurisdiction early; association rebuilds frequently trigger corridor, egress, fire-rating, accessibility, and electrical upgrades across common elements.
• →Photograph non-compliant conditions before demolition removes evidence of why upgrades are required.
• →Collect permits, inspection reports, and written AHJ directives that support ordinance or law line items on association scope.
• →Separate code upgrade scope in the estimate and documentation index so reviewers evaluate ordinance lines independently of like-kind repairs.
• →Track inspection milestones chronologically across buildings — code scope often expands mid-project on multi-building associations.
• →Coordinate with the Code Upgrade Documentation Guide and peril-specific guides while keeping association indexing consistent.

• →Publish the Community → Building → Common Element / Unit → Room index within 24 hours and enforce it on every crew.
• →Separate common elements, units, and shared systems in folders, estimates, and carrier packets.
• →Maintain contemporaneous board/manager authorization and unit access logs — reconstruct them after a dispute and carriers discount the file.
• →Reconcile equipment, materials, and labor to location IDs before invoice or supplement submission.
• →Send area-indexed progress packages boards and management companies can review — unlabeled photo dumps force rework.
• →Apply peril specialty guides under this indexing framework — never drop association organization when switching from water to fire or mold phases.

• →Common-element scope omitted from unit-only carrier estimates — roofs, exteriors, corridors, and amenities frequently appear only after indexed association documentation.
• →Adjacent or stacked unit discoveries after initial walkthrough — openings and moisture/smoke migration expand beyond carrier-selected sample units.
• →Shared-system repairs (roof, stack, HVAC) revealed by multi-unit or multi-building pattern evidence.
• →Association production costs: after-hours labor, phased mobilizations, escorts, and temporary facilities authorized by board or manager.
• →Code-driven upgrades documented with AHJ evidence after demolition or inspection on common elements.
• →Package every supplement by building/common-element/unit ID with discovery photos, revised sketches, and estimate deltas — HOA supplements fail when evidence is blended.

See Supplement Submission Guide for package structure; use this section’s triggers with association-indexed attachments.

• →Front matter: association identification sheet, board/manager/management contacts, site map, common-element index, and unit index.
• →Common-element evidence: photo sets, notes, and sketches labeled to association location IDs.
• →Unit evidence: per-unit photo sets, notes, moisture/smoke maps as applicable, and ownership/status notes.
• →Shared-systems packs with cross-references to affected common elements and units.
• →Mitigation and production logs: emergency records, daily logs, equipment reconciliation, and change tracking.
• →Estimate history: initial, revised, and supplement estimates with section headers matching the association index.
• →Coordination and code: stakeholder communication logs, authorizations, permits, AHJ notes, and communication chronology.
• →Closeout: table of contents, line-to-evidence cross-reference, punch list with completion photos by location ID, and archive using the same folder structure used in production.

• →Documentation plan and naming convention published within 24 hours.
• →Association governance and management package on file.
• →Master vs homeowner policy notes recorded as confirmed by association/unit owner.
• →Common-element inventory complete (buildings, roofs, exteriors, corridors, amenities, grounds).
• →Unit inventory complete (affected, adjacent, status notes).
• →Common-element photo and note sets labeled to association IDs.
• →Unit documentation sets labeled to association unit numbers when interiors are in scope.
• →Stakeholder communication/access log contemporaneous (board, manager, management company, unit owners).
• →Emergency mitigation indexed by common element and unit.
• →Shared building systems pack cross-referenced to locations.
• →Association estimate index with quantity validation.
• →Code/ordinance file with AHJ evidence when upgrades apply.
• →Daily project logs by building/common-element/unit ID.
• →Supplement change log with discovery drivers.
• →Final indexed claim package with line-to-evidence cross-reference.
• →QC spot-check: random locations resolve photos, logs, and estimate lines to the same IDs.

• →Pre-inspect: obtain site map, building list, common-element list, and affected-unit list from management; publish naming convention before crews mobilize.
• →Exterior and common-path walk: document elevations, roofs when accessible, corridors, amenities, and migration clues before opening units.
• →Common-element pass: complete association-owned scope packs with site-map labels before or in parallel with unit work.
• →Unit sequence: work building by building using association unit numbers; complete overview-to-detail photos before leaving each unit.
• →Adjacent-unit check: inspect and document units above, below, and beside known damage for migration.
• →Shared-systems pass: inspect roof, stacks, HVAC, and life-safety interfaces; cross-index findings to common elements and units.
• →Same-day office sync: upload and label all sets before the next shift.

• →Day one: confirm primary manager contact, board claims liaison (if any), and emergency authorization path in writing.
• →Daily: send indexed status to the primary contact — buildings worked, common elements documented, units entered, discoveries requiring board/manager decisions.
• →Access events: log unit-owner notices, entry windows, denials, and escorts keyed to unit IDs the same day.
• →Change orders: route scope expansions through the documented approval path before production expands; attach discovery photos by location ID.
• →Carrier meetings: schedule through management; bring building and common-element indexes, not unlabeled drives.
• →Closeout: deliver the final indexed package in the folder structure boards and management companies can archive and forward.

• →Treating association losses like single-family residential files.
• →Merging common-element and unit photos into one unlabeled dump.
• →Ignoring master vs homeowner policy documentation boundaries.
• →Using crew nicknames instead of association building/unit numbers.
• →Missing board/manager authorization and unit access logs.
• →Estimating HOA scope as a single residential block.
• →Burying roofs and exteriors inside a representative unit folder.
• →Submitting supplements without location-indexed discovery evidence.
• →End-of-job narratives replacing contemporaneous daily association logs.
• →Skipping adjacent-unit and shared-system checks that explain multi-unit patterns.

• →HOA and association insurance claims are recovered through governance-aware coordination, master vs unit evidence separation, common-element indexing, and disciplined estimate organization — not more unlabeled photos.
• →Apply the Commercial Insurance Claims Documentation Guide as the parent standard; use Commercial Water, Fire, Mold, and Roofing guides for peril procedures; use the HOA Roofing Claims Guide for roof specialty association workflows; use the Multifamily & Apartment guide when rental multifamily ops dominate.
• →Claims Ninja supports contractors with documentation standards, large-loss estimating, supplement packaging, and claim recovery workflows on HOA and community association losses.