Every submission should build on what you already know about the insured.

Keep a durable entity record for the company behind the risk, then use that record when new submissions arrive instead of rebuilding identity and context from the beginning.

Northmere Foods Ltd.Private corporation
Active record
Industry
Food manufacturing
Province / Country
Ontario, Canada
Website
northmere.example
CRM reference
NMF-2048
An insured record showing the identity and business context available to underwriting.

Give the insured an identity that survives the transaction.

Company name, Entity type, Industry, location, website, and CRM reference belong to the insured record. They do not need to be reinterpreted as unrelated submissions move through the operation.

Recognizable identity
Search the register by company, industry, or CRM reference.
Editable business context
Maintain the supported entity details in one record as the relationship changes.
Stable reference
Use the entity identifier to connect underwriting work without merging it into the submission itself.
Company name
Northmere Foods Ltd.
Entity type
Private corporation
Industry
Food manufacturing
Province / Country
Ontario, Canada
Website
northmere.example
CRM reference
NMF-2048

Reuse the record while preserving the submission around it.

Submission Workbench can resolve and display the insured name from the selected entity record. The insured remains reusable, while each submission keeps its own product, evidence, pricing, status, and decision.

No duplicate identity work
New underwriting work starts from an established entity when one already exists.
Clear boundaries
The entity record and submission record remain connected without becoming the same object.
  1. Submission received

    Commercial property renewal

  2. Insured selected

    Existing entity record reused

  3. Record available

    Underwriting sees the established context

See how an insured record carries context into new business.