Government Robot Procurement, Surveillance, and Records

Published October 18, 2026

Law checked through October 18, 2026.

A Texas public entity must establish authority for the proposed robotic mission, use the purchasing law applicable to that buyer, and address operational rules, data, records, and security restrictions. Buying a robot does not authorize a search or use of force. State agencies, municipalities, counties, and school districts have different procurement provisions, and public-information obligations can reach vendor-held records. [1; 2; 3; 4; 5]

Begin with the public function

The agency should identify the mission, legal authority, places of operation, affected people, supervision, and expected information. A public reception robot, inspection crawler, school device, and police robot raise different operational issues. Constitutional and sector-specific limits should be evaluated before a procurement specification assumes the capability will be used. [6; 7]

The acquisition record should also identify who approves new functions after deployment. A robot initially purchased for inspection can later receive surveillance, identification, or remote-control features. The original purchase approval does not automatically establish authority for each added mission.

Use the correct purchasing framework

Government Code Chapter 2155 contains state purchasing rules, and Chapter 2157 addresses automated information systems within its scope. Municipal purchasing under Local Government Code Chapter 252, county purchasing under Chapter 262, and school purchasing under Education Code § 44.031 require separate treatment. Thresholds, methods, exceptions, delegations, and available contracts should be checked for the actual buyer and transaction. [1; 2; 3; 4]

A robot package may include equipment, software, cloud service, connectivity, maintenance, and professional work. The purchaser should identify the proper method and total arrangement rather than split related components to assume a preferred exception. A pilot, donation, or subscription can still create public duties and contractual commitments requiring review.

Specifications and acceptance

Recommended specifications define the task, environment, safety assumptions, human control, data handling, support life, and measurable acceptance criteria. NIST response-robot methods can support repeatable mission-capability tests, but NIST does not thereby certify the legal suitability of a public program. The procurement should identify the evidence supporting the actual intended use. [8]

Acceptance should connect test results with the delivered configuration. The buyer should address failed tests, corrective work, warranty start, payment, changes, and suspension of unsafe operation. A successful demonstration on a vendor's course is not the same as verified performance at a school, port, utility site, or emergency scene.

Surveillance and public interaction

Police or emergency missions require analysis of search authority and other constitutional constraints. The Fourth Amendment inquiry depends on the actual conduct and circumstances; using a robot does not eliminate it. Drone image capture also requires Chapter 423 analysis, including warrants, exceptions, reporting, and restrictions on use or disclosure. [6; 7]

TRAIGA contains government-specific provisions, including consumer-interaction disclosure and targeted prohibitions. The definition of governmental entity and each provision's wording should be read rather than assuming every public institution is treated identically. Procurement should obtain the information needed to implement any applicable notice and to document the system's purpose and limits. [9, §§ 552.001 and 552.051 through 552.054]

Records retention and vendor access

Chapter 552 defines public information broadly within its statutory conditions. Data does not necessarily cease to be public information because a vendor stores it. The agreement should address agency access, exports, search assistance, retention, deletion, security, and transition when the contract ends. [5, § 552.002]

Confidentiality is record-specific. Law-enforcement, privacy, statutory confidentiality, and trade-secret provisions require the actual conditions of the claimed exception. A vendor's confidential label or a general contract promise does not automatically establish lawful withholding. The agency should coordinate public-information requests with retention schedules, legal holds, and applicable confidential-data controls. [5, §§ 552.101, 552.108, and 552.110]

Sourcing and continuing oversight

Federal drone procurement and funding restrictions, FCC equipment authorization, and Texas prohibited-technology policies address different questions. Buyer identity, source of funds, equipment, vendor, exceptions, and effective dates determine applicability. The purchasing file should retain the actual authority and current eligibility evidence rather than a general statement that the product is approved for government use. [10]

Continuing oversight should cover software changes, new data uses, incident reports, support access, and end of life. Contractual ownership of a robot is insufficient if the agency cannot operate it safely or retrieve its records after a vendor exits. Those implementation controls should be connected to the purchasing method and legal duties identified at the outset.