Portfolio

Insurance document management system

Insurance company achieves compliance with automated underwriting software

Influential Software helped an insurer meet industry regulations and streamline underwriting with a custom insurance document management system.

Contract representing insurance document management system

Executive brief

Custom insurance workflow automation

Our client is the London branch of one of the world’s largest insurance groups. The client engaged our intranet experts to provide a modern solution for its paper-based underwriting processes. This insurance document management system enabled the company to:

meet regulatory standards

accelerate binding processes

cut risk of manual error

boost underwriting productivity

Wondering how we developed this automated underwriting software? Read on for the full details.

The full story

Purple arrow encouraging readers to scroll down for the rest of the insurance document management system case study

The challenge

Paper processes caused regulatory issues

At the time of this project, the insurance group’s underwriting team was relying on paper-based documents. While this system had worked in the past, it was preventing the company from meeting higher industry standards. This meant that the insurer could not take on new clients and grow its business.

 

Besides being a barrier to growth, the paper-based process also had the following drawbacks:

 

  • limited ability to track and audit insurance binding and bundling
  • time-consuming and error-prone document management
  • low performance and satisfaction in the underwriting team

 

For these reasons, the company decided a new insurance document management system was urgently required.

The solution

Delivering insurance workflow automation

Having seen our web portal experience, the insurer contacted Influential to design a new insurance workflow solution. As the client was already familiar with SharePoint’s flexibility and security, we opted to develop the new system within SharePoint.

 

Our goal was to deliver a single-page application that would be suitable for non-technical users. The application would cover task management, data capture, management information, and reporting. Additional features included search functionality and archiving.

 

Breaking the software down further, it included six workflows to digitise the paper-based processes:

 

  • pre-bind bundle
  • post-bind bundle
  • issue policy bundle
  • pre-renewal bundle
  • post renewal bundle
  • service bundle

 

The components within the overall insurance document management system included:

 

Task management

This component used SharePoint tasks and workflow to automate the six insurance bundling processes. We set up custom email notifications to suit the company’s regulatory requirements.

 

Data entry

We built new data entry forms to allow staff to record data at various stages of the workflow.

 

Logging

We built a web service to capture events during the workflow timeline. These events were then written to the database for reference.

 

Database

We configured a database to store the logged events and reference data needed for management information.

 

Management information

We built dashboards to display KPI data related to the workflows, as well as enabling reporting on the data.

 

Once the build was complete, we then migrated the company’s underwriting data into the new system. We also provided in-depth software design and technical documentation.

The benefits

Underwriters equipped to grow

The main benefit of this project was enabling the company to meet regulatory standards. We achieved this and also gained buy-in from the underwriting team, who were happy to be freed from paper documents.

 

In fact, the automated underwriting software was so successful that it gained an award from the company’s chief operating officer.

 

The positive effects of the new insurance document management system were:

 

  • the ability to grow the business while meeting insurance regulations
  • faster and more accurate insurance binding and bundling processes
  • increased employee satisfaction among the underwriting personnel

Time for business automation?

We’re experts at digitising and automating complex business tasks. Find out more on our digital portals page.

Info

29th January 2021
document management, software development, intranet, SharePoint

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by Influential.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress, Intercom
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
intercom-id-[app_id],intercom-session-[add-id]