Line of Business Manager

Line of Business (LOB) profiles are templates of coverages unique to a line of business and ACORD form. This section will guide you through how to create and manage line of business templates.

LOB profiles are templates that represent the various ways a policy is shown on an ACORD form. For example, imagine there exists an Umbrella policy with a policy limit of $5M, and an agency shows this policy three different ways on certificates, depending on the need of the request: one referencing $5M, one referencing $2M and one referencing $1M. Each of these entries is a LOB profile.

Once created, the required LOB profile can be added to a certificate within the Certificate Editor or COI Template Editor in order to display the policy and its coverages.

Within the LOB Manager, a user can create, edit, delete or deactivate an existing LOB profile from the manager or create a new one. Continue reading below to learn more.

 


Create a New LOB Profile

To create a new LOB Profile, click the orange "Create Profile" button.

In the modal that populates, start by selecting the applicable data from the fields on the left.

ACORD Form: Select the ACORD form the LOB profile is being built for.

Policy: Select the applicable policy.

If you see the policy you need, check the Policies Manager to make sure the policy is in the Certificate Hero system.

LOB Type: Based on the policy chosen in the step above, you will have a list of associated lines of businesses to select from. Most of the time, the system will select the appropriate LOB Type for you, and action is not needed in this field.

LOB Type Name: Enter the name for the policy - this is how the policy will be referenced on the ACORD form.

Profile Name: Enter a name for the profile - this is how the LOB profile will display in the LOB Profile Manager.

Certificate Hero will give each Profile a prefix showing the Year of the Policy Effective Date for ease of naming.

Set as Default: If needed, you can set this LOB profile as default. A default LOB profile is pulled through during contract parsing when a contract requires a line of business.

For example, if you create two GL profiles, "GL Main"(default) and "GL Extra Coverages", you start a certificate using a contract that required General Liability coverage, the "GL Main"(default) profile would auto-populate on the certificate editor because it was selected as the default LOB Profile.

 

Once you have completed the steps above, the LOB creator will expand and you will see the coverages and limits that have been pulled into the LOB Profile from the policy that was integrated or imported into Certificate Hero.

The view will differ depending on the ACORD form and line of business selected.

Below is an example of the ACORD 25 - Umbrella form:

Below is an example of the ACORD 25 - Auto form:

 

Regardless of the ACORD form or LOB type, the LOB Profile creator works the same. Any coverages Certificate Hero has mapped from the user's Agency Management System will pull through automatically.

The LOB Profile can be added to or removed from the Certificate Editor or COI Template Editor by clicking the "Add Policy" grey selector.

 

And once the LOB profile is added to the ACORD form, the primary coverages will populate in their applicable box on the ACORD form, and overflow policies and coverages will populate on the Certificate Hero 101 Policy Overflow page. 

Below is an example of the ACORD 25 - Umbrella policy:

Below is an example of the Certificate Hero 101 Policy Overflow page:

 


Edit an Existing LOB Profile

There may be times when the LOB Profile needs to be edited. Perhaps when the Umbrella policy $5M LOB Profile was created, someone inadvertently entered $4M instead. 

To edit an existing LOB Profile, click the "Actions" dropdown menu and select "Edit".

Within the LOB Editor, make the required change. When all changes are finished, click "Save" to save the changes.

 

You will be brought back to your LOB Profile Manager and those changes are now saved.

 


Delete a LOB Profile

There may also be times when a LOB Profile is no longer needed. For instances, a user might have inadvertently duplicated the $5M Umbrella LOB Profile and, depending on their user permissions, needs to delete the duplicate profile.

To delete an existing LOB Profile, click the "Actions" dropdown menu and select "Delete".

 

A modal will pop up asking you to confirm that you want to delete the LOB Profile. 

If clicked in error, click "Cancel" to return to the LOB Profile Manager.

To proceed with deleting the profile, click "Delete".

 

You will be brought back to the LOB Profile Manager and the deleted profile will no longer show.

 

Any certificate that had previously referenced the deleted LOB Profile will now flag during a revision to advise the user that the profile is no longer on the certificate, so the user can update to include the correct profile.

 


Deactivating a LOB Profile

There may also be times when a LOB Profile is no longer needed but an agency does not wish to fully delete the profile. Instead, a user can select to deactivate the profile, storing it in the LOB Profile Manager as inactive, in case it needs to be referenced for future use. For instances, imagine mid-term that a policy was cancelled, so the profile is no longer needed. But for historical purposes, an agency wishes to keep it inactive on file.

Note: If the LOB Profile is marked as default, the profile cannot be deactivated. An alternative profile of the same policy number would need to be selected as default to permit deactivation.

 

To deactivate an existing LOB Profile, click the "Actions" dropdown menu and select "Deactivate".

 

A modal will pop up asking you to confirm that you want to deactivate the LOB Profile. 

If clicked in error, click "Cancel" to return to the LOB Profile Manager.

To proceed with deactivating the profile, click "Yes, Deactivate".

 

You will be brought back to the LOB Profile Manager and the deactivated profile will no longer show.

 

Any certificate that had previously referenced the deactivated LOB Profile will now flag during a revision to advise the user that the profile is no longer on the certificate, so the user can update to include the new profile.