The second gap

It’s the start of the most expensive stretch of the deal, and the capital tied up in it is yours.

A land bank came to us with a large project and a date.

The entitlement was done. Development was underway. And somewhere in the months between those two facts, the schedule had slipped, not dramatically, not in a way that showed up in any single status report, but steadily, in the ordinary manner of a project where several people are each responsible for part of it and nobody is responsible for the whole.

Year end was a hundred and twenty days away. They needed the project moving, and they needed their money out.

That is not a story about incompetence. Every party on that deal was doing their job. It is a story about what happens in the gap between the people who got a project approved and the people building it, and about the fact that on most deals, nobody owns that gap.

What the approval actually was

When a rezoning passes, what you have is not permission. What you have is a set of promises.

Some of them are written into conditions of approval. Some were made out loud at the hearing, in response to a question from a commissioner or an objection from a neighbor, and never made it into the ordinance at all, but the people in that room remember them, and they will remember them again in eighteen months when something needs a waiver.

Then the entitlement team’s engagement ends, and a delivery team picks up a project defined by a document they weren’t in the room for.

Four ways that gap costs money

1. Conditions the delivery team never saw A development manager inherits conditions they did not negotiate and frequently do not know exist. The place those surface is plat review, which is the most expensive point in the process to discover anything, because by then the engineering is done, the grading plan is drawn, and the fix is a redesign rather than a decision.
2. What was promised in the room, versus what got codified Boards approve projects on the strength of statements that never appear in the conditions. A commitment about construction traffic routing. An assurance about a buffer. The person who was in the room is the only one who knows what the board and the neighbors believe they were told, and that belief is what you’ll be measured against when you come back for anything.
3. Going back to the board mid-development Every project eventually needs a modification, a waiver, or an interpretation. If the entitlement relationship is still live, that’s a phone call to someone at the counter who knows the file. If it has to be hired cold, it is a two-month restart: new counsel, new reading, new introductions, and a staff member who has to be brought up to speed on a project they last saw a year and a half ago.
4. Closeout is entitlement work wearing a hard hat Bond release and final acceptance are condition-compliance exercises. They are entitlement questions, decided at the planning counter, and they are routinely handed to a construction team that is very good at building things and has no relationship with the person signing off.

The arithmetic nobody underwrote

Active development management on a typical project runs about fourteen months. That’s the number most pro formas are built around, and it’s roughly right.

Closeout doesn’t arrive until past month thirty-six, because bonds don’t release until houses sell and commercial space fills. For nearly two years after the active work is finished, there is a project that is technically still open, with conditions still outstanding, still consuming somebody’s attention in small increments, and still holding capital that the model assumed had come back.

Your money isn’t waiting on construction. It’s waiting on paperwork nobody owns.

That tail is where the land bank found itself. Not in trouble on the build, in trouble on the dozen small unresolved things between a finished project and a released bond, each of which belonged to somebody and none of which belonged to anybody in particular.

What one accountable team means

It means the person who negotiated the conditions is the person who closes them out. It means the file doesn’t get handed across a gap, because there is no gap. And it means that when something needs to go back in front of the board, and eventually it will, the relationship is already there.

That’s not a claim about being better at any individual task. Your engineer is a good engineer. Your attorney is a good attorney. The failures above are not failures of skill; they are failures of continuity, and continuity is a structural choice you make when you assemble the team, not a quality you can hire for later.

One thing worth saying plainly

We manage development. We don’t develop, and we don’t buy land.

That matters more than it might sound. A development manager who works for a firm that also acquires land is, at least in perception, sitting on the other side of your table, looking at your deal, your pricing, your seller relationships. Nobody here is. We have no position in your project other than getting it built on the terms you were approved for, on the dates you underwrote.

Where this starts

Usually in one of two places. Either a project is coming out of entitlement and you’d rather not hand it across a gap, in which case the conversation is about carrying it through. Or a project is already underway and behind, and the question is what’s actually holding it up, which is a diagnosis before it’s an engagement.

If your project is running on schedule with someone accountable for the closeout, you don’t need us, and we’ll say so. If it isn’t, we’re YES, if it’s in our wheelhouse, we’ll figure out how to make it work.