06.12.2012 Views

Contracts Management Guide - Texas Comptroller of Public Accounts

Contracts Management Guide - Texas Comptroller of Public Accounts

Contracts Management Guide - Texas Comptroller of Public Accounts

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix 3<br />

Pre-Solicitation Conference <strong>Guide</strong>lines<br />

Objective: A pre-solicitation conference is sometimes required to clarify specifications. It may be<br />

essential for potential bidders to visit the site prior to submitting a bid. Typically, the program staff, in<br />

conjunction with the Purchasing Department, determines if a pre-solicitation conference is necessary. If a<br />

pre-solicitation conference is necessary, the solicitation document must include:<br />

� Exact physical location, including room number.<br />

� Date and time <strong>of</strong> conference. The date must allow sufficient time for bidders to receive and review<br />

the solicitation prior to the conference. Typically, this is 7-10 days after the solicitation is published.<br />

If the conference is mandatory, the following statement must be included in the solicitation. "Failure to<br />

attend the pre-bid conference will result in disqualification <strong>of</strong> the solicitation."<br />

Typically, the purchaser conducts the conference. The purchaser provides:<br />

� A recording device (optional)<br />

� A sign-in sheet for attendees<br />

� Additional copies <strong>of</strong> the solicitation<br />

The conference begins as follows:<br />

� Purchaser's opening remarks such as the purpose <strong>of</strong> the conference, requisition number and title <strong>of</strong><br />

the procurement.<br />

� Announce conference is being recorded, if applicable. Advise attendees to turn <strong>of</strong>f or turn to vibrate<br />

any cell phones or pagers.<br />

� Remind everyone to sign in, especially for mandatory conferences.<br />

� Introduce agency representatives.<br />

� Introduce attendee's. (optional depending on number attending conference)<br />

� Review solicitation by section or page and ask for questions regarding each section and/or page. (Do<br />

not read the RFP word for word – summarize and allow for questions)<br />

� Take notes <strong>of</strong> any addendum items or significant discussions.<br />

� Site inspections may be conducted prior to or after the solicitation review, depending on the<br />

circumstances, but prior to close <strong>of</strong> the conference. After site inspections all attendee's should return<br />

to conference room to ask any questions as a result <strong>of</strong> the site inspection.<br />

� Recap – Discuss and confirm the items to be included in addendum, if any. Remind attendees that<br />

oral changes are not <strong>of</strong>ficial until they are included in an addendum.<br />

� Collect sign-in sheets. Note: Usually attendees want copies <strong>of</strong> the sign-in sheets. If possible, make<br />

copies for attendees prior to the end <strong>of</strong> the conference.<br />

After the conference:<br />

� Keep recorded conference minutes in the contract file as <strong>of</strong>ficial documentation <strong>of</strong> the meeting. The<br />

minutes may or may not be transcribed.<br />

� Purchaser prepares addendum with input from the program staff. Program staff will review for<br />

accuracy prior to mailing.<br />

� Purchaser will determine if there is sufficient time until bid opening or if bid date should be extended.<br />

� Mail or fax addendum to attendees if needed.<br />

� Send copy <strong>of</strong> addendum to program staff. If architectural or engineering plans are involved, advise<br />

program staff to provide a copy to the Architect or Engineer so they can provide copies to the plan<br />

rooms.<br />

� Post addendum on the Electronic State Business Daily.<br />

105

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!