Multifamily & Apartment Insurance Claims Guide for Contractors

• →Residential claims typically involve one dwelling, one primary stakeholder, and a photo set that maps to a single sketch — multifamily claims multiply that footprint across dozens or hundreds of units.
• →Carrier scrutiny scales with invoice total and unit count: specialist adjusters and desk reviewers reconcile evidence unit by unit, not as a blended residential dump.
• →Access is controlled by property management — contractors cannot treat unit entry like a homeowner handshake; notices, escorts, and denial logs become claim evidence.
• →Common areas and shared systems create scope that does not exist on single-family files: corridors, stacks, roofs, and mechanical rooms must be indexed separately from units.
• →Ownership structures (owner, REIT, condo/HOA master policy) change who authorizes work and which policy responds — documentation must track responsibility boundaries.
• →Operational difference: same craft fundamentals, higher evidence volume, stricter Building → Floor → Unit → Room indexing, and continuous property manager coordination.

See the Commercial Insurance Claims Documentation Guide for the parent commercial framework; this playbook specializes that framework for apartment and multifamily footprints.

• →Identify ownership type at intake: private owner, ownership group, REIT/institutional owner, condo association, HOA, or mixed condominium with rental units.
• →Document who controls day-to-day access — on-site property manager, regional manager, building engineer, board, or owner representative — and capture preferred communication channels.
• →Note master policy versus unit-owner policy boundaries when condominiums or HOAs apply; association-owned common elements often sit on different coverage than unit interiors.
• →Record lease versus owner-occupied status per building or community when it affects contents ownership and tenant coordination.
• →Photograph and file site maps, building directories, and unit numbering schemes from management — every claim artifact must use those IDs.
• →Clarify authorization chain for emergency mitigation, after-hours work, and change orders before production expands beyond day-one emergency scope.

For HOA and condominium roofing-specific ownership and board workflows, see the HOA Roofing Claims Guide and Multi-Building Roofing Claims Guide.

• →Establish a single contractor liaison and a single PM contact for documentation packages — dual channels create conflicting unit lists and missed notices.
• →Request the official unit roster, vacancy list, and keys/access protocol before detailed inspections; align your index to management records on day one.
• →Send unit-indexed status updates that PMs can forward to ownership groups — building summaries without unit IDs force rework.
• →Log every PM authorization (emergency work, after-hours access, unit entry, temporary relocation) with date, name, and scope — verbal-only approvals fail commercial audits.
• →Coordinate carrier walkthroughs through the PM so unit access, elevator holds, and common-area staging are scheduled — not improvised on inspection day.
• →Treat ownership group reporting cadence as claim evidence: weekly area-indexed packets support large-loss scrutiny and BI-related timeline questions.

• →Pre-inspect: obtain site map, building list, affected-unit list from PM, and publish naming convention before crews enter units.
• →Exterior and common-path walk: document building elevations, roof overview when accessible, lobby/corridor conditions, and migration clues before opening units.
• →Unit sequence: work building by building, floor by floor, using management 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 — especially on water and smoke losses.
• →Common-area pass: after unit blocks, document corridors, laundry, amenities, and mechanical spaces with separate folder IDs.
• →Shared-systems pass: inspect roof, stacks, HVAC, and life-safety interfaces that explain multi-unit patterns; cross-index findings to affected units.
• →Same-day office sync: upload and label all unit sets before the next shift; backlog labeling destroys multifamily attribution.

This inspection workflow is the operational backbone for water, fire, mold, and roofing multifamily 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.
• →Use fixed naming: Building_Floor_Unit_Room_Stage (e.g., Bldg2_Fl3_Unit312_Bath_Before_001).
• →Capture entry overview, each affected room overview, damage detail with scale, and undamaged adjacent rooms that define scope boundaries.
• →Record contents ownership notes (tenant vs owner fixtures) when contents or TI-like finishes appear in units.
• →Never merge Unit 312 and Unit 314 into one gallery — mixed unit dumps are a primary multifamily underpayment driver.
• →Spot-check daily that random photos resolve to the correct unit ID before carrier packages leave the office.

For apartment water-specific unit chamber standards, see the Commercial Water Loss Documentation Guide and Water Damage Documentation for Apartment Complexes blog.

• →Index common areas separately from units: corridors, lobbies, stairwells, elevators, laundry rooms, fitness/amenities, mailrooms, and exterior shared spaces.
• →Photograph common-area damage with location labels that match the site map — hallway between Units 310–318 needs a label desk reviewers can find.
• →Separate owner/association common-element scope from in-unit scope in both photos and estimates.
• →Document temporary protection in common paths (floor coverings, containment, signage) as production evidence and life-safety context.
• →Do not bury corridor or lobby scope inside a single unit folder — carriers cut common-area lines when evidence is inseparable from unit dumps.
• →On condo/HOA files, align common-area labels to association records used for master-policy claims.

• →Status every unit at intake: occupied, vacant, model/show, under renovation, or temporarily displaced — update when status changes.
• →Occupied units require access logs, tenant notices, and contents care documentation; vacant units still need full damage indexing but different contents and access evidence.
• →Document why vacant units were entered and who authorized entry — unauthorized vacant-unit work creates disputes with ownership groups.
• →Displaced tenants: log temporary relocation dates, unit release criteria, and return photos when units are cleared for re-occupancy.
• →Avoid applying occupied-unit labor assumptions to vacant blocks without authorization notes — and vice versa.
• →Reflect occupancy status in estimate narratives so after-hours or multi-entry labor is explainable at desk review.

• →Route tenant communications through property management unless the PM authorizes direct contractor contact — dual messaging creates claim and liability risk.
• →Document notice timing for unit entry: date notice posted/sent, entry window, and actual entry time keyed to unit ID.
• →Record tenant-reported damage separately from contractor findings; verify and photograph reported conditions rather than accepting narrative alone.
• →Protect tenant privacy in photo sets — avoid capturing personal documents, faces of minors, or unrelated personal effects when possible; crop or retake when needed.
• →Log access denials and reschedules — missed drying or inspection windows become duration and labor evidence when documented contemporaneously.
• →Keep tenant communication factual and operational; coverage opinions belong with the insured, PM, and carrier — not contractor field notes.

• →Capture arrival conditions before extraction, drying, or board-up alters the scene — multifamily baselines establish what carriers compare to later production.
• →Index emergency work by unit and common-area ID: extraction volumes, equipment set, temporary protection, and safety actions with dates and PM authorization.
• →Photograph equipment placement per unit with asset tags visible; building-level equipment photos do not defend per-unit lines.
• →Start unit-level dry logs and moisture maps on day one for water losses — see Commercial Water Loss Documentation Guide and Dry Log Collection Guide.
• →Separate emergency mitigation packages from reconstruction estimates so carriers can approve emergency scope without waiting on full rebuild pricing.
• →On fire and mold emergencies, apply Commercial Fire and Commercial Mold indexing while keeping this guide’s unit/common-area structure intact.

• →Structure Xactimate with building and unit section headers that mirror the documentation index — single residential blocks fail multifamily audit.
• →Estimate common areas and shared systems in dedicated sections, not buried inside a representative unit.
• →Validate quantities per unit: flooring SF, drywall SF, fixture counts, and equipment days must reconcile to that unit’s photos and sketches.
• →Use consistent material grades across similar units when finishes match; document exceptions when upgrades or TI-like finishes differ by unit.
• →Track phased approvals when carriers authorize work building-by-building or floor-by-floor — hold pending units as separate sections.
• →Run pre-submission QC: pick random units and confirm every high-dollar line has photo and measurement support under the same unit ID.

• →Document roof systems with zone labels that correlate to interior top-floor units and corridor stains — see Commercial Roofing and Multi-Building Roofing guides.
• →Map plumbing stacks and risers to stacked unit damage; shutoff locations and repair authorizations belong in the shared-systems pack.
• →Inspect HVAC zones, corridors, and mechanical rooms that distribute smoke, humidity, or contaminants across multiple units.
• →Photograph life-safety impairments (alarms, sprinklers, egress) and temporary protections — multifamily AHJs scrutinize these during reconstruction.
• →Document elevators, trash chutes, and vertical shafts as distinct systems when they drive access costs or contamination paths.
• →Cross-reference every shared-system finding to the list of affected unit IDs so desk reviewers see why multi-unit scope is connected.

• →Identify AHJ jurisdiction early; multifamily rebuilds frequently trigger corridor, egress, fire-rating, accessibility, and electrical upgrades.
• →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.
• →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 multifamily campuses.
• →Coordinate with the Code Upgrade Documentation Guide and peril-specific code guides while keeping multifamily unit indexing consistent.

• →Adjacent-unit discoveries after initial walkthrough — openings and moisture/smoke migration often expand beyond carrier-selected sample units.
• →Common-area scope omitted from unit-only carrier estimates — corridors, laundry, and lobbies frequently appear only after indexed documentation.
• →Shared-system repairs (roof, stack, HVAC) revealed by multi-unit pattern evidence.
• →Occupied-property production costs: after-hours labor, multiple mobilizations, escorts, and temporary facilities authorized by PM.
• →Code-driven upgrades documented with AHJ evidence after demolition or inspection.
• →Package every supplement by unit/common-area ID with discovery photos, revised sketches, and estimate deltas — multifamily supplements fail when evidence is blended.

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

• →Publish the Building → Floor → Unit → Room index within 24 hours and enforce it on every crew.
• →Separate units, common areas, and shared systems in folders, estimates, and carrier packets.
• →Maintain contemporaneous PM and tenant access logs — reconstruct them after a dispute and carriers discount the file.
• →Reconcile equipment, materials, and labor to unit IDs before invoice or supplement submission.
• →Send area-indexed progress packages rather than unlabeled photo dumps when ownership groups request updates.
• →Apply peril specialty guides under this indexing framework — never drop multifamily organization when switching from water to fire or mold phases.

• →Front matter: property identification sheet, ownership/PM contacts, site map, and master unit index.
• →Unit evidence: per-unit photo sets, notes, moisture/smoke maps as applicable, and contents notes.
• →Common-area and shared-systems packs with cross-references to affected 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 unit index.
• →Coordination and code: PM/tenant logs, authorizations, permits, AHJ notes, and communication chronology.
• →Closeout: table of contents, line-to-evidence cross-reference, punch list with completion photos by unit ID, and archive using the same folder structure used in production.

• →Merging multiple units into one unlabeled photo dump.
• →Documenting common areas inside unit folders.
• →Using crew nicknames instead of property management unit numbers.
• →Missing property manager authorization and tenant access logs.
• →Building-level equipment photos defending per-unit equipment lines.
• →Estimating multifamily scope as a single residential block.
• →Ignoring adjacent units and shared systems that explain multi-unit patterns.
• →Treating vacant and occupied units with identical undocumented assumptions.
• →Submitting supplements without unit-indexed discovery evidence.
• →End-of-job narratives replacing contemporaneous daily unit logs.

• →Documentation plan and naming convention published within 24 hours.
• →Ownership/management package and site map on file.
• →Unit inventory complete (affected, adjacent, vacant, displaced).
• →Unit-by-unit photo and note sets labeled to management unit numbers.
• →Common-area pack separated from unit folders.
• →Occupied vs vacant status log current.
• →PM and tenant coordination/access log contemporaneous.
• →Emergency mitigation indexed by unit and common area.
• →Shared building systems pack cross-referenced to units.
• →Multi-unit estimate index with quantity validation.
• →Code/ordinance file with AHJ evidence when upgrades apply.
• →Daily project logs by unit/common-area ID.
• →Supplement change log with discovery drivers.
• →Final indexed claim package with line-to-evidence cross-reference.
• →QC spot-check: random units resolve photos, logs, and estimate lines to the same IDs.

• →Multifamily and apartment insurance claims are recovered through unit-indexed documentation, common-area separation, property manager coordination, 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 under this multifamily framework.
• →Claims Ninja supports contractors with documentation standards, large-loss estimating, supplement packaging, and claim recovery workflows on apartment and multifamily losses.