Indiana Employment Practices & Management Liability Insurance

Map four activities to their own policy questions: staff selection and supervision, board approval and use of contributions, client and donor information, and employee-benefit arrangements. EPLI, D&O, cyber and fiduciary liability may each be relevant, but the package should not be presented as replacing premises, vehicle, professional or participant-related coverage.

Prepare an integration chart showing the legal entities, governing boards, paid workers, volunteer coordinators and systems. Mark decisions that remain with a partner organization. The purpose is to compare actual responsibility with insured definitions, not to imply that operational cooperation automatically transfers insurance. Keep known complaints and unresolved funding restrictions visible during the review rather than letting them disappear beneath the new program name.

Indiana agency guidance describes the Civil Rights Law with a generally six-or-more-employee threshold, subject to statutory definitions and exemptions, the Indiana Civil Rights Commission and a 180-day filing period with that commission. It separately records a 300-day EEOC deferral period for covered Indiana charges. These facts do not resolve every allegation, and neither legal period establishes the insurer's notice deadline.

Retain the staffing criteria, interview records and complaint communications used during integration. Compare administrative-charge coverage, defense arrangements and employment-related exclusions. If one partner employed the affected worker before consolidation, identify that history explicitly. A new supervisor's involvement does not alone answer which entity or policy period is relevant to the allegations.

That does not establish that every consolidation decision qualifies or that insurance defense expenses will be advanced. Counsel's analysis of the statute and governing documents is separate from the insurer's obligations under the proposed form.

Preserve the board packet, disclosed conflicts and reasons for choosing the operating model. Ask how member or former-director demands are treated, whether entity coverage fits the nonprofit and whether defense costs reduce a shared aggregate. A grant repayment request and an allegation of governance misconduct are not necessarily the same covered loss. Review the actual requested remedy rather than assuming a D&O policy reimburses program funding.

During program consolidation, inventory intake forms, donor systems, volunteer rosters and employee records separately. A combined mailing list may be easy to create while obscuring which organization collected each field and which users should retain access. Record the migration steps and old-system shutdown plan rather than assuming the new platform contains the only copies.

Compare approved response vendors, restoration and privacy-liability terms. Ask whether the proposed cyber policy includes the actual affiliates and hosted intake platform. A partner's agreement to administer the database is not proof that the partner's insurance covers the nonprofit. Review fraudulent donation instructions separately from ordinary data-restoration costs and avoid describing every loss of fundraising revenue as insured interruption.

Ask how fiduciary coverage addresses specified plan-management allegations and how that differs from administrative-error protection. Record who selects providers, receives reports and approves corrections. A volunteer treasurer may have a different function from the payroll coordinator; titles alone do not explain the activities being offered for insurance.

Compare schedules, prior acts, insured people and defense terms with appropriate advisers. If one program previously used another organization's arrangements, retain those documents for review. The goal is an accurate submission and clear policy comparison, not a promise that all integration-related benefit complaints are insured.

Provide coordinators with the current version rather than relying on informal understandings developed before consolidation. Preserve the approval trail when authority changes. A volunteer who has historically arranged transportation or accepted donations may continue acting unless the operational transition is explained clearly; insurance review should reflect those actual practices.

Use the matrix to test insured-person and entity definitions with the broker. Ask whether committees or volunteer leaders need additional clarification in the proposal. An internal delegation document does not amend a policy or establish statutory protection. Its practical value is showing where decisions occur and helping the organization avoid describing itself differently to donors, staff, partner organizations and prospective insurers.

Prepare an inventory of exports, backups and vendor accounts so the old platform is not forgotten after migration. Test whether departed staff and former volunteers can still log in. Assign responsibility for vendor escalation and preserve a way to contact the response team outside the shared database.

Explain the migration and partner access in the insurance submission when relevant to the questions asked. Compare the cyber policy's insured entities and service-provider provisions with the real arrangement. If a donor or partner requests an insurance representation, confirm the wording before promising protection. Integration planning supports a clearer response to an incident but does not prove security or guarantee that any resulting loss falls within coverage.