| Ah, but in what way is the under-bidding contractor the problem? Who gave the contract to the contractor? The problem is the process of going for the lowest bidder, or one of the lowest. Moreover, in this case, incredibly, going for the same low bidder with the knowledge of all the history of the bids from that contractor being unrealistic lowballs and requiring costly change requests. Don't blame the contractor. They get the job and make their money. From their angle, they are successful. They know that the city is aiming for the bottom and so they adjust their bidding accordingly. If they didn't submit a low bid, the job would go to someone else. True story: some decades ago. My father was bidding on a contract with the GVRD (Greater Vancouver Regional District). Something in the tens of thousands of dollars, probably. He was out-bid by $5. That was all they cared about. So he pulled out a $5 bill and plonked it on the table. If you ever drive in Vancouver, Canada and wonder how the roads can be so shitty, remember that story. |
The phrase "lowest bidder" gets a lot of mileage in jokes and social commentary, but I'm pretty sure that the original idea is "the lowest bidder who fulfills the requirements of the contract." In that context it's a pretty obvious process, not something to be feared or mocked. The contract should be "build X to exactly these specifications," and of course the contract should be given to the lowest bidder who can reasonably be expected to fulfill the contract.
In this case, the contractor is clearly unable (or unwilling, or unincentivized) to fulfill the contract, and thus the contractor's bid should be irrelevant. The contractor should not even be considered. After all, if it's fine to not fulfill the terms of the contract, then I'm confident I could submit an even lower bid.