Start with the organization and service model
does crime insurance cover employee theft at a nonprofit can involve a nonprofit, board, officer, employee, volunteer, consultant, donor, grant, event, retirement plan, client fund, data system, or professional service. The policy question depends on the actual role, activity, allegation, and issued terms.
Describe programs, beneficiaries, locations, paid and volunteer duties, board authority, funds flow, grant obligations, events, contracts, data, technology, and changes since the prior application.
Collect the governing and operating record
Gather entity and board records, policies, employment and volunteer materials, grant agreements, event and vendor contracts, program descriptions, payment controls, data map, incident or complaint timeline, current declarations, policy forms, endorsements, and certificates.
Preserve original communications, approvals, records of funds movement, event details, and notices. A dated file makes it possible to distinguish a current fact from a later conclusion.
Compare the policy terms and agreement separately
Compare D&O, EPLI, professional liability, general liability, cyber, crime, fiduciary, fidelity, property, event, and other forms only where the facts support the question. Check insured definitions, exclusions, limits, retentions, sublimits, claims-made dates, conditions, and notice duties.
Read the grant, consultant, donor, event, employment, and vendor agreements separately. A policy does not automatically match a contractual or governance obligation.
Map governance, program delivery, and funds authority
For does crime insurance cover employee theft at a nonprofit, map the practical route from a board decision or program commitment to delivery, payment, and reporting. Identify the entity involved, board or committee authority, executive owner, employee or volunteer responsibilities, consultant role, beneficiary interaction, and any grant, donor, or vendor obligation that shapes the work.
Use meeting minutes, delegations of authority, program plans, approval records, job descriptions, volunteer materials, and payment workflows to show who could approve, direct, access, or communicate at each step. This is especially useful when an allegation concerns oversight, employment, professional services, a payment instruction, or a missed commitment rather than a single physical incident.
Separate board, workforce, volunteer, grant, donor, and data records
A complaint, payment loss, program dispute, employment matter, event incident, or data concern may touch multiple groups, but the facts and policy questions for each are different. Maintain separate, dated records for governance actions, personnel decisions, volunteer activity, grant deliverables, restricted funds, donor communications, service files, and system access.
Preserve original emails, approvals, invoices, bank or payment evidence, complaints, contracts, incident reports, and notices. Then build a timeline that identifies the first awareness date, decision points, people involved, remediation steps, and unresolved facts. That makes it possible to review claims-made dates, reporting duties, insured definitions, and exclusions against evidence instead of a retrospective summary.
Use grants and events as contract triggers
For every major grant, sponsored program, fundraiser, or event, record the scope, dates, venue, participants, fund restrictions, reporting promises, vendor duties, insurance requirements, indemnity language, and cancellation or incident-notice provisions. Add a review point before public launch, a material change, payment approval, and closeout.
Compare these requirements with the issued forms and endorsements before relying on a certificate or informal assumption. A grant, sponsor, venue, or vendor clause can allocate responsibility differently from the policy. Flag gaps early for leadership and legal review, while the organization can still change the agreement, process, or operational plan.
Record a follow-up before the next change
Document the question, facts, source records, policy form and endorsement references, unresolved item, owner, and deadline. Reopen the record after a new program, board change, grant, event, workforce shift, data system, payment process, claim, or renewal.
The board can use this follow-up list to assign work after a program or staffing change. It does not confirm protection for an event or claim; retain the grant conditions, activity record and issued insurance terms for a specific review.
Decision checklist for your coverage review
Use these questions with the current policy, relevant agreements, and the latest operating records. They help identify what needs a document-level answer before requesting or comparing terms.
- What changed in the organization, program, workforce, or agreement?
- Which issued policy form or endorsement needs direct review?
- Which governance, grant, or operating records support the question?
- What deadline, event, or renewal date is next?
Bring the records into the conversation
Set the declarations, applicable endorsements, governing or service agreements, and the operational record beside this guide. Record the document reviewed, the question raised, the answer received, and anything that remains unresolved. That file helps a board, finance lead, or firm principal revisit the decision when circumstances change.
Yerba Buena Partners can help prepare a commercial insurance submission and compare available terms against the organization’s actual responsibilities. This guide is educational and does not decide a claim or promise coverage; policy wording, declarations, and endorsements control.