District of Columbia Employment Practices & Management Liability Insurance

Build an exposure map around the conference calendar. Temporary registration workers belong in the employment review; member challenges to a board vote belong in the governance review; compromised attendee records belong in the cyber review. A retirement committee's selection of service providers belongs in a separate fiduciary discussion. Event cancellation and professional advice to members should not be silently folded into management liability.

Ask the broker to match each named entity and committee to the proposed wording. An association, educational foundation and separately organized conference subsidiary may have different roles. Use the organizational chart and actual contracts rather than assuming a shared brand means every activity is insured.

For conference staffing, preserve assignment criteria, supervisor instructions and complaint communications. A dispute over which coordinator received a prominent sponsor account needs a factual timeline, not a general statement that assignments were fair. Compare wage-related exclusions, defense arrangements and any restrictions concerning temporary personnel before treating the employment section as complete.

D.C. Code section 29-406.90 provides conditional civil-liability immunity for qualifying uncompensated nonprofit volunteers, including directors. That reference is not a reason to assume every director, decision or defense expense is protected. Have counsel assess the provision separately from the insurer's agreement and the association's own indemnification arrangements.

Consider a board approving an exclusive conference sponsor while a director has a business connection to the sponsor. Preserve conflict disclosures, voting records and the approval materials. Ask how insured-versus-insured provisions could affect a member or director dispute, whether employment allegations are carved out, and whether defense expenses draw from a limit shared with EPLI. A governance policy is not a guarantee of sponsorship revenue.

An association's registration platform can hold attendee contact details, accessibility requests, payment references and sponsor exports in different locations. Record what each vendor actually stores, who can download it and whether an executive's mailbox contains copies. The association's incident lead should be able to locate that inventory without access to the compromised account.

Compare forensic services, privacy counsel, approved vendor arrangements and restoration provisions. Conference registration interruption and privacy claims are different loss categories. Ask whether an outside registration provider's outage fits the wording and whether the policy distinguishes a malicious incident from ordinary system failure. Do not describe every missed registration fee as an insured interruption loss.

A small association may use the same finance director for conference deposits and retirement administration. Separate those workflows in the submission: choosing a recordkeeper, handling an enrollment correction and paying an event invoice are not the same activity. Ask how the proposed policy distinguishes plan-management allegations from administrative mistakes and whether another coverage part addresses the latter.

This discussion therefore recommends contract review, not a new legal obligation. Compare covered plans, insured committees, prior acts and defense provisions. When an educational foundation shares staff with the association, obtain a clear answer about which sponsor and employees the proposal actually includes.

Keep the underlying agreement and board record together without rewriting either after a complaint arrives. Staff should distinguish an ordinary request for a refund from a written accusation of misconduct, while still escalating uncertain communications for policy review. The definition of claim, not the complaint's subject line, controls the insurance analysis.

Ask the broker to identify possible overlaps with event, professional or contractual coverage without promising that any form responds. Track separate notice addresses and consent requirements for the policies being considered. When multiple allegations concern the same sponsor arrangement, related-claims wording and shared limits deserve attention before the association assumes separate limits will be available.

The approval packet should identify the fields transferred, access roles, export settings, vendor contacts and a fallback registration process. Include an explanation of who can suspend the integration and who can approve incident-response spending. These are practical decision records, not assurances that the integration is secure or that the insurer will approve it.

At renewal, describe the live system rather than last year's standalone database. Ask whether changes affect vendor-interruption terms or application answers concerning access controls. Keep the board's project approval separate from the insurance placement decision: an approved budget does not establish cyber coverage, and a cyber limit does not establish that contractual promises to members can be funded.