Deprecated: Optional parameter $content declared before required parameter $post is implicitly treated as a required parameter in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/functions.php on line 840

Deprecated: Creation of dynamic property wpdb::$categories is deprecated in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/wp-db.php on line 668

Deprecated: Creation of dynamic property wpdb::$post2cat is deprecated in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/wp-db.php on line 668

Deprecated: Creation of dynamic property wpdb::$link2cat is deprecated in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/wp-db.php on line 668

Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-theme.php on line 553

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-theme.php on line 594

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-theme.php on line 534

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-theme.php on line 543

Warning: Private methods cannot be final as they are never overridden by other classes in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-session-tokens.php on line 69

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/comment-template.php on line 1720

Deprecated: Optional parameter $object_id declared before required parameter $taxonomy is implicitly treated as a required parameter in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/nav-menu.php on line 1060

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 934

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 954

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 966

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 977

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/class-wp-block-list.php on line 199

Deprecated: Optional parameter $block_name declared before required parameter $block_content is implicitly treated as a required parameter in /home/devfl9/wls.dev.fl9.uk/public_html/wp-includes/blocks.php on line 405

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/devfl9/wls.dev.fl9.uk/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 942

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/devfl9/wls.dev.fl9.uk/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 942

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/devfl9/wls.dev.fl9.uk/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 1498

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/devfl9/wls.dev.fl9.uk/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 2207

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/devfl9/wls.dev.fl9.uk/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 2992

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/devfl9/wls.dev.fl9.uk/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 2998

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/devfl9/wls.dev.fl9.uk/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 3116
Protective Property Trust - Wills & Legal Services
01885 490 380

Protective Property Trust

A major concern for many people is that their home may be used to fund care costs in later life. This may happen if you have just made a simple mirror Will. On first death, your home will default to the survivor. If the survivor then goes into care and no other assets are available to fund care costs, the Local Authority will means-test 100% of the property value and may request sale of the property. A Protective Property Trust (PPT) can help you protect your share of the home and ensure that it is passed on to the people you care about.

Care costs range from £750 – £1200 per week. A PPT can protect your share of the property from being used to fund care home fees.

If you die and your partner were to remarry, your children’s inheritance could pass to a stranger’s family. This is known as sideways disinheritance. A PPT will protect your share of the property, keeping it in the bloodline

Most people own their property jointly as Beneficial Joint Tenants, meaning that typically the house passes to their spouse on first death and to their children or beneficiaries on second death.

A PPT has to be created whilst both partners are alive. The joint tenancy of the property is severed, meaning that Mr and Mrs will then own 50% of the property each, known as ‘Tenants in Common’.

Following this procedure, we will then create a new Will with the PPT incorporated, meaning that upon 1st death, instead of leaving the share of the property to the surviving spouse, their half will be held in trust for the beneficiaries (usually the children) of the Will. Therefore if they go into care, the Local Authority can only means-test the other 50% of the property value. The surviving spouse has a ‘life interest’ or ‘right of occupancy’ and can live in the property for life or substitute it for another one.

With average residential care fees often well in excess of £750 per week, it does not take long to erode the value of your estate. Currently, anyone with assets above £23,250 in England and £50,000 in Wales may not receive state help with care costs, meaning that many families would have to sell their home to fund care. If a PPT has been established, then half the value of the property is automatically protected on first death and the deceased’s share will not be used to fund care costs for the survivor.

Yes. If the surviving partner remarries, the deceased’s part of the Will cannot be changed, thereby protecting the beneficiaries’ inheritance by preventing the deceased’s share passing to a new family, which is known as sideways disinheritance. A PPT is also very useful for couples who have children from different partners. A PPT will ensure each partner’s share passes to their child or named beneficiary whilst the surviving partner has the legal right to remain in the property for the rest of their life.

Find out more

Your Trusted Partner

In an effort to support causes close to our hearts, 5 years ago we decided that we would no longer charge for writing Wills, instead asking clients to make a recommended donation of £40 to charity. We were so confident that people would be happy with our Will-Writing service that we believed they would come back in the future for other legal services, at which point we could charge our usual fees. This has proved true, and over 63% of clients do come back for further advice.

We are proud to have raised over £2,000.000 in upfront donations, supporting fantastic causes up and down the country.

Contact us

219-221 Worcester Road
Malvern
WR14 1SU

112-118 Worcester Road
Malvern
WR14 1SS

Company details

Registered in England and Wales.
Company no. 7744618

Privacy policy