should rfp include estimated construction cos

huangyhg

should rfp include estimated construction cost?
i work for a utility and am preparing an rfp for engineering design services to rehabilitate a large industrial building.  based on a previous engineering inspection, a fairly detailed list of anticipated construction items has been assembled.  i am including this list in the rfp, but i am debating about including the estimated construction cost (ecc).  on the one hand, i think it would help the proposers determine the level of effort.  on the other hand, i am concerned that it might encourage the proposers to submit a price based on a percentage of the ecc without fully studying the scope.  one of my managers has also expressed a concern that including the ecc in the rfp will influence the construction contractor bids.  i did a web search and saw several rfps for design services that did include the ecc.
your opinions would be greatly appreciated.
check out our whitepaper library.
graybeach:
personally, i would not require that rfp responses to include a estimate of construction cost.
you may limit the number and types of companies that will submit a response to your rfp if you intend to solictit  seperate bids for the construction.
i work for an engineering company. we can estimate fairly quickly, based on our collective expererience, how much engineering effort will be required in the design. our expectation is, obviously, if we have the best proposal (note: i say 'best', not neccesarily cheapest. they are two entirely different things.) we will be selected. we do not do construction estimating. it would be difficult for us to find a construction company to partner with to do the construction estimating unless they (the construction company) had some expectation that if our 'team' won, they would get the construction contract. if you plan on later solicting bids for the construction, there is no incentive for a construction company to team up with us and spend their time estimating the construction cost. knowing this, we would probably conclude that we are not able to respond to the rfp and would not submit a proposal. i suspect this would be the attitude of a lot of engineering companies. you might fairly quickly limit your pool of available responders. not neccesarily what you want when you are looking for the best proposal.
if you are looking for engineering services and construction services, you would be best served by soliciting a design/build proposal.
jmho. others will likely disagree.
regards.
lkjh345,
we have done an in-house conceptual estimate and believe the work will cost approximately $4,000,000.  do you think we should state in the rfp:  "the estimated construction cost is $4,000,000 in 2007 dollars?"
this depends upon how well define the scope of work is. if the scope of work is not well defined, include the ecc. if the scope is well defined, the ecc is not necessary. if in doubt about the scope then include it.
graybeach:
i think i would give a range of costs, just so potential engineering responders know if it is something that is in their usual range of work and is not potentially too large for some firms.
i might say 'the estimated construction cost of the project is between $3,000,000 and $6,000,000 in 2007 dollars.'
thats not specific enough for anyone to just put a percentage estimate together, but it also gives an indication this is not a $100,000 project nor a $20,000,000 project.
again, just my opinion.
thank you lkjh345.  that is a good point about communicating the magnitude of the project to potential responders.  my manager is very much against including the cost, and maybe i can sway him with this argument.  at least the rfp includes a fairly detailed scope of expected construction work which may suffice as jike pointed out.