STEERS Filing Assistance

What is STEERS?

STEERS — the State of Texas Environmental Electronic Reporting System — is TCEQ's online permitting system. It is where a construction project's stormwater coverage actually happens: the account that signs, the form that files, and the confirmation that lets dirt move.

The filings that go through it

The electronic route is not a convenience feature — it is the default path the permit prescribes. Applicants must submit the NOI using the online ePermits system, accessed using STEERS through the TCEQ website, or request and obtain a waiver from electronic reporting from the TCEQ. The exit paperwork rides the same rails. The NOT is also submitted using the online ePermits system available through the TCEQ website, unless the operator has requested and obtained a waiver from electronic reporting. One system opens the record and closes it, which is why getting the account right once pays for the whole life of the project. The names confuse first-timers — one is the doorway, the other the form set inside it — but operationally they are a single path: log in, file, confirm.

When coverage begins

Speed is the electronic path's argument. Primary operators of large construction activities that submit the NOI electronically are authorized immediately following confirmation of receipt of the electronic form by the TCEQ, unless otherwise notified by the executive director. Electronic filing rewards preparation: when the form data is right, coverage follows confirmation without a mailbox in the loop. The number that makes it official comes next. An authorization stops being provisional when the executive director finds the NOI administratively complete and issues an authorization number for the construction site. That authorization number is the project's permit identity from then on.

The paper path still exists

Filing on paper is possible — with a waiver, and with patience. Operators with an electronic reporting waiver must submit a completed paper NOI at least seven days before commencing construction activity, and provisional coverage begins 48 hours from the postmark date. Waivers from electronic reporting are not transferable and expire on the same date as the authorization to discharge, except for temporary waivers that expire one year from issuance. For a schedule measured in days, the difference between immediate confirmation and a postmark clock is the difference between mobilizing this week and next.

Getting the account right

The classic filing-day emergency is an account problem wearing a deadline costume. The account has to exist, the right person has to hold it, and the signature authority has to match how the company actually delegates — corporate structure, project roles, and who is allowed to certify what. None of that is hard, and all of it takes longer than the form itself when it is discovered late. The desk's checklist is short and boring on purpose: account established, roles assigned, signatory confirmed, project facts assembled from the plan, and the filing rehearsed before the day it matters. Boring checklists are what fast filings are made of.

There is also a life-of-project angle: the same account that opens coverage will correct it and close it, sometimes years later, often after the people who set it up have changed jobs. Documenting where the account lives and who can reach it is cheap continuity insurance — the kind that gets remembered gratefully at closeout.

How Terradyne helps

Terradyne prepares and files a project's NOI, NOC, and NOT directly in TCEQ's STEERS system on the operator's behalf; the operator signs in STEERS under their own electronic reporting number, so certification stays with the operator. Terradyne prepares the completed TCEQ permit forms — the NOI and construction site notice as applicable — alongside the SWP3 narrative. The e-filing desk carries the rest: account setup questions, signatory roles, form data pulled straight from the plan so the filing and the narrative agree, and the confirmation tracked until the authorization number is in hand. For operators running several projects, the desk keeps the filing pattern consistent across all of them — same data discipline, same records, no per-project reinvention.