How to Hand Off a Site Evaluation Without Losing Institutional Knowledge
One of the most consistent sources of wasted effort in affordable housing development happens at handoffs. An analyst screens a site, forms a clear view of what works and what doesn't, and moves on to the next one. The site gets handed to a senior director for a go/no-go decision — and the decision gets made without the context that informed the analysis.
Or the senior director evaluates a site, concludes it needs more work before advancing, and the site goes back into the queue. Three months later it comes back up. The person who looks at it again doesn't know what was already evaluated, what was concluded, or what specific question was supposed to be resolved in the meantime.
These aren't failures of individual performance. They're failures of handoff design. Here's how to fix them.
What a good handoff document captures
The purpose of an evaluation handoff isn't to summarize everything that was researched. It's to transfer the judgment that was formed from that research — the specific things that make this site potentially viable, the specific constraints that could kill it, and the specific question that the next step needs to resolve.
A good handoff document for a first-pass screen should cover:
The program hypothesis. What deal type is this site being evaluated for? What's the basis for that hypothesis? If it's a 9% deal, what makes this site competitive in the relevant QAP?
The viable path. What does the deal look like if it works? Rough unit count, AMI targeting, capital stack structure. Not a full proforma — the directional scenario that makes the deal worth considering.
The primary constraint. The single most important thing that determines whether this site can advance. Land basis gap. Zoning that needs to change. Soft debt availability that's uncertain. Competitive positioning that's weak. There's almost always one thing that matters most.
The open question. What specific question needs to be answered before this site earns more investment? This is the decision-relevant output of the screen — not a summary of everything that was checked, but the thing that most needs to be resolved next.
What was already done. A brief record of what was researched, who was contacted, and what was found — so the next person doesn't duplicate work.
Format matters
A handoff document that takes 45 minutes to write will stop being written. The format needs to be fast enough to complete in 10-15 minutes for a first-pass screen — which means it needs to be structured (the evaluator fills in defined fields rather than writing prose) and limited to what actually matters for the decision.
Structured templates are more consistently useful than open-ended formats, even when they feel constraining. The constraint is part of the value — it forces the evaluator to identify the primary constraint and the open question explicitly, rather than leaving them implicit in a narrative that the next person has to interpret.
The asymmetry of rejection documentation
Handoffs for sites that advance get attention because they have a clear next step and someone who needs the information. Handoffs for sites that are rejected get less attention because the deal is over.
This is backwards. The record of why a site was rejected — captured at the moment the rejection decision is made, while the reasoning is fresh — is organizational knowledge that will be useful when the site comes back up, when a similar site is evaluated in the same market, and when the team is building its understanding of what works and what doesn't in a given geography.
Treat rejection documentation with the same care as advancement documentation. It's the same information, with a different immediate use.
Alpha Deal helps development teams capture and transfer site evaluation context — so institutional knowledge survives handoffs and doesn't have to be rebuilt from scratch.