Why the description is more than a title
“Consulting,” “design,” or “advisory” can describe very different work. A firm may provide recommendations, manage a client project, deliver a report, hold client data, use subcontractors, or accept responsibility for a defined outcome.
When the work changes, update the description even if revenue, address, and legal name remain familiar.
Build a usable operating narrative
Describe clients, services, deliverables, jurisdictions, typical fees, subcontracted work, data access, and any work that carries a design, certification, or supervisory responsibility. Identify exceptions separately rather than hiding them in a general capability statement.
Keep sample current agreements, scopes, statements of work, and any client insurance exhibit available for the review.
Compare the wording with the promise
Read the professional-liability insuring agreement, professional-services definition, exclusions, retention, retroactive date, claims-made conditions, and any cyber or management-liability provisions separately. Check whether a proposed definition tracks the actual services described.
Contract indemnity and insurance clauses can identify questions, but they do not amend the policy. Record any mismatch between the requested requirement and the proposal.
Refresh the file when work expands
Revisit the narrative when the firm introduces a new offering, works with a new client type, hires subcontractors, enters a new jurisdiction, or takes on a larger project. Save the dated narrative with the final proposal comparison.
Policy wording, declarations, and endorsements control.
Use the statement of work as the starting point
Professional liability insurance for consultants, designers, advisors, and other professional-service firms should be discussed alongside the work promised to the client. Read the statement of work for advice, recommendations, deliverables, project management, design responsibility, data access, subcontracting, timing commitments, and indemnity language. A short service label can hide a responsibility that deserves a direct question in the insurance submission.
Firms should describe their typical work and their exceptions. A project that involves a regulated client, a new technology, client funds, a certification, a public-facing recommendation, or an outside subcontractor may be unusual enough to warrant separate documentation rather than being folded into a generic “consulting” description.
Professional liability, cyber, and management terms
A complete business insurance review may involve professional liability, cyber insurance, general liability, D&O, EPLI, and commercial crime as distinct coverage discussions. Compare the professional-services definition and exclusions with the actual scope, then read any cyber or management-liability terms separately. Do not assume that a technology-related service is automatically handled by cyber insurance or that a client contract changes an exclusion.
Keep an approved scope narrative, representative agreements, current policy forms, and a record of questions asked at renewal. This gives a San Francisco professional firm a practical file for new work, contract negotiations, and the next insurance application.
Turn a sample engagement into a precise service description
Choose two recent client agreements: a routine engagement and one with unusual responsibilities. For each, state the deliverable, intended user, professional judgment exercised, deadline, client inputs, subcontracted work, data access, and promised remedy if the result is disputed. Distinguish advice from a technology platform, administrative support, training, fundraising, or direct program delivery. The description should match what the firm actually signs and does.
Record which legal entity contracts with the client and whether staff work on the client’s site or systems. A general industry label may be too broad to show the relevant professional-services definition or territory in a proposal. Keep the signed statements of work and a short approved summary together.
Compare contract risk with policy language without merging them
Flag indemnity, warranties, performance standards, audit rights, data-security duties, intellectual-property promises, and requirements to redo work. A contract can make a firm responsible for something its insurance policy does not address. Compare the proposed professional-liability form’s service definition, claim trigger, retroactive date, exclusions, defense provisions, and retention with the actual engagement. Then review cyber and general liability separately where their triggers may differ.
Ask for a written form-level answer on a material mismatch before signing a new kind of work. Do not infer that a client’s demand for a limit or certificate changes an exclusion or creates coverage. Legal counsel should assess contract obligations; insurance review is a separate part of the decision.
Create an approval trigger for nonstandard work
Set a short intake process for a new client sector, regulated activity, high-value project, software deliverable, use of a subcontractor, control of client funds, or contract outside the firm’s usual geography. The project lead records the scope and start date, legal reviews nonstandard promises, and the insurance contact checks whether the operating description or form requires attention. Document the outcome before work begins when possible.
Retain the approved agreement, submission update, written question, proposal response, and issued endorsement in one file. At renewal, compare that file with the services narrative instead of copying last year’s application. Policy wording, declarations, endorsements, facts, and applicable law control.
Use an allegation scenario to locate the right form
Imagine a client alleges that a report was late and caused a project delay. Separate the factual questions: what did the contract promise, which entity signed it, what work was actually delivered, what remedy was demanded, and when was the first written allegation received? Compare professional liability terms with those facts, then examine any cyber or general-liability issue independently if the allegation also involves a system or physical event.
Keep the original demand and response deadline with the engagement file, and follow the policy’s notice and consent instructions with the appropriate advisers. A scenario clarifies what to ask; it does not tell the firm which policy will respond.
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.