DAS RFP Guide: Define Scope, Pricing and Accountability

DAS RFP Checklist: 10 Requirements to Establish Before Bidding

The enterprise should issue one requirements baseline and one response format. The integrator's job is to show compliance, document exceptions and recommend a better approach when one exists. Innovation belongs in a clearly identified alternate, not in silently changing what was requested.

A bidder may recommend a technically superior or lower-cost solution. The recommendation should explain how it satisfies or improves on the owner's baseline, identify any tradeoffs and show its price separately, so the base bids remain comparable.

Define Coverage and Facility Requirements on One Set of Drawings

Start with controlled floor plans, the building's use, required occupancy scenarios, known service complaints, projected changes and a target in-service date. Mark the required cellular service areas directly on the drawings, including offices, common areas, elevators and lobbies, garages, back-of-house spaces, stairwells and outdoor transition areas where applicable. State which spaces are deliberately outside the required scope and which expansions require separate option pricing.

The owner should set the coverage and service objectives by area, with advice from a qualified RF designer where necessary. A performance specification is more useful than a generic request for “good coverage.” Describe minimum acceptable signal levels and quality, applicable carriers and technologies, representative voice and data tests, and higher-density spaces requiring additional capacity analysis.

Distribute any existing surveys, carrier correspondence, as-built records and construction restrictions to every bidder on the same basis. Where discovery is incomplete, make that fact explicit and apply the same paid or staged discovery requirement to all bidders. All clarifications and drawing revisions should be formally shared with the entire bidding group.

For a three-building campus, the enterprise might require coverage in two occupied buildings and a connecting garage, then price the third building as an alternate. All bidders should price the same base buildings. They may recommend additional future-ready pathways or a different distribution design, but those changes must be identifiable against the owner's scope.

Commercial cellular coverage supports subscribers on public mobile networks. Emergency responder radio coverage and public safety DAS carry separate code-driven requirements, approvals and acceptance tests and should have distinct technical specifications and contractual deliverables, even if construction is coordinated.

Set Carrier, Band, Signal-Source and Capacity Standards

A DAS distributes cellular radio signals; its indoor antennas cannot compensate for a source that lacks the necessary capacity, quality or carrier authorization. The RFP should therefore specify more than the number of carriers sought. The enterprise, supported by its wireless advisor, should establish a carrier and frequency-band schedule covering required operators, LTE and 5G technologies and the frequency bands the project must support. If that schedule cannot responsibly be finalized before bidding, define a common engineering-validation stage and approval gate, rather than allowing each DAS integrator to choose a different technical baseline.

Also establish anticipated occupancy and peak-hour demand, high-density zones, technology-upgrade expectations, coverage-quality requirements and the minimum source reliability and support obligations. For a structured methodology, see DAS Capacity Planning: Size for Peak Indoor Demand.

Managed carrier-connected sources versus off-air donor/BDA sources

An off-air arrangement uses an outdoor donor antenna and a properly engineered repeater or BDA to receive and amplify available outdoor macro signal for distribution indoors. It may be cost-effective where outdoor signal conditions, donor isolation, carrier authorization and demand make it suitable. It does not create new carrier capacity, and indoor service remains exposed to limitations and changes in the outdoor source.

A managed carrier-connected signal source uses carrier-approved radio infrastructure, coordinated transport and an operating model intended to provide a defined source to the DAS, rather than relying on the available outdoor macro signal. CTS Forté Neutral Source is an enterprise-funded managed source option designed to deliver carrier-connected signal with ongoing source-layer coordination and support, similar in function to a carrier-provided in-building source. It offers a more predictable procurement path than waiting for discretionary carrier-funded equipment, although the precise carriers, scope, timing and service commitments must be stated in the applicable agreement.

The RFP must say which signal-source arrangements are acceptable in the base bid. If the owner requires managed carrier-connected sources, a donor antenna/BDA proposal should be a separately identified alternate, not an undisclosed low-cost substitution. If off-air sources are permitted, require documented donor measurements, operator permissions where applicable, capacity limitations, expected variation in source conditions, maintenance obligations and an owner-approved plan if outdoor service changes.

Do not confuse a funding pursuit with committed carrier service

For each operator, require written disclosure of whether source equipment, approvals and financial participation are committed, pending or merely anticipated. An integrator's statement that it will pursue carrier-funded equipment is not a carrier funding commitment or a guarantee of activation. A low initial bid that uses off-air equipment as an interim solution while promising free carrier signal sources later can leave the owner with a permanent stopgap if that funding never appears.

An enterprise-funded managed source can instead be included in the project scope from the outset, with clearly identified costs, responsibilities and contractual service commitments. This does not eliminate carrier approvals or dependencies. Any guaranteed delivery date, supported carrier or performance obligation should be documented in the signed service agreement, together with applicable prerequisites and exclusions.

Require separate carrier-specific participation milestones, the party accountable for coordination and approval, a fallback or remedy if an expected source fails to materialize, and clear treatment of recurring source charges. The related article DAS Carrier Activation: Plan Each Operator's Go-Live provides the detailed implementation framework.

A bid comparison that treats them as interchangeable measures price, not the service the enterprise will receive.

Evaluate Active, Passive and Hybrid DAS Against the Same Outcomes

The RFP should make clear what must be achieved, without unnecessarily requiring every integrator to use the same equipment architecture. Depending on building scale, distances, existing pathways and capacity needs, a bidder may propose active DAS using powered remote electronics and fiber, passive DAS using coaxial distribution and passive components, or hybrid DAS combining the two. The design should be judged against the issued carrier, band, coverage, capacity, acceptance and lifecycle requirements.

Digital indoor small-cell systems can also be architectural alternatives to DAS. Depending on the solution, configuration and operator arrangements, distributed indoor radio nodes may support single-carrier or neutral-host cellular service without using a conventional DAS antenna-distribution architecture. These designs merit consideration when they satisfy the same coverage, capacity, supported-carrier, security, approval and lifecycle requirements.

A bidder proposing a different architecture should supply its RF design basis, supported operators and bands, peak-capacity model, scaling assumptions, headend or radio-room needs, network dependencies, monitoring and lifecycle costs. The response should distinguish full compliance from exceptions, and price the proposed alternate separately when the RFP requires a comparable DAS base bid. A lower-priced design that drops a requested band, carrier or building is not a like-for-like cost improvement.

Specify Construction, Building and IT Responsibilities

A common scope should identify who supplies or prepares headend rooms, space and cooling, normal and backup power where required, risers, fiber, pathways, antenna mounts, rooftop access, firestopping, ceiling restoration, security credentials, permitting and after-hours access. The enterprise should establish the governing site standards and contractual allocation of responsibilities before issuing the RFP, then require bidders to price and acknowledge the same assignments.

Likewise, publish baseline enterprise IT and cybersecurity requirements where equipment will need IP transport, firewalls, remote management, monitoring, timing or protected connectivity. Bidders should document the actual connections, bandwidth, addresses, ports, security controls and handoff requirements of their proposed equipment. Deviations, unavailable owner-furnished resources and third-party dependencies must be conspicuous in the response, not buried in a footnote.

A contract called “turnkey” is not automatically complete. Its responsibility matrix should match the owner's stated requirements and name the accountable party for each deliverable, even when work is coordinated with landlords, the general contractor, IT, mobile operators or specialty subcontractors.

Require One Pricing Template for Every Proposal

The enterprise should issue a required pricing template covering discovery, engineering, carrier coordination, signal sources, headend and DAS equipment, pathway work, installation, commissioning, acceptance testing, documentation, backhaul and post-deployment support. Every bidder should price the same required service scope and evaluation period before presenting any alternates.

The common pricing template should identify:

• Base price: A complete, compliant proposal that meets all mandatory scope and performance requirements.
• Unit prices and allowances: Defined quantities or provisional sums using common measurement and reconciliation rules.
• Exceptions and exclusions: Any item omitted from the mandated scope and the cost and schedule consequences of that omission.
• Optional alternates: Design variations, future areas, source strategies or enhanced service levels with separate pricing and clearly stated tradeoffs.
• Recurring charges: Managed source fees, transport, software, monitoring, maintenance, licenses and escalation.
• Lifecycle total: All owner and supplier costs across the enterprise's stated comparison period, including renewals, upgrades and exit obligations where quantifiable.

A low base price can be misleading when it excludes the source equipment, assumes free carrier participation, understates owner-provided infrastructure or omits recurring services. Compare both the base-price compliance and the total cost to deliver and operate the specified service.

A bidder may propose Network-as-a-Service or another fully managed contracting approach, but it should be priced as a transparent alternate if the common base is a purchase-and-support model. Financial structure should not obscure technical omissions or transfer risks that the owner's RFP requires the supplier to carry.

Set Delivery Milestones and Carrier Activation Conditions

The enterprise should specify required completion dates, approval gates, documentation, notice periods and the consequences of delays. The bidder should return a critical-path schedule covering discovery, design approval, carrier engagement, equipment lead times, construction, source integration, per-carrier activation, testing, deficiency correction and final acceptance.

Installation completion is not the same as live multi-carrier service. A system may be mechanically complete while one operator remains unapproved, unconnected or untested. The RFP should prescribe how partial activation affects milestone payments, service commencement, acceptance status and the integrator's ongoing duty to complete the project. Require verifiable evidence of the carrier-specific status, not a general declaration that the DAS is “multi-carrier ready.”

Establish Acceptance Testing and Closeout Requirements

The owner should define the required performance thresholds, areas and scenarios to be validated, applicable operators and bands, minimum acceptance evidence, deficiency-resolution rules and approval authority. Each DAS integrator should propose an appropriate RF measurement and active-service testing methodology for approval, demonstrating how its plan will verify the same owner-defined criteria.

Require both applicable RF measurements and active subscriber service testing, with clearly defined voice, data and signal-quality objectives. Measure performance in representative high-use conditions when busy-hour capacity matters; a low-traffic walk test does not validate peak demand. Thresholds and metrics must be appropriate to LTE or 5G NR technology, applicable carrier configurations and the owner's service requirements.

Closeout should include as-built drawings, equipment and asset inventories, carrier-specific activation evidence, test logs, unresolved exceptions, warranty and software information, maintenance procedures and support contacts. The companion DAS Acceptance Testing: Verify Every Carrier's Service addresses how to turn these contractual requirements into a consistent field-verification record.

Define Operating Commitments, Ownership and Exit Terms

The enterprise should set minimum operating requirements in the RFP: monitoring hours, fault detection, response times, escalation rules, preventive maintenance, dispatch coverage, restoration objectives, reporting, spare equipment expectations and cybersecurity responsibilities. Bidders should price those obligations against the same service levels, and identify the difference between response commitments and restoration guarantees.

State which assets are owner-owned or supplier-owned, who holds software and service licenses, who controls configurations and documentation, and what happens after renewal, carrier network changes or termination. Establish rights to access records and support a handover, along with costs for equipment removal or replacement where applicable.

CTS MMRD (Monitoring, Maintenance, Repair and Dispatch) is one example of a support structure; the governing requirement should remain the owner's documented level of service. Service labels alone are not a substitute for comparable commitments.

Sample DAS RFP Requirements

The following sample provisions establish core technical, delivery and operating requirements for a commercial cellular project. Complete the referenced drawings, performance schedules, responsibility matrix and commercial terms with input from engineering, IT, facilities, procurement and legal stakeholders before issuing the RFP.

1. Base coverage and performance (owner requirement). The successful proposer shall design, furnish, install, commission and deliver the commercial indoor cellular system covering all mandatory areas on Drawing Set [revision/date] and meeting Coverage and Service Schedule [A]. No mandatory areas may be excluded from the compliant base bid. Owner-designated optional areas [Schedule B] shall be priced as alternates. Any exception must appear in a separate deviation register; it does not amend the owner's base requirement.

2. Carrier, technology, band and source requirements (owner requirement). The base system shall support the mobile operators, LTE/5G technologies and frequency bands listed in Carrier and Band Schedule [C], together with the minimum source, capacity and service criteria in Performance Schedule [D]. Permitted base-bid source arrangements are defined in [D]; other arrangements, including off-air donor/BDA designs where not permitted in [D], must be offered as separately priced alternates. Each bidder shall provide a compliance matrix by carrier and band, identify confirmed versus pending approvals and source commitments, and document dependencies and costs.

3. Delivery, pricing and acceptance (owner requirement). The proposer shall price every mandatory deliverable using Owner Pricing Template [E], satisfy Responsibility Matrix [F] and Delivery Milestones [G], and perform acceptance testing against Owner Acceptance Criteria [H], using an owner-approved test plan proposed by the integrator. Bidder-generated limitations, allowances and exceptions shall be listed separately. Additional designs or cost-saving alternatives may be proposed in the designated alternate section without changing the compliant base scope.

4. Operations and lifecycle (owner requirement). The successful proposer shall meet Monitoring and Support Schedule [I], asset and record ownership provisions [J], renewal and termination requirements [K], and the agreed service handover process. The bidder shall state the equipment, staffing, third-party services and recurring fees needed to meet each obligation and identify any exception explicitly.

Evaluation rule: First assess compliance with the common base scope, including the quality and certainty of the signal-source commitments. Then evaluate separately priced alternatives for better performance, lower lifecycle cost, flexibility or reduced delivery risk. Do not compare noncompliant base bids as though they deliver the same result.