Section 2: Procedure for Archiving Design Notes


Scan Notes

Scan the notes (or convert electronic files) and gather them into a single PDF file. Create separate PDF files for each bridge. In the case of a single design done for twin structures, submit the same notes under two separate NBI numbers.

A hard copy of computer software input files is not required. Hard copies of computer software output should be included with the following:

    Anchor: #ENETPSKF
  • Input echo
  • Anchor: #BISNOPKG
  • Key pages of output, annotated by hand if necessary, such that the design's outcome, including controlling load case and limit state, can be understood by review of the output annotation.
  • Anchor: #LYKDVULC
  • Key pages of output, annotated by hand if necessary demonstrating that other load cases and limit states do not control the outcome of the design.

Include the following required design elements in the PDF file:

Additionally, the file should contain:


Naming Convention

Name the file using the following naming convention:

    Anchor: #HPPOVFBF
  • Design notes: NBI_DN_yyyy-mm, with yyyy-mm being the year and month the PDF file is submitted (ex. 1234567890abcde_DN_2015-01)
  • Anchor: #MUHGHPSE
  • Change Orders: NBI_CO_yyyy-mm (ex. 1234567890abcde_CO_2015-01)

Delivering the File

Deliver the PDF file using DropBox, at

If the PDF is created by a Consultant designer, the Consultant sends the PDF bridge design notes to the TxDOT contract manager or the District Bridge Engineer, who will submit the notes at the DropBox link above.

Once the file has been uploaded, the auto-generated email will serve as notification to the Bridge Management Group that files have been received. The Bridge Management Group is responsible for transferring the files into TxDOT’s bridge inspection database management system, where they will become part of the permanent bridge file.

Previous page  Title page