INSURE360™ Part 6: Protecting the Revenue You Don’t Control — Contingent BI, Civil Authority & Ingress/Egress

This sixth installment of Dawgen Global’s INSURE360™ series explains how to design, model, and prove these dependency-driven claims—especially in the Caribbean context where logistics chokepoints, utility fragility, and tourism/retail footfall create outsized exposure.

1) Quick Definitions (Plain-English)

• Contingent Business Interruption (CBI): Covers your lost income when a third party in your revenue chain (key supplier, contract manufacturer, customer, distributor, warehouse, port) suffers covered physical damage that impairs your operations or sales.

• Civil Authority (CA): Covers lost income when a government order restricts access or use due to damage to nearby property—even if your own location is undamaged.

• Ingress/Egress (I/E): Covers lost income when physical access to your premises is prevented or impaired by damage (e.g., roads, bridges, debris), again regardless of direct damage to your site.

These coverages often have time franchises (minimum hours before they respond), radius limits (e.g., damage within X miles), and sometimes shorter maximum indemnity periods than traditional BI. The fine print matters.

2) Why These Three Decide Caribbean Outcomes

• Concentrated chokepoints: Ports, airports, bridges, causeways, and a small number of critical suppliers and distribution centers can grind commerce to a halt—even in areas with minimal building damage.

• Tourism & retail dependency: Hotels, malls, office towers, attractions, and schools act as leader/attraction properties. If they close, surrounding businesses suffer.

• Utility and access overlap: Service interruption (power/telecom/water) may be insured under different clauses, but CA and I/E can trigger when authorities restrict access or when roads are blocked—even if the utility clause is narrow.

• Cross-island ripple effects: A damaged mill or warehouse on one end of the island can cut inputs to factories or retailers on the other end.

3) The Coverage Mechanics That Move Real Money

A) Triggers & Proximity

• CBI: Requires covered physical damage at the dependent property. Many policies require those third parties to be scheduled or to fall within defined categories (supplier/customer/contract manufacturer). Confirm whether unscheduled dependent locations are included.

• CA: Requires a government order due to nearby property damage. Watch for distance limits (e.g., within 1 or 5 miles) and maximum durations (often 2–4 weeks, but varies).

• I/E: Requires physical damage that prevents/impairs access—often with a proximity requirement. Some wordings require “prevention” (hard stop), others accept “impairment” (reduced access), which is much more practical.

B) Waiting Periods & Time Limits

• CA and I/E often include waiting periods (e.g., 24–72 hours) and shorter maximum indemnity periods than standard BI. Model these carefully; early days are the steepest revenue losses.

C) “Physical Damage” at the Dependency

• CBI typically needs direct physical loss at the supplier/customer site. For CA/I/E, it’s physical damage nearby or along access routes. Ensure your policy expressly recognizes storm surge/flood where relevant.

D) Attraction/Leader Property

• If your revenue depends on a nearby property that pulls your customers (mall, school, theme park, office tower), confirm Leader/Attraction coverage and the radius.

4) Mapping Dependencies the Dawgen Way

Within INSURE360™, we build a Contingent BI Network Map:

1. Revenue lens: Start with your top revenue streams and rank dependencies by revenue concentration, lead time, and substitutability.

2. Nodes: Suppliers, contract manufacturers, DCs/warehouses, ports/airports, largest customers, anchor attractions (for retail/hospitality).

3. Edges: Transport corridors (roads, bridges, ferries), typical transit times, customs exposure, and alternative routes.

4. Risk tags: Flood/wind zones, elevation, historic outage duration, single-point-of-failure flags.

5. Policy tie-ins: Which dependencies are scheduled? Which are covered by “unscheduled dependent property” language? Where do CA/I/E radius limits bite?

Outcome: A prioritized procurement/coverage plan and the business case for CBI/CA/I/E limits by node and corridor.

5) Designing Limits, Sublimits & Words That Work

• Sublimits by category: Allocate CBI limits to supplier, customer, and logistics nodes that dominate revenue (often a few account for most exposure).

• Unscheduled dependencies: If operationally realistic, add endorsements for unscheduled dependent property with sensible sublimits.

• Impairment vs. prevention: Push I/E wording to cover impairment, not just total prevention. Reality is often partial access.

• CA distance & duration: Right-size radius (miles) and maximum indemnity period to local conditions; many Caribbean municipalities cover large zones with single orders.

• Attraction/Leader: Ensure the list (or category definition) captures the true traffic drivers for your sites.

• Waiting period: Model revenue curves to justify 24–48 hours where 72 hours would erase the steepest losses.

6) Modeling the Loss (So Adjusters Can Say “Yes”)

A) Build a Revenue Engine per Site

• Baseline sales/occupancy/throughput with seasonality curves.

• Identify footfall drivers (attraction property calendars, school terms, cruise schedules).

• Map supply lead times and minimum operating inventory.

B) Scenario Playbook

• Supplier down (X days): What SKUs or processes stop? What’s the revenue slope?

• Port closure (Y days): Backlog impact on imports/exports; EPI needs.

• CA order (Z days): Footfall drop vs. full closure; partial vs. total suspension.

C) Evidence to Triggers

• CBI: Third-party damage evidence (photos, public statements, repair orders); your purchase orders and lead times; stock-out reports.

• CA: Copy of the government order, dates/times, coverage of your area; media advisories; law-enforcement notices.

• I/E: Photos of blocked routes, official closure notices, contractor reports on road/bridge damage; GPS logs for detours and added travel time.

D) Partial Suspension Matters

Ensure your BI wording recognizes partial suspension. For CBI/CA/I/E, partial access/operation is common and should not penalize you for keeping the lights on.

7) Documentation & Notices (What to Send, What to Save)

• Parallel notices: Send separate notices for CBI, CA, and I/E. Don’t assume a single property notice suffices.

• CA evidence pack: The actual order, maps or descriptions of the affected area, and a timeline of when orders lifted. Keep screenshots and PDFs.

• I/E proof: Route block photos, municipal reports, police/fire advisories, and contractor assessments linking damage to access limitations.

• CBI proof: Supplier/customer letters, photos (if available), third-party press or regulatory updates, purchase history and cancellation notices.

• Revenue variance: Daily/weekly dashboards tying drops to the specific trigger and period—with reconciliation to ledgers.

8) Common Pitfalls (and Dawgen Fixes)

1. Relying on property BI only.
   Fix: Procure CBI/CA/I/E with adequate sublimits; model dependencies.

2. “Prevention” wording in I/E.
   Fix: Amend to “prevention or impairment.”

3. Unscheduled dependencies excluded.
   Fix: Add unscheduled dependent property coverage or schedule the big ones.

4. CA radius too tight, duration too short.
   Fix: Calibrate to local municipal practice; evidence why a wider radius makes sense.

5. Late or single notice.
   Fix: Use Dawgen’s multi-branch notice tree (CBI, CA, I/E, plus service interruption if relevant).

6. Weak linkage from trigger to numbers.
   Fix: Prepare adjuster-ready packets with orders, maps, photos, and daily revenue variance.

9) Caribbean Playbook: Practical Tactics

• Ports & customs: Pre-arrange expediting SLAs; document backlogs with carrier letters; right-size EPI to reflect slow market re-entry after port reopenings.

• Bridges & causeways: Pre-map alternatives; capture detour time and delivery costs (EE) to show BI avoided.

• Attraction properties & schools: Maintain calendars and attendance reports; evidence their closures and reopening dates.

• Cruise schedules: For retail districts tied to cruise arrivals, archive itinerary cancellations and port advisories.

• Fuel & power: Where service interruption clauses are narrow, CA/I/E may become your practical path—capture orders and access conditions thoroughly.

10) KPIs & Governance

• Dependency Coverage Index (0–100): % of top dependencies with explicit CBI/Leader coverage.

• CA/I/E Fit Score (0–100): Wording suitability (radius, duration, impairment, waiting period).

• Notification SLA (%): On-time CBI/CA/I/E notices.

• Time-to-Packet (days): Trigger to first adjuster-ready dossier (target ≤ 7–10).

• Recovery Ratio (%): Paid vs. claimed for dependency-driven losses.

• EPI Utilization: % of cases where EPI was needed and used effectively.

Use these metrics at renewal to demonstrate mature, analytics-led risk governance.

11) Templates You Can Lift

A) Civil Authority Notice (Excerpt)

We provide initial notice under the Civil Authority coverage for Policy [#] due to Order [# / Agency] restricting access to [Location(s)] from [Date/Time] following [Named Storm/Event]. A copy of the order and affected-area map is attached. We will supplement with revenue variance and additional documentation.

B) I/E Evidence Index (Excerpt)

C) CBI Supplier Impact Memo (One Page)

• Supplier/site; nature of damage; expected downtime

• SKUs/processes impacted; average daily volume lost

• Substitution options and lead times

• Planned EE to mitigate; BI avoided estimate

12) Your 12-Point Dependency Readiness Checklist

1. Contingent BI dependencies mapped and ranked by revenue reliance

2. Unscheduled dependent property coverage present (or key nodes scheduled)

3. Civil Authority wording: workable radius and duration

4. Ingress/Egress language recognizes impairment (not only prevention)

5. Attraction/Leader properties identified and covered

6. Waiting periods modeled against daily revenue curves

7. Parallel notice templates for CBI/CA/I/E ready to send

8. Government order capture SOP (PDFs/screenshots, timestamps)

9. Access route evidence plan (photos, GPS, municipal notices)

10. Supplier/customer proof SOP (letters, orders, cancellations)

11. Daily revenue variance dashboard aligned to triggers

12. Adjuster-ready packets assembled within 7–10 days

If any box is unchecked, revenue you don’t control can become cash you don’t recover.

 Make Dependencies Pay—Not Hurt

Your business shouldn’t be crippled by third-party damage, blocked roads, or government orders. With the right CBI/CA/I/E architecture, evidence, and operating rhythm, you can turn dependency risk into recoverable loss.

Book an INSURE360™ CBI/CA/I/E Readiness Scan
We’ll map your revenue dependencies, calibrate coverage (limits, wording, waiting periods), and implement the notice/evidence playbooks that make these claims pay.

Contact Dawgen Risk Assurance Services

• 🔗 Discover More: https://dawgen.global

• 📧 Email: [email protected]

• 📞 USA: 855-354-2447

At Dawgen Global, we help you make Smarter and More Effective Decisions—especially when the revenue you depend on lies beyond your walls.