Underwritten flows

The diagram below describes a quote and buy journey for a product that requires a standard rulebase, i.e. a rulebase that is positioned after the quote and policy creation stages of the journey.
The journey consists of the following steps:

create client (individual person or organization),
create quote (quote calculations for the price of policy),
create policy (creates policy in ‘application’ status),
underwriting (the outcome of underwriting is the application is accepted, declined, or various amendments to the quote can be made, e.g. exclusions or loadings),
if a payment has not been created, it is possible return to an already finished underwriting session,
create a payment,
complete policy (policy activated, client documentation and emails produced and sent).

Data capture underwritten flow

The diagram below describes a quote and buy journey for a product that requires a ‘data-capture’ rulebase, i.e. a rulebase that is positioned prior to the quote and policy creation stages of the journey, following a quick quote.

The journey consists of the following steps:

create client (individual person or organization),
create pre-quote (this is a very basic indicative quote, usually just one or two parameters selected),
underwriting (the outcome of underwriting is the application is accepted, declined, or various amendments to the quote can be made, e.g. exclusions or loadings),
if a payment has not been created, it is possible return to an already finished underwriting session,
create quote (quote calculations for the price of policy),
create policy (creates policy in ‘application’ status),
create a payment,
complete policy (policy activated, client documentation and emails produced and sent).

Simple MTA Flow

The diagram below describes an MTA journey for a product that does not require underwriting.
The journey consists of the following steps:

begin MTA process (get effective dates and quote parameters),
create new quote (quote calculations for the price of policy),
create new policy (creates policy in ‘application’ status),
calculate MTA price (based on the new parameters selected),
complete MTA policy (policy activated, client documentation and emails produced and sent).",

Underwritten MTA Flow

The diagram below describes an MTA journey for a product that requires a standard rulebase, i.e. a rulebase that is positioned after the quote and policy creation stages of the journey.

The journey consists of the following steps:

begin MTA process (get effective dates and quote parameters),
create new quote (quote calculations for the price of policy),
create new policy (creates policy in ‘application’ status),
underwriting (the outcome of underwriting is the application is accepted, declined, or various amendments to the quote can be made, e.g. exclusions or loadings),
calculate MTA price (based on the new parameters selected),
complete MTA policy (policy activated, client documentation and emails produced and sent).

Data Capture Underwritten MTA Flow

The diagram below describes an MTA journey for a product that requires a ‘data-capture’ rulebase, i.e. a rulebase that is positioned prior to the quote and policy creation stages of the journey, following a quick quote.

The journey consists of the following steps:

begin MTA process (get effective dates and quote parameters),
create new pre-quote,
underwriting (the outcome of underwriting is the application is accepted, declined, or various amendments to the quote can be made, e.g. exclusions or loadings),
create new quote (quote calculations for the price of policy),
create new policy (creates policy in ‘application’ status),
calculate MTA price (based on the new parameters selected),
complete MTA policy (policy activated, client documentation and emails produced and sent).