Evidence explainer
A Texas construction filing is strong evidence of activity, not proof of completion
TDLR records can establish a named building, owner, scope, cost and schedule. They still need to be matched carefully to the wider campus and delivery story.
Examples from public Texas Department of Licensing and Regulation Architectural Barriers records reviewed on 22 September 2026.
Construction filings are among the most useful sources in a Texas data-centre dossier because they can move a project beyond a press release. They can also be misread if a building-level record is silently turned into a campus-level conclusion.
TDLR’s Architectural Barriers records often identify the facility, owner, location, stated scope, square footage, estimated cost and planned dates. That makes them valuable for confirming that a real construction programme exists at a specific address.
A filing can materially strengthen the record
For example, a June 2026 TDLR record for Project Eagle - Building D in Wharton County identifies Amazon Data Services as owner, describes new data-centre construction, gives a stated 189,060 square feet and lists an estimated cost of $300 million. TDLR Project Eagle record.
A separate July record for AUS02 Building 2 in Bell County identifies Rowan Digital Infrastructure as owner, describes a 500,000-square-foot data-centre building and lists an estimated project cost of $780 million. TDLR AUS02 record.
Those are much stronger signals than an unattributed market rumour. They anchor activity to a named owner, place and building scope.
But the filing still has boundaries
TDLR dates are planned project dates in the filing record; they are not the same thing as independent confirmation that the building started or finished on schedule. Likewise, an estimated construction cost in the filing should not automatically be treated as total campus capital expenditure.
The same issue applies to scope. Microsoft’s SAT82 filing in Medina County describes a specific building and a stated construction programme. That is evidence about that filed project. It should not be multiplied across a wider campus unless other records establish the relationship. TDLR SAT82 record.
Match the filing before you use it
The first diligence task is entity and site matching. Does the filing owner correspond to the project developer or a project vehicle already in the dossier? Does the address map to the same parcel? Is the building name a phase of an existing campus or a separate project?
A strong match lets the filing support construction status, cost, size and schedule fields at the correct level. A weak match should remain a lead until corroborated.
What to seek next
Once a construction filing is linked, look for the rest of the delivery chain: land control, permits or inspections, electrical works, utility or ERCOT evidence, procurement milestones and tenant evidence where relevant.
No single source has to prove the entire project. The point is to build a chain in which each record proves exactly what it can support and no more.