Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the fl-builder domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uabb domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Warning: Cannot modify header information - headers already sent by (output started at /home/bailey/public_html/wp-includes/functions.php:6131) in /home/bailey/public_html/wp-content/themes/robintek-child-theme/functions.php on line 48

Warning: Cannot modify header information - headers already sent by (output started at /home/bailey/public_html/wp-includes/functions.php:6131) in /home/bailey/public_html/wp-content/themes/robintek-child-theme/functions.php on line 49

Warning: Cannot modify header information - headers already sent by (output started at /home/bailey/public_html/wp-includes/functions.php:6131) in /home/bailey/public_html/wp-content/themes/robintek-child-theme/functions.php on line 50

Deprecated: Function WP_Dependencies->add_data() was called with an argument that is deprecated since version 6.9.0! IE conditional comments are ignored by all supported browsers. in /home/bailey/public_html/wp-includes/functions.php on line 6131
An Important New Asset Protection Tool: The Ohio Legacy Trust Act - Bailey Cavalieri

An Important New Asset Protection Tool: The Ohio Legacy Trust Act

Ohio House Bill 479, which was recently signed into law by Governor Kasich, permits the creation of a new type of trust in Ohio, the “Legacy Trust”, allowing an individual to more effectively shield assets from future creditors.
Historically, if you created an Ohio Trust for your own benefit (e.g., retaining the right to income and/or principal), your creditors could reach the Trust assets. As of March 27, 2013, you may create a Legacy Trust for your own benefit and protect the assets of the Trust from the reach of future creditors. This can be an important planning tool, especially for professionals who have a significant amount of exposure to potential liability (e.g., accountants, attorneys, doctors, dentists, chiropractors, professional athletes, etc.). Additionally, this type of creditor protection could also be beneficial for individuals who would like to insulate assets from future medical expenses. A Legacy Trust could also limit the exposure of assets to a potential property distribution, spousal support order, or child support award in a divorce, as long as the Trust is put in place prior to marriage. This type of planning could be paired with, or even take the place of, a prenuptial agreement.There are some limitations on the grantor’s personal use of assets transferred to a Legacy Trust. The grantor may continue to have access to (1) the current income produced by the Legacy Trust assets and (2) principal distributed at the trustee’s discretion or under a distribution standard. The Legacy Trust assets could also be used to pay any income tax obligations attributed to the Trust assets, as well as to pay debts, expenses, and/or taxes of the grantor’s Estate after his or her death. The Legacy Trust must have a third party trustee serve over the Trust at all times, but the grantor may retain the power to remove and replace the third party trustee at any time.

It is important to understand that the Legacy Trust cannot protect you from all creditors. To be effective, the proper planning of many issues involved in the implementation of a Legacy Trust is essential. Those who plan ahead and strategically use a Legacy Trust as part of their estate plan will benefit; not those who wait — it is important to plan before any type of creditor protection is necessary.

Authors
Robert Dunn
Member
Harlan Louis
Member
David Onega
Member
Service Affiliation
Share
Scroll to Top