When the site plan is the clock

A queue row says someone asked for megawatts. A county site-plan or development-review packet says the campus footprint is on a public calendar — stamped, noticed, continued, or denied. Watt Brief treats a new or amended site-plan approval, conditional site-development order, major site-plan amendment, or staff report that names a data-center or large-load campus as a delta: one identity, one document ID, one reason the stamp binds. It is not color for a marketing site tour.

What counts as a site-plan delta

The identity is still source + document ID + event class. The headline names what moved: a site-plan approval, a continued hearing on a revised site plan, a staff recommendation with a binding comment clock, a major amendment that changes pad count or access, or a denial that closes a path. County and parcel stay when the packet prints them. MW stays only if the filing states or bounds it. We do not invent document IDs. Teaching examples stay labeled EXAMPLE. Live rows use the ID the county printed.

Where these clocks actually appear

• County / city planning portals — site-plan, site-development, and major amendment packets with case numbers.
• Planning commission and board agendas that attach the stamped plan set or staff report.
• Continuances and revised plan sets posted under the same case ID — that is usually an update on the same identity, not a louder restatement.
• Companion rezoning or special-use rows only when the ordinance page is a separate document ID — that is a different row from the site-plan stamp.

Why the stamp binds before the ribbon-cutting

Site-selection decks sell acreage and renderings. The site-plan packet sells the footprint the county will enforce: setbacks, access, phasing, outdoor equipment yards, and the conditions tied to the stamp. An approved plan can unlock building permits. A continuance with a new submittal date can push the construction calendar later than the interconnection queue alone implied. A denial can strand a land option you were about to renew. None of that is a $/kW comps product and none of it is a trade-magazine feature. It is a pointer to the plan set and staff report you can open.

Related dates sit on the same row: filing date, notice date, hearing date, continuance date, approval or denial date, and any condition-compliance clock printed on the order. They are not six separate headlines. If the same document ID later gets a major amendment or a revised stamped set, that is a new delta on the same identity — not a duplicate with a restated lede.

What it is not

A site-plan row is not proof the campus will energize. Operators walk. Boards reverse. Packets get withdrawn. It is also not a substitute for the interconnection-queue row, the PUC tariff case, or the county rezoning vote — those are separate identities when the sources are separate. Open the case URL. Match the document ID. If the data-center or large-load campus is not on that packet, the row is not for you yet.