Data center transmission service request: the TSR clock that binds

A queue row says someone asked for megawatts at a point of interconnection. A transmission service request says how those megawatts intend to move across the grid — and on what clock. For data-center campuses that need network or point-to-point service, Watt Brief reads TSRs the same way it reads any other public record: identity first, then the one study or response deadline that binds. A slide that says “transmission secured” is not a row. A public filing with a document ID is.

Four fields before you believe deliverability

Open the RTO, ISO, or transmission provider OASIS or queue portal. Pull these before you change a site-visit plan or a power-purchase narrative:

• Document ID — the TSR number, OASIS assignment, or queue tracking ID the provider printed. That is the identity key with source and event class. We do not invent one because a broker said capacity was “spoken for.”
• Service product — network, point-to-point, interim, or conditional. Emergency-only or short-term service is a different campus story than long-term firm network service tied to a POI.
• MW and path — requested capacity, source/sink or POI, and whether the filing is study-phase or confirmed. If the packet bounds MW, we keep the bound. If it only says “campus load,” we do not convert marketing copy into a fake TSR MW.
• Clock dates — submittal, deficiency notice, study start, study due, offer, confirmation, withdrawal, or restudy. An open study without a due date is not the same row as a confirmed service agreement.

Why the TSR binds before campus PR

Campus PR moves when the developer wants a headline. A TSR moves when the transmission provider accepts the request into study or confirmation — or when a deficiency clock forces a response. For colo and hyperscale site-selection BD, utility large-load teams, and infra PE, the binding fact is not that someone announced power. It is that a named document ID changed status on a dated transmission clock.

A deficiency notice is not soft feedback. It is a public clock: cure, withdraw, or miss the window. Watt Brief treats a new deficiency or study milestone on a known document ID as a delta. A restated “transmission in process” headline on the same ID is not.

What counts as a TSR delta

• New TSR with a document ID, product, and MW/path.
• Deficiency issued or cured with a dated clock.
• Study start, study complete, or restudy on that ID.
• Offer, confirmation, or service agreement executed.
• MW, POI, or product amendment that revises the table.
• Withdrawal or termination of the TSR.

None of that is a trade-magazine feature. It is a pointer to the OASIS record or study PDF you can open. If the same document ID later gets a restudy or a revised MW path, that is a new delta on the same identity — not a duplicate with a restated lede.

What we skip

We skip generic “power available” press kits that do not attach a TSR or queue ID. We skip restated headlines about the same document ID. We skip empty mornings. We skip inventing an OASIS number because a broker shared a screenshot without a public ID.

A TSR row is not proof the campus will energize. Studies recondition. Offers expire. Customers withdraw. It is also not a substitute for the generation interconnection queue entry, the facilities study, ERCOT Batch Zero verification, a water or air permit, or a county land-use stamp — those are separate identities when the sources are separate.

Open the TSR URL. Match the document ID. If the data-center load is not on that filing, the row is not for you yet.