Published with an APP 11 context note and explicit limits on what a sharing workflow can establish or authorise.
Why this matters
Insurance documents can contain personal, financial and sensitive contextual information. OAIC guidance on APP 11 provides useful privacy context: organisations subject to the Privacy Act need to take reasonable steps to protect personal information. The exact obligations depend on the organisation and circumstances, but the operational lesson is simple: treat sharing as a specific action with a stated purpose, not as an invisible by-product of using a platform. That improves client understanding and gives broker teams a clearer handover to review.
Key points to carry into the work
- Name the broker contact or team role receiving the selected records and the stated insurance purpose.
- Let the client see the scope of a share rather than imply a permanent, unrestricted relationship with every record.
- Record the fact of the handover and its purpose without turning a consent screen into a legal conclusion.
- Use clear escalation paths when a client wants to ask a question, correct a record or limit what is shared.
- 01Name the purpose
- 02Select records
- 03Identify recipient
- 04Retain the handover
- 05Ask again when scope changes
Make a share understandable
Where Insia fits
Insia presents selected broker sharing as part of a connected policyholder and Broker Workspace story. Its public conversion journeys keep broker and policyholder paths distinct, with software supporting context and handovers rather than treating a client record as unrestricted brokerage data.
Keep the boundary clear. Insia does not create legal consent on behalf of a client, provide legal advice, grant a broker unrestricted access to records or replace the privacy and professional obligations that apply to the people and organisations involved.
Checklist
- Can the client understand the purpose of this specific share?
- Are the records selected rather than described as an open-ended collection?
- Is the recipient identifiable in language the client can recognise?
- Does the handover retain its stated purpose and date?
- Is there a clear route for questions, corrections or a new sharing request?
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 consent-led sharing?
It is a process that makes the purpose, recipient and selected records visible before information is shared in a broker workflow.
Does one share give a broker access to every record?
No. A clear sharing workflow should keep scope visible and avoid assuming a prior handover covers a new purpose or a different set of records.
Is a consent screen a legal opinion?
No. It supports clearer communication and record keeping. Legal and privacy obligations still depend on the organisation, circumstances and applicable law.
Why retain the sharing record?
It helps a later reviewer understand what was shared, why it was shared and what context supported the handover.
Can a client ask for clarification?
A responsible workflow should give clients a clear way to ask questions, correct a record or understand a new request before more information is shared.
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