Retail & Office Commercial Insurance Claims Guide for Contractors

• →Residential claims often organize around rooms in a single dwelling; retail and office claims organize around Property → Building → Floor / Suite / Tenant Space → Common Area / System indexes.
• →Multiple stakeholders control access and approvals: ownership, property management, tenants, and security — not a single homeowner decision path.
• →Demising walls, leasehold improvements, and shared systems create ownership and documentation boundaries residential templates do not capture.
• →Business operations often continue in undamaged suites while contractors mitigate elsewhere under after-hours and security rules.
• →Evidence volume scales with suite count and common-area footprint; desk reviewers cannot navigate unlabeled commercial photo dumps.
• →Carrier scrutiny scales with invoice total and multi-tenant complexity: specialist adjusters reconcile evidence by suite, floor, and system — not as a blended residential gallery.

See the Commercial Insurance Claims Documentation Guide for the parent commercial framework; see Multifamily and HOA guides for residential multifamily or association-governed properties; see Industrial & Warehouse for plant and distribution footprints.

• →Single-tenant retail or office losses may still require shell versus TI separation and landlord/tenant coordination — do not assume one folder equals one claim.
• →Multi-tenant properties require a suite directory index matching property management labels before crews photograph; crew nicknames fail desk review.
• →Mixed-use properties combine retail, office, and sometimes residential components — publish indexes that match how ownership labels the campus, not a single commercial finishes block.
• →At intake, classify single-tenant versus multi-tenant footprint and whether common areas or shared systems are in scope.
• →Estimate sections should mirror the footprint: per-suite blocks plus common-area and building-system sections.
• →Obtain written direction from ownership or property management on which spaces are included in the contractor’s engagement before expanding into adjacent suites.

• →Confirm primary ownership or property management contact and preferred approval channel in writing on day one.
• →Log tenant notifications and access requests keyed to suite IDs; do not rely on verbal hallway conversations as the record.
• →Route change orders and scope expansions through the documented approval path before production expands into additional suites or common areas.
• →Schedule carrier walkthroughs through property management or ownership — bring suite and common-area indexes, not unlabeled drives.
• →Separate communication logs for ownership/PM decisions versus tenant operational requests so the file shows who authorized what.
• →When ownership, PM, and tenant disagree on access or boundaries, pause and obtain written direction from the appropriate party — do not improvise lease or coverage positions.

• →Identify shell versus leasehold/TI boundaries at intake using property management or ownership direction — contractors document conditions; they do not interpret leases.
• →Photograph TI finishes and fixtures with suite IDs before demolition; post-demo-only photos fail TI attribution.
• →Keep leasehold/TI packs in suite-labeled folders separate from base-building packages when ownership or responsible parties differ.
• →Record who provided written direction on TI versus shell boundaries (ownership, PM, tenant, or consultant) with date and scope.
• →Cross-reference TI evidence to estimate sections and to common-area or system causation (e.g., roof leak into Suite 210).
• →Update related commercial TI documentation standards when shell/TI separation applies; use this guide’s suite indexing for retail and office footprints.

See commercial tenant improvement documentation FAQ and Commercial Insurance Claims Documentation Guide for parent TI standards; keep Property → Suite indexing intact.

• →Index lobbies, corridors, restrooms, elevators, stairs, loading docks, and parking structures as common-area packs with location IDs.
• →Document roofs, HVAC risers, fire protection, electrical distribution, and life-safety systems as system packs labeled to floors and suites they serve.
• →Tie system findings to affected suites: a roof or riser failure into Suites 110–114 must appear in both system and suite packs with reciprocal IDs.
• →Capture undamaged comparison common areas when partial replacement or matching is disputed across floors.
• →Do not bury common-area damage inside a representative suite folder — shared-space underpayment often starts with inseparable photos.
• →Apply Commercial Roofing and Photo Documentation standards under this retail/office indexing — never drop floor/suite labels mid-claim.

Peril field standards for water, fire, and mold live in the corresponding commercial specialty guides; keep Property → Building → Floor / Suite indexing intact.

• →Map open versus closed suites and common areas on day one; update when tenants reclaim or release spaces.
• →Coordinate security badges, escort rules, and business hours through property management; log access events keyed to suite IDs.
• →Photograph temporary barriers, containment, and protection that separate operating businesses from loss zones.
• →Document customer-facing or professional-office continuity constraints that force after-hours or phased mobilizations — attach written authorization.
• →Keep daily status packets property managers can forward to ownership and tenants: suites worked, discoveries, and decisions needed.
• →Do not improvise carrier walkthroughs into open retail floors without PM scheduling — unsafe or disruptive access destroys credibility and evidence quality.

• →Capture arrival conditions before extraction, drying, or temporary protection alters the retail/office scene.
• →Confirm who authorized emergency stop-loss (ownership, PM, tenant, or written emergency rule) and log authorization with scope and date.
• →Index emergency work by suite and system ID: extraction volumes, equipment set, temporary roof protection, and safety actions.
• →Photograph mitigation equipment placement per suite/chamber with asset tags visible; property-level equipment photos do not defend per-suite lines.
• →Separate emergency mitigation packages from reconstruction estimates so stakeholders can approve stop-loss while rebuild decisions continue.
• →On water, fire, and mold emergencies, apply Commercial Water, Fire, and Mold indexing while keeping this guide’s suite/system structure intact.

• →Publish a phase plan keyed to suite and common-area IDs: which spaces are released, held, or after-hours only.
• →Log after-hours and weekend windows with PM/ownership authorization before billing shift differentials or remobilizations.
• →Complete overview-to-detail photo packs and same-day labeling for each phase before opening the next block of footprint.
• →Document temporary protection between phases that keeps open businesses operational.
• →Reconcile crew counts and equipment to phase logs before invoice or supplement submission.
• →On multi-floor buildings, keep per-floor indexes so reinspections can isolate one floor without reopening the entire office or center file.

• →Use Property → Building → Floor / Suite / Tenant Space naming on every photo, log row, and estimate section.
• →Complete overview-to-detail sequencing in each suite before leaving; include ceiling, floor, and wall conditions separately.
• →Document undamaged adjacent suites that define scope boundaries and support quantity disputes.
• →Maintain a suite directory checklist so no affected space is omitted from the photo index.
• →Cross-link moisture, smoke, or mold maps to suite IDs on water and fire losses using commercial peril standards.
• →Never merge multiple suites into one unlabeled gallery — multi-tenant underpayment often starts with inseparable photos.

• →Structure Xactimate or estimates with per-suite sections plus distinct common-area and building-system sections.
• →Validate quantities against suite-indexed photo packs and measurements — sample-suite estimating fails multi-tenant review.
• →Keep leasehold/TI line blocks attributable to suite IDs when TI scope differs from shell.
• →Separate general conditions and after-hours labor with authorization references keyed to location IDs.
• →Reconcile materials and equipment to field logs by suite before supplement submission.
• →Do not bury multi-suite scope inside a single commercial finishes block — desk reviewers cut what they cannot attribute.

• →Label base-building finishes, leasehold/TI, and tenant contents/FF&E in separate packs when ownership differs.
• →Photograph tenant contents in place before relocation when safe; log tenant- or PM-directed moves with date and destination.
• →Obtain written direction on ownership boundaries from ownership, PM, tenant, or consultant — do not invent coverage or lease conclusions.
• →Keep contractor contents handling packs distinct from tenant inventory evidence when both exist on the file.
• →Cross-reference contents and finish packs to suite IDs and to causation from common systems.
• →Never bury tenant contents inside unlabeled building finish galleries.

• →Roof and envelope failures into multi-tenant interiors require reciprocal IDs between roof bays and affected suites.
• →On water losses, apply Commercial Water Loss Documentation Guide procedures under suite/floor indexing — moisture maps must resolve to suite IDs.
• →On fire and smoke losses, document migration paths through corridors, HVAC, and adjacent suites using Commercial Fire Claims Guide standards.
• →On mold losses, keep chamber and suite labels consistent with Commercial Mold Claims Guide protocols.
• →Capture temporary weatherization and board-up on storefronts and office entries with location IDs and authorization dates.
• →Peril procedures never replace Property → Suite indexing — they nest under it.

Use Commercial Roofing Documentation Guide for roof-specific field standards on retail and office campuses.

• →Identify AHJ jurisdiction early; commercial rebuilds frequently trigger fire protection, egress, accessibility, electrical, and restroom 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 suites and floors — code scope often expands mid-project on multi-tenant losses.
• →Coordinate with the Code Upgrade Documentation Guide and peril-specific guides while keeping retail/office indexing consistent.

• →Complete property security orientation and record badge or escort requirements as production constraints documented in the file.
• →Log delayed access and standby time with suite IDs when property management or tenants control entry — contemporaneous logs support general conditions lines.
• →Photograph restricted areas, alarm zones, and after-hours entry points that limit crew and adjuster windows.
• →Never bypass security protocols to 'save time' — unauthorized entry creates liability and destroys claim credibility.
• →Include security-driven temporary barriers and protection in estimates with photo evidence of why they were required.
• →Schedule adjuster access through the same PM/security path used for crews so walkthrough evidence matches production records.

• →Suite or floor scope omitted from a sample-suite carrier estimate — adjacent suites and common areas frequently appear only after indexed documentation.
• →Leasehold/TI discoveries after initial walkthrough — finishes and fixtures expand beyond carrier-selected samples.
• →Occupied-business production costs: after-hours labor, escorts, phased mobilizations, and temporary barriers authorized by ownership/PM.
• →Shared-system discoveries that explain multi-suite damage patterns (roof, HVAC, fire protection).
• →Code-driven upgrades documented with AHJ evidence after demolition or inspection.
• →Package every supplement by suite/floor/system ID with discovery photos, revised sketches, and estimate deltas — multi-tenant supplements fail when evidence is blended.

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

• →Route carrier meetings through ownership or property management; confirm attendees and suite access in writing.
• →Present suite and common-area indexes at every walkthrough — unlabeled photo dumps invite proportional reductions.
• →Log adjuster requests and follow-ups keyed to location IDs the same day.
• →Obtain written stakeholder approvals before expanding scope into additional suites, floors, or common areas.
• →Separate stop-loss mitigation approvals from reconstruction authorizations when stakeholders approve phases independently.
• →Close communication loops with a dated status packet: suites complete, pending decisions, and open supplement items.

• →Front matter: property identification sheet, ownership/PM/tenant contacts, suite directory, and floor index.
• →Building-systems and common-area evidence: roof, HVAC, fire protection, lobbies, corridors labeled to location IDs.
• →Per-suite and TI packs with reciprocal cross-references to systems.
• →Building-owned versus tenant-owned finishes and contents packs when ownership differs.
• →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 retail/office 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.
• →Property identification and stakeholder package on file.
• →Building, floor, and suite / tenant-space index complete.
• →Tenant-space documentation sets complete for each affected suite.
• →Leasehold and TI pack labeled to suite IDs.
• →Common areas and shared building systems pack labeled to location IDs.
• →Building-owned versus tenant-owned finishes and contents notes on file.
• →Occupied business access and authorization log contemporaneous.
• →Emergency mitigation indexed by suite and system.
• →Retail/office estimate index with quantity validation.
• →Code/ordinance file with AHJ evidence when upgrades apply.
• →Daily project logs by suite/floor/system ID.
• →Supplement change log with discovery drivers.
• →Final indexed claim package with line-to-evidence cross-reference.
• →QC spot-check: random suites resolve photos, logs, and estimate lines to the same IDs.

• →Pre-inspect: obtain site map or suite directory, floor list, and common-area list from property management; publish naming convention before crews mobilize.
• →Exterior and roof walk: document elevations, storefronts, roof areas when accessible, and drainage clues before opening interiors.
• →Building-systems and common-area pass: complete roof, HVAC, fire protection, lobbies, and corridors with location labels.
• →Suite sequence: work floor by floor or wing by wing; complete overview-to-detail photos before leaving each suite.
• →TI and contents pass: document leasehold finishes and tenant contents with suite IDs and ownership labels.
• →Adjacent-suite check: document undamaged boundary suites and shared-system paths that explain multi-suite patterns.
• →Same-day office sync: upload and label all sets before the next shift.

• →Suite ID matches property management directory on every photo and log row.
• →Overview-to-detail photo sequence complete before leaving the suite.
• →Ceiling, floor, and wall conditions captured separately.
• →Leasehold/TI finishes photographed before demolition with suite label.
• →Tenant contents/FF&E documented in place when present and safe.
• →Building-owned versus tenant-owned items labeled per written stakeholder direction.
• →Reciprocal cross-reference to common-area or system causation when applicable.
• →Undamaged adjacent suite or demising-wall context captured when it defines scope.
• →Mitigation equipment placement photos with asset tags for this suite.
• →Estimate section header exists for this suite ID with quantity validation.

• →Confirm Property → Building → Floor / Suite / Common Area / System naming is consistent across photos, logs, and estimate sections.
• →Spot-check three random suites: each resolves overview-to-detail photos, daily log rows, and high-dollar lines to the same IDs.
• →Verify TI packs are not merged into unlabeled building finish galleries.
• →Confirm common-area and systems packs are distinct from suite folders.
• →Validate occupied-business authorizations and access logs are contemporaneous for after-hours and escort lines.
• →Reject packages that use crew nicknames, missing suite IDs, or end-of-job narratives in place of daily suite logs.

• →Treating retail and office losses like residential single-dwelling files.
• →Merging multiple suites into one unlabeled commercial photo dump.
• →Mixing leasehold/TI evidence into base-building folders without suite IDs.
• →Using crew nicknames instead of property management suite and floor IDs.
• →Ignoring occupied-business access logs and after-hours authorizations.
• →Estimating multi-tenant scope as a single commercial finishes block.
• →Burying common areas and shared systems inside a representative suite folder.
• →Submitting supplements without suite-indexed discovery evidence.
• →End-of-job narratives replacing contemporaneous daily suite logs.
• →Skipping adjacent-suite and building-system checks that explain multi-suite patterns.

• →Day one: confirm primary ownership or PM contact, tenant notification path, and emergency authorization path in writing.
• →Daily: send indexed status to the primary contact — suites worked, common areas documented, discoveries requiring decisions.
• →Access events: log entry windows, escorts, denials, and security clearances keyed to suite and common-area 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 ownership/PM; bring suite and common-area indexes, not unlabeled drives.
• →Closeout: deliver the final indexed package in the folder structure ownership and risk managers can archive and forward.

• →Suites or floors omitted from sample-suite carrier estimate — separate suite photo packs and estimate sections ready.
• →Leasehold/TI damage beyond initial carrier sample — suite-labeled discovery photos before demolition.
• →Common-area or shared-system findings explaining multi-suite patterns — reciprocal IDs attached.
• →After-hours or escorted mobilizations — written PM/ownership authorization and access logs keyed to location IDs.
• →Phased releases creating remobilization or standby — contemporaneous phase logs by suite ID.
• →AHJ or code inspection triggering upgrade scope — permits, photos of non-compliant conditions, ordinance citations.
• →Equipment or drying duration exceeding initial assumption on multi-suite loss — per-suite equipment photos and daily logs.
• →Storefront or entry temporary weatherization beyond initial board-up — location-indexed protection photos and authorization.

• →Retail and office insurance claims are recovered through suite-indexed documentation, leasehold/TI discipline, common-area and systems separation, occupied-business coordination, and estimate organization that mirrors property management directories — 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 Multifamily, HOA, and Industrial guides when those property types dominate.
• →Claims Ninja supports contractors with documentation standards, large-loss estimating, supplement packaging, and claim recovery workflows on retail and office losses.