DHHS Home Page NC DHHS On-Line Manuals  
     DHHS Manual Home Manual Admin Letters Change Notices Archive Search Index Help Feedback

Previous PageTable of ContentsNext Page

DHHS POLICIES AND PROCEDURES

___________________________________________________________________________________________________________________

Section VII:

Procurement and Contracts Services

Title:

General Contracting Manual Chapter 3; Requests for Applications (RFAs), Requests for Information (RFIs), and Requests for Proposals (RFPs)

Current Effective Date:

December 18, 2003

Revision History:

8/1/02

Original Effective Date:

8/1/02

___________________________________________________________________________________________________________________

Purpose

The purpose of this document is to provide guidance to Department of Health and Human Services (DHHS) staff as it relates to Requests for Applications (RFAs), Requests for Information (RFIs), and Requests for Proposals (RFPs).

Policy

DHHS Office of Procurement and Contract Services provides written documentation relative to the requests processes and requirements. The requirements are detailed below in the Implementation Section.

Implementation

Definitions

  1. Request For Applications:
    A Request for Application (RFA) is a competitive process that usually results in the award of more than one contract. Unlike an RFP, the applicants are knowledgeable of the award amount and are asked to submit an application that includes a description of services to be performed and a budget narrative of the potential award amount. Although the contract format may be used, a preprinted application is usually provided by the funding source and is completed by the potential applicant. The application outlines the services to be provided to recipients by specialized vendors such as private non-profit organizations, colleges and universities, or local units of government. An RFA may be used when the funding source--an agency of the Department of Health and Human Services--is acting as a flow-through for grant funding.

  2. Request For Information:
    A Request for Information (RFI) is an informal method of soliciting general information to aid in later planning of specification writing. (No contract award results from this process.) This is used to obtain technical information only and not pricing information.

  3. Request For Proposals:
    A Request for Proposal (RFP) is an open and competitive method of soliciting proposals for the delivery of a product or service. This consists of a purchase description of the time and/or service required, information on quantities, required delivery schedules, special terms and conditions, and standard terms and conditions. Unlike an RFA, the applicants are not informed of the award amount. RFPs are usually handled as a one step or a two-step process. When the offeror submits a separate sealed technical proposal and a separate sealed cost proposal, the cost proposal shall be opened only if the technical proposal is determined to be acceptable and has met all mandatory requirements. An award will be made to the offeror presenting the most advantageous overall proposal to the State.

Organization of this Chapter

This chapter consists of separate sections devoted in turn to RFAs, RFIs, and RFPs. Much of the information is similar. Please refer to the appropriate part depending upon the type of request being developed.

RFAs

The following component parts and/or guidelines should be used when preparing a RFA.

  1. Pre-Application Conference Guidelines:
    The using agency may want to conduct a pre-application conference for Request for Applications (RFA) to clarify program initiatives. The using agency should conduct a pre-application conference within two weeks after the mailing of the RFA. The RFA stipulates the time, date, and location of the pre-application conference. All attending the pre-application conference should sign the sign-up sheet requiring all attendees' names, agency, address, phone, and fax number.

    Everyone in attendance at the pre-application conference should have a copy of the RFA prior to the conference, but the using agency should have copies available for those who may not have obtained them. The project director should provide an overview of the project, explaining the specifications, scope of work, objectives, and techniques. A representative of the using agency should tape the meeting and record each vendor's inquiries, points of contention, and requests for clarification. A written summary of all questions received in writing prior to the pre-application conference, questions asked during the conference, and all answers provided should be posted on the internet within one week of the pre-application conference. This written summary should also include answers to questions that required additional research. The written summary of Questions and Answers becomes Addendum I to the RFA and must be labeled as such.

  2. The Procurement Process
    The following is a general description of the process by which an agency or organization will be selected to complete the goal or objective.
    1. RFAs are being sent to prospective agencies and organizations
    2. All prospective agencies and organizations are ENCOURAGED to attend the BIDDER'S CONFERENCE. A written summary of all questions and answers will be mailed to all agencies and organizations sent a copy of the RFA.

    OR

    1. Written questions concerning the RFA specifications will be received until the date specified on the cover sheet of this RFA. A summary of all questions and answers will be mailed to all agencies and organizations sent a copy of the RFA
    2. Applications in one original and (at least two) copies will be received from each agency or organization. The original must be signed and dated by an official authorized to bind the agency or organization.
    3. All applications must be received by the funding agency not later than the date and time specified on the cover sheet of the RFA.
    4. At that date and time the applications from each responding agency and organization will be logged in. Budgets will be included as part of the application.
    5. At their option, the evaluators may request additional information from any or all applicants for the purpose of clarification or to amplify the materials presented in any part of the application. However, agencies and organizations are cautioned that the evaluators are not required to request clarification: therefore, all applications should be complete and reflect the most favorable terms available from the agency or organization.
    6. Applications will be evaluated according to completeness, content, experience with similar projects, ability of the agency's or organization's staff, cost, etc. The award of a grant to one agency and organization does not mean that the other applications lacked merit, but that, all facts considered, the selected application was deemed to provide the best service to the State.
    7. Agencies and organizations are cautioned that this is a request for applications, and the funding agency reserves the unqualified right to reject any and all applications when such rejections are deemed to be in the best interest of the funding agency.

  3. General Information on Submitting Applications
    1. Award or Rejection
      All qualified applications will be evaluated and award made to that agency or organization whose combination of budget and service capabilities is deemed to be in the best interest of the funding agency. The funding agency reserves the unqualified right to reject any or all offers if determined to be in its best interest.
    2. Decline to Offer
      Any agency or organization that receives a copy of the RFA but declines to make an offer is requested to send a written "Decline to Offer" to the funding agency. Failure to respond as requested may subject the agency or organization to removal from consideration of future RFAs.
    3. Cost of Application Preparation
      Any cost incurred by an agency or organization in preparing or submitting an application is the agency's or organization's sole responsibility; the funding agency will not reimburse any agency or organization for any pre-award costs incurred.
    4. Elaborate Applications
      Elaborate applications in the form of brochures or other presentations beyond that necessary to present a complete and effective application are not desired.
    5. Oral Explanations
      The funding agency will not be bound by oral explanations or instructions given at any time during the competitive process or after awarding the grant.
    6. Reference to Other Data
      Only information that is received in response to this RFA will be evaluated; reference to information previously submitted will not suffice.
    7. Titles
      Titles and headings in this RFA and any subsequent RFA are for convenience only and shall have no binding force or effect.
    8. Form of Application
      Each application must be submitted on the form provided by the funding agency, and will be incorporated into the funding agency's Performance Agreement (contract).
    9. Exceptions
      All applications are subject to the terms and conditions outlined herein. All responses will be controlled by such terms and conditions. The attachment of other terms and condition by any agency and organization may be grounds for rejection of that agency or organization's application. Funded agencies and organizations specifically agree to the conditions set forth in the Performance Agreement (contract).
    10. Advertising
      In submitting its application, agencies and organizations agrees not to use the results therefrom or as part of any news release or commercial advertising without prior written approval of the funding agency.
    11. Right to Submitted Material
      All responses, inquiries, or correspondence relating to or in reference to the RFA, and all other reports, charts, displays, schedules, exhibits, and other documentation submitted by the agency or organization will become the property of the funding agency when received.
    12. Competitive Offer
      Pursuant to the provision of G.S. 143-54, and under penalty of perjury, the signer of any application submitted in response to this RFA thereby certifies that this application has not been arrived at collusively or otherwise in violation of either Federal or North Carolina antitrust laws.
    13. Agency and organization's Representative
      Each agency or organization shall submit with its application the name, address, and telephone number of the person(s) with authority to bind the agency or organization and answer questions or provide clarification concerning the application.
    14. Subcontracting
      Agencies and organizations may propose to subcontract portions of work provided that their applications clearly indicate the scope of the work to be subcontracted, and to whom. All information required about the prime grantee is also required for each proposed subcontractor.
    15. Proprietary Information
      Trade secrets or similar proprietary data which the agency or organization does not wish disclosed to other than personnel involved in the evaluation will be kept confidential to the extent permitted by NCAC TO1:05B.1501 and G.S. 132-1.3 if identified as follows: Each page shall be identified in boldface at the top and bottom as "CONFIDENTIAL." Any section of the application that is to remain confidential shall also be so marked in boldface on the title page of that section.
    16. Participation Encouraged
      Pursuant to Article 3 and 3C, Chapter 143 of the North Carolina General Statutes and Executive Order No. 77, the funding agency invites and encourages participation in this RFA by businesses owned by minorities, women and the disabled including utilization as subcontractor(s) to perform functions under this Request for Applications.
    17. Contract
      A contract will be issued between the funding agency and the recipient of a grant. The agency's or organization's application will be included by reference.

  4. Procedures for Developing Evaluation Criteria, the Evaluation Process, and Establishing valuation Committee for RFAs
    1. Evaluation Criteria:
      1. Establishing the evaluation criteria should be accomplished during the writing of the RFA and is usually included (at least in part) in the RFA document.
      2. The criteria should be based on the degree of importance of the different requirements of the RFA. Decide what the requirements and deliverables are and establish which are mandatory and which are not. Obviously, the RFA should reflect these criteria.
      3. "Weigh" the criteria from most important to least important and use this to formulate your evaluation methodology. If points are used, the relative value of the various sections can be assigned appropriate points to reflect such.
      4. Evaluate all qualified applications whose combination of budget and service capabilities is deemed to be in the best interest of the funding agency.

    2. Evaluation Committee:
      1. Select an odd number of participants that have the appropriate credentials and expertise needed to properly evaluate the applications.
      2. Send a letter from the division director to selected committee members outlining their duties and the time frames proposed for the evaluation.
      3. Ensure participants' names are kept confidential and express need for confidentiality to committee members.
      4. Inform committee members to avoid contact with any of the offerors.
      5. Keep as close as possible to the established time frames for the completion of the evaluation process.

    3. Evaluation Process:
      1. At the stated time, date, and place for the receipt of the applications, the funding agency will open the applications and eliminate those not meeting the mandatory requirements. All applications meeting the mandatory requirements will be referred to the evaluation committee.
      2. Establish a timetable for the evaluation committee; include in this timetable a "reconciliation meeting" to answer any questions from the committee and to discuss any big variances in their opinions. Evaluators may adjust their evaluations at the reconciliation meeting.
      3. After the committee has completed the evaluation of the applications, a narrative of the process must be developed. The narrative should include the approximate number of potential offerors receiving the RFA, the date of the pre-application conference, the mailing date of written responses to questions asked during the pre-applications conference, the names of the potential offerors evaluated, and a description of the evaluation process and how proposals were eliminated from consideration.
      4. This narrative is kept on file in the Division.

  5. Procedures for Awarding RFA to Offeror
    1. Present final evaluation with recommendation to contract to the division director or designee. All evaluation material should be kept confidential and there should be no contact with offerors until the award(s) is/are made.
    2. When appropriate approvals are received, send award notice to the successful vendor and another notice to the unsuccessful vendors.
    3. Develop and process contracts according to proper contracting procedures as outlined in Chapters I and II.

See the Procurement & Contract Services Manuals and forms for information, instructions, examples and contract forms, templates, general terms and conditions, performance-based contracting (PBC) requirements, performance measures, sample amendments, supplemental material to required forms and miscellaneous information.

RFIs

RFIs are straightforward, simple requests for information. These may be written as best suits the issuing office. The RFI may be a free-form document in which whatever information needed is solicited. Meetings with respondents may be informal. No contracts arise from RFIs, so no funding information is required on RFI documents. Draft RFIs shall be forwarded to DHHS Procurement and Contract Services for review and posting on the internet.

 RFPs

The following component parts and/or guidelines should be used when preparing a RFP.

  1. RFP Approval Form (with instructions) and RFP Endorsement Letter
  2. Instructions for Completing Request for Proposals (RFP) Approval Form
  3. Recommended RFP Processing Time Frame
  4. Pre-proposal Conference Guidelines
  5. Request for Proposals includes the following:
    1. Proposal Requirements
    2. Evaluation Process (for use in RFP)
    3. The Procurement Process (for use in RFP)
    4. Cost Proposal/Execution of Proposal
    5. Contract Requirements
    6. NC General Contract Terms and Conditions
    7. DHHS Supplemental Terms and Conditions
  6. RFP Attachments. Includes the following:
    1. Certification Regarding Lobbying
    2. Certification Regarding Debarment, Suspension, Ineligibility...
    3. Certification Regarding Drug-Free Workplace Requirements
    4. Certification Regarding Environmental Tobacco Smoke
    5. Conflict of Interest Policy for Private Not-for-Profit Agencies
    6. Verification of 501(c)(3) Status
  7. Documentation Required for Posting RFPs to the State Web-page
  8. Internet RFP Notice
  9. The Procurement Process (Discussion)
  10. Procedures for Developing Evaluation Criteria, the Evaluation Process, and Establishing Evaluation Committee for RFPs
  11. Procedures for Awarding RFP to Vendor

Description of guidelines are described below:

  1. RFP Approval Form and Endorsement Letter

    The RFP Approval Form shall be executed and attached to all RFPs. The Endorsement Letter following thereafter shall be executed, signed by DHHS Secretary, and attached to RFPs for consultant services. Note that approval by the Governor's Office may be required in the case of certain consulting contracts. Guidance is contained in NCAC T01:05D.0203, reproduced below:

    .0203. REQUESTS FOR AUTHORITY TO CONTRACT WITH CONSULTANTS
    “Before receiving authorization to seek consultant services, an agency shall submit to the division of purchase and contract written justification for its request for consultant services. This written justification shall at a minimum explain what services the agency desires to secure, why the work to be performed by the consultant cannot be reasonably accomplished by employees of the requesting agency, how the work to be performed relates to the proper functions of the agency, what benefits the agency expects to receive from the consultant's services, what the agency estimates to be the cost of the services sought, what potential sources of consultant services if any the agency has identified and such additional information as the Governor or the division of purchase and contract may require. If the agency is requesting authority to contract for consulting services outside of state government, it shall also detail what potential sources of those services exist within state government and explain why the desired services were not available from those sources. The written justification shall be accompanied by a letter of endorsement for the proposed contract(s) from the agency head or his designee.”

  2. Pre-Proposal Conference Guidelines

    The using agency may want to conduct a pre-proposal conference for the Request for Proposals (RFP) that are highly technical and complex in nature. The opportunities for ambiguity, unforeseen and nonessential restrictiveness or technical error are greater in highly complex or technical proposal invitations. Pre-proposal conferences can aid in the early detection and the clarification of these circumstances. The using agency should conduct a (mandatory or non-mandatory) pre-proposal conference within two weeks after posting the RFP on the internet. The RFP stipulates the time, date, and location of the pre-proposal conference. All attending the pre-proposal conference should sign the sign-up sheet requiring all attendees' names, agency, address, phone, and fax number. There are mandatory pre-proposal conferences and non-mandatory conferences. If a conference is made mandatory only the vendors that attend can bid on the project. If non-mandatory any vendor can submit a bid. Mandatory conferences are discouraged due to the fact that some vendors might not be able to attend due their time schedule and the expensive travel requirements. However if a project is highly complex, the division might need all interested vendors to attend as to not miss any important facts about the project. If only one vendor attends a mandatory pre-proposal conference, the RFP must be cancelled. The division must contact possible offerors and document why they did not plan to bid.  The division can then either re-issue the RFP with possible scope changes or request to negotiate with the lone vendor that attended the conference.

    Everyone in attendance at the pre-proposal conference should have a copy of the RFP prior to the conference, but the using agency should have copies available for those who have not obtained them. A sign in sheet should be made available to all vendors recording name of person, company name, address, phone number, and fax number.  The project director should provide an overview of the project, explaining the specifications, scope of work, objectives, and techniques. A representative of the using agency should tape the meeting and record each vendor's inquiries, points of contention, and requests for clarification. Questions will be attempted to be answered but the vendors will be instructed that the correct answer will be the ones in writing. If a non-mandatory conference, a written summary of all questions received in writing prior to the pre-proposal conference, questions asked during the conference, and all answers provided should be posted on the internet within one week of the pre-proposal conference.  If conference was a mandatory conference, all questions and answers will be mailed/faxed to the vendors that attended the conference. It will not be posted on the internet since only vendors attending the conference can submit a proposal. The written summary should also include answers to questions that required additional research. The written summary of Questions and Answers becomes Addendum I to the RFP and must be labeled as such.

  3. Request for Proposals

    The attached RFP format, adapted from the "standard" version published at P&C's website, is recommended for use by DHHS divisions and institutions. Please note that this is but an outline: each RFP is a unique document, the contents of which are governed by the requirements of the request. Those requirements must be clearly and completely specified in order to elicit proposals that respond to the division's or institution's specific needs. Departmental writers of RFPs must therefore consider the expected results thoroughly and craft a document that addresses all eventualities. Perhaps the best way to create an RFP that will satisfy all practical and legal requirements is to base it on a prior RFP that solicits like or similar information. Copies of previous RFPs are available upon request from DHHS Procurement and Contract Services at 919/733-2105.

    This RFP format is based on an actual RFP. It is intended as a guide and sample ONLY.

    When using the format, bear in mind the fact that only some of the things that you may require are included herein. Your RFP may contain some or all of the following and perhaps other items, too, based upon your specific requirements. Be sure to select only one option where several are given and to fill in applicable information where blanks occur.

    Additional details and copies of forms are contained in this chapter. Forms contained herein may be copied in whole or in part and used in the finished RFP as needed.

    NOTE: It is highly recommended that pages and paragraphs/sections be numbered for easy reference.

    It is much better to give too much information than too little. The goal is to make your RFP a stand-alone document that provides all the information a prospective contractor requires to meet your needs.

    Finally, please note that the vast majority of RFPs issued by DHHS are of sufficient magnitude to require use of the two-step (i.e., separate technical proposal and cost estimate) process.

RFP Attachments

Label attachments as “ATTACHMENT I, etc.
Use attachments and fill in same as needed

Documentation Required for Posting RFPs to the State Web-page

Prior to DHHS P&C  posting the RFP on the State Web-page, the following is required:

  1. Internet RFP Notice

    RFP’s are posted on the IPS system for vendors that have registered in “Vendor Link” under this type service. The vendor will receive an e-mail notifying them of the opportunity. This notice can be sent as a courtesy to known vendors that provide this service but the department is under no obligation to send notices. It is the responsibility of the vendors to register with the state under “Vendor Link”. The department is not responsible if any vendor fails to be notified.

    See: Internet RFP Notice.

  2. The Procurement Process

    Below are two examples of the procurement process:  the one-step process and the two-step process. Adjust the language used depending on whether you are using a one-step (technical and cost together) or two-step (separate technical and cost proposals) method. Most RFPs issued by DHHS divisions or institutions are of sufficient magnitude and require the TWO-STEP METHOD.

  3. Procedures for Developing Evaluation Criteria, the Evaluation Process, and Establishing Evaluation Committee for RFPs
    1. Evaluation Criteria:
      1. Establishing the evaluation criteria should be accomplished during the writing of the RFP and is   (at least in part) in the RFP document.
      2. The criteria should be based on the degree of importance of the requirements of the RFP. Decide what the requirements and deliverables are, establish which are mandatory and which are not. Obviously, the RFP should reflect these criteria.
      3. "Weigh" the criteria from most important to least important and use this to formulate your evaluation methodology. If points are used, the relative value of the various sections can be assigned appropriate points to reflect such.
      4. Establish a point at which a vendor meets the committee's minimum requirement in order to advancing to the Cost Proposal evaluation. (such as a certain number of points.) This step is extremely important because most "marginal" technical proposals present the lowest cost proposals. The contract is usually awarded to the vendor with the lowest cost proposal that meets the minimum requirements. However, a contract may be awarded to another vendor with a higher cost if their proposal results in a better value to the State and can be justified. Make certain the committee is willing to contract with any vendor that meets the minimum requirements of the technical proposal. This is most important prior to opening the cost proposal ( if using a two step process).
      5. Establish the relative value of the technical proposal to the cost proposal (such as 60/40) so there will be a pre-established committee evaluation process. This must be explained in the RFP to the offerors so they will know what they will be evaluated against.
      6. Develop an evaluation criteria document (sample attached) that will be used by each committee member. This document should correspond with the criteria established in the RFP and have space for each evaluator to take notes as the proposal is read.
    2. Evaluation Committee:
      1. Select an odd number of participants that have the appropriate credentials and expertise needed to properly evaluate the proposals. They must all be department employees. Any exception to this should be requested in writing and sent to the DHHS Procurement and Contract Services Officer.
      2. Send a letter from the division director or designee to selected committee members outlining their duties and the time frames proposed for the evaluation.
      3. Ensure participants' names are kept confidential and express need for confidentiality to committee members.
      4. Inform committee members to avoid any contact with any potential offerors.
        Keep as close as possible to the established time frames for the completion of the evaluation process.

      Prior to DHHS Procurement and Contract Services releasing the proposals to the evaluation committee, a list of the committee members, including each member’s title and qualifications, must be submitted to DHHS Procurement and Contract Services.

      A copy of the evaluation documentation form (sample attached) to be used by the evaluation committee in evaluating each proposal must be submitted to DHHS Procurement and Contract Services prior to the release of the proposals. The completed evaluation documents will remain with the evaluation committee, but may be requested by DHHS Procurement and Contract Services in the event of a protest.

      The overall evaluation summary must be compiled from each committee member’s evaluation documentation.  The summary is to be submitted to DHHS Procurement and Contract Services at the time of vendor selection recommendation.

    3. Evaluation Process:
      1. At the stated time, date, and place for the receipt of the proposals, DHHS Procurement and Contract Services will open the technical proposals (two step process), keeping one original and one copy, and releasing the other original and copies to the evaluation committee.  The cost proposal remains sealed and kept in Procurement and Contract Services until the technical evaluation is completed. At this point only the costs of the vendors that met the technical requirements are opened. The names of those presenting proposals for this RFP will become public upon request. In a one step process the entire proposal will be released to the committee. A one step is when the cost and technical is evaluated together.
      2. Establish a timetable for the evaluation committee; include in this timetable a "reconciliation meeting" to answer any questions from the committee and to discuss any big variances in each member’s opinion. Evaluators may adjust their evaluations at the reconciliation meeting.
      3. After the committee has completed the evaluation of the technical proposals, a narrative memo (see below) of the process must be developed.  This should be addressed to the DHHS Procurement and Contract Services Officer. The narrative should include the approximate number of vendors receiving the RFP or the date the RFP was posted on the internet, a copy of the RFP that was posted, the date of the (mandatory or non-mandatory) preproposal conference, a copy of the sign in sheet at the conference, the mailing date or date posted on the internet of written responses to questions asked during the preproposal conference, a copy of the questions and answers,  the names of the vendors evaluated, and a description of the evaluation process and how proposals were eliminated from consideration. This should be developed from the evaluation document referred to in  #7 above. The narrative memo should include the following about each offeror:
        1. List each vendor and summarize what the committee members had documented on their individual evaluation sheets.
        2. List what requirements each did meet and ones they didn’t meet.
        3. List strengths and weaknesses
        4. Make references to the reference number being evaluated in the proposal. For example: The vendor did not supply a list of names that would be assigned to the project as required in 5.1. and All references listed in 4.1 were contacted. All references were excellent.
        5. Compare each offer with requirements in RFP and never compare offerors with each other.
        6. Do not use points or percentages unless they were explained in the RFP to the vendors.
      4. This narrative is sent to DHHS Procurement and Contract Services for approval. If approved, DHHS Procurement and Contract Services opens the cost proposal (if using a two step process) and releases to the evaluation committee. A committee representative should be present when the cost proposals are opened.
      5. All cost proposals that meet the minimum requirements of the RFP should be listed from lowest to highest cost. Award the highest points to the lowest cost proposal and award prorated points to the other proposals according to cost.
      6. Combine the technical evaluations and the cost evaluations (if using a two step process). Draft a recommendation to DHHS Procurement and Contract Services requesting approval of the selected vendor. If the recommendation is not the lowest offeror, include a narrative that justifies the recommendation. Once DHHS Procurement and Contract Services approves, they will forward to Division P&C for approval, if applicable.

  4. Procedures for Awarding RFP to Vendor    
    1. Present final combined evaluation (technical and cost) with recommendation to contract to DHHS Procurement and Contract Services for approval. All evaluation material should be kept confidential and there should be no contact with offerors until the award is made. DHHS Procurement and Contract Services submits for concurrence to State P&C, if applicable.
    2. The RFP approval form will be returned to the Division once the award is made. At the bottom of the form the DHHS Procurement and Contract Services Office would have signed off on the award.  The vendor name, not to exceed and the contract period will be filled in.  The Division should get the Division Budget Office and DHHS Budget, Planning and Analysis to sign off on the funds that will be needed for this contract.
    3. The award will be posted on the internet and a letter of award/Execution of Proposal page is signed by Division and then sent to the successful vendor once the Budget Offices have approved the funds. Once the award is posted, the Division is free to contact the specified vendor. Vendors not awarded the contract are not sent a letter. The posting on the internet is their notification of the award.
    4. The RFP sample contract found in this manual, should be issued to the vendor. It should not contain any issues that were in the RFP or vendor’s proposal. This contract is only used as an agreement to clarify the not to exceed amount and the date the work will start and end.
    5. The Division should develop and process contracts according to proper contracting procedures as outlined in the Contract Manual.

See the Procurement & Contract Services Manuals and forms for information, instructions, examples and contract forms, templates, general terms and conditions, performance-based contracting (PBC) requirements, performance measures, sample amendments, supplemental material to required forms and miscellaneous information.

For questions or clarification on any of the information contained in this policy, please contact Procurement and Contract Services. For general questions about department-wide policies and procedures, contact the DHHS Policy Coordinator.

Previous PageTop Of PageNext Page



 


     DHHS Manual Home Manual Admin Letters Change Notices Archive Search Index Help Feedback