PROJECT CONTACT

Tell Us About the Site

A concise description is enough to begin. Include the property, what you observe and the decision you are trying to make.

ASPHALT PROJECT INTAKE

Send the site facts

Name the property, the observed surface condition and the decision ahead. The public form stays deliberately short.

01

Do not enter payment or sensitive personal information

“Do not enter payment or sensitive personal information” needs a distinct entry for do not enter payment in the project contact file. For do not enter payment, place on a measured sketch. Within do not enter payment, connect to observed pavement conditions. Regarding do not enter payment, give bidders identical information. While reviewing do not enter payment, request quantities, methods, and exclusions. Before closing do not enter payment, retain verification through closeout. Connect do not enter payment to the affected proposal line. Keep do not enter payment dates and locations together. Classify do not enter payment as observed or unresolved. Verify do not enter payment before dependent work. Retain do not enter payment revisions in project contact.

02

Photos are not collected by this form

“Photos are not collected by this form” needs a distinct entry for photos are not collected in the project contact file. For photos are not collected, place on a measured sketch. Within photos are not collected, connect to observed pavement conditions. Regarding photos are not collected, give bidders identical information. While reviewing photos are not collected, request quantities, methods, and exclusions. Before closing photos are not collected, retain verification through closeout. Connect photos are not collected to the affected proposal line. Keep photos are not collected dates and locations together. Classify photos are not collected as observed or unresolved. Verify photos are not collected before dependent work. Retain photos are not collected revisions in project contact.

03

Confirm the Abbotsford asphalt response path

“Confirm the Abbotsford asphalt response path” needs a distinct entry for abbotsford asphalt response path in the project contact file. For abbotsford asphalt response path, place on a measured sketch. Within abbotsford asphalt response path, connect to observed pavement conditions. Regarding abbotsford asphalt response path, give bidders identical information. While reviewing abbotsford asphalt response path, request quantities, methods, and exclusions. Before closing abbotsford asphalt response path, retain verification through closeout. Connect abbotsford asphalt response path to the affected proposal line. Keep abbotsford asphalt response path dates and locations together. Classify abbotsford asphalt response path as observed or unresolved. Verify abbotsford asphalt response path before dependent work. Retain abbotsford asphalt response path revisions in project contact.

04

State driveway, parking, lane or loading use

“State driveway, parking, lane or loading use” needs a distinct entry for driveway parking lane loading in the project contact file. For driveway parking lane loading, plot routes by operating period. Within driveway parking lane loading, separate vehicle and pedestrian movement. Regarding driveway parking lane loading, protect delivery and emergency access. While reviewing driveway parking lane loading, name zones that remain usable. Before closing driveway parking lane loading, define reopening evidence by phase. Connect driveway parking lane loading to the affected proposal line. Keep driveway parking lane loading dates and locations together. Classify driveway parking lane loading as observed or unresolved. Verify driveway parking lane loading before dependent work. Retain driveway parking lane loading revisions in project contact.

05

Describe distress and drainage observations

“Describe distress and drainage observations” needs a distinct entry for distress drainage observations in the project contact file. For distress drainage observations, map high and low points. Within distress drainage observations, photograph during representative rainfall. Regarding distress drainage observations, trace outlets and edge discharge. While reviewing distress drainage observations, separate investigation from construction details. Before closing distress drainage observations, assign design responsibility in writing. Connect distress drainage observations to the affected proposal line. Keep distress drainage observations dates and locations together. Classify distress drainage observations as observed or unresolved. Verify distress drainage observations before dependent work. Retain distress drainage observations revisions in project contact.

06

Name access, traffic and timing constraints

“Name access, traffic and timing constraints” needs a distinct entry for access traffic timing constraints in the project contact file. For access traffic timing constraints, plot routes by operating period. Within access traffic timing constraints, separate vehicle and pedestrian movement. Regarding access traffic timing constraints, protect delivery and emergency access. While reviewing access traffic timing constraints, name zones that remain usable. Before closing access traffic timing constraints, define reopening evidence by phase. Connect access traffic timing constraints to the affected proposal line. Keep access traffic timing constraints dates and locations together. Classify access traffic timing constraints as observed or unresolved. Verify access traffic timing constraints before dependent work. Retain access traffic timing constraints revisions in project contact.

07

Keep known facts separate from assumptions

“Keep known facts separate from assumptions” needs a distinct entry for known facts separate assumptions in the project contact file. For known facts separate assumptions, place on a measured sketch. Within known facts separate assumptions, connect to observed pavement conditions. Regarding known facts separate assumptions, give bidders identical information. While reviewing known facts separate assumptions, request quantities, methods, and exclusions. Before closing known facts separate assumptions, retain verification through closeout. Connect known facts separate assumptions to the affected proposal line. Keep known facts separate assumptions dates and locations together. Classify known facts separate assumptions as observed or unresolved. Verify known facts separate assumptions before dependent work. Retain known facts separate assumptions revisions in project contact.

08

Save current City and property records

“Save current City and property records” needs a distinct entry for current city property records in the project contact file. For current city property records, describe the exact proposal. Within current city property records, check against current authority sources. Regarding current city property records, separate approvals from paving prices. While reviewing current city property records, assign application and locate duties. Before closing current city property records, save written responses by scope line. Connect current city property records to the affected proposal line. Keep current city property records dates and locations together. Classify current city property records as observed or unresolved. Verify current city property records before dependent work. Retain current city property records revisions in project contact.

09

Record scope changes and verification responsibility

“Record scope changes and verification responsibility” needs a distinct entry for scope changes verification responsibility in the project contact file. For scope changes verification responsibility, issue identical facts to bidders. Within scope changes verification responsibility, normalize quantities and terminology. Regarding scope changes verification responsibility, separate fixed work from allowances. While reviewing scope changes verification responsibility, define change authorization in writing. Before closing scope changes verification responsibility, retain completion and maintenance records. Connect scope changes verification responsibility to the affected proposal line. Keep scope changes verification responsibility dates and locations together. Classify scope changes verification responsibility as observed or unresolved. Verify scope changes verification responsibility before dependent work. Retain scope changes verification responsibility revisions in project contact.

Keep observation and diagnosis separate.

Observe from stable, accessible areas. Excavation, grade design and pavement specifications require qualified review for the actual site.

ABBOTSFORD SOURCE LEDGER

Verify the boundary before the method

Use the City source for the actual address and proposal. Competitive pages only describe the published result set.