How to Screen More Sites Without Expanding Your Team | Alpha Deal News

Pipeline capacity in affordable housing development is a function of two things: the number of sites you can evaluate and the quality of the evaluation you bring to each one. Most teams can improve one at the expense of the other. The harder challenge — and the more valuable one — is improving both simultaneously.

The teams that consistently outperform on pipeline don't do it by hiring more analysts. They do it by building processes and using tools that let a lean team cover more ground without sacrificing the judgment that separates good deals from bad ones.

Here's how they do it.

Diagnose where your capacity actually goes

Before you can fix a pipeline capacity problem, you need to understand where the time is going. In most affordable housing acquisitions teams, the distribution looks roughly like this:

Data assembly: pulling together AMI data, zoning parameters, QAP criteria, program eligibility rules, comparable transactions — the research that has to happen before any real analysis can begin
Initial analysis: the actual feasibility thinking — does this site work for this program at this density, given what we know about the capital stack?
Documentation and communication: recording the findings, communicating the recommendation, tracking the pipeline

The insight most teams miss is that data assembly — the least skilled part of the process — often consumes the most time. An analyst who could spend an hour on genuine feasibility thinking instead spends three hours assembling the inputs that enable that thinking. That ratio is fixable.

Standardize the screen before you automate it

The instinct when facing a capacity problem is to look for tools immediately. But tools applied to a poorly defined process don't fix the underlying problem — they just make the mess faster.

Before optimizing, clarify what the screen is supposed to produce. Specifically:

What are you deciding? Early-stage screening should produce one of three outputs: go (advance to underwriting), no (move on), or conditional maybe (specific questions need to be resolved before advancing). If your team is producing something more ambiguous than that, the screen isn't well-defined enough.

What information do you need to make that decision? For most affordable housing teams, the minimum is: program eligibility, density supportability, rough capital stack viability, and absence of disqualifying site conditions. Document this explicitly so every analyst is running the same screen.

What counts as disqualifying? Define your hard stops — the flags that end a screen regardless of everything else. Fundamental program ineligibility, title issues with no clear resolution path, environmental contamination beyond a threshold your organization is willing to carry. These should be checked first, in sequence, before you invest time in anything else.

With a defined screen, you can measure how long it takes, identify where time is going, and make targeted improvements — rather than optimizing in the dark.

Front-load the deal-killers

The single most effective pipeline efficiency move most teams can make is changing the sequence in which they check things. Specifically: check disqualifying factors first.

If program eligibility is your most common deal-killer, check it before you look at anything else. If land basis is frequently the constraint, run a rough land basis calculation early — before density analysis, before site conditions, before the full research stack.

This sounds obvious, but in practice most teams don't do it. They run through a fixed sequence regardless of what's most likely to fail for a given deal type in a given market. That means they frequently spend significant time on steps 3 and 4 of a screen before they encounter the step 2 issue that would have stopped everything.

Front-loading deal-killers doesn't require new tools. It requires discipline and a defined decision sequence.

Build organizational knowledge that doesn't live only in people's heads

One of the biggest hidden inefficiencies in affordable housing acquisitions is that critical knowledge — program parameters, QAP nuance, local soft loan availability, what comparable deals have looked like in specific markets — lives primarily in senior staff. Junior analysts reinvent the wheel. Senior staff get pulled in for questions they've answered dozens of times.

Building accessible documentation of program knowledge, market norms, and evaluation criteria doesn't just help junior analysts move faster. It frees senior staff to do the high-judgment work that actually requires their expertise, rather than being the organizational memory everyone queries.

This takes time to build, but the compounding return is significant.

Use tools for the parts of the process that don't require judgment

Once you've defined your screening process and documented your organizational knowledge, the question becomes: which parts of this process are genuinely judgment-dependent, and which are research and data assembly?

Research and data assembly — pulling AMI figures, checking QCT and DDA status, reading zoning code, understanding program eligibility rules — are work that can be systematized. The judgment calls — is this site worth the entitlement risk? is this a market where our team can build competitively? does this deal fit our organizational capacity? — can't be.

Tools that surface the research layer faster create capacity for the judgment layer. That's the right division of labor between software and expertise.

The teams that screen the most sites without expanding their headcount aren't working harder. They're working in a process that's structured to concentrate human judgment where it matters — and handles everything else as efficiently as possible.

Alpha Deal is built to support exactly this workflow — handling the research and data assembly layer so your acquisitions team can focus on the judgment calls that actually require their expertise.