Dysfunction at the California Fiduciaries Bureau

The California Department of Consumer Affairs Professional Fiduciaries Bureau (“DCAPFB”) has recently released, through its advisory committee, a 2013 Strategic Planning Session with attachments, which indicates great dysfunction within the DCAPFB, and which also includes a 2013 DCAPFB Environmental Scan Analysis.

The analysis includes interviews conducted with Advisory Committee Members of the DCAFFB, three separate online surveys for internal Department of Consumer Affairs (“DCA”) stakeholders, external stakeholders, and advocates of consumers, though Fiduciary Watch, Inc., was not asked to participate.  And, three separate online surveys for internal DCA stakeholders, external stakeholders and advocates of consumers, which the DCAPFB claims it planned to use as a discussion guide for the August 1, 2013, Fiduciary Bureau planning sessions of August 1, 2013, and August 2, 2013, which conveniently, the DCAPFB did not video tape, thereby preventing those who did not attend, including the California Pubic, and vulnerable California consumers, from knowing that licensing, not consumer protection, is first and foremost, at the DCAPFB.

Full Article and Source:
Dysfunction at the California Fiduciaries Bureau

Read the report:  Professional Fiduciaries Bureau Strategic Planning Session

3 Responses to “Dysfunction at the California Fiduciaries Bureau”

  1. Kenny Says:

    Fiduciary Watch is watching for sure!

  2. Thelma Says:

    So what else is new?

  3. Clarice Says:

    Thanks for all you do, NASGA and Fiduciary Watch!

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: