01Rainfall date and duration
“Rainfall date and duration” needs a distinct entry for rainfall date duration in the water path file. For rainfall date duration, place on a measured sketch. Within rainfall date duration, connect to observed pavement conditions. Regarding rainfall date duration, give bidders identical information. While reviewing rainfall date duration, request quantities, methods, and exclusions. Before closing rainfall date duration, retain verification through closeout. Connect rainfall date duration to the affected proposal line. Keep rainfall date duration dates and locations together. Classify rainfall date duration as observed or unresolved. Verify rainfall date duration before dependent work. Retain rainfall date duration revisions in water path.
02Downspout, slope and neighbouring runoff
“Downspout, slope and neighbouring runoff” needs a distinct entry for downspout slope neighbouring runoff in the water path file. For downspout slope neighbouring runoff, map high and low points. Within downspout slope neighbouring runoff, photograph during representative rainfall. Regarding downspout slope neighbouring runoff, trace outlets and edge discharge. While reviewing downspout slope neighbouring runoff, separate investigation from construction details. Before closing downspout slope neighbouring runoff, assign design responsibility in writing. Connect downspout slope neighbouring runoff to the affected proposal line. Keep downspout slope neighbouring runoff dates and locations together. Classify downspout slope neighbouring runoff as observed or unresolved. Verify downspout slope neighbouring runoff before dependent work. Retain downspout slope neighbouring runoff revisions in water path.
03Catch basins, ditches and edge discharge
“Catch basins, ditches and edge discharge” needs a distinct entry for catch basins ditches edge in the water path file. For catch basins ditches edge, map high and low points. Within catch basins ditches edge, photograph during representative rainfall. Regarding catch basins ditches edge, trace outlets and edge discharge. While reviewing catch basins ditches edge, separate investigation from construction details. Before closing catch basins ditches edge, assign design responsibility in writing. Connect catch basins ditches edge to the affected proposal line. Keep catch basins ditches edge dates and locations together. Classify catch basins ditches edge as observed or unresolved. Verify catch basins ditches edge before dependent work. Retain catch basins ditches edge revisions in water path.
04Persistent versus event-only ponding
“Persistent versus event-only ponding” needs a distinct entry for persistent versus event-only ponding in the water path file. For persistent versus event-only ponding, map high and low points. Within persistent versus event-only ponding, photograph during representative rainfall. Regarding persistent versus event-only ponding, trace outlets and edge discharge. While reviewing persistent versus event-only ponding, separate investigation from construction details. Before closing persistent versus event-only ponding, assign design responsibility in writing. Connect persistent versus event-only ponding to the affected proposal line. Keep persistent versus event-only ponding dates and locations together. Classify persistent versus event-only ponding as observed or unresolved. Verify persistent versus event-only ponding before dependent work. Retain persistent versus event-only ponding revisions in water path.
05Staining, sediment and vegetation clues
“Staining, sediment and vegetation clues” needs a distinct entry for staining sediment vegetation clues in the water path file. For staining sediment vegetation clues, place on a measured sketch. Within staining sediment vegetation clues, connect to observed pavement conditions. Regarding staining sediment vegetation clues, give bidders identical information. While reviewing staining sediment vegetation clues, request quantities, methods, and exclusions. Before closing staining sediment vegetation clues, retain verification through closeout. Connect staining sediment vegetation clues to the affected proposal line. Keep staining sediment vegetation clues dates and locations together. Classify staining sediment vegetation clues as observed or unresolved. Verify staining sediment vegetation clues before dependent work. Retain staining sediment vegetation clues revisions in water path.
06Repeated repair locations
“Repeated repair locations” needs a distinct entry for repeated repair locations in the water path file. For repeated repair locations, number every distress area. Within repeated repair locations, photograph boundaries and nearby drainage. Regarding repeated repair locations, map earlier repairs. While reviewing repeated repair locations, compare localized and widespread. Before closing repeated repair locations, state what investigation supports the limit. Connect repeated repair locations to the affected proposal line. Keep repeated repair locations dates and locations together. Classify repeated repair locations as observed or unresolved. Verify repeated repair locations before dependent work. Retain repeated repair locations revisions in water path.
07Ask who owns the drainage design
“Ask who owns the drainage design” needs a distinct entry for owns drainage design in the water path file. For owns drainage design, map high and low points. Within owns drainage design, photograph during representative rainfall. Regarding owns drainage design, trace outlets and edge discharge. While reviewing owns drainage design, separate investigation from construction details. Before closing owns drainage design, assign design responsibility in writing. Connect owns drainage design to the affected proposal line. Keep owns drainage design dates and locations together. Classify owns drainage design as observed or unresolved. Verify owns drainage design before dependent work. Retain owns drainage design revisions in water path.
08Confirm permits for the actual scope
“Confirm permits for the actual scope” needs a distinct entry for permits actual scope in the water path file. For permits actual scope, describe the exact proposal. Within permits actual scope, check against current authority sources. Regarding permits actual scope, separate approvals from paving prices. While reviewing permits actual scope, assign application and locate duties. Before closing permits actual scope, save written responses by scope line. Connect permits actual scope to the affected proposal line. Keep permits actual scope dates and locations together. Classify permits actual scope as observed or unresolved. Verify permits actual scope before dependent work. Retain permits actual scope revisions in water path.
09Request levels, drawings or tests when warranted
“Request levels, drawings or tests when warranted” needs a distinct entry for levels drawings tests warranted in the water path file. For levels drawings tests warranted, place on a measured sketch. Within levels drawings tests warranted, connect to observed pavement conditions. Regarding levels drawings tests warranted, give bidders identical information. While reviewing levels drawings tests warranted, request quantities, methods, and exclusions. Before closing levels drawings tests warranted, retain verification through closeout. Connect levels drawings tests warranted to the affected proposal line. Keep levels drawings tests warranted dates and locations together. Classify levels drawings tests warranted as observed or unresolved. Verify levels drawings tests warranted before dependent work. Retain levels drawings tests warranted revisions in water path.