These guides connect the coverage decisions below; use the questions to drill into a
specific rule.
Industry guide · 2026 edition
Before an accounting firm accepts work, its engagement letter, client-data terms, and office lease can each require proof of insurance. This guide explains what those documents request, what a certificate can prove, and what to check before signing. For liability exposures and potential claims, see pleasedontsue.us.
Read the guide → Industry guide · 2026 edition
An architect’s insurance requirements arrive with the project: in the design agreement, site-access rules, consultant contracts, and office lease. This guide explains what each document can require, what proof to provide, and how to check the policy before work begins. For liability exposures and claims, see pleasedontsue.us.
Read the guide → Industry guide · 2026 edition
A law firm needs to keep its malpractice coverage connected to prior work as partners join, leave, retire, or dissolve the firm. This guide explains that continuity, along with client, lease, and state requirements and the documents used to prove coverage. For liability exposures and claims, see pleasedontsue.us.
Read the guide → Industry guide · 2026 edition
A managed service provider’s client contract usually asks for both technology errors-and-omissions coverage (technology E&O) and cyber coverage. This guide explains why the two are requested together, what a certificate proves, and what to verify before you send one. For liability exposures and claims, see pleasedontsue.us.
Read the guide → Coverage-line guide · 2026 edition
A miscellaneous professional liability policy only responds if its form mechanics line up with the work and the claim. This guide is the mechanics side: the claims-made trigger and the retroactive date that decide whether old work stays covered, the "professional services" definition that controls what work the policy answers, tail coverage at a practice change or retirement, the client contract that sets the demanded limit, and the certificate that evidences it. The liability side — who can sue and what is at stake — is on pleasedontsue.us.
Read the guide → Industry guide · 2026 edition
A SaaS consultant often sees insurance requirements while completing a client agreement or vendor-onboarding form. This guide explains the policies and proof those documents commonly request, including how to check that a policy covers the software work you actually do. For liability exposures and claims, see pleasedontsue.us.
Read the guide →