Terms and Conditions

To complete your login to CLIEDIS, please agree to the Terms and Conditions below.

Don't have a CLIEDIS member ID yet? Register Now
Back to all news and events

2025 Annual DAWG Meeting

Event Information

Date: April 1 2025 08:00 - 16:00 ET
For: Members
Location: Vantage Venues: 150 King ST W, Toronto ON, 16th Floor

Overview

REGISTRATION CLOSED

 

FAWG rolls out and the DAWG comes in

FAWG (Feed Adoption Working Group) will now be DAWG (Data Adoption Working Group).

 

DAWG: a slang term used to denote friendship, camaraderie or solidarity

FAWG, established as a forum for distributors to work through issues preventing feed adoption, has morphed from its original intention. We are no longer just about feeds, but about data, APIs included. The conversations between carriers and distributors have taken central stage.  More and more carrier members attend so that they can meet their customers and hear first-hand their experience. Distributors and vendors want to have those conversations. There’s a lot to say. Our members want to understand how the data is used, how business processes are impacted, and how to best serve the needs. They want to learn from each other.

 

We are reinventing this session to focus on those conversations. We will reach out to you in January to help us in setting the agenda for April.

 

In the meantime, we will try to not inundate you with bad puns.

 

Eligible Participants

You must be a CLIEDIS member to attend the meeting.

 

Due to space considerations we may need to limit the number of representatives per company. You will be notified if we face that situation.

 

There is no cost to attend this session.

 


This event is open to CLIEDIS members.

Please login below to attend.
IF YOUR COMPANY IS A CLIEDIS MEMBER AND YOU DO NOT HAVE AN LOGIN ID, register here.
Registration Fee: $00 CAD
Registration Fee: $00 CAD

Pay By Credit Card

Registration Fee: $00 CAD

Send Me An Invoice

If you have been given a promo code, please apply it below.
The CVV security code is a number that provides extra security to credit card holders.

Here's where you can find the CVV on different credit card types:
CVV

THANK YOU FOR REGISTERING FOR THIS EVENT.

AN EMAIL WITH INFORMATION ABOUT THE EVENT WILL BE SENT TO YOU SHORTLY.

THANK YOU FOR REGISTERING FOR THIS EVENT.

AN EMAIL WITH INFORMATION ABOUT THE EVENT WILL BE SENT TO YOU SHORTLY.

A RECEIPT FOR YOUR PAYMENT WILL BE SENT TO YOU SEPARATELY.

THANK YOU FOR REGISTERING FOR THIS EVENT.

AN EMAIL WITH INFORMATION ABOUT THE EVENT WILL BE SENT TO YOU SHORTLY.

AN INVOICE WILL BE SENT TO YOU SEPARATELY.

Materials

This file is only accessible to members Register

Agenda

Time:

Full session: 08:00 – 13:00

Customer meetings: 13:00-16:00

Overview of Day:

  • 8-9am Breakfast
  • 9-12pm Full Meeting
  • 12-1pm Lunch and one-on-one carrier-distributor meetups as needed
  • 1-4pm Vendor Customer Meetings
    • Equisoft and iPipeline are confirmed. They will communicate details directly with their customers.

 

Distributors and Carriers – please let us know who you hope to meet with in a one-on-one session while there.

 

For the morning session, topics to date include (not necessarily in this order):

  • Implementation progress reporting
  • Refresher for understanding what is in each of the carrier feeds
  • Getting Value from Feeds – Roundtable discussion
    • How to bring value to advisors
    • Business process changes, staffing impacted by feeds
    • How data is used
    • Differences in system capabilities
    • Challenges implementing
  • How to help distributors with feed management
    • What information can carriers provide to make the process easier
    • How to communicate – changes, issues, availability, gaps, etc. What is critical to know?
  • Status of APIs, review of roadmap priorities
  • Preparing for API implementation
    • Heather LeBlanc, Financial Horizons to present
    • Key learnings from initial implementation
      • Change Management, operations processes impact
      • Need for consistency in data and behavior
    • How to prepare for impact of APIs in advance