14.10.2013 Views

Construction Program Management and Inspection Guide

Construction Program Management and Inspection Guide

Construction Program Management and Inspection Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Both photographs <strong>and</strong> sketches are recommended, as<br />

they can be of considerable value in depicting details,<br />

providing documentation, <strong>and</strong> reducing the report writing<br />

effort. Digital cameras are recommended.<br />

Steps in Evalution<br />

1. Record Facts<br />

Facts are irrefutable: what is seen, what is recorded, what<br />

test results demonstrate, what actions are taken.<br />

2. Make Observations<br />

Observations may be factual or they may only represent the<br />

project as the inspecting engineer sees it. If an observation<br />

can be disputed, it should be supported. FHWA engineers<br />

may request that additional inspections, measurements, or<br />

tests be performed to verify opinions or satisfy concerns (see<br />

23 CFR Subsections 1.5 <strong>and</strong> 1.36). This privilege should not<br />

be abused, but likewise it should not be overlooked.<br />

3. Seek Opinions<br />

When faced with decisions on controversial or highly<br />

technical topics, the STA project engineer <strong>and</strong> the FHWA<br />

engineer should take steps to assure that the appropriate<br />

technical <strong>and</strong> authoritative sources are consulted.<br />

Documentation of sources used provides assurance that the<br />

most appropriate decisions are being made <strong>and</strong> that the<br />

work is being adequately supervised.<br />

4. Offer Advice Where Appropriate<br />

The FHWA engineer is expected to have some degree of<br />

technical expertise <strong>and</strong> competence as well as access to<br />

subject area specialists. FHWA engineers should provide<br />

assistance or reassurance as appropriate but always with the<br />

underst<strong>and</strong>ing that they are not directing the operation.<br />

Advice or opinions offered should always be recorded in the<br />

inspection report. If the advice concerns the limit of Federal<br />

participation, this must be clearly understood.<br />

5. Draw Conclusions<br />

Based on all the available information, the inspecting<br />

engineer should draw conclusions on the acceptability of<br />

operations, actions taken, the finished product, <strong>and</strong> the<br />

quality of supervision. These conclusions serve as a basis for<br />

acceptance of the project <strong>and</strong> should serve to support the<br />

division’s construction program risk assessment.<br />

6. Make Decisions <strong>and</strong> Inform Affected Parties<br />

If acceptance decisions must be made as a result of<br />

conclusions drawn, the inspection report should record<br />

these conclusions <strong>and</strong> all affected parties should be<br />

informed in a timely manner. Notification can be done in<br />

the inspection report or in other formal correspondence, as<br />

appropriate.<br />

<strong>Construction</strong> <strong>Program</strong> <strong>Management</strong><br />

CONSTRUCTION PROGRAM MANAGEMENT AND INSPECTION GUIDE (5/01/04)<br />

<strong>Inspection</strong> reports should have substance rather than just<br />

verbose wording. It is important not to lose track of what is<br />

observation, hearsay, fact, or opinion when it comes time to<br />

write the report. Reports should be as specific as possible,<br />

<strong>and</strong> ambiguity should be avoided. Hearsay should never be<br />

documented unless upon further review facts are found to<br />

support the hearsay. By following the six steps outlined in the<br />

sidebar, engineers can produce reviews that effectively meet<br />

their objectives. The sidebar on the next page highlights<br />

important precautions for inspection reports.<br />

Inspectors may also refer to Appendix F, Examples of<br />

Reporting Practices, which critiques the appropriateness <strong>and</strong><br />

significance of different reporting practices. The examples<br />

shown are extracts from actual reports <strong>and</strong> commentary. It<br />

will be helpful to review the extracts <strong>and</strong> comments, which<br />

can be applied to other reporting items as well.<br />

Writing the Report<br />

Forms<br />

<strong>Inspection</strong>s<br />

Two FHWA forms are suggested for use in filing inspection<br />

reports for all Federal-aid projects:<br />

▼ Form FHWA 1446 A (or similar) “<strong>Construction</strong><br />

<strong>Inspection</strong> Report” (Appendix G, Project Implementation<br />

<strong>and</strong> Reporting Forms), may be used to report all<br />

construction inspections, including final inspections.<br />

▼ Form FHWA 1446 B (or similar) “Final Acceptance<br />

Report” (Appendix G), may be used to report final<br />

acceptance, or the division office may include an<br />

alternative method of documenting final acceptance in<br />

its construction management program. (Note: The final<br />

acceptance report is not required, although some<br />

division offices use it to assist in project closeout <strong>and</strong> to<br />

support payment of final voucher.)<br />

Other Reviews<br />

The forms to be used for process reviews <strong>and</strong> emphasis area<br />

reviews where summary reports are to be prepared have not<br />

been prescribed. It is suggested that Form FHWA 1446 A be<br />

used for the individual project reports on which the summary<br />

will be based. A narrative report form is typically used for the<br />

summary with graphics or tabular displays as appropriate to<br />

demonstrate the importance or occurrence of findings.<br />

4–3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!