Reading the Board: Blocked, Delayed, and Advanced

If opposition is a first-order risk, the first discipline is to observe it systematically rather than react to it anecdotally. That means sorting projects into a small set of honest outcome states and watching how a given market moves projects through them. I use three primary states, and I resist the temptation to add more, because clarity beats precision here.

The first state is blocked. A blocked project has hit a hard stop: a permit denied, a rezoning voted down, a lease terminated, an announcement formally withdrawn. Blocked is unambiguous and, paradoxically, the least useful state to track in isolation, because by the time a project is blocked the information it could have given you is spent. The value of tracking blocked projects is comparative. When you see a cluster of denials in a county over a short window, you are looking at a jurisdiction whose politics have turned, and that turn will affect the next applicant regardless of how clean their proposal is.

The second state, and the one that repays the most attention, is delayed. A delayed project is still alive but has slipped its schedule because of a contested hearing, a demanded environmental study, a moratorium that froze intake, or litigation. Delay is where most of the economic damage actually happens, and it is where the early signal lives. A project does not usually leap from healthy to blocked; it grinds through a sequence of delays first. If you are tracking delay honestly, you can often see the trajectory before the participants admit it to themselves. The tell is repetition: a hearing continued once is procedure; continued three times is a project in trouble.

The third state is advanced. An advanced project cleared its approvals and moved into construction or energization on something like its intended timeline. Advanced projects are not merely the happy residue; they are your most valuable teaching cases. When you study why a project advanced smoothly in a jurisdiction where a comparable project stalled, you isolate the variables that actually matter: the quality of early engagement, the specific mitigation commitments, the local economic context, whether the developer offered a community benefit that landed, whether the power arrangement avoided burdening existing ratepayers.

Reading the board well requires a few habits. First, hold the states as a flow, not a snapshot. The useful question is not how many projects are blocked today but how the ratio of advanced to delayed to blocked is trending in a market over successive quarters. A market where the delayed bucket is swelling is a market tightening against new development, and that tightening is a leading indicator you can act on before it hits your own project.

Second, normalize for base rates. A market with a great deal of activity will show more absolute blockages simply because it has more attempts. The signal is the rate, not the raw count, and the change in the rate more than its level. A jurisdiction that denied its first-ever large-load application just told you something far louder than a busy market that denied its twentieth.

Third, attend to the reasons, not just the outcomes. Two counties can each deny a project, but if one denied over water draw and the other over truck traffic, they are telling you different things about what a survivable proposal would need to look like. The reason codes are the raw material for the pattern analysis that comes later in this course, and they are only capturable if you record them at the moment of the event rather than reconstructing them afterward.

Fourth, watch the neighbors. Opposition outcomes correlate spatially. A denial in one town raises the odds of resistance in the adjacent town, because the same regional groups, the same news coverage, and the same template arguments move across municipal lines. When you map outcomes geographically rather than listing them, the clusters practically announce which corridors are hardening.

Finally, be honest about survivorship. The advanced projects you can see are the ones that made it; the proposals that never got announced because a savvy developer read the room and walked away are invisible in the public record. That silent attrition means the true friction in a hardening market is always somewhat worse than the visible blocked-and-delayed tally suggests. Reading the board is the foundation; the next module turns to the specific mechanisms, the denials and moratoria, that move projects into the states we have just defined.