Construction Program Management and Inspection Guide
Construction Program Management and Inspection Guide
Construction Program Management and Inspection Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Progress <strong>and</strong> Quality of Work<br />
Report Item<br />
Time Elapsed: 121 percent<br />
Progress of Work: Unsatisfactory<br />
At the time of this inspection, the asphalt concrete leveling<br />
work was substantially completed <strong>and</strong> the contractor was just<br />
beginning the paving of the base lift, starting at the westerly<br />
end of the project.<br />
The contractor hopes to start paving operations the first week<br />
in August.<br />
Currently the contractor is behind schedule but he has<br />
developed an accelerated schedule that shows he may complete<br />
the work on time.<br />
It was clear that the contractor on this project has done<br />
everything he could to maintain his construction schedule.<br />
However, the nature of the somewhat abnormal rains this<br />
summer combined with the volcanic silt in this area has slowed<br />
his progress. It is important to note that the contractor did<br />
work every time that soil conditions allowed.<br />
The contract time was extended 42 days to completion time of<br />
252 days. The contractor used 253 days <strong>and</strong> is being charged<br />
one day of liquidated damages.<br />
For a project of this magnitude, it appeared that very little<br />
construction activity was occurring at the time of the<br />
inspection. <strong>Construction</strong> weather <strong>and</strong> soil conditions were<br />
ideal. (Note: time = 15 percent, work = 3 percent)<br />
Although the percentage of work completed (16 percent) lags<br />
the percentage of time elapsed (50 percent), it is anticipated<br />
that the contractor will complete this project on time. Once<br />
the paving operations commence, the percentage of work<br />
completed will accelerate.<br />
Appendix F: Examples of Reporting Practices<br />
CONSTRUCTION PROGRAM MANAGEMENT AND INSPECTION GUIDE (5/01/04)<br />
Comments<br />
It is undesirable to get report heading data such as this without<br />
an explanation <strong>and</strong> a projection of future progress or actions to<br />
be taken. Expansion of statistical data is encouraged.<br />
This example of project status presents a meaningful picture of<br />
the ongoing major work on the project at the time of<br />
inspection.<br />
Future scheduling is appropriate for reporting. Is this ahead of<br />
or behind schedule?<br />
Information on revised scheduling is also of interest.<br />
This comment is not as speculative as the last one. It is<br />
apparent that some support for the conclusion probably exists<br />
in addition to the general statements here. The level of<br />
support here is fully acceptable. It is helpful if the information<br />
source can be identified (e.g., project engineer, diaries, etc.).<br />
This is a factual report of contract time charges, but it really<br />
adds very little value to the report without further explanation.<br />
Also, it does not discuss justification for the 42-day extension<br />
or whether it was agreed to by FHWA.<br />
The inspecting engineer should add sufficient information to<br />
clarify the reasons why no construction has taken place,<br />
his/her reaction to these reasons, <strong>and</strong> a remark resolving the<br />
issue of lack of progress.<br />
A logical explanation has been included for the slow progress<br />
to avoid creating alarm on the part of the reader.<br />
Continued on next page<br />
F–3