Classic deliverables core concepts

BriteCore’s Classic deliverables include numerous stock deliverables and enables custom deliverables that have the same look and feel as stock deliverables, but can be customized using HTML/Jinja. You can also fully customize a document.

Core concepts

  • Attachments: The BriteCore module where generated documents and uploaded files are stored. Deliverables generated by BriteCore are stored in Attachments automatically. Other files can be uploaded by policyholders, agents, and carrier users, and stored in this module.
  • Date Added: The date a deliverable was added to the Attachments tab. This date typically matches the transaction date.
  • Deliverable: A deliverable is any document produced by BriteCore as a part of the quote/policy/claim lifecycle. BriteCore has standard deliverables a carrier can use. They can also add their logo and other carrier-specific fields. All deliverables are built in Settings > Deliverables. When a deliverable is produced on an individual contact, policy or claim, the deliverable is stored in Attachments.
  • Effective Date: The date an insurance policy becomes active.
  • Jinja: Jinja is an open source templating language used to build custom and deliverables.
  • Print Date: The date adeliverable is scheduled to print, not the date the deliverable printed.
  • Stock vs. custom: Deliverables can be built using a default structure or a custom template:
    • Stock deliverables: A set of documents that BriteCore provides out of the box. They are semi-customizable and produced automatically by a trigger event in BriteCore as part of a workflow, such as issuing a policy.
    • Custom deliverables: Custom deliverables allow a user to create documents that cover use cases not covered by the stock deliverables using HTML/Jinja. Jinja is an open source templating language used to build custom and deliverables.
    • Deliverables: Written in HTML/CSS/Jinja, these documents are completely customizable.
  • Transaction: A point-in-time action that results in a document exchange among parties, such as agents, insureds, or underwriters.
  • Transaction Date: The date a transaction took place. For policies, this is also known as the Commit Date.