Check attendance rules, document proof, capture site findings, and reconcile written addenda before committing a public bid.
If a public solicitation schedules a pre-bid meeting or site visit, read the current notice and amendments before assuming attendance is optional or mandatory. Record who may represent the bidder, the exact meeting and registration rules, how the buyer proves attendance, and what written follow-up will control the bid. Preserve your attendance evidence, but never treat your notes or an oral answer as a substitute for the buyer's written solicitation or addenda.
The buyer's current documents control. A useful intake review asks whether the event is mandatory, merely encouraged, or informational; whether registration and attendance are separate requirements; whether a prime, named subcontractor, or authorized representative must attend; and whether multiple dates or a remote option exist. Capture the document name, clause, version, and official source URL beside the answer. If the wording conflicts across a portal notice, attachment, and addendum, ask the authorized buyer contact through the stated channel before relying on a guess.
Texas's current statewide procurement guide says a pre-bid conference notice should give the date, time, location, and whether attendance is mandatory or voluntary. Where a Texas state conference is mandatory, the solicitation must include a disqualification warning, and the agency's sign-in sheet is its official attendance record. Those are Texas state guide rules, not a universal rule for every city, school, county, or federal buyer. (Texas Comptroller — Procurement and Contract Management Guide, version 4.0)
Oregon DOT's construction process gives another concrete example: for its mandatory pre-bid meetings, the attendee list is important to confirm that the low responsive bidder attended. The agency also calls for a posted summary that identifies attendees and their organizations. That ODOT procedure does not determine another buyer's representation or sign-in rule. (Oregon DOT — PD07, PS&E Submittal to Bid Opening)
Federal construction provisions show why the specific solicitation matters. FAR 52.236-27 urges offerors to inspect the site and gives a basic method to arrange a visit or an alternate for an organized visit with a meeting point. The provision alone does not say every federal construction visit is a mandatory eligibility gate. (Acquisition.gov — FAR 52.236-27)
| Control | Record before the meeting | Verify afterward |
|---|---|---|
| Attendance rule | Exact mandatory or optional language and source version | Whether an amendment changed the rule |
| People | Required bidder entity, authorized representative, and any subcontractor role | Who actually attended for which firm |
| Logistics | Local date, time zone, address or meeting link, check-in, security, and registration deadline | Arrival and sign-in evidence |
| Site access | Safety gear, identification, photography limits, escorted areas, and accessibility instructions | What areas were actually available to inspect |
| Questions | Written question deadline and authorized submission channel | Which answers were officially published |
| Follow-up | Buyer portal, meeting minutes, addenda, and bid due date | Whether the response set reflects every current change |
Assign one person to own the event and one backup. Confirm that the registered legal entity matches the bidder identified in the solicitation. Save the registration receipt when the buyer provides one, and tell the attendee how the buyer will record presence. A calendar invitation proves scheduling, not buyer-recognized attendance. If travel or access fails, contact the designated buyer representative promptly and document the answer; do not assume a substitute visit or later attendance is permitted.
Read the complete current bid set, not only the event notice. Bring the project identifier, relevant drawings or scope sections, a structured observation sheet, and the buyer's permitted question route. For a prime-subcontractor team, decide whose attendance is required and who will carry site findings into pricing, schedule, and scope. The state and local RFP response checklist gives the wider deadline and document inventory around this event.
Follow the buyer's sign-in process exactly. Confirm the attendee name and represented firm are entered as required; do not substitute your own photo of the room for the buyer's official record. Keep a lawful copy or confirmation when offered, and note the time and contact. If the buyer will later publish an attendee list, compare it with your internal record and raise any discrepancy through the authorized channel.
Record observations as observations: location, condition, measurement source, photo reference if allowed, and who saw it. Distinguish a visible condition from an assumption about hidden conditions or future work. Track pricing and safety questions separately. A site visit helps estimate the work, but it does not give a bidder permission to disregard the written specifications or use an informal answer that other bidders have not received.
A meeting is useful for understanding the work; it does not automatically rewrite the solicitation. In federal sealed bidding, FAR 14.207 says a pre-bid conference may explain complex specifications but must not replace an amendment to a defective or ambiguous invitation. FAR 14.208 says material changes and information needed to bid fairly require an amendment even when the topic arose at a conference. (Acquisition.gov — FAR 14.207; FAR 14.208) Texas's guide similarly says verbal answers that affect the solicitation must be confirmed in a written addendum. (Texas Comptroller — Procurement and Contract Management Guide, version 4.0)
After the meeting, compare your notes with the buyer's posted minutes, Q&A, and current addenda. Mark each issue as observation, submitted question, official answer, written change, or unresolved. An unresolved price or scope issue belongs in a named decision queue; it should not silently become a bid assumption. For the full process of submitting and reconciling questions, use the pre-bid Q&A guide. For version changes and acknowledgments, use the RFP addendum-tracking guide.
Oregon DOT's procedure illustrates the separation: its meeting summary records attendees, agenda, and follow-up issues, while changes to plans, special provisions, or bid items require an addendum. (Oregon DOT — PD07) Your team should apply the same distinction in its internal record while following the rules of the actual buyer.
A mandatory event can be an early eligibility gate. If the required bidder did not attend or cannot prove attendance under the buyer's stated method, stop and obtain an authorized answer before spending more response effort. Also revisit scope, site access, safety conditions, specialty trades, schedule, bonding, and pricing assumptions. A visit that reveals an unpriced condition or an unavailable subcontractor can change a pursuit decision even if attendance was valid. Document that decision using the go/no-go framework.
Before submission, a reviewer should reopen the official portal and confirm the latest solicitation version, attendance status, written answers, addenda, due date, and required acknowledgments. The prime should verify that subcontractor quotes reflect the same document set. Keep the proof and decision record together, but submit only what the buyer requests. An internal attendance log is useful evidence for the team; it is not a substitute for the agency's own eligibility determination.
GreenLight can work from the current opportunity files your team supplies, organize detected response requirements into a source-linked package inventory, and surface response artifacts that need review after a document-set change. A team can use those controls to track meeting-related instructions or addendum acknowledgments found in the files and to revisit affected response work.
GreenLight does not register for or attend a meeting, certify that a bidder signed in, monitor every procurement portal automatically, decide the legal effect of a missed visit, or guarantee that every instruction was extracted. The team must verify the buyer's current notice, attendance record, and written changes. This is an operational aid for the human reviewer, not proof of bid eligibility.
Research reviewed September 22, 2026. The Texas, Oregon, and federal examples describe different procurement systems. A city, county, school district, state, or federal solicitation may use different attendance, registration, sign-in, and amendment rules. Event dates, access instructions, and bid deadlines can change. Reopen the current official buyer documents and obtain an authorized answer when eligibility is uncertain.
No. Read the current solicitation and addenda for the exact buyer's attendance rule. The federal site-visit provision cited here encourages inspection in its construction context but does not itself make every visit mandatory.
Not necessarily. Registration reserves or requests access; the buyer may use a sign-in sheet or another official method to verify who attended and which firm they represented. Follow the method in the solicitation.
Only if the buyer's instructions permit that arrangement. Record the required entity and representative before the event; do not infer that any team member's attendance satisfies a mandatory bidder rule.
Treat the answer as an issue to reconcile. Ask through the designated channel and check the official written response or addendum before relying on a material change.
See how GreenLight helps your team qualify the opportunity, organize the buyer's requirements, and check the package before you submit it.