Maryland Employment Practices & Management Liability Insurance

Begin with a responsibility chart showing the employing organization, contract holder, data custodian, and plan sponsor. A research nonprofit may share an office with an affiliated laboratory while using separate payroll and grant administration. A services contractor may supervise staff at customer premises. These arrangements should be explained to the broker in operational language rather than compressed into a single industry description.

Ask each department to name the decisions it can approve and the records it holds. Procurement can explain vendor promises; HR can explain role assignments; finance can explain benefit deductions and ownership. Use those accounts to compare the insured-organization definition with the structure. If a package combines several coverage parts, identify whether defense expenses and payments draw from one pool. The objective is a traceable review, not a universal recommendation for every Maryland employer.

The Maryland employment-complaint provision states a 300-day period for employment complaints other than harassment and two years for harassment under the cited provision. EEOC Baltimore guidance separately describes the 300-day deferral deadline for covered Maryland charges. Counsel should apply those references to the facts; they are not interchangeable insurance reporting periods.

For a contract-driven reassignment, retain the customer’s instruction, internal alternatives, selection rationale, and employee communications. Ask whether the proposed form addresses an administrative proceeding and how contractual-liability or professional-services exclusions might affect the allegations. Do not describe a contract loss as proof that every resulting personnel decision is outside management's control. Review temporary staff and jointly supervised workers against the actual insured-person and claimant definitions.

Prepare a diagram of the parent, foundation, laboratory, and any service entities. List directors serving more than one organization and identify outside-board roles separately. An affiliated organization's name on a website is not evidence that its board has protection under another entity's policy. Request the relevant definitions and endorsements rather than relying on a group label.

Consider a donor questioning the allocation of restricted research funding or a board disagreement over a program partnership. Preserve minutes, delegations, and conflict-review materials so the organization can explain the decision process. Ask about entity coverage, advancement of defense expenses, insured-versus-insured terms, and the relationship to EPLI. D&O is not a substitute for professional liability on laboratory work, and an affiliation agreement does not establish an insurer's obligation to fund a defense.

Test the cyber response process against a vendor-hosted outage and an unauthorized email login. Does the form require advance consent for specialists? Which interruption provision addresses a service provider? What limits or exclusions concern contractual obligations? Keep these questions distinct from whether notice is legally required. Document the incident timeline and preserve messages, but avoid making coverage or liability admissions simply to complete a vendor's standard questionnaire.

An education-adjacent nonprofit using a 403(b) arrangement should describe that arrangement accurately rather than selecting a generic retirement-plan category on an application. Assemble provider contracts, committee appointments, participant and asset information, and the record of provider reviews. Ask what the proposed policy requires when a new plan or affiliate is added during the year.

Research organizations can have people funded through different projects but participating in one benefits platform. Reconcile the sponsor and payroll records before deciding that each affiliate's arrangement is identical. Compare protection for the organization and the individuals against exclusions, defense provisions, and plan definitions. Treat a separate bond and administrative-error coverage as separate review items. An outsourced recordkeeper's agreement is useful evidence of delegated tasks, not proof that every decision or allegation has moved away from the employer.

A contract manager may learn that a customer no longer wants a person assigned to a project. The HR file should distinguish that instruction from the employer's decision about reassignment, pay, leave, or separation. Preserve the written instruction and contemporaneous alternatives; do not reduce the explanation to a vague note that the contract required termination. Counsel can assess the actual duties and allegations.

Identify who may receive a complaint at the customer site and how it reaches the employing organization. A project manager, security contact, and HR director may each hold only part of the chronology. Establish a handoff that brings those pieces together promptly. At quotation, describe customer-premises work and supervision accurately, and ask the broker about any wording tied to contractual performance. This supports a focused review without asserting that a contract's staffing language creates coverage.

Suppose a laboratory, fundraising foundation, and education program use one finance office. List which entity approves hiring, signs vendor agreements, receives donations, and controls access to shared files. Then check those names against the proposed insured schedule. A common executive director or email domain should trigger questions, not an assumption that every affiliate is automatically included.

Build a renewal packet that includes the service agreement and examples of how authority works in practice. Identify directors who also approve benefit providers, and explain which committee minutes support those decisions. For operations around Baltimore and the Washington suburbs, provide actual work locations so counsel can assess location-specific questions and underwriters can see the workforce footprint. The useful result is a documented boundary between shared administration and each organization's decisions, with unresolved insurance questions recorded for follow-up.