BriteCore offers a variety of deliverables for client use.

Core Concepts

Deliverable

Any document produced by BriteCore.

Attachments

The name of the tab on each contact, policy, and claim where deliverables are stored.

A deliverable may have the following print states.

Print state Typically set by Purpose
To be determined (tbd) BriteCore Indicates the deliverable will print
Email, but do not print BriteCore Indicates the deliverable will email
Printed BriteCore Indicates the deliverable printed
Not mailed User Indicates the deliverable printed but was not mailed
Void User Removes the deliverable from the screen
Use only if the deliverable should have never existed
Do not print or email User Keeps a deliverable from printing or emailing
Use only with deliverables that have yet to print (tbd) or email
Transferred BriteCore Indicates the Return Premium Notice was transferred
Used with the On rewrite, automatically transfer return premium to the newly rewritten policy setting

Dates

The Attachments tab contains important dates related to deliverables.

Transaction Date

The date a user made the change. For policies, this is also known as the commit date.

Effective Date

The date the change is effective.

Date Added

The date the deliverable was added to the Attachments tab. This date typically matches the transaction date.

The date the deliverable is scheduled to print, not the date the deliverable printed.

When a deliverable is added to a policy or claim, whether by a user or the system, the title of the folder and file will reflect the transaction date. The exceptions are the Declaration and Billing Statements, which will have the effective date.

Example

The above example is a 7/1/2016 effective policy issued on 5/24/16. 7/1/2016 is the effective date, and 5/24/16 is the transaction date.

Transaction Date and Effective Date

  • The Declaration matches the policy effective date of 7/1/16 even though the transaction date is 5/24/16
  • The invoice matches the effective invoice date according to settings. This carrier bills policies 35 days in advance of the policy effective date. As such, 5/27/16 is the invoice's effective date even though the transaction date is 5/24/16

Date Added
All documents were added to the Attachments tab on 5/24/16.

Print Date
The Declaration and invoice print together, scheduled on 5/27/16 according to the carrier's settings.

Organization

Within a policy or claim, deliverables are organized in folders by type, transaction, or effective date, and then recipient. The below Declaration example illustrates this concept in a tree view and assumes no mortgagee on the policy:

  • Declaration folder
    • 12-01-2017 - Declaration
      • 12-01-2017 - Declaration - John Smith
      • 12-01-2017 - Declaration - Agency
    • 08-01-2017 - Declaration
      • 08-01-2017 - Declaration - John Smith
      • 08-01-2017 - Declaration - Agency
    • 05-01-2017 - Declaration
      • 05-01-2017 - Declaration - John Smith
      • 05-01-2017 - Declaration - Agency

HTML Tags

Tags allow data to be pulled onto a deliverable dynamically and include

{adjuster}
{adjuster_phone}
{agency}
{agent}
{agent_phone}
{agency_phone}
{amount_due}
{app_id} {auto_rewrite_message} if automatic rewrite setting is enabled
{billing_schedule}
{cancellation_date} references revisions.cancelDate if one exists; otherwise revisions.revisionDate
{cancellation_reason}
{claim_number}
{due_date} returns the due date of the invoice less your grace period setting (Display Due Date on Invoices As Day)
{effective_date}
{expiration_date}
{current_expiration_date} returns the closest expiration date to today
{insured}
{insured_address}
{insured_phone}
{insured_properties}
{last_nonpay_due_date} returns the date the invoice went into non-pay
{last_nonpay_cancel_date}
{last_payment_date}
{last_payment_amount}
{late_payment_fee}
{loss_date}
{mortgagee}
{nonrenew_reason}
{nonrenew_description}
{past_due}
{payoff_amount}
{policy_status}
{policy_type}
{policy_number}
{print_description}
{premium}
{reinstatement_date}
{return_premium_reason}
{todays_date}
{inception_date}

Certified Mail

Deliverables sent via certified mail will appear on the Certificate of Mailing report the day they print. Learn more about the Certificate of Mailing.

Triggerable Events

The table below summarizes what action and by whom leads to the generation of a deliverable.

Deliverable Action and initiator
Declaration Commit revision (admin user or system)
Initial Billing Statement Commit revision on a new business policy (admin user)
Change billing schedule (admin user)
Edit and Reprint an invoice (admin user)
Renewal Billing Statement Commit revision on a renewal policy (admin user or system)
Change billing schedule (admin user)
Edit and Reprint an invoice (admin user)
Installment Billing Statement Commit revision on a policy with an installment billing schedule (admin user or system)
Change billing schedule (admin user)
Edit and Reprint an invoice (admin user)
Amended Billing Statement Commit endorsement revision with premium increase (admin user)
Notice of Non-Renewal Set policy to Non-Renewal then notification date comes to pass (admin user then system)
Notice of Cancellation Click Cancel Policy button (admin user)
Notice of Cancellation Non-Payment of Premium Invoice due date comes to pass and amount due is above cancellation threshold (system)
Confirmation of Cancellation Cancel date comes to pass (system)
Notice of Reinstatement Click Reinstate Policy button (admin user)
Claim Acknowledgment Letter Set claim to Open, Standard (admin user)
Pre-Authorized Payment Schedule Set up policy on auto pay (admin user then system)
Return Premium Notice Cancel date comes to pass (system)
Click Cancel Policy button and cancel policy (admin user)
Quote Summary Click Print Quote Summary button (agent)
Policy Application Click Print Application button (agent)
Click Submit Application button (agent)
Continuation of Coverage - Non-Pay Payment is received against a policy in cancellation pending for non-pay (user)
Continuation of Coverage - Other Click Reinstate Policy button when a policy is in cancellation pending (admin user)
Reminder Notice - Renewal Billing Offer Sent in place of the notice of cancellation for non-pay when the invoice due date is reached (system)
Combined Billing Statement Policies are linked and invoices for those policies print on the same date (system)
Insured Letter Click Custom Deliverable button on a policy (admin user)
Loss Notice Click Custom Deliverable button on a claim (admin user)
Notification of Property Reinsurance loss Click Custom Deliverable button on a claim (admin user)
Insurance Scoring Notification Click Custom Deliverable button on a policy (admin user)
Other Custom Built Deliverables Click Custom Deliverable button on a policy (admin user)
Deliverable prints with initial or renewal Declaration (system)

BriteCore Setup

A variety of settings provide some customization of stock deliverables.

Settings > Modules > BriteQuote > Options

Allow Agents/Agencies to Create Certain Deliverables

When checked this settings allows identified deliverables to be generated by agents. See the Allow Agent Deliverable Generation how-to below.

Settings > Deliverables > Graphics

Upload a company logo and signature graphic. Click the magnifying glass for suggestions on optimizing the graphics.

Settings > Deliverables > Header Information

Add your company name, address, phone number, and email in the upper-right of stock deliverables.

Basic HTML tags are supported. For example, <font size="12"><b>Mutual Insurance Company</b></font size>.

Settings > Deliverables > Agent/Agency Display on Deliverables

Display

If agencies are attached to policies in Settings > Modules > Policies > Contacts, only agency contact information can be displayed on the Declaration. However, if agents are attached to policies, the option to display both the agent and agency contact information is available.

Include Both Agent Copy and Insured Copy of Deliverables in Agent Emails

Recall that agencies can receive emails via two different methods.

Method 1

An individual email by policy, sent from Policies > Processing > Pending Email.

Method 2

One email to the agency of all policies using the Send Daily "Print List" Email setting that appears on the individual agency contact.

This setting applies only to method 1 and, when checked, emails the agent and insured copies to the agent or agency.

Best practice indicates that clients should use Method 2 above. As such, this setting is no longer recommended for use.

Settings > Deliverables > Options

Add Primary Insured's Phone Number to All Deliverable Copies

When checked, displays the named insured's phone number in the Named Insured(s) box of the deliverable header.

Add Primary Insured's Mailing Address to All Deliverable Copies

When checked, displays the primary named insured's address in the Named Insured(s) box of the deliverable header.

Show Form Descriptions on Declarations, Quote Summaries, and Policy Applications

See the form appearance documentation.

If Fees Total $0, Omit the Total on the Declaration, Quote Summary, and Policy Application

By default, a total fees line item appears on the Declaration, Quote Summary, and Policy Application. When checked, this setting hides the fee line item when it equals $0. To view the fee line item, access a sample Declaration below.

Embolden the Policy/Quote ID on Declaration, Quote Summary, and Policy Application

When checked, the policy number or quote ID is formatted in bold.


Database Only

Policy_Type_Items.DecAliases

By default, rate categories associated with a line item appear under the Rating Information section of a Declaration, Quote Summary, or Policy Application, which is typically on page two. With decAliases, rate category values can appear prominently on the first page with the associated line item. Engineers may reference PR 4586. Complete the following steps:

  1. Locate the desired line item in the policy_type_items table
  2. The decAliases column for the line item takes a JSON dictionary with two keys: item_alias and category_aliases. Update the dictionary using this format
    {"category_aliases": {"Category 1": "cat1"},  
    "input_aliases": {"User Input": "input1"},  
    "item_alias": "A python formatted str. {cat1} {input1}"}

Example

The example pictured below displays the result of the following decAliases for the coverage A. Building:

{"category_aliases": {"Loss Settlement, Building": "cat1"},
"input_aliases": {"Risk Description": "input1"},
"item_alias": "A. Building - {cat1}, {input1}"}

Show-Change-Of-Address-On-All-Invoices

When enabled, the Change of Address section will appear at the end of both Initial and Renewal Billing Statements. When disabled, the Change of Address section will appear on Installment Billing Statements only.

To enable, run UPDATE settings SET value=1 WHERE option='show-change-of-address-all-invoices'


Deliverable Types

Deliverables can be built using a default structure or a custom template and can be divided into two categories:

  • Stock deliverables are semi-customizable and produced automatically by BriteCore via a process (e.g., issuing a policy)
  • Custom deliverables are fully customizable and either produced by a user or replace a stock deliverable

Stock Deliverables

Custom Deliverables

Standard with Your BriteCore Site

  • Insured Letter can be used for any communication with the insured
  • Loss Notice is sent to adjusters, along with the most recent version of the Declaration (must be enabled when setting up the deliverable), for efficient claim processing
  • Insurance Scoring Notification is used with a credit scoring vendor. For that reason, see the ISO Credit Scoring documentation
  • Notification of Property Reinsurance Loss is used to notify your reinsurer of the claim transaction history

Deliverables we recommend you build

Overwrite Stock Deliverables

Though stock deliverables come standard with your BriteCore site, those deliverables may be customized. See the Customize a Stock Deliverable how-to below.

Settings

Custom deliverables have the following settings.

This Is a Policies/Claims Deliverable

Allows you to associate the deliverable with either policies or claims.

Will print the deliverable with new business Declarations.

Will print the deliverable with renewal business Declarations.

This setting appears if either of the two settings above are checked. When selected, the custom deliverable will print with either the initial or renewal Declarations or both when Payment Method on the Accounts Receivable screen of the policy is Manual Pay.

A specific use case for this setting is the Direct Debit Letter. Use this setting to mail the Direct Debit Letter custom deliverable to insureds who are not currently on auto pay in an effort to incentivize them to auto pay.

Built in HTML/CSS

All custom deliverables are built using HTML and CSS.

Requires User Input (Will be Gathered at Generation)

Requires the staff member who generated the deliverable to type information specific to that policy or claim.

Requires E-Signature

Requires the agent and insureds to electronically sign the deliverable as part of the submittal process.

The HelloSign vendor must be enabled to use this setting.


How-Tos

Manage Print States of Deliverables
Customize a Stock Deliverable
Add an OCR Code to a Custom Deliverable
Modify a Custom Deliverable on Multiple States Within the Database
Allow Agent Deliverable Generation
Manually Create a Render.py Deliverable on a Policy
Remove an Unwanted Deliverable from the Screen

Manage Print States of Deliverables

Individual Policy or Claim

  1. Navigate to a policy or claim's Attachments tab
  2. Locate the file(s) in question
  3. Click on the row(s) you want to update. Ensure you click on the whitespace of the row and not the deliverable title
  4. Click the Print State button
  5. Select the appropriate print state
  6. Click OK

Policies > Processing > Pending Email

This queue allows you to manage print states across all policies.

General Functionality

The date the deliverable appears in the queue is the scheduled print date and not the actual print date. If a document is scheduled to print today but does not print until tomorrow, the deliverable will be in today’s queue.

Before the Deliverable Is Printed or Emailed

A copy of the deliverable to print will be in the tab with a print state of to be determined and an email state of do not email.

The email version will have a print state of to be determined and an email state of to be emailed.

After the Deliverable Is Printed or Emailed

A copy of the deliverable that printed will be in the tab with a print state of printed and an email state of do not email.

When Send All Pending Email is clicked, the email version will have a print state of printed and an email state of emailed.

For sites that send summary emails to agents in the Cron (Send Daily "Print List" Email setting on agency contacts), the Send All Pending Email is never clicked and the email deliverables retain a status of to be emailed.

Using the Red X

Regardless of whether the deliverable printed or was emailed, clicking the red X

  • Removes the deliverable from the Pending email box
  • Retains the deliverable in the policy’s Attachments tab but changes the print state to Do Not Print or Email

Customize a Stock Deliverable

Customizing stock deliverables is a feature available to users skilled in HTML, CSS, and Jinja templating.

Standard Option

Customizable but less flexibility. Complete the following steps:

  1. Navigate to Settings > Deliverables
  2. Select a state if you write in more than one
  3. Identify the name of the stock deliverable you would like to overwrite
  4. Scroll to Custom Deliverables section
  5. Click + once
  6. Scroll to the bottom of the section
  7. Click the pencil next to the New Custom Deliverable
  8. Name the custom deliverable the exact same as the stock deliverable to be overwritten
  9. Check the Built in HTML/CSS box
  10. Check other desired settings
  11. Build the report
  12. Copy and retain the deliverableId= UUID from the custom deliverable's URL
  13. Click Save
  14. Insert the deliverableId= UUID as the id in the update statement then run, or have IWS run, #UPDATE x_report_locations SET overwriteStock=1 WHERE id=''

Advanced Option

Fully customizable with powerful tools, render.py is a standalone class for rendering context-aware HTML inside of BriteCore. Its primary purpose is to allow for better Jinja deliverable templates. Engineers with code access should read PR 3898.

A new function, Get_Policy_System_Tags, has been added to render.py that allows users to pull system tags into deliverables.

To use render.py, complete the following steps:

  1. Run
    UPDATE settings SET value=1 WHERE option= 'render_enabled';
  2. Navigate to Settings > Deliverables
  3. If you write in more than one state, select the appropriate state
  4. Scroll to the Custom Deliverables section
  5. Click Add a Custom Template
  6. Click Add a New Template
  7. Complete the prompts
  8. Click Save Changes. You will then be directed to the in-browser Ace editor
    • Templates are saved to the html_template database table
  9. To see the list of exposed methods
    • Enter {{ get_available_function_names() }} into the editor
    • Click Preview HMTL in the top-right of the screen
  10. Build your report using HMTL, CSS, and Jinja. Updates save automatically

Buttons in the top-right of the screen allow you to

  • Return to the template list
  • Preview your work in HTML
  • Preview your work as a PDF
  • Update the settings for the current project

Add an OCR Code to a Custom Deliverable

Stock billing statement deliverables have an OCR code for use with scanning devices. The OCR code contains the policy number and amount due. With custom billing statements built in HTML/CSS, an OCR code may be added by calling get_ocr_code(), and then placing it anywhere on the custom deliverable:

  1. Navigate to Settings > Deliverables
  2. Create the custom deliverable using HTML/CSS
  3. At the top of the Text Area enter {% set ocr_code = get_ocr_code() %}
  4. Place the below code wherever the OCR code should appear (generally at the bottom of the deliverable)
    {{ ocr_code }}

Modify a Custom Deliverable on Multiple States Within the Database

The deliverable name and settings appear in x_report_locations. The content of deliverable appears in report_flow where x_report_locations.id = report_flow.reportId.

Select Statement

Update the customName to the deliverable name in question, and then run

SELECT t1.name, t1.customName, report_flow.* FROM
(SELECT business_locations.name, x_report_locations.id, customName FROM x_report_locations
JOIN business_locations ON business_locations.id = x_report_locations.locationId
WHERE customName = 'Notice') AS t1
JOIN report_flow ON report_flow.reportId = t1.id

Update the contient in the value column.

Update Statement

This update statement should be used with caution:

  1. Build the deliverable as you want it to appear within one state
  2. Copy the wording into a text document in case an error occurs in this process
  3. Run the select statement above
  4. Right click on the rows that have the correct wording
  5. Select Copy SQL INSERT
  6. Paste the copy into a text document or into the MySQL query field
  7. Locate and copy the information for the value column
  8. Copy the value information into the value section, update the customName, and then run
    #UPDATE report_flow JOIN x_report_locations ON  
    x_report_locations.id = report_flow.reportId SET value = 
    'insert desired value here' WHERE customName = 'Notice';

Consider adding to the where clause to update one deliverable only before updating the deliverable across all states (and 'report_flow'.'id'= "specific UUID").

Allow Agent Deliverable Generation

The video just below details how to setup this feature. Text instructions are provided just below the video.

  1. Navigate to Settings > Modules > BritQuote > Options
  2. Check Allow agents/agencies to create certain deliverables
  3. Scroll to the top of the page
  4. Click Save
  5. Navigate to Settings > Deliverables
  6. Scroll to the Custom Deliverables section
  7. Identify the desired custom deliverable
  8. Click the pencil
  9. Locate the Options section
  10. Check Allow agents/agencies to generate this deliverable in BriteQuote
  11. Click Save

Important notes

  • Agents may only generate deliverables on unsubmitted quotes or applications
  • This feature is only available for Custom Deliverables that do not use the Requires User Input setting
  • The primary use case for this feature is for agents to generate and print the Insured Scoring Notification prior to application submission
  • Once generated by an agent, the deliverable appears in the Attachments tab of the quote or application within a folder by the deliverable's name
  • Staff have access to the deliverable in the Attachments tab of the policy within the Administrative Portal once the deliverable is generated by the agent
  • The print state of the generated deliverable is automatically set to printed

Manually Create a Render.py Deliverable on a Policy

  1. Create a deliverable using render.py via the Customize a Stock Deliverable how-to
  2. Update the deliverable name in the below statement, and then run
    #UPDATE html_template SET showAsCustomDeliverable=1 WHERE name='name of deliverable'
  3. Navigate to a policy
  4. Click Custom Deliverable

Remove an Unwanted Deliverable from the Screen

  1. Access the policy
  2. Click Attachments
  3. Locate the deliverable file
  4. Click on the white space in the deliverable's row rather than on the deliverable name
  5. Click Print State
  6. Select Void
  7. Click OK

FAQs

Policies > Processing > Pending Email

Can emails be sent for selected days in Policies > Processing > Pending Email?
Yes.

If agencies have the Send Daily "Print List" Email setting enabled, do I need to send email from Policies > Processing > Pending Email?
No. If you send emails from Policies > Processing > Pending Email, agencies will receive duplicate copies of deliverables.

If I change the print state of an Email, but Do Not Print deliverable to Void or Do Not Print or Email, will the deliverable still get emailed to the agency when I click Send All Pending Email from Policies > Processing > Pending Email?
No.


Feedback

Report unclear or missing documentation.