How Much Time Should You Spend Screening a Site? | Alpha Deal News

There's no universally correct answer to how long site screening should take. But there are wrong answers on both ends — and most teams are closer to one extreme than they realize.

Teams that spend too little time on initial screening miss things that kill deals later, when the cost of discovering them is much higher. Teams that spend too much time on the initial pass consume capacity that should be going toward deals that have already cleared the basic threshold. Both problems are real. The second one is more common.

This piece is about finding a workable standard for screening time — not as an arbitrary target, but as a diagnostic tool for how your pipeline process is actually functioning.

What "screening time" actually includes

Before calibrating the right amount of time, it's worth being specific about what screening encompasses. For our purposes, early-stage screening means the work you do before deciding whether a site earns full underwriting attention. It includes:

Program eligibility assessment
Zoning and density check
Rough capital stack sanity check
Site conditions scan (environmental flags, physical constraints)
Competitive context read (QAP scoring, local market dynamics)

It does not include full underwriting, detailed environmental review, market studies, legal work, or community engagement. Those come after the site has passed the screen.

The spectrum of practice

In practice, we've seen first-pass site screening range from about 45 minutes to several weeks. Here's what drives that variance:

45 minutes to 2 hours describes teams with well-defined criteria, good access to program and zoning data, and enough deal volume that pattern recognition is fast. They're making quick go/no-go calls based on a consistent mental model. The risk: speed can produce blind spots, especially on less familiar site types or markets.

Half a day to two days is common for teams doing more thorough first-pass work — pulling comps, running a rough proforma, making preliminary calls to local housing finance officials. This is more thorough but also more expensive in terms of staff time. It makes sense for deals that have already passed an initial filter and warrant closer attention before a full underwriting commitment.

A week or more typically indicates one of two things: either this is a deal that's genuinely complex and has already earned extended attention, or the team doesn't have a clear enough standard for what the screen is supposed to produce. The latter is more common than people admit.

The pipeline math argument

Here's a way to think about screening time from a pipeline perspective.

If your team evaluates 50 sites per year and converts 5 into active deals, your screening-to-conversion ratio is 10:1. The time you invest in the 45 sites that don't advance is largely overhead — necessary overhead, but overhead nonetheless. Reducing that overhead without reducing screening quality is how you create more capacity for the 5 that do advance.

If screening a site that doesn't advance takes 3 days of staff time, 45 rejections costs 135 person-days per year. If you can get that to 1 day of staff time on average without missing important signals, you've freed up 90 person-days — roughly 4 months of one analyst's time — to reinvest in the deals that actually merit it.

That's not a trivial number.

What enables faster, better screening

Screening speed isn't just about working faster. It's about having the right inputs organized in the right way at the right moment.

The things that slow down screening:

Fragmented data sources. When program parameters, zoning information, AMI data, and QAP scoring criteria are scattered across different sources, assembling them takes time regardless of how experienced the analyst is.

Unclear decision criteria. If the team doesn't have an agreed-upon standard for what the screen is supposed to produce — specifically, what constitutes a go, a no, and a conditional maybe — individual analysts spend time relitigating decisions that should be settled by process.

Insufficient deal volume to build pattern recognition. Teams that see relatively few deals per year have fewer opportunities to develop the fast-pattern-recognition that experienced developers use to triage quickly. This is a structural challenge for smaller organizations, not a performance criticism.

A practical standard

Rather than prescribing a specific number of hours, here's a more useful calibration question: Can your team complete a first-pass screen and produce a documented go/no/maybe recommendation for a typical site in under half a workday?

If yes, your screening process is reasonably efficient. If no — and especially if it typically takes several days for a first-pass screen — it's worth examining where the time is going and whether the output it's producing justifies the investment.

The point isn't to screen carelessly. It's to be precise about what you're deciding at this stage, and to make that decision with exactly the information it requires — not more, not less.

Alpha Deal is built to accelerate early-stage site screening — surfacing the program, zoning, and feasibility signals your team needs to make faster, better-informed triage decisions.