BACKYARD NY / PROJECT REGISTRY
METHODOLOGY

Methodology

Backyard NY documents Hudson Valley development and infrastructure projects — primarily battery energy storage (BESS) — and what happens to them. This page explains how each project is classified and sourced, so the labels on every detail page mean the same thing from one case to the next.

Sourcing & neutrality

The site aims to read even-handed; the point of view lives in what is documented and how carefully, not in editorializing. Opposing values and positions are presented with equal weight; factual claims are weighed by the strength of the evidence behind them (see How we weigh evidence, below).

How we weigh evidence

Even-handed does not mean treating every claim as a coin-flip. The site weighs factual claims by the strength of the evidence behind them — not by how many people are on each side — and it keeps three different kinds of claim apart:

This is why the site can state the climate and grid backdrop as established fact while still presenting both sides of a specific project: they are different kinds of question. Stating the backdrop never prejudges whether a particular battery belongs in a particular place — that siting question turns on values and local judgment, and the site does not decide it for you. One guardrail throughout: a person's values are always respected, but the factual claims offered in support of them are checked on their own merits.

How this site is researched

This site's research is performed by AI agents. Software agents locate and read the underlying records — adopted local laws, town board minutes, agency filings, news coverage — and draft the summaries and structured data behind every page. A human editor directs that work, decides what gets documented, and approves what publishes. Saying so plainly is part of the point: a reader deserves to know how the thing in front of them was made, and to weigh it accordingly.

The division of labor is deliberate:

Several constraints are built into the site rather than left to good intentions:

What this does not guarantee

The controls above establish that a claim is sourced — that a citation exists, resolves, and is properly attached to what it supports. They do not establish that the source says what the page says it says. That is the real limit of this method: a citation can be present, well-formed, resolvable, and still not support the claim built on it, and no automated check will catch that. Only reading the underlying document will.

That reading is directed by this site's editor and performed by the same pass that writes the pages — a careful re-reading, not an independent audit. So the machinery narrows the ways this can go wrong; it does not close them, and it is not a substitute for the record. Where a page matters to you, follow its sources.

There is a limit on coverage, too, not only on claims. Much local argument happens in neighborhood Facebook groups, on Nextdoor and on Reddit. This site does not cover it. Organized groups and petitions are cited for their own stated positions; individual posts are not, because they cannot be re-checked later, and because posting in a neighborhood group is not the same as speaking on the record at a public meeting. Where a project's opposition looks thin here, that may reflect where we looked.

Corrections

If you are named on this site, or you know a record here is wrong, please tell us. Corrections are welcome from anyone — a town clerk with the filed law, a developer with the actual capacity, a resident who was in the room.

Outcome

The honest scorecard — where a project actually ended up:

Source confidence

How well-sourced a case's facts are (labeled Source confidence on the detail page, with the specifics in a tooltip). The meter fills from one to four segments:

Process

The legal or procedural lever(s) that shaped the outcome (labeled Process on the detail page; each value has a tooltip). The controlled vocabulary:

For it · Against it · Context

For it and Against it list the actors on each side, with sources. Context is a separate, neutral strip for backdrop that is not a position — statewide policy targets, market conditions — so a policy is never miscast as a project's supporter or opponent.

Capacity

Battery projects are described by power (megawatts, MW — how much it can deliver at once) and energy (megawatt-hours, MWh — how much it stores). These are not the same number: a 250 MW / 1,000 MWh project is a 4-hour battery (energy ÷ power = duration). Power, energy, and duration are the measures used by the U.S. Energy Information Administration and the national labs, so they are what this site reports. There is no single industry standard for labeling a project "small," "medium," or "large," so the site does not yet assign size bands; that convention is still being worked out.

Why no "homes served" figure. Developer and press materials often describe a battery as enough to "power N homes." The site does not adopt that number, because no government body, national lab, or standards organization publishes a rigorous way to convert storage capacity into homes served. The familiar "homes powered" gloss is a generation approximation — annual energy output divided by an average household's yearly use — and even there agencies treat it as a rough estimate that swings widely by region. A battery generates no annual energy: it shifts a fixed amount of stored energy and discharges it for a limited duration, then must recharge. An unqualified "powers N homes" therefore misrepresents storage as if it were a power plant. Where such a claim is relevant, it is reported as the explicit statement of whoever made it — not as a site-asserted fact — alongside the MW / MWh / duration that can actually be sourced.

Freshness

These are live fights. Where a fact can change, the case carries an "as of" date so its age is visible. A status with an old date may simply not have changed — or may need re-checking.

A living document

Cases are maintained on an ongoing basis, including with agent-assisted research. This methodology is the shared rulebook that keeps that work consistent over time.

// every field traceable to a primary source · outcome classified per documented record · BACKYARD NY