Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php on line 2858

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php on line 2862

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home1/rcfs/public_html/wp-content/plugins/revslider/includes/output.class.php on line 3708

Warning: Cannot modify header information - headers already sent by (output started at /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php:2858) in /home1/rcfs/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php:2858) in /home1/rcfs/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php:2858) in /home1/rcfs/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php:2858) in /home1/rcfs/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php:2858) in /home1/rcfs/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php:2858) in /home1/rcfs/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php:2858) in /home1/rcfs/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/rcfs/public_html/wp-content/plugins/revslider/includes/operations.class.php:2858) in /home1/rcfs/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":26459,"date":"2019-08-31T18:04:49","date_gmt":"2019-08-31T18:04:49","guid":{"rendered":"https:\/\/rolandcriss.com\/?p=26459"},"modified":"2019-12-30T11:21:27","modified_gmt":"2019-12-30T11:21:27","slug":"pursue-risk-assurance-backward","status":"publish","type":"post","link":"https:\/\/rolandcriss.com\/pursue-risk-assurance-backward\/","title":{"rendered":"Pursue Fiduciary Risk Assurance Backward"},"content":{"rendered":"

Tip for August 2019<\/span><\/strong><\/em><\/p>\n

We\u2019ve studied the effect that adoption of a regulatory risk management (\u201cRRM\u201d) system has on enterprises that sponsor ERISA plans.<\/strong><\/p>\n

The most effective benefit plan committees approach fiduciary risk based on the results sought, not derived from old methods with which they were most comfortable but are out of date.<\/p>\n

Simply, the best fiduciary risk management designs originate backward from the outcomes sought.<\/p>\n

\"\"<\/p>\n

There are two prevalent design approaches on which RRMs are constructed. We call them “Features Focused<\/em>” and “Results Focused<\/em>.” The former takes a passive approach, while the latter is a prudent proactive approach.<\/strong><\/p>\n[table \u201c31\u201d not found \/]
\n\n

Emerging results of plan designs appearing in lawsuits and regulators\u2019 enforcement reports reveal the imprudence of the Features Focused approach.<\/span><\/strong><\/p>\n

\n