Skip to content
Insia
Open menu
Resources
Trust and permissionsFor brokers and policyholders

Broker Consent Logs Explained for Policyholders

A practical explanation of what a broker-sharing consent record should show, how its scope changes and what it does not authorise.

Update note

Updated to separate sharing consent from advice and authority records, and to remove unsupported partner language.

Why this matters

Policyholders often need to share policy schedules, renewal notices, claim notes or certificates with a broker before renewal or quote review. Without a consent record, it can be hard to remember what was sent, which version was shared and whether access should still remain open. A useful receipt makes the decision legible later: it connects the selected records to a purpose, recipient and point in time. That context matters when a renewal ends, a new request begins or a policyholder wants to narrow access without erasing the earlier history.

Key points to carry into the work

  • Consent logs should make selected sharing visible to the policyholder.
  • The log should identify the record shared, recipient, date, purpose and current status.
  • Revocation or expiry should be easy to understand when supported by the workflow.
  • A consent log is administrative evidence, not a recommendation or advice record.
  • The purpose and scope should be understandable without reading a technical audit record.
  • A later change should preserve the earlier receipt instead of rewriting the history of what was agreed.
A visible sharing decision
  1. 01Choose the records
  2. 02Name the purpose
  3. 03Confirm the recipient
  4. 04Record the permission
  5. 05Preserve later changes

What a consent log should capture

Selected recordsList the policy records, documents or notes the policyholder chose to share.
Recipient detailsShow the authorised broker relationship or recipient connected to the sharing request.
Purpose and contextUse simple context such as renewal preparation, quote review, document request or new client onboarding.
Dates and statusRecord when access started, whether it is active, expired or revoked, and when changes occurred.
Source documentsKeep the policy schedule, renewal notice or other source file linked to the shared record.
Change historyPreserve when access was granted, narrowed, expired or revoked so the current state has an inspectable history.

Where Insia fits

Insia is designed around client-controlled, consent-led broker sharing. A policyholder can bring selected records into an authorised broker relationship so the broker receives structured context instead of an unexplained bundle of files.

Keep the boundary clear. Insia is not an insurer, broker, financial adviser, legal adviser or claims handler. A consent log helps record sharing activity; it does not provide personal financial advice or recommend which policy to choose.

Checklist

  • Check which records are being shared before granting access.
  • Confirm the broker recipient and purpose.
  • Keep renewal notices and policy schedules linked to the shared record.
  • Review active access when the renewal or quote review is complete.
  • Ask the broker, insurer or licensed adviser about decisions or advice needs.
  • Review whether the purpose is still current before extending access to a later workflow.
  • Keep consent evidence separate from the broker's advice, recommendation or service records.

Sources and scope

Sources support the external context in this guide. Current product capability and availability are explained on the linked Insia product page.

Common questions

What is a broker consent log?

It is a record showing what a policyholder shared with a broker, who received access, when it happened and whether access is active or changed.

Why is a consent log useful?

It helps policyholders see the document sharing trail instead of relying on memory or old email attachments.

Can I revoke broker access?

A consent-led workflow should make access status clear and preserve a revocation event. The practical effect can depend on records already lawfully held by a recipient and applicable obligations.

Does a consent log replace broker advice documents?

No. It records sharing activity. It is not a substitute for documents or advice a licensed broker or adviser may provide.

Does Insia choose which broker sees my records?

No. The policyholder selects the records and the authorised broker relationship. Insia records and applies that scoped sharing choice.

Is consent the same as a broker authority or advice record?

No. A sharing receipt records a permission and its scope. Broker authorities, advice documents and other regulated records have their own purposes and requirements.

Put the context to work

Turn this evidence task into a visible case.

Discuss how the evidence, requirements and human decisions in this guide could become a reviewable Compliance Case Manager workflow. This starts a product conversation and does not guarantee pilot access.

Discuss Compliance Case Manager
Register Compliance interest