Amendment Documentation. Amendment documentation will be grouped in a single electronic document with the naming convention, "Amendment [X] ([Project#])'', where [X] identifies the amendment's sequential identifier and [Project #] represents the unique project number(s) of the program element(s) being amended. Email correspondence will use the naming convention, "Amendment [X], [Organization]" in the subject line where [X] identifies the amendment's sequential identifier and [Organization] represents name of the organization (MPO) submitting the amendment. The body of the email or cover letter/project description within the packet will include all applicable information as needed such as: amendment number, PIN, STIP/TIP ID, project sponsor, location of project, route, termini, project description, funding type (e.g., STBG, 5310), length, and description of amendment. Correspondence will include ccs to the appropriate representatives within TDOT’s Long Range Planning Division and/or Multimodal Resources Division.
Appears in 2 contracts