How a lot takedown schedule works

A lot takedown schedule is the timetable in a contract between a land developer and a homebuilder under which the builder buys finished lots in tranches on stated dates, rather than buying the whole subdivision at once. It sets how many lots fall in each take, when each take is due, what a lot costs in each period and how that price moves over the life of the schedule, and what happens when a take is missed. The builder posts a deposit against the agreement, and that deposit is credited back a piece at a time as lots close rather than sitting until the end. One document, read from two ends: it is the developer’s revenue plan and the builder’s lot supply at the same time.

The deposit burns down, it does not sit

The builder posts earnest money, or a lot deposit, against the whole agreement, and what happens to it next is the part most often modelled wrongly. It is not returned at the end and it is not money the developer keeps. A piece of it is credited against the price of each lot as that lot closes, so the pool falls take by take until it is gone.

How much each lot credits is a contract term. A flat amount a lot is the same dollars whatever the lot sells for. A pro rata credit is a percentage of that lot’s price, so it grows with every escalation and spends the pool faster than dividing it by the lot count would suggest. Two consequences follow.

• The cash arriving is not lots times price. It is gross proceeds less the deposit credit and less whatever is paid to release the lot, so a forecast built on the gross overstates every period until the pool is spent.
• The pool is shared. A deal running two products, two townhome widths on the same cadence at different prices, is two schedules and one deposit. Credited side by side, each draws on the full balance and the two together hand back roughly twice what the builder posted. Takes have to be ordered by when they happen and the pool spent in that order.

Which makes the date the pool empties worth knowing in advance. The net per lot steps up that day, and a forecast built without the burn-down puts the step in the wrong month.

Why the schedule exists at all

The developer needs committed absorption. Finished lots with no contracted buyer are an inventory position, and a lender sizing a facility would rather see contracted takedowns with a counterparty’s name on them than a projection of retail demand. The builder needs lots without the land basis, because buying the subdivision outright means carrying every lot from the first day and that capital is worth more in vertical construction.

Neither side gets that free, which is what makes it a risk trade rather than a courtesy. The developer gives up selling into whatever the market turns out to be, holds the concentration risk of one counterparty for years, and collects the difference through the escalators. The builder commits to buy on dates chosen before anybody knows their sales pace. Every clause is one of those two risks being priced.

Escalation, as a mechanic

Lots are delivered over years at a price agreed before the first one closed, so most schedules raise the price as they run. The term takes two forms, and the choice belongs in the underwriting.

A flat step each period

A stated amount added to each lot’s price every period after the first. The price in any period is the base plus the step times the periods elapsed, which is the whole of it.

A percentage

A rate applied to a base, and the base is the question. Applied to the original price it is a straight line. Applied to the previous period’s price it compounds, and across a long schedule the two produce visibly different late periods. A rate stated without its base leaves the more consequential half of the term to whoever builds the model.

One mechanic applies to both. Escalation is normally indexed to the period rather than the calendar, so a schedule whose anchor slips delivers period three at period three’s price, later. That is usually what the parties meant, and it is worth confirming before a slip turns it into a live question.

A missed take, and the provision behind it

A take is a dated obligation, and dated obligations get missed. The first thing to notice is that a miss can originate on either side: the builder’s absorption slowed and they do not want the lots, or the lots are not finished and cannot be conveyed. Both land on the schedule as a take that did not happen, and they are not the same event.

What follows is the agreement’s business. Agreements commonly provide for some combination of notice and cure, a deferral rolling the missed lots into a later take, a consequence for the deposit, and a right to terminate the remainder. Which of those apply, on what notice, and what any of it does to money already posted are contract questions with real variation behind them, and they belong with the agreement and with counsel rather than with a page like this one. What does travel is why the clause is load-bearing on both sides.

The developer’s lender underwrote the takedown series, so a missed take is a covenant conversation before it is a revenue one, and the builder has a deposit at risk and a pipeline that assumed those lots. A clear provision costs both sides an awkward phone call; a vague one costs them a negotiation at the worst possible moment to be having one. And whatever the remedy, the record is the same: which take was missed, how many lots, whether they rolled or lapsed, and what the deposit did. A deferral agreed on a call and confirmed in an email is a schedule that has quietly stopped matching the contract it came from.

The first take hangs off the plat

A lot cannot be taken down before it is a lot. The first take waits on the final plat recording and on acceptance of the improvements that finish the lots, so its date derives from events belonging to a county and a utility rather than being typed by whoever built the schedule. Often it is the later of two conditions, and it moves when whichever one is governing moves.

The sentence to take away is that a slip upstream does not move a date, it moves revenue. Three weeks added to the plat is three weeks added to the first closing, to the deposit credit that closing applies and to the loan paydown it funds. Which is why takedown dates belong on the same schedule as the development work: when the anchor moves they move with it, and whether the first take still lands inside the builder’s window is answered that morning. That mechanic is the subject of its own page, and the takedown is the row on it with money attached.

What arrives is not what closes

Every lot is encumbered by the development loan, and at each closing the lender is paid a release price to free that lot from the lien. That money crosses the closing table and never reaches the developer. So a take produces four numbers rather than one: gross proceeds, the deposit credit applied, the release payment, and what is left.

Where the release price sits relative to the lot price decides how fast the facility retires against how much cash the developer sees on the way, and it is set in the loan agreement rather than the purchase contract. Two documents govern one closing, and they were negotiated across two different tables.

This is the same loan read from the other end. A draw package funds the work that turns dirt into finished lots; the takedowns retire what those draws advanced. A project drawing faster than it is taking down is spending the facility faster than the schedule repays it, and that is visible months ahead, but only if the draws and the takedowns sit on one timeline.

One take, worked through

The same sample project as the rest of this library, where the plat slipped and carried the first take to the twentieth of November. A hundred and twenty lots, twenty to a take, one every six months.

Most of what closed that day never reached the developer. What is left after the lender and the deposit is the figure that answers whether the next draw can be covered, and that gap is the difference between reading a takedown schedule as a revenue plan and reading it as a liquidity one.

Written alongside PadFlow, which keeps a land development schedule, budget and draws on one record.