When attending a pre-proposal conference or site visit, separate spoken observations from the written solicitation and route follow-up clarification requests through the solicitation's authorized communication channel.

Under FAR 15.201(f), after release of the solicitation, the contracting officer must be the focal point of any exchange with potential offerors. Use a structured intake sheet to capture event observations and convert discrepancies into formal clarification questions.

Reconciling Event Observations With the Solicitation Baseline

During a pre-proposal briefing or facility tour, technical speakers and program personnel often describe operational conditions or respond to attendee questions. While the contracting officer serves as the post-release focal point under FAR 15.201(f), the solicitation or contracting officer may specify designated portals, contract specialists, or structured conference question procedures for submitting inquiries.

Whenever a briefing slide, spoken comment, or physical site observation appears to conflict with the written statement of work, treat that gap as a candidate for the official clarification and amendment process rather than an informal promise or automatic scope change. For instance, if a speaker mentions 40,000 database records while the written solicitation specifies 120,000 records, only a formal solicitation amendment alters the baseline requirement. Connecting your conference preparation to your capture management 101 workflow and earlier pre-RFP intelligence gathering helps your attendees know which solicitation sections need verification before stepping into the room.

Hypothetical Pre-Proposal Conference Intake Sheet

These hypothetical conference intake records show how an offeror logs briefing remarks, permitted site observations, and attendee floor questions. Take notes, photographs, or physical measurements during a site walk only when and to the extent permitted by the agency's event and security rules.

1. CONF-01

  • Event source: Program Briefing Slide 9 (Hypothetical)
  • Observed remark: Slide chart listed 2 helpdesk shifts (06:00 to 22:00)
  • RFP section: Section C.2.4 states 24x7x365 coverage
  • Sensitivity / interpretation: Neutral scope discrepancy; asking does not expose our staffing model
  • Next action: Submit clarification question through the CO-designated channel asking whether Section C.2.4 or Slide 9 governs

2. CONF-02

  • Event source: Permitted Site Walk Observation (Hypothetical)
  • Observed remark: Freight doorway clearance observed at 54 inches (where measurement is permitted by site rules)
  • RFP section: Attachment J-4 lists 60-inch pre-assembled equipment racks
  • Sensitivity / interpretation: Phrasing should avoid revealing our modular assembly layout
  • Next action: Submit neutral question asking whether equipment racks may be delivered unassembled for on-site assembly

3. CONF-03

  • Event source: Attendee Floor Question #4 (Hypothetical)
  • Observed remark: Another attendee asked whether cloud FedRAMP Moderate inheritance is acceptable
  • RFP section: Section C.4.1 specifies on-premises agency hosting
  • Sensitivity / interpretation: Floor question is an observation of a topic raised, not proof of that vendor's actual bid strategy
  • Next action: Monitor official Q&A and amendment postings to see whether the agency modifies or retains Section C.4.1

4. CONF-04

  • Event source: Closing Administrative Remarks (Hypothetical)
  • Observed remark: Speaker noted that briefing slides and attendee list will post to the portal
  • RFP section: Section L Q&A submission deadline
  • Sensitivity / interpretation: Administrative tracking item
  • Next action: Check the official solicitation portal for the posted slides and submit questions before the stated cutoff

Hypothetical Elapsed-Clock Turnaround From Briefing to Q&A Cutoff

Because agencies often set a short window between the pre-proposal conference and the question submission deadline, map your internal review against continuous elapsed clock hours (which include overnight intervals, not active staff labor hours).

Suppose a hypothetical conference concludes on Wednesday at 15:00 and the solicitation's question cutoff is Friday at 12:00:

  • Total elapsed clock window from Wednesday 15:00 to Friday 12:00: 45 elapsed clock hours
  • Stage 1 (Attendee debrief and intake sheet consolidation): 4 elapsed clock hours (completed Wednesday at 19:00)
  • Stage 2 (Overnight interval plus technical and pricing impact review): 16 elapsed clock hours (completed Thursday at 11:00)
  • Stage 3 (Overnight interval plus contracts sanitization and package preparation): 18 elapsed clock hours (ready Friday at 05:00, totaling 4 + 16 + 18 = 38 elapsed clock hours)
  • Remaining submission margin before the Friday 12:00 cutoff: 45 elapsed clock hours - 38 elapsed clock hours = 7 elapsed clock hours

During the sanitization step, remove phrasing that telegraphs your unique technical approach. Instead of asking whether a named proprietary tool can compress a maintenance task to 2 hours, ask neutrally whether tools already listed on the agency's approved software baseline may be used to perform the requirement.

Three Practical Rules for Conference and Site-Visit Teams

  1. Follow the solicitation's authorized communication procedure: Route post-solicitation questions through the contracting officer or the exact portal and contact designated in the RFP rather than relying on hallway conversations with technical staff.
  2. Treat attendee floor questions as signals to watch, not confirmed competitor plans: Vendors ask floor questions for many reasons, including testing ambiguity or exploring alternatives they ultimately reject. Use floor questions to anticipate potential solicitation amendments rather than re-architecting your proposal around a competitor's question.
  3. Keep your baseline aligned with the written RFP until amended: Price and write to the current written solicitation documents unless and until an official amendment modifies the requirement.

Next Step With FedFinder

Explore public contracting opportunities on FedFinder. Check current plans and terms on the pricing page.

Sources

  • FAR 15.201 - Exchanges with industry before receipt of proposals (FAR 15.201(f)): https://www.acquisition.gov/far/15.201 (Retrieved 2026-11-06; Acquisition.gov baseline FAC 2026-01 effective 2026-03-13. Scope covers the FAR 15.201(f) requirement that after release of the solicitation, the contracting officer must be the focal point of any exchange with potential offerors; check actual agency deviations and solicitation terms.)

  • FAR 15.206(a) - Amending the solicitation: Solicitation amendment rule. Retrieved 2026-11-06; negotiated-acquisition baseline, subject to applicable agency deviations.