Your First Home scheme price caps revealed for Sussex
Summarised from 2 outlets · Updated 7 Nov, 06:14 · Archive
The Government has revealed price caps for its Your First Home scheme across Sussex areas, ranging from £300,000 to £460,000.
The Government has revealed property price caps for the Your First Home scheme across Sussex. The £4.7 billion scheme aims to help 70,000 households in England become homeowners. Eligible first-time buyers can purchase a new-build home with a 2.5 per cent deposit and a 20 per cent government equity loan, interest-free for five years.
Price caps vary across Sussex, with Mid Sussex's cap at £460,000 being the highest in the county and Worthing's at £300,000 being the lowest. Buyers must generally be first-time buyers purchasing within their local price cap, and the property must be their main home. Household income must not exceed £110,000 outside London or £140,000 in London.
Aneisha Beveridge, research director at Connells group, said the price caps should give first-time buyers access to a choice of flats and smaller houses in most areas. She noted that the caps may encourage more first-time buyers to consider apartments to benefit from the interest-free equity loan.
Pre-registration opens by the end of December 2026, followed by full applications in February 2027 and the first loans in April 2027.
How it is being reported
- What first-time buyers can afford in Sussex under new schemeFirst-time buyers in Sussex can now see what they could afford under the Government’s new Your First Home schemeThe Argus · 7 Nov, 05:00
- Your First Home scheme price caps across Sussex revealedThe property price caps in areas across Sussex for the new Your First Home scheme have been revealed by the Government.Chichester Observer · 6 Nov, 14:09
In this story: Your First Home · Sussex · Mid Sussex · Worthing · Aneisha Beveridge · Connells group
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)