How off-plan payment structures actually work

An off-plan purchase spreads the price across the construction period instead of demanding it at handover. That is genuinely useful: it lets a buyer commit at today's price and fund it out of income rather than a single lump. It also means you are extending credit to a developer, and the structure of the plan is what determines how exposed you are while you do it.

Milestone-linked, not date-linked. The important distinction is what triggers each payment. A plan tied to construction stages — foundation, structure to a given floor, roof, first fix, completion — means you pay for progress you can verify. A plan tied to calendar dates means you pay whether or not anything has been built. Ask which one you are signing, and if it is the latter, ask why.

Who confirms the milestone? Ideally an independent project monitor or the financing bank's own surveyor, not the developer's word. On bank-financed schemes this is usually already in place, because the lender has the same interest you do.

Where does the money sit? Payments held in a project account that can only be drawn against certified work behave very differently from payments paid directly to the developer's operating account. Ask the question plainly. The answer is a good proxy for how the whole scheme is run.

What is the shape of the curve? Plans vary widely — some front-load, taking thirty or forty per cent before ground is broken; others hold a substantial balance to completion. A heavier balance at handover keeps the developer's incentive pointed at finishing, and keeps more of your capital under your control in the meantime. It may cost slightly more in headline price. That is often a reasonable trade.

What happens if you need to exit? Assignment before completion is permitted on some schemes and prohibited on others. If your circumstances might change over a two-year build, this clause matters more than the interest saved on any part of the schedule.

A payment plan is not a financing product and should not be assessed as one. It is a description of how much trust the structure asks you to place in the developer, and at what point.