36 Miss. Code. R. 2-12-212.3
* Read and follow all instructions in the Request for Proposal (RFP). The proposal becomes part of the contract with the awarded vendor and a non-responsive proposal will be removed from further consideration.
* Work from the Microsoft Word version of the RFP, inserting direct, clear answers below each item in the Technical Requirements section, as instructed in Item 1 of that section, with a clear delineation (through color/font/vertical bars in the margins, e.g.) to show vendor's response versus original RFP text.
* If you take exception to an item, it's best to clearly outline an alternative, what you CAN do or offer, because the option might be acceptable to the State or at least allow the State to identify the level of risk.
* Tab the response and insert a table of contents, showing where the signed cover sheet, proposal bond, exception summary, response to technical specifications, cost proposal, response to exhibits, etc. are found.
* Don't include "brochure" type language -- vendors sometimes make the mistake of marketing themselves rather than just responding to the requirements directly.
* Another issue for some proposals is providing the right level of information in response to technical requirements--enough information versus not enough or too much. For most items, the evaluators want to see how the vendor will meet the requirement, not just "will comply." But too much information, especially when it doesn't directly respond to the requirement, is also negative, because the answer gets lost in all the excess verbiage.
* When the RFP requires an Experience Information & Reference Workbook, follow all instructions carefully in completing the Microsoft Excel spreadsheet. Experience must be quantified in months. Do not submit candidates without the required amount of experience in each area--they cannot be considered.
36 Miss. Code. R. 2-12-212.3