Who manages approvals for sensor pilots in Washington, DC?

Approvals are coordinated by city technology and permitting offices, typically the Office of the Chief Technology Officer (OCTO) and District Department of Transportation (DDOT).

Are there standard privacy requirements?

Projects must document data categories, retention, access controls, and perform privacy impact assessments where personal data may be collected.

What penalties apply for non-compliance?

Penalties depend on permit and contract terms; specific fine amounts are not listed on the cited OCTO guidance page and vary by enforcing office.

Washington Smart City Sensor Pilot Ordinance Guide

Technology and Data District of Columbia 3 Minutes Read · published February 07, 2026

Overview

Washington, District of Columbia is advancing pilot deployments of smart city sensors to improve traffic, environmental monitoring, and city services while balancing privacy and local rules. Pilots are typically coordinated by city technology and transportation offices and require advance review of data practices, site permissions, and community outreach. For guidance on pilot coordination and technical standards see the Office of the Chief Technology Officer's Smart Cities information page: OCTO Smart Cities^[1].

Sensor pilots that collect personal data commonly trigger privacy and data-use reviews.

Pilot process and approvals

Pilot proposals usually follow these steps: scope definition, technical design, privacy and civil liberties review, site and rights-of-way permissions, and a defined pilot period with reporting obligations. Responsible city units include the Office of the Chief Technology Officer (OCTO) and District Department of Transportation (DDOT), which coordinate permits, data-sharing agreements, and operational oversight.

Prepare a project summary describing sensors, data types, retention, and purpose.
Conduct a privacy impact assessment and publish required notices to the public.
Obtain site permits or right-of-way approvals from DDOT or other property owners.
Coordinate community outreach and stakeholder briefings with affected neighborhoods.

Penalties & Enforcement

Enforcement for non-compliance with pilot terms, data-use agreements, or permit conditions is administered by the responsible agencies (typically OCTO, DDOT, or other permitting offices). Specific monetary fines for sensor pilot violations are not specified on the cited OCTO guidance page; enforcement relies on contract, permit conditions, and administrative remedies.

Fine amounts: not specified on the cited page; penalties depend on permit or contract terms and administrative orders.
Escalation: first and repeat offences are handled through notices of violation, corrective orders, and potential suspension or termination of pilot permissions; exact escalation steps are not specified on the cited page.
Non-monetary sanctions: corrective orders, mandatory data deletion, suspension/termination of pilot, revocation of right-of-way permits, and referral to enforcement counsel or law enforcement.
Enforcer and complaint pathways: complaints or suspected violations are reported to the operating department (OCTO or DDOT) and may be escalated to permit offices or the Office of the Attorney General for civil enforcement.
Appeals and review: administrative appeals or requests for review typically follow agency-specific procedures; explicit time limits for appeals are not specified on the cited page and will depend on the enforcing office and the controlling permit or ordinance.

If your project collects imagery or personal data, prepare a clear retention and access plan before applying.

Applications & Forms

There is no single published, citywide "smart sensor pilot" application form available on the OCTO Smart Cities guidance page; pilots generally require a combination of agency-specific permit applications, data-sharing agreements, and privacy impact assessments depending on scope and location.

Operational compliance and common violations

Common compliance checks include data minimization, retention limits, signage, and adherence to permited locations and times. Typical violations and consequences include:

Unauthorized data collection at unapproved locations — may trigger corrective orders or suspension.
Failure to complete or publish a privacy impact assessment — may delay approval or require mitigation actions.
Installation without required permits for right-of-way or infrastructure — may result in removal and restoration orders.

FAQ

Who manages approvals for sensor pilots in Washington, DC?: Approvals are coordinated by city technology and permitting offices, typically the Office of the Chief Technology Officer (OCTO) and District Department of Transportation (DDOT).
Are there standard privacy requirements?: Yes. Projects must document data categories, retention, access controls, and perform privacy impact assessments where personal data may be collected.
What penalties apply for non-compliance?: Penalties depend on permit and contract terms; specific fine amounts are not listed on the cited OCTO guidance page and vary by enforcing office.

How-To

Define the pilot scope and list all sensor types and data categories to be collected.
Prepare a privacy impact assessment and data management plan describing retention, access, and publication.
Contact OCTO and DDOT early to confirm necessary permits, right-of-way approvals, and agency contacts.
Conduct community outreach in affected areas and publish notice of the pilot where required.
Execute required agreements, secure permits, and schedule inspections or progress reporting as stipulated by agency approvals.

Key Takeaways

Coordinate early with OCTO and DDOT to identify required permits and privacy reviews.
Document data practices thoroughly to avoid delays and enforcement actions.