Notifications
Clear all
Topic starter
07/06/2026 9:18 pm
TL;DR: Embedded eSignatures in insurance workflows reduce manual handling, improve completion rates, and create electronic audit trails for disputes, according to OneSpan’s CURE Auto Insurance example. The deeper lesson is that digital workflow controls now carry identity and evidence obligations, not just customer-experience benefits.
NHIMG editorial — based on content published by OneSpan: How CURE Auto Insurance digitized with OneSpan Sign for Guidewire InsuranceNow use cases
By the numbers:
- (53%) of first-time auto insurance buyers initiate provider, itiate provider relationships through online channels.
- CURE reduced costs and improved overall efficiencies by 22-25%.
Questions worth separating out
Q: How should security teams govern eSignatures in regulated workflows?
A: Security teams should treat eSignatures as governed transaction evidence, not just a convenience layer.
Q: Why do digital signing workflows need identity governance?
A: Digital signing workflows need identity governance because the signature is an approval event with accountability consequences.
Q: What breaks when eSignature channels differ across business units?
A: When eSignature channels differ across business units, policy consistency and evidence quality are usually the first things to break.
Practitioner guidance
- Bind signatures to workflow state Ensure each eSignature is tied to a specific policy version, transaction stage, and approval event so the signed record can be reconstructed without ambiguity.
- Standardise audit evidence fields Define minimum evidence requirements for signer identity, timestamp, document hash, and approval sequence so disputes can be resolved consistently across channels.
- Review channel consistency Test online, agent-assisted, and back-office signing paths for identical retention, exception handling, and policy enforcement rules.
What's in the full article
OneSpan's full case study covers the operational detail this post intentionally leaves for the source:
- How OneSpan Sign is embedded inside Guidewire InsuranceNow for policy workflows.
- The specific user journey changes that reduced mailing, scanning, and manual verification.
- CURE Auto Insurance's operational observations on retention, completion, and efficiency.
- The digital evidence and audit-trail considerations behind dispute handling.
👉 Read OneSpan's case study on embedded eSignatures for Guidewire InsuranceNow →
Embedded eSignatures in insurance workflows: what IAM teams should note?
Explore further
08/06/2026 9:11 am
Digital signing is now an identity-backed workflow control, not a document convenience feature. The value in this case is not the removal of paper alone. It is the fact that the approval becomes traceable, time-bound, and easier to defend in a regulated transaction flow. For identity teams, that pushes eSignature into the same governance conversation as non-human access and transactional assurance. Practitioners should treat the signing step as part of the control plane, not a peripheral user-experience add-on.
A few things that frame the scale:
- 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which shows how often governance depends on partial rather than complete identity inventory.
A question worth separating out:
Q: How can insurers tell if embedded eSignatures are actually reducing risk?
A: Insurers can tell embedded eSignatures are reducing risk when completion rates improve without increasing manual exceptions, dispute failures, or audit reconstruction effort. Useful signals include fewer NIGO records, lower rework, cleaner approval traces, and shorter policy cycle times with the same or better evidence quality. If speed rises but records get thinner, the programme is only moving the bottleneck.
👉 Read our full editorial: Digital signatures in insurance: what embedded eSignatures change
