These minimum requirements must be satisfied to achieve the LIDMA E-Solution “Seal of Approval”. The vendor description of how each requirement is met is intended to help LIDMA members evaluate different eSignature options and pick the solution that is right for their business model.
The Seal of Approval Process will occur twice annually. Below is the annual submission calendar:
Approval Cycle
ApplicationDue Date*
Review Process & Verification of References
Seal Announcements
Summer
August 26th
August 27 - September 9
Seal Approvals announced LIDMA Annual Meeting
Winter
February 28th
March 1 – March 30
*Any submissions received after the posted deadline will be held until the next review period. Applicant will be notified of this action.
In addition to the announcement by LIDMA of all Seal awards, all Seal recipients (both winter and summer submissions) will receive special recognition at the LIDMA fall meeting. Please remember the purpose of LIDMA, “The ultimate objective is to serve people better, to enhance the buying experience and efficiently get more life insurance protection in force for the families and businesses that need it.” We hope this Seal Process will help you find ways to do this more efficiently.
1. About Your Company
These important factors are required to ensure your solution is a valid ESIGN process protected under Federal and State Laws. Failure to meet the requirements in this section may increase legal risk by undermining the integrity of the electronic signature.
Details are needed for each requirement as well as status of the requirement – please indicate present status using the following: "Y" (Yes, In Production), "N" (N, Currently Not Supporting) or "D" (Development Underway). **Please note Production does not necessarily mean pilot, if presently piloting please use "P" **
2. The system provides an enforceable Consumer Disclosure process.
3. The system includes a process to show signer's intent to be bound.
4. Documents are presented during the signing process as they appear in paper format.
5. The system ensures that the documents have not been tampered with after the signing is completed.
6. The system provides the signer with a copy of the signed documents.
7. The system produces an audit trail after the signing is complete.
8. The audit trail provides evidence of authentication, consumer disclosure if given and time/date stamp of transaction.
9. The system provides for multiple signers to sign the same documents.
10. The system provides business rules to expire documents that haven't been completely signed after a specific period of time.
11. The system accommodates business rules to ensure In Good Order (IGO) documents.
12. Please upload any supporting documentation.
These important factors are recommended for an E-Solution receiving the LIDMA Seal of Approval. They assist both senders and signers to ensure they have all the proper equipment and knowledge of the process to result in high sender and signer adoption rates.
13. Does the signing process require any digital certificates, additional software, web plug-ins or hardware?
14. Which web browsers has your system been tested against?
15. Is your solution modular? Or is it embedded within a specific e-processing solution?
16. If modular, how does the sender prepare and deliver documents for electronic signing using your solution?
17. Does your system electronically transfer images, data or both to the carrier's systems?
18. Does your system support multiple forms in a single signing ceremony such as supplemental forms and illustrations?
19. Please upload any supporting documentation.
A well-designed process enabling the DM to authenticate signers and manage document workflow are recommended factors for an E-Solution receiving the LIDMA “Seal of Approval”.
20. What authentication method(s) are utilized by your solution?
21. How is the signer notified that the document(s) is available for electronic signature?
22. What process steps are taken by the signer to electronically sign documents using your solution?
23. If multiple signers are supported, does your solution provide for both serial and parallel routing to the multiple signers?
24. Does your solution allow for signers to add/edit data fields in the documents during the signing process?
25. If such client-side editing is supported, how is this managed within your solution so it does not impact the integrity of the electronically signed document?
26. Does your solution allow for the signer to opt out of electronically signing the documents? If so, how does the signer revert back to the traditional paper process?
27. Does your solution allow for the signer to decline to electronically sign the documents once the signing ceremony has begun? If so, how does the signer revert back to the traditional paper process?
28. Does your solution provide a way for the sender to void documents prior to completion of the electronic signature process?
29. Please upload any supporting documentation.
MINIMUM REQUIRED 2 – MUST BE GIVEN TO VALIDATE WORK FLOWS ARE IN PRODUCTION - 1 DM, 1 CARRIER
30. Reference #1
31. Reference #2
32. Reference #3
