{"id":231971,"date":"2026-04-04T01:10:43","date_gmt":"2026-04-03T17:10:43","guid":{"rendered":"https:\/\/publicinput.com\/wp\/?p=231971"},"modified":"2026-04-04T01:11:02","modified_gmt":"2026-04-03T17:11:02","slug":"the-hidden-compliance-risk-in-how-dots-collect-public-comments","status":"publish","type":"post","link":"https:\/\/publicinput.com\/wp\/2026\/04\/04\/the-hidden-compliance-risk-in-how-dots-collect-public-comments\/","title":{"rendered":"The Hidden Compliance Risk in How DOTs Collect Public Comments"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Is Your Project Manager\u2019s Inbox a Public Record?\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Picture a scene that plays out every day across state transportation agencies. A project manager finalizes a public meeting notice, scrolls to the bottom, and adds their email address as the contact for comments. It takes seconds. It feels helpful. It gives the public a direct line to the person who knows the project best.

<\/span><\/p>

Over the next few weeks, comments arrive. They land alongside meeting invites, contractor questions, and internal review requests. The comment period closes. The project advances. The project manager moves on.

<\/span><\/p>

So what happens to those comments?

<\/span><\/p>

Under federal law, the answer is not flexible. For many agencies, current practice does not align with what the regulations require.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

What the Regulation Actually Requires\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Federal transportation law is explicit about how public input must be handled and documented.

<\/span><\/p>

For federally funded highway projects, <\/span>23 CFR \u00a7 771.111(h)(2)(vi)<\/span><\/a><\/span> requires that agencies include written statements from the public received during the announced comment period as part of the official project record submitted to FHWA.

<\/span><\/p>

That phrase, announced comment period, matters. The moment an email address is listed as a submission channel, messages received through that channel may be considered part of the public record for the project.

<\/span><\/p>

A parallel requirement in <\/span>23 CFR \u00a7 450.210(a)<\/span><\/a><\/span> requires agencies to maintain a documented public involvement process.
A process that exists within an individual inbox does not meet the intent of a documented, consistent, and auditable public involvement process.

<\/span><\/p>

For Environmental Assessments, <\/span>23 CFR \u00a7 771.119(g)<\/span><\/a><\/span> requires that, as applicable, agencies provide FHWA with comments received and responses to those comments when recommending a Finding of No Significant Impact (FONSI).

<\/span><\/p>

In practice, this means agencies must be able to account for comments received and demonstrate how they were addressed.

<\/span><\/p>

While specific documentation requirements may vary depending on project type and level of environmental review, the expectation of a complete and accessible public comment record is consistent across federal guidance.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Why a Personal Inbox Creates a Real Compliance Risk\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This is not a theoretical concern. When public comments are routed through individual email accounts, several predictable issues can arise.
<\/span><\/p>