LIDMA eDelivery Evaluation Checklist

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 mobile data collection 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

Application
Due Date*

Review Process & Verification
of References

Seal
Announcements

Summer

August 15th

August 16 - September 15

Seal Approvals announced
LIDMA Annual Meeting

Winter

February 28th

March 1 - March 30

Seal Approvals announced
LIDMA Annual Meeting

*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

Requirements:

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 policy delivery solution.

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 solution is configured to satisfy legal and compliance requirements at a carrier and state level.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

3. The system allows a carrier to electronically deliver the policy directly to the policy owner.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

4. The system allows the DM to review/approve the policy before it is released for electronic delivery to the owner.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

5. The system allows the DM to review/approve the policy electronically, but elect to print the policy.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

6. The system notifies the DM that the policy is available for electronic delivery.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

7. The system provides an enforceable Consumer Disclosure process.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

8. The system includes a process to show signer's intent to be bound.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

9. Documents are presented during the signing process as they appear in paper format.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

10. The system ensures that the documents have not been tampered with after signing is completed.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

11. The system provides the signer with a copy of the policy and any delivery requirements.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

12. The system produces an audit trail after the signing is complete.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

13. The audit trail provides evidence of authentication, consumer disclosure if given and time/date stamp of transaction.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

14. The system allows for electronic collection of all signatures required to place a policy in effect.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

15. The system provides business rules to expire access to policies that have not been electronically accepted during the specified delivery period.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

16. The system provides a method for a carrier to void a policy prior to electronic acceptance by the owner.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

17. The system provides a method for the consumer to authorize electronic premium payment.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

18. The system allows for electronic completion and signature of all delivery requirements.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

19. The solution is configured at a carrier level to provide for the return of data and/or images documenting success or failure of the electronic policy delivery.

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

20. Please upload any supporting documentation. 

System Features:

These important factors are recommended for an E-Solution receiving the LIDMA Seal of Approval. A well-designed process enabling the DMs to authenticate participants, manage document workflow and multi-party communications will result in high sender and signer adoption rates.

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" **

21. Does your policy delivery process require any digital certificates, additional software, web plug-ins or hardware?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

22. Which web browsers has your system been tested against?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

23. Is your solution designed as a multi-carrier platform?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

24. What authentication method(s) are utilized by your solution?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

25. Does your system employ a proprietary e-signature process or is it integrated with a vendor's e-signature solution?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

26. Once electronic delivery of a policy has been completed, does your system continue to host the policy in a manner accessible to the DM and/or consumer? If yes, how long beyond the delivery date is the policy maintained?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

27. Does your solution allow for workflows to vary by DM?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

28. Does your solution allow for the carrier and/or DM to establish a different workflow for cases that have been Approved Other Than Applied (AOTA)?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

29. Does your platform allow for carrier/DM co-branding of emails and the consumer portal?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

30. Can the DM attach document(s) to be delivered to the policy owner along with the policy (e.g., cover letters, electronic business cards, referral requests)?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

31. When and how is the DM notified of the success or failure of the electronic policy delivery?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

32. What types of DM requests can be communicated to the carrier via your solution (e.g., policy corrections, delivery extensions, cancellations)?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

33. Can your solution allow for real-time modification of the policy by dynamically generating an amendment and collecting additional premium?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

34. What type of status and/or metrics reporting is available on the carrier or DM user interface?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

35. What type of standard or custom reporting can be accessed from the carrier or DM user interface?

  Y - Yes, In Production
  N - Currently Not Supporting
  D - Development Underway
  P - Presently Piloting

36. Please upload any supporting documentation.

References:

MINIMUM REQUIRED 2 – MUST BE GIVEN TO VALIDATE WORK FLOWS ARE IN PRODUCTION - 1 DM, 1 CARRIER

37. Reference #1

38. Reference #2

39. Reference #3

reload