Turn the award into an operations map
Before the first program date, identify the legal grantee, fiscal sponsor if any, service recipients, work sites, start and end dates, staff, volunteers, subcontractors, transportation, equipment, information handled, and funds movement. Separate what the organization will do itself from what a partner promises to do. A grant title such as “community outreach” is too broad to explain the activity an insurer or contract reviewer needs to evaluate.
Assign an owner to each fact and attach the signed scope, budget, staffing plan, and venue or partner agreements. Mark planned activities that are not yet operational with expected dates. An application should not present a future service as a current practice or omit a launch already approved.
Read the signed grant, not only the award letter
Locate the final grant agreement, attachments, amendments, insurance exhibit, indemnity clause, reporting requirements, subcontracting rules, and notice contacts. San Francisco’s G-100 form is a useful example of how a city agreement may specify different insurance lines and additional-insured language, but the executed document for this award is the one to review. Do not copy amounts from a template into a different contract.
Build a clause-to-evidence table listing requirement, agreement page, named entity, limit, policy line, certificate or endorsement requested, deadline, owner, and unresolved question. Some requirements may need negotiation or a policy change rather than a certificate.
Identify the insurance conversations the program creates
A new service may prompt general liability, professional or program liability, management liability, employment practices, property, cyber, crime, auto, or workers’ compensation questions. Which ones matter depends on the actual activity and agreement. For example, staff transporting materials, volunteers supervising clients, and a consultant delivering advice create different facts; do not infer one policy responds to all three.
Compare the submitted operations description with named insureds, insured-person definitions, scheduled locations, service definitions, limits, retentions, exclusions, conditions, and endorsements. Ask for the exact form or written response behind any material assurance. Policy names alone are insufficient.
Check personnel, partners, and custody
Write down who hires, supervises, and trains each worker or volunteer and who can sign on behalf of the nonprofit. For a subcontractor or fiscal sponsor, record who controls the service, holds client information or funds, owns equipment, and sends any required notices. Avoid describing a partner’s insurance as the organization’s own without reviewing the agreement and evidence.
If the program handles sensitive personal information, use approved systems and share only the necessary operating summary in the insurance process. If it handles restricted funds, trace approval and reconciliation duties. These details make policy and contract questions more precise without turning an insurance article into legal or compliance advice.
Plan venue and event dependencies
If program delivery includes a San Francisco venue or public event, identify the actual address, activity, attendance, dates, equipment, vendors, food or transportation, and any city or venue permission needed. Local permit rules vary by activity; check the relevant city guidance rather than assuming every nonprofit event uses the same process. A permit or fee waiver does not alter an insurance policy.
Keep the venue agreement and any certificate request with the grant file. If the location, audience, or activity changes, reopen both the permit and insurance questions before assuming the original documentation still fits.
Set a pre-launch sign-off
Have program leadership confirm the work and people; finance confirm the budget, funds controls, and asset values; legal review nonstandard promises; facilities or event staff confirm locations; and the insurance contact compare available documents with the signed contract. Capture each open item, owner, due date, and written answer. Do not represent a requirement as satisfied merely because a certificate has been requested.
Save the final certificate, relevant endorsements, delivery confirmation, and counterparty acknowledgment with the signed agreement. If the grant has an ongoing reporting or renewal obligation, put it on the calendar with the policy dates.
Review after the first month of delivery
Compare the original proposal with actual staffing, client flow, partner duties, systems, property, event schedule, and spending. A program may scale or change soon after launch. Update the operational narrative and raise material differences through the appropriate contract and insurance channels. Retain a dated change log so the next renewal is based on real delivery.
The checklist makes the conversation more complete but cannot determine compliance with a particular grant or whether a claim will be paid. The signed agreement, issued policy wording, declarations, endorsements, facts, and applicable law control.
Prepare a clear market-submission summary
Give the insurance contact a dated two-page account of the new program: purpose, legal entity, services, target population, site and hours, staffing and volunteer supervision, vendor and fiscal-sponsor relationships, vehicles or transportation, property, data, budget, and contract duties. Attach the exact insurance exhibit and identify anything still conditional. A concise factual summary is more useful than forwarding a full grant application without explaining which activities will begin.
Request a written list of unanswered underwriting questions and the forms or endorsements being reviewed. If the city agreement requires evidence before a program start date, place that deadline beside the quote and board-approval dates. Do not wait until the final certificate request to discover that the operational description differs from the signed grant.
Reconcile scope changes and amendments
City-funded work can change through an amendment, revised deliverable, new partner, different site, or extended period. For each change, compare the new scope and budget with the original insurance submission, policy period, scheduled locations, insured entities, and any certificates already delivered. Keep the amendment, effective date, and person approving the change in the same register as the original grant.
When a requirement cannot be met as written, preserve the question and the counterparty’s written response. Neither a grant amendment nor a certificate silently changes the policy. The signed contract and issued insurance documents must be reviewed separately.
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, its programs, workforce, services, or agreements?
- Which current policy form, declaration, or endorsement should be read with that change in view?
- What definition, exclusion, condition, limit, retention, or policy date needs a documented answer?
- Which agreement, operating record, or final policy document belongs in the review file?
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.