TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re:  Request for Proposal forms From:Rowena Hart <rhart -at- XCERT -dot- COM> Date:Fri, 5 Mar 1999 12:00:37 -0800
One final thing that pops into mind when I think
about RFPs and contracts:
If you are responding to an RFP, you can not
change the description of work or any other
terms specified in the RFP. For example:
If the company wants APPLES, then you are
bidding to provide APPLES only. You can not
bid to provide APPLES as well as ORANGES,
even if you want to impress the company with
your knowledge of fruit. By changing the scope
of work, you are in fact changing the terms of
the agreement. The evaluation committee can
no longer fairly judge your proposal in relation
to the other proposals it received.
Failure to respond using the terms of the RFP will
result in your proposal being rejected.
HOWEVER, if you respond to an RFP that does
not have certain terms clearly stated (in particular
the PAYMENT TERMS, DELIVERABLES,
TIMELINE, or DESCRIPTION OF WORK), it is
still possible to have these terms written into the
contract that you sign. This is only possible if
these terms were not defined clearly in the RFP,