Study guide
Bid/Tender Support
BICSI RCDD Registered Communications Distribution Designer
Track your progress as you read
Finished sections get a check mark.
1 Introduction & the RCDD Exam
RCDD Exam Facts, Format & the v15 Blueprint Eligibility, the TDMM & How to Study
2 Codes, Standards & the Design Framework
The Standards Ecosystem & Order of Precedence Structured Cabling Architecture Overview Telecommunications Administration & Labeling
3 Principles of Transmission & Media
Transmission Fundamentals Balanced Twisted-Pair Copper Optical Fiber Media Coaxial, Specialty Media & Remote Powering
4 Telecommunications Spaces
Space Hierarchy & Sizing Environmental & Power/HVAC Coordination Space Infrastructure & Layout
5 Pathways
Horizontal Pathways Backbone / Riser Pathways Pathway Sizing & Fill Calculations
6 Horizontal & Backbone Distribution Design
Work Area & Outlets Horizontal Cabling Design Backbone Distribution Design Design Documentation, BOM/LOM & QA
7 Grounding, Bonding & Electrical Protection
Bonding & Grounding Infrastructure Power Distribution, Lightning & Surge Protection Electrical Protection, Separation & the NEC
8 Firestopping & Life Safety
Firestop Systems & Penetrations
9 Field Testing & Verification
Copper Field Testing Fiber Testing & Certification
10 Specialized Environments
Outside Plant (OSP) Data Centers Intelligent Buildings, AV, ESS & Specialty Environments
11 Project Delivery: Scope, Bid/Tender & Installation
Defining Project Scope & Estimating Bid/Tender Support Installation Process Support Project Administration, Risk & Closeout
Bid/Tender Support
Key Takeaways Explain This Topic AI
The Support ICT Bid/Tender Process domain represents 11% of the RCDD exam and covers generating/responding to RFPs, RFQs, and RFIs, reviewing bids, and supporting bidders' conferences.
An RFP (Request for Proposal) is used when the owner wants contractors to propose an approach and price, while an RFQ (Request for Quotation) is used when scope is fully defined and only price is being solicited.
An RFI (Request for Information) is the formal mechanism a bidder uses to seek clarification on ambiguous or conflicting bid documents, and RCDD responses to RFIs become part of the bid record.
Bid review evaluates both completeness (all required items priced and submitted) and design compliance (proposed materials and methods meet the specified design).
A bidders' conference and site walk lets all prospective bidders ask questions and view existing conditions together, so every bidder prices the work from the same information.
Last updated: July 2026
Generating and Responding to RFPs and RFQs
Once design documents are complete enough to competitively price, the project moves into the bid/tender process — the domain in which contractors are solicited, questioned, and evaluated before a construction contract is awarded. The RCDD's role spans both sides of this process: generating solicitation documents on behalf of an owner or design team, and responding to solicitations when the RCDD is retained by a contractor or manufacturer's representative.
Two solicitation vehicles dominate ICT procurement, alongside the RFI used during the bid period itself:
Vehicle When Used What It Solicits
RFP (Request for Proposal) Scope is defined at a conceptual or performance level; the owner wants contractors to propose their approach An approach/methodology, qualifications, and price — often evaluated on best value, not lowest price alone
RFQ (Request for Quotation) Scope, materials, and methods are fully defined in construction documents A firm price to execute a specifically defined scope — typically evaluated on lowest responsive, responsible price
RFI (Request for Information) Issued during the bid period by a bidder Clarification of an ambiguous, conflicting, or missing item in the bid documents
An RCDD generating an RFP or RFQ is responsible for making sure the package is unambiguous enough that every bidder prices the identical scope — inconsistent or vague bid documents produce bids that cannot be fairly compared, and set up disputes during installation when a contractor claims a requirement was never clearly specified.
The RFI Process
The RFI is the formal channel through which a bidder raises questions during the bid period rather than making assumptions or pricing contingencies into a bid. A well-run bid process treats every RFI answer as an addendum distributed to all bidders — never as a private clarification to one bidder — because selective information sharing undermines fair competition and can be legally challenged.
RCDD responsibilities in the RFI process include:
Reviewing incoming RFIs for design impact, not just answering the literal question asked.
Determining whether an RFI reveals a genuine design gap, error, or conflict that requires a documented change to the bid documents (an addendum) rather than a simple clarification.
Tracking RFI responses so the eventual bid record — and later, the construction contract — reflects every clarification made.
Turning around RFI answers quickly enough that bidders have adequate time to incorporate the answer into their price before the bid deadline.
The Bid Document Package
The bid documents are the complete package a bidder prices from. For ICT scope, this typically includes the RCDD's construction documents (drawings and specifications), a bill or list of materials, general and supplementary conditions, the bid form itself, and any addenda issued during the bid period. The RCDD is responsible for ensuring the ICT-specific portions of this package are internally consistent — that the drawings, specifications, and bill of materials all describe the same scope — because bidders price against the tightest reading of whichever document is most restrictive, and gaps between documents become change-order opportunities after award.
Reviewing Bids for Completeness and Design Compliance
When bids are returned, the RCDD's role shifts to bid review — evaluating submissions on two distinct axes:
Completeness — did the bidder price every line item required by the bid form, submit all required qualification and bonding documentation, and respond to every addendum?
Design compliance — do the bidder's proposed products, manufacturers, and installation methods actually meet the specified design, or has the bidder substituted something that changes performance, warranty, or code compliance?
A bid that is low but incomplete, or low but non-compliant, is not automatically the bid to recommend — the RCDD's review protects the owner from a bid that looks attractive on price but does not actually deliver the specified design. Where a bidder has proposed a substitution, the RCDD evaluates it against the design intent (see Section 11.1) to determine whether it is a genuine equal or a scope reduction in disguise.
Bidders' Conferences, Site Walks, and Qualifying Bidders
A bidders' conference (sometimes combined with a site walk ) is held during the bid period so every prospective bidder receives the same information at the same time, in the same room. This serves two purposes: it lets bidders ask questions face-to-face (which are then formalized as RFI/addenda for all bidders), and — critically for renovation work — it lets every bidder see the same existing conditions the RCDD documented during the original site survey, reducing the risk of unpriced field-condition surprises later.
Finally, qualifying bidders is the process of confirming that firms invited to bid (or that respond to a public solicitation) have the licensing, bonding capacity, safety record, manufacturer certifications, and relevant experience to actually perform the specified ICT scope. An unqualified low bidder is a greater risk to the project than a qualified bidder at a higher price, and the RCDD often contributes technical qualification criteria — such as required manufacturer certifications for a specified structured cabling warranty — to the owner's overall bidder-qualification process.