Policies and Procedures Update on TDA Article 3 (Res. 4108) I. Update to list of eligible project types
I. BPAC requirement revision
II. Additional application and invoice documentation
*Will not include non-construction projects*
III. Formalize Extension request process
Description Rationale
Capital purchases for maintenance of Class I
or Class IV separated bikeways such as
compact street sweeping vehicles
Various sponsors have expressed concerns that
the future cost of maintenance on separated
bikeways or multi-use trails has been an
obstacle in pursuing projects
Description Rationale
Change language regarding BPAC
involvement; Countywide BPAC or equivalent
body shall review and adopt an annual list of
projects to submit for funding. Each project
shall include a statement of review and
funding recommendation
To clarify BPAC’s role in the project selection
process
Description Rationale
Request sponsors to provide a mapped link of
the project site in their application
This additional documentation will be part of an
eƯort to collect data for future public facing
mapping tool of completed and in progress
projects
In addition to the paragraph summary of the
work completed with final reimbursement
request, sponsors shall submit to MTC a
photo(s) of the completed project.
This additional documentation will be part of an
eƯort to collect data for future public facing
mapping tool of completed and in progress
projects.
Description Rationale
If a project cannot be completed within the
time allowed, a claimant may request an
extension through the county coordinator.
County coordinators will coordinate time
extensions with claimants by requesting a
written status update of the given project and
a summary of all expenditures to date. County
coordinators will submit a list of extension
requests with supporting materials to MTC no
later than three months before the project
sunset date (March 31th). MTC staƯ will review
the list of extension requests and recommend
approval
Policies and procedures do not formalize
process for extensions, nor do we collect
documentation of extension requests;
Attachment 3