Member Designated Projects

The Committee on Transportation and Infrastructure will soon begin the process of considering a long-term reauthorization of surface transportation programs, with Committee action expected later this spring.Any requests submitted to the Committee will be posted online in accordance with Committee guidance to ensure transparency and accountability.

All submissions are due to the office by April 9th, 2021


Required fields are followed by *.
General Project Information

In order to qualify to receive designated funding, projects must be eligible under title 23, United States Code, or chapter 53 of title 49, United States Code. Projects included on the STIP or TIP have been vetted and do not require further verification of eligibility. If the project is not on the STIP or TIP, further documentation will be required. See additional questions.

Ex: Federal Highways Administration (FHWA), Federal Railroad Administration (FRA), Maritime Administration (MARAD), etc.

Provide a short name by which the project will be labelled. This name will be listed in legislative text and the Committee on Transportation and Infrastructure legislative report and should provide accurate information to identify the exact project being funded. If the project is on the STIP or TIP, or if you have other information from your state or local transportation agency or transit agency about the formal name of the project, please use that information in the project request.

Location of Project
Sponsor Information

List the public agency that is sponsoring the project – a state DOT, MPO, transit agency, local government, territory, Tribal government or other public entity. Requests for projects listed on the STIP or TIP, or in some cases the long range transportation plan, will be most successful in receiving designated funding. The Committee seeks to ensure that designated funds will be able to be obligated by an entity versed in the requirements and process of advancing a project with federal surface transportation funding. Please list only one project sponsor—the entity that will be responsible for carrying out the project. Not-for-profit organizations should coordinate with a public entity that is an eligible recipient of federal-aid funds under title 23 or chapter 53 of title 49.

Provide a name, phone number, and email for a point of contact at the public agency that is sponsoring the project.

Specific Project Information

If the project is on the STIP or TIP, the description of the project as listed on those documents should be incorporated. If the project has a project website, please include a link.

In listing project benefits, please include any benefits, if applicable, to help advance the goals of the surface transportation authorization legislation.

Please provide the amount of funding requested for the project.

The requested amount may not exceed the federal share allowable under highway and transit programs, which is typically 80 percent of the project cost. However, there are exceptions to this standard. More information is here for FHWA projects and here for FTA projects.

In addition to identifying non-federal match, the Committee is requiring that project requests identify all funds necessary for the project in addition to the requested amount, to ensure the project can advance in a reasonable timeframe. Please see question † and question ‡, if applicable. The Committee will not designate funding for projects for which the requested amount represents a portion of the project costs, without the remainder of funding identified.

Describe the community benefits and goals of the project. Please be succinct.

Please provide the total project cost. This information must come from the state DOT, local transportation agency, transit agency, territory, Tribal government, or other project sponsor. Please check the STIP or TIP for this amount.

In addition to the statutory requirements for non-federal match, if the requested amount plus the non-federal match does not fully make up the total project cost, the Committee is requiring that projects have funds identified for the project outside of the requested amount. This requirement is to ensure the project can advance in a reasonable timeframe and that designated funds do not sit unspent.

Additional amounts may come from federal funding, such as FHWA formula funding, provided that the total amount of federal funding does not exceed the allowable federal cost share.

Acknowledgement of the availability of this funding for this purpose by the state DOT or other public agency that administers this funding is required. All funding does not have to be “in the bank” at the time of the request, but the specific sources must be identified and reasonably expected to be available within the obligation window. The STIP or TIP is the easiest way to identify project funding. If a project is on the STIP or TIP, funding reasonably expected to be available is sufficient to ensure the project is obligated within the period of availability for the project funding. If you choose to request a project not on the STIP or TIP, it is the responsibility of the requesting office to demonstrate identified funding to the Committee, and commitment by the transportation agency that controls the identified funding to use those funds on the project. The Committee will not designate funding for projects for which the requested amount represents a portion of the project costs, without the remainder of funding identified.



Documents must be the following file types: .doc, .docx, .pdf, .txt
All documents must be less than 500kb total.
Macintosh users: Your document must have a file extension. Resave it using your word processor with the appropriate extension from the above list.

Please select the status of environmental review for the project from the options provided. These options are recognized phases of the environmental review process carried out to satisfy NEPA. Pre-review

Projects that are on an approved STIP or TIP that have been through public comment do not need to solicit additional public comment. If the project has solicited public input as it advanced through the NEPA process, that can also be cited under this question.

The Committee is requiring demonstrated support from the sponsor of the project to accompany each request. The submission must be on letterhead from a public agency responsible for carrying out the project, and must include an expression of willingness to carry out the project and the ability for the funding to be obligated within the time period set forth under federal-aid highway or federal transit requirements.

Each project request must be accompanied by a letter, on the Member’s letterhead and signed by the Member (electronic signature accepted), certifying that the Member, their spouse, and other immediate family members do not have a financial interest in the project, and an explanation as to why it is an appropriate use of taxpayer funds will be required for submission. For the purposes of this certification, the term ‘‘immediate family’’ means an individual who is related to the Member, Delegate, or Resident Commissioner, as father, mother, son, daughter, brother, sister, husband, wife, father-in-law, mother- in-law, son-in-law, or daughter-in-law. Further guidance, sample language, and required information to be included in the letter is available here and on the homepage of the database.



Documents must be the following file types: .doc, .docx, .pdf, .txt
All documents must be less than 500kb total.
Macintosh users: Your document must have a file extension. Resave it using your word processor with the appropriate extension from the above list.

If the project is not on the STIP, please see question § for additional requirements.

Documentation that the project is on the STIP is a clear way to document project readiness and funding availability beyond the requested amount and demonstrates that a transportation agency is ready and able to carry out a project consistent with federal requirements.



Documents must be the following file types: .doc, .docx, .pdf, .txt
All documents must be less than 500kb total.
Macintosh users: Your document must have a file extension. Resave it using your word processor with the appropriate extension from the above list.

If the project is not on the TIP, because the project is not located in a metropolitan planning area, please select option b, not applicable.

If the project is not on the TIP but the project is located in a metropolitan planning area, please see question for additional requirements.



Documents must be the following file types: .doc, .docx, .pdf, .txt
All documents must be less than 500kb total.
Macintosh users: Your document must have a file extension. Resave it using your word processor with the appropriate extension from the above list.

If the answer is yes, the Committee is requesting a letter from the agency indicating this is the case. If the answer is no, that is a likely indicator that the project may not be ready for designated funding.

Only answer this question if you are requesting a project that is not on the STIP or TIP. While the Committee realizes that the timeframe to submit projects into the database is short, ensuring projects are eligible for funding is a fundamental requirement for project designation. Offices will only have to seek confirmation of project eligibility from the relevant U.S. DOT agency if the requested project is not on the STIP or TIP and if the requesting office is unable to verify that the project can be added to the STIP or TIP in a reasonable timeframe (see question ‡).

If the project is not on the STIP or TIP, inclusion of a project or a suite of projects on a statewide, regional, or local transportation plan will help to indicate whether the project has had a sufficient level of planning and scoping to advance in a reasonable timeframe. If the project is not on the STIP or TIP or a long-range plan, that is a likely indicator that the project may not be ready for designated funding.

Please include the name(s) of the coordinating Member office of which you are submitting the same project request for. The project names on both Member requests should be identical. Request amounts should be coordinated between the project sponsor and any other members making requests for the same project.