12.1 Site Visits, RFIs, Substitution Requests & Pre-Bid Meetings

Key Takeaways

  • A mandatory site visit or pre-bid conference is typically a responsiveness gate; a no-show is not an equally informed bidder
  • An optional walk still leaves existing-condition risk on the bidder; optional is not a waiver of due diligence
  • RFI answers that change price or scope belong in addenda issued to every bidder, not in hallway emails to one firm
  • Equal-product substitution requests must prove functional equivalence in the published window so an addendum can authorize them for all
  • A useful pre-bid agenda walks riser rooms and head-ends, clarifies Division 28 versus power and communications, and covers safety; silent bidders who skip the walk fail later on claims
Last updated: September 2026

Site Visits, RFIs, Substitution Requests, and Pre-Bid Meetings

Independent OpenExamPrep teaching for published PSP Domain 3 Task 1 knowledge is that implementation starts before a shovel hits dirt. Domain 2 produced drawings and shall-language. Domain 3 asks whether the owner can buy that design without a secret handshake, a surprise closet, or a camera family that appears after award. The bid process—site visits, requests for information (RFIs), substitution requests, pre-bid meetings, and addenda—is how every serious bidder prices the same job.

Exam focus: Mandatory walks can disqualify no-shows. Optional walks still leave site-condition risk on the bidder. Hallway answers are not addenda. Equal-product substitutions belong in the published window.

Why this task sits in implementation

A complete Division 28 book that nobody walked is still a change-order machine waiting for a purchase order. The practitioner who wrote identification at the badge plane still has to put bidders in the riser rooms, on the dock, and in the IDF that is already out of rack units. Skipping that ritual does not make the designer faster. It makes the first invoice a fight about what “existing conditions” meant.

Public owners and many private owners use a formal solicitation. The names of the packages (RFP, RFQ, IFB) are the next section. This section is the process that surrounds every package: who saw the site, who asked questions, who got a written answer, and who is allowed to offer an equal product. If that process is sloppy, evaluation in 12.4 is theater. You will be scoring firms that did not price the same physical world.

Mandatory versus optional site visits

A mandatory (sometimes “required”) site visit or pre-bid conference is a condition of responsiveness. If the advertisement says attendance will be recorded and that non-attendees will not be considered, a silent bidder who prices from PDF drawings is not clever. That bid is typically rejected as non-responsive. The owner is not being petty. The owner is documenting that every remaining bidder saw the cramped head-end, the occupied pharmacy that can only be worked at night, and the plenum that will not take the specified jacket.

An optional visit still matters. Optional does not mean “the site is fictional.” It means the owner will not throw out a bid solely for absence, but the bidder still assumes existing-condition risk that a reasonable walk would have revealed: conduit fill, spare pairs, ceiling type, working hours, escort rules, infection-control barriers, and whether the “security closet” is a janitor’s sink. On exam stems, optional is not a waiver of due diligence. A later claim that “the drawings did not dimension the rack” fails if a competent estimator could have opened the rack on the advertised walk.

Some packages split the difference: a mandatory conference in a room plus an escorted walk that is strongly urged. Read the advertisement. If sign-in is the gate, sign in. If photos of interiors are forbidden, the walk is the only lawful way to see the riser. If union or badging rules limit who may enter, say so in the notice so out-of-town firms can send a local licensed partner instead of skipping the site.

Keep a sign-in sheet with printed names, firms, and emails. That sheet is evidence in a protest. It is also the distribution list for addenda if the procurement portal fails. Do not let a salesperson “sign for” three companies. Each bidder’s representative should be identifiable.

Why silent bidders who skip the walk fail later

The pattern is predictable. A firm copies device counts from the drawing, misses that Camera 40’s homerun crosses a hazardous occupancy that needs a different cable listing, misses that the access panel sits behind a transformer with no working clearance, and misses that the owner’s IT standard forbids the specified VLAN. After award, every one of those facts becomes a change order or a claim. The contractor says the documents were silent. The owner says a competent estimator would have walked. The professional who allowed a mandatory walk and still awarded to a no-show has a record problem. The professional who made the walk optional and wrote “bidders shall verify existing conditions” has a stronger contract position, but still a project that will slip.

Silent bidding also fails safety and operations. Division 28 work in a live hospital, a school in session, or a cash vault needs badging, infection control, hot-work permits, and after-hours windows. Those rules are easier to believe when you have stood in the corridor. A bid that assumes eight-hour weekday access to a pharmacy anteroom will blow the schedule on week one, then bill overtime as if it were a hidden condition.

Worked warehouse: Door 4 from earlier chapters is a dock leaf with one spare copper pair. The drawing shows four new heads and a note that pathway is “by others.” A bidder who walks the closet sees four pairs used, a PoE switch at capacity, and a long homerun. That bidder prices a switch, a small fiber run, or an honest exclusion the owner can evaluate. The silent bidder prices cameras only and will be back with a claim. The walk did not create the constraint. It made the constraint visible in time to price it.

Worked clinic: the specified maglock power supply will not fit the listed fire-alarm release module once you see the existing can. The silent bidder discovers this at submittal. The bidder who opened the can at the pre-bid prices a larger enclosure or a different listed assembly and does not spend the first month arguing.

Pre-bid meeting agenda that actually protects the owner

A pre-bid meeting is not a sales mixer. Independent study for this published task treats the agenda as a control:

  1. Sign-in and identity of the procurement contact. Questions after this date go through one mailbox, not through a friendly integrator’s former colleague on the design team.
  2. Safety briefing. Escort rules, PPE, no photography in certain suites, infection control, lockout, roof access, and who may enter a riser. If a bidder is injured on an unofficial walk-through, the owner’s process failed twice: safety and fairness.
  3. Walk the riser rooms, IDFs, MDF, security head-end, and typical doors. Open the panel. Count spare slots. Look at pathway fill. Stand at the badge desk and the dock. Look at ceiling type. Confirm generator and UPS if the spec assumes them. Look at the pharmacy anteroom and the dock leaf that carry residual risk from Domain 1.
  4. Clarify Division 28 versus Division 26/27. Electronic safety and security is usually CSI MasterFormat Division 28. Power, raceway, and fire-alarm interfaces often live in electrical or fire documents. Communications pathways may sit in Division 27. If the bid form is silent on who pulls homeruns, every bidder will assume the other trade. Say it in the meeting and put it in an addendum.
  5. Working hours, phasing, and occupied-building constraints. Pharmacy nights only. School summer only. Airport badging lead time. Loading-dock blackout during receiving waves.
  6. RFI and substitution deadlines, bid date, and how addenda will be issued.
  7. Bonding, insurance, and manufacturer-certification expectations at a high level (evaluation details in 12.4).

Minutes that say “discussion held” without an addendum do not change the contract. If someone asked whether the specified VMS license tier includes analytic channels, the answer belongs in writing to all. Oral “we always do it this way” is how incumbents get a cheaper number.

RFI windows

A request for information during bidding is a written question about an ambiguity, conflict, or missing fact in the solicitation. Owners set an RFI window that closes several days before bids so there is time to issue an addendum. Late RFIs are often unanswered; the bidder then must price the documents as written or take a qualified bid that many public owners will reject as non-responsive.

Private hallway conversations—“just use our usual camera”—are how one firm gets a cheaper number and everyone else prices the spec. That is both an ethics problem (12.4) and a process failure. The professional move is: receive the question, decide whether the documents need a change, and publish.

RFIs are not a substitute for a walk. “How many rack units are free?” is often answerable only in the closet. “Does Door 4 need fail-secure or fail-safe?” should already be in the functional requirement; if it is not, the RFI is doing Domain 2’s leftover homework in Domain 3, and the addendum should fix the shall-language for everyone.

Group similar RFIs. Twenty firms asking whether training is included should produce one addendum sentence, not twenty private replies. Stamp the addendum date. Require acknowledgment on the bid form.

Addenda

An addendum (plural addenda) is a written change to the solicitation before bid opening. It can add a drawing, correct a door schedule, extend the bid date, mandate a walk, or authorize an equal product. Bidders typically acknowledge addenda on the bid form. A bid that misses the last addendum may be non-responsive if that addendum affected price or scope.

Addenda are how you keep competition fair. They are also how you stop the project from inheriting a known error. If the walk revealed that the “security closet” is a wet janitor room, do not leave that to oral folklore. Issue a sketch, a relocated head-end, or a pathway note.

Substitution requests and equal product

Owners often name a manufacturer and model or equal. The or-equal path is a substitution request submitted in the published window, with cut sheets, listing evidence, license implications, and a statement of functional equivalence against the performance requirements (identification at a named plane, encrypted supervised reader traffic, documented fail state, and so on). The designer or owner accepts or rejects in an addendum. That way every bidder may use the approved equal.

What substitution is not:

  • Shipping a different camera after award because the specified model is on backorder, unless the contract’s substitution clause is followed.
  • A private email to one dealer.
  • “Equal” meaning only that both products are cameras.

If the specification is proprietary (no or-equal), that is a sole-source flavor and needs the justification ethics of 12.2 and 12.4. Do not hide a proprietary spec inside “or equal” language you never intend to honor.

ArtifactWhat it doesExam trap
Mandatory site visitCondition of responsiveness; records who saw the siteTreating no-shows as equally informed
Optional site visitDue diligence still on the bidderThinking optional means existing conditions are free extras
Pre-bid agendaSafety, risers, Division 28 splits, deadlinesA mixer with no addendum
RFIWritten question in a windowPrivate answers to one firm
AddendumChanges the documents for all; usually must be acknowledgedHallway promises
Substitution / or-equalTimed request proving equivalent functionAfter-award brand swap

The bid process is a fairness machine and a discovery machine. Use both. Section 12.2 names the package types that this process sits inside.

Loading diagram...
Pre-bid process: one set of documents for every bidder
Test Your Knowledge

A bidder never attends a mandatory pre-bid site walk and later claims extra cost because the IDF had no spare rack units. What is the most defensible owner position?

A
B
C
D
Test Your Knowledge

A vendor wants to bid a different camera family than the specified model under an or-equal clause. When is that substitution request properly handled?

A
B
C
D
Test Your Knowledge

Why should owners publish RFI answers as addenda instead of answering each bidder privately?

A
B
C
D