Parties
Identify each contracting entity by full legal name, business form, and contact information so responsibility and notice procedures are unambiguous between insurer, insured, and any third parties.
A concise written agreement reduces disputes, clarifies timelines and responsibilities, supports regulatory reviews, and creates documentary evidence for claims and audits. It also documents reasonable procedures and good-faith efforts to resolve matters.
The Insurance Good Faith Agreement is used by multiple stakeholders across the lifecycle of a claim or policy administration.
Roles vary by use case; include legal, compliance, and claims representatives where appropriate for authorization and signature.
Identify each contracting entity by full legal name, business form, and contact information so responsibility and notice procedures are unambiguous between insurer, insured, and any third parties.
State the effective date and any retroactive application clearly; the effective date controls when duties and limitations begin for claims and statute-of-limitations purposes.
Describe the claims, policies, or transactions covered and list explicit obligations such as investigation timelines, information exchanges, and confidentiality responsibilities.
Set step-by-step handling rules — initial notice, investigation deadlines, documentation standards, and escalation paths — to reduce misunderstanding and improve operational consistency.
Specify remedy options, mediation or arbitration clauses, governing law, and venue to limit litigation cost and define how disagreements will be resolved.
Detail signing method (electronic or wet ink), required signer authority, any notarization or witness needs, and the record-retention approach for executed copies.
| Authentication | Email link, SMS code, or KBA depending on signer risk |
|---|---|
| Field Types | Use required fields, date pickers, and read-only policy references |
| Conditional Logic | Show clauses only when relevant using conditional visibility |
| Attachments | Require supporting documents like proof of loss or policy declarations |
| Audit Trail | Enable timestamp, IP capture, and certificate retention |
Choose a platform that supports secure delivery, required file formats, and an audit trail for regulatory review.
Ensure your workflow preserves tamper-evident records, stores signed PDFs with audit metadata, and meets any industry-specific authentication or BAA requirements.
Many policies require notice within 30–90 days of loss; check the policy language.
Insurers typically have 30–60 days to acknowledge and investigate a reported claim.
Some statutes require payment or written denial within a set period after proof of loss.
Retain executed agreements for the period required by applicable law and the retention policy.
Allow time for regulator requests—state insurance departments often set 30–60 day response windows.
Agreement drafted and internal review scheduled.
Legal and compliance sign-off obtained.
Signatures collected via chosen method.
Final document stored with audit trail and access controls.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Free trial available | Free trial available | Free trial available | Free trial available |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
An insurer and claimant agree on investigation timelines and documentation requirements
Two carriers set intercompany cooperation rules for liability allocation