Digital Transformation

What Digitizing an Insurance Application
Actually Takes

Jey Kumaresan
May 2026
13 min read

In 2016, the insurance application at Equitable Life was a paper form. By 2019, it was fully electronic: e-signature, FINTRAC-compliant identity verification, and a bilingual digital experience for advisors and clients across Canada. That transition took three years. Here is what it actually involved.

Starting point: not as simple as it looks

A paper insurance application is not just a form. It is a legal document, a compliance record, a data collection instrument, and a business process. When you digitize it, you are not just moving questions from paper to screen. You are re-examining every assumption baked into the paper version and deciding which ones survive the translation.

Some things that worked on paper do not work digitally. Handwritten signatures in wet ink have a different legal standing than e-signatures in some contexts. Certain disclosure obligations that were met by a physical form being handed to the client require rethinking when the client is filling out a form on a tablet in an advisor's office.

We spent the first four months of the program doing nothing but mapping the existing process: every question on the form, the regulatory obligation it served, the data destination in the policy administration system, and the downstream processes that depended on it. That map was the foundation for everything that followed.

3
Product divisions the platform was extended across after initial launch, each with different form requirements and compliance obligations.

The FINTRAC requirement

FINTRAC identity verification was the hardest compliance piece. The regulation requires that certain information be collected and verified before a policy is issued. In the paper world, the advisor collected this information and retained the records. In a digital world, you need a system that collects, verifies, and retains in a compliant way.

We evaluated three identity verification vendors before selecting one. The evaluation criteria went well beyond price: what data does the vendor retain? How does it integrate with our policy administration system? What happens if verification fails? What is the audit trail? Who is responsible for the regulatory obligation if the vendor's verification process has a defect?

That last question is the one most programs underestimate. When you outsource a compliance function, you do not outsource the regulatory obligation. You still own it. The vendor selection had to reflect that.

E-signature: not as simple as adding a button

Electronic signature legislation in Canada varies by province and by document type. Not all signatures that are legally valid in Ontario are valid in Quebec. Not all document types that can be e-signed are the same as paper originals in terms of evidentiary weight.

We brought external legal counsel into the e-signature workstream early. That was the right call. There were three document types in the application package where e-signature was not available as an option in all jurisdictions. Discovering that in testing rather than after launch saved us from a significant rollout problem.

E-signature is a legal question before it is a technology question. Get the legal analysis done early. The technology is the easy part.

User testing with advisors

Advisors are sophisticated users. They are also users who will not tell you something is confusing because they do not want to look confused. The testing methodology had to account for that.

We ran testing with advisors in their own offices, using real client scenarios. Not usability scripts. Real situations they recognized. The insights from those sessions were more useful than anything we got from structured testing in a lab environment.

The biggest finding: advisors did not read the screen in sequence. They skipped to fields they knew, filled those in, and then came back. The application had to be designed for non-linear completion. The paper form tolerated non-linear completion because you could flip between pages. The digital form did not tolerate it at all until we redesigned the navigation.

Bilingual delivery

The application was bilingual. Not translated. Bilingual. Those are not the same thing.

A translated form takes an English form and produces a French version. A bilingual form is designed from the start to work in both languages, with both languages tested with their respective user groups, and both versions maintained as equal-priority deliverables throughout the program.

We tested with French-speaking advisors in Quebec. The feedback was different from what we got in Ontario. Not in kind, but in emphasis. Things that were minor friction points in English were more significant friction points in French. The form design had to accommodate both.

Key takeaways
  • Map the existing process before you design the digital one. Every question on the form serves a purpose. Know what it is before you move it.
  • FINTRAC compliance requires system design, not just vendor selection. Understand who owns the regulatory obligation when a vendor is involved.
  • E-signature is a legal question before it is a technology question.
  • Advisors are non-linear users. Design for how they actually work, not how the process assumes they work.
  • Bilingual is not the same as translated. Test both versions with their actual user groups.

The platform launched in 2019 across individual insurance. By 2021 it had been extended to savings and group products. It is still running. The three years it took to build it properly were worth it. The programs I have seen try to do this in twelve months have not produced anything still running five years later.

JK
Jey Kumaresan, CBAP
Professor, Conestoga College · Former Product Owner, Equitable Life