Request for Clarification Responses

Fowler and Olive Traffic Signal Tree Removal

Supplemental Information - Not Part of the Contract Documents

The following list is comprised of paraphrased Requests for Clarification (RFC) submitted by potential bidders or sub-bidders in writing via email, letter, and the Request for Clarification Form (archived).

These paraphrased questions and associated responses are not part of the contract documents and shall have no bearing whatsoever on the interpretation of the Standard Specifications, the Standard Plans, the Special Provisions, or the Plans. Nor shall they have any bearing whatsoever on the interpretation of other publications referenced therein.

Questions without answers may be posted here to indicate that we have received them before the deadline and we intend to respond.

Last updated: December 14, 2023 @ 4:00 p.m.

Is a well drilling licensed contractor eligible to bid on this project? (RFC 2318-1 submitted 12/12/2023)

The eligible contractors licenses are listed on the Notice to Bidders. They are Class A (General Engineering), Class C-27 (Landscaping Contractor), or Class C-61 / D-49 (Tree Service). Response date: 12/14/2023

I wanted to see if a bid bond form was needed from Fresno or is a generic from the bond company ok? (RFC 2318-2 submitted 12/13/2023)

The bid bond itself can be issued by the bond company. The section of the electronic solicitation or hardcopy bid, “Bid Security,” – Proposal 4 should be filled out with information regarding the bid bond by the bidder. Response date: 12/14/2023

Specification No. 17-301E
The Specifications state that chipping operations are not required for the project. If the contractor chooses to do so, the operations cannot take place in County of Fresno owned properties or ROW. If we cannot chip the trees on site, can we grind the stumps on site? (RFC 2318-3 submitted 12/14/2023)

See Addendum #1. Response date: 12/14/2023

Is there a specific bid bond form that's needed for this project? (RFC 2318-4 submitted 12/14/2023)

See response to RFC 2318-2. Response date: 12/14/2023