What Standards Are Applied?

Part Seven of Understanding the
Texas Resource Stewardship Protocol (TRSP)

Once a project crosses a review trigger, the next question is not whether someone likes or dislikes the project.

The next question is whether the project can meet clear standards.

The Texas Resource Stewardship Protocol, or TRSP, is designed to move that discussion away from general promises and toward measurable evidence.

A standard should tell the applicant what responsible performance requires, tell reviewers what evidence to examine and tell the public how compliance will be verified.

That is the difference between saying a project should “minimize impacts” and identifying what must actually be measured, limited, reported and corrected.

Standards make review practical

A public review process cannot operate on concern alone.

Words such as reasonable, sufficient, minimal and responsible may express a goal, but they do not tell anyone how to determine whether the goal has been met.

A useful standard connects four things:

• The condition being protected.
• The evidence needed to evaluate it.
• The measurable expectation or threshold.
• The response required when the expectation is not met.

A standard should be clear enough to guide the decision before approval and specific enough to support monitoring afterward.

TRSP standards are not one-size-fits-all

Large-impact projects differ in their design, location and operating demands.

A data center, power plant, battery facility, manufacturing site and major industrial expansion may raise different questions.

The standards applied to a project should therefore match the triggers it crossed and the impacts supported by the evidence.

A project with limited road impacts should not be forced through an unrelated technical review. A project with substantial groundwater demand should not avoid water review because its traffic impact is small.

The scope should fit the project while the standards remain consistent.

Standard One: Water and groundwater

Water review should begin with a complete accounting of demand, source and long-term reliability.

Depending on the project, the evidence may include:

• Expected daily, seasonal and peak water demand.
• Water source, ownership and legal availability.
• Effects on nearby wells, aquifers, streams or reservoirs.
• Conservation, reuse and drought-response plans.
• Baseline testing and continuing monitoring where nearby wells may be affected.
• Contingency plans if the proposed source becomes unavailable.

The standard should require more than a statement that water is available. It should show where the water will come from, how much will be used and what happens when conditions change.

Where the county lacks groundwater authority, the review should clearly identify which protections can be negotiated now and which require action through a groundwater conservation district or the Texas Resource Stewardship Initiative.

Standard Two: Noise, vibration and low-frequency sound

Noise should be evaluated at the places where people may actually experience it, not only beside the equipment creating it.

Review may consider:

• Baseline conditions before construction.
• Daytime and nighttime sound limits.
• Low-frequency sound, tones and vibration.
• Measurement locations at property lines and nearby receptors.
• Construction noise and operating noise.
• Complaint investigation and retesting procedures.

A useful noise standard identifies how sound will be measured, under what operating conditions and what correction is required when the limit is exceeded.

The goal is not silence. The goal is a measurable boundary between ordinary operation and unreasonable impact.

Standard Three: Lighting and dark skies

Outdoor lighting should provide safety and security without unnecessarily extending glare or skyglow into the surrounding area.

Standards may address:

• Shielded and downward-directed fixtures.
• Maximum illumination at the property boundary.
• Color temperature and glare control.
• Lighting schedules and dimming where practical.
• Emergency lighting exceptions.
• Verification after construction and after major lighting changes.

In rural Texas, darkness is part of the surrounding environment. A lighting plan should show that the project can operate safely without treating the night sky as unused space.

Standard Four: Roads, traffic and construction

Large projects can create road damage and traffic demands long before normal operations begin.

Review may include:

• Construction routes and heavy-haul loads.
• Road and bridge condition surveys before work begins.
• Traffic volumes, turning movements and school-route conflicts.
• Dust, mud, debris and temporary access controls.
• Repair responsibilities and financial assurance.
• Emergency access during construction and operation.

The standard should identify who is responsible for unusual project-specific damage and how the condition of the road will be documented before, during and after construction.

That protects the county, the applicant and everyone who depends on the route.

Standard Five: Drainage, runoff and erosion

Development can change how water moves across a site and into neighboring property.

Standards may require:

• Existing and proposed drainage maps.
• Stormwater detention or retention plans.
• Erosion and sediment controls.
• Protection of county roads, ditches and downstream property.
• Inspection after major rainfall events.
• Correction of failures, washouts or unauthorized discharge.

Drainage review should focus on whether the project changes the timing, direction or volume of runoff in a way that creates preventable harm beyond the site.

Standard Six: Emergency readiness

A large-impact project should be able to explain not only how it expects to operate but how it will respond when something goes wrong.

Review may address:

• Fire, medical and hazardous-material risks.
• Emergency shutdown and isolation procedures.
• On-site detection, alarm and notification systems.
• Training and equipment needed by local responders.
• Access routes, water supply and staging locations.
• Coordination with dispatch, emergency management and neighboring jurisdictions.

The project should fund the reasonable systems, training and equipment associated with risks created by its operation.

Public responders should receive the information needed to prepare, verify and escalate without making the county responsible for designing the operator’s internal safety program.

Standard Seven: Reporting, monitoring and public accountability

A promise is difficult to enforce when the agreement does not identify what must be reported or how the public will know whether the promise was kept.

Standards may require:

• Baseline reports before construction or operation.
• Scheduled compliance reports.
• Continuous or near-continuous monitoring where conditions can change quickly.
• Public dashboards or organized project files.
• Incident and complaint records.
• Corrective-action deadlines and verification.
• Independent review where specialized expertise is required.

Applicant-funded monitoring does not mean applicant-controlled monitoring.

The public process should determine the standards, reporting format, reviewer qualifications and access to records.

Standard Eight: Financial assurance and long-term responsibility

Some commitments continue long after construction is complete.

Review may consider:

• Road-repair security or reimbursement agreements.
• Funds for independent technical review and monitoring.
• Decommissioning, closure or site-restoration obligations.
• Responsibility after ownership or operator changes.
• Insurance, bonds or other financial assurance tied to defined risks.
• Clawbacks or loss of benefits when material commitments are not met.

Financial assurance should fit the obligation. It should not become an arbitrary fee, but it should prevent known project-specific costs from being shifted to local taxpayers.

Standards should be measurable and connected to evidence

A standard is strongest when the record shows how it will be evaluated.

That may require a numerical threshold, a recognized technical method, a certified plan or a defined performance outcome.

Not every issue can be reduced to one number. Even then, the agreement should identify the evidence, reviewer and decision rule that will be used.

For example, a drainage standard may rely on engineering calculations and approved plans. An emergency-readiness standard may rely on a written response plan, equipment list, training schedule and inspection record.

The key is that the conclusion can be explained and checked.

Standards should distinguish requirements from goals

Public documents often mix mandatory conditions with aspirational language.

That creates confusion later.

Every commitment should make clear whether it is:

• A required condition of public support.
• A measurable operating limit.
• A reporting or monitoring duty.
• A corrective-action requirement.
• A voluntary goal or best practice.

A voluntary goal may still be valuable, but it should not be presented as an enforceable protection when no consequence follows from missing it.

Standards should allow correction without becoming optional

Responsible operation does not mean that no problem will ever occur.

It means the process can identify the problem, verify the facts and produce correction.

A well-written standard should therefore connect the measured condition to a response:

• Green: operating within the standard.
• Yellow: approaching a threshold, missing information or requiring corrective attention.
• Red: exceeding the standard, failing a material commitment or requiring escalation.

The exact response should fit the issue. A missed report may require submission and verification. A noise exceedance may require operational changes and retesting. A serious safety condition may require immediate notification and shutdown procedures.

Flexibility should exist in how a problem is corrected, not in whether the standard matters.

Existing law, negotiated conditions and proposed authority

Not every TRSP standard rests on the same legal authority.

Some standards can be incorporated now into tax-abatement agreements, road-use agreements, development agreements and other discretionary county actions.

Some protections already fall within the jurisdiction of state agencies, municipalities, groundwater conservation districts or other public bodies.

Other standards may require additional authority proposed through the Texas Resource Stewardship Initiative.

The review record should identify which category applies:

• Existing legal requirement.
• Condition negotiated in exchange for discretionary public support.
• Technical standard used to evaluate evidence.
• Voluntary commitment made by the applicant.
• Authority that requires legislative action.

Clear authority is part of a clear standard. The public should not be told that a condition is enforceable when the county lacks the power or agreement needed to enforce it.

A standard creates a shared measuring point

Clear standards are not only protections for the public.

They also give responsible applicants a way to show that their project has been designed carefully and is operating as promised.

They give county officials a consistent basis for decisions.

They give residents a record they can follow.

They give operators a known path for correcting problems.

That is the purpose of the standards applied through TRSP:

• Define responsible performance.
• Identify the evidence needed.
• Record measurable commitments.
• Verify the results.
• Correct problems when they occur.

The next step is deciding what happens when the evidence shows that a project cannot yet meet one or more of those standards.

That will be the subject of Part Eight.

Continue exploring

• TRSP in Plain Language
• How the Three Pillars Work Together
• Pillar One: Good Neighbor Policy
• Pillar Two: Texas Resource Stewardship Initiative
• Pillar Three: Industrial Monitoring and Enforcement
• What Triggers a Large-Impact Project Review?
• Large-Impact Project Review
• Large-Impact Project Standards and Conformance Review
• TRSP Resource Library

Let’s keep building.

Shared Resources. Shared Standards. Shared Stewardship.