When fiber quotes come back “all-in,” they often are not all-in. The gaps usually hide in construction assumptions, handoff details, route diversity, taxes and surcharges, and order milestones. A tighter RFP forces every bidder to price the same scope, disclose every add-on, and commit to the same delivery and SLA terms.
Make every bidder price the same scope, disclose the same categories of fees, and commit to the same delivery and performance definitions. That is the fastest way to turn “apples to apples” into a reality for fiber quotes.
- MRC = monthly recurring charge for the service.
- NRC = non-recurring charges (install, cross-connect, port, activation, engineering).
- Special construction = make-ready or build costs required to extend network to the service location.
- Demarc = the handoff point where provider responsibility meets customer responsibility (suite, MDF/MMR, MPOE).
- UNI / EVC = common carrier ethernet terms used to define handoff and virtual circuit attributes. :contentReference[oaicite:0]{index=0}
- 🟦Street address, floor, suite, and building name
- 🟦Site type: office, DC, plant, warehouse, retail, temporary
- 🟦Desired demarc: suite, MPOE, MDF/MMR, meet-me room cross-connect, or provider NID on wall
- 🟦Required delivery window and any blackout dates
- Dedicated Internet Access (DIA) with committed bandwidth and SLA.
- Ethernet (E-Line / E-LAN / E-Tree) for site-to-site connectivity, with clear UNI and service attributes. :contentReference[oaicite:2]{index=2}
- Wavelength when transparent transport and optics matter.
- Backup path option (separate physical route and provider, if possible).
- 🟩Include all labor, materials, splicing, testing, and turn-up activities through demarc
- 🟩Include building entry work, riser access coordination, and any conduit assumptions
- 🟩Include fees for ports, handoff optics, smartjack/NID, and cross-connects if applicable
- 🟥Exclude internal LAN work beyond demarc only if clearly stated with boundary diagram
- 🟥Exclude any “TBD” fees; use an estimated value and the rule for true-up
If the bidder anticipates construction, the response must separate (1) base service pricing from (2) special construction pricing and assumptions. Many providers and contract documents treat engineering, installation, and construction as potentially billable elements, so the RFP must force early disclosure. :contentReference[oaicite:3]{index=3}
Fee transparency is a known pain point. The FCC’s broadband label framework highlights categories like one-time fees and early termination fees, which are exactly the items that often surface late in telecom orders. :contentReference[oaicite:4]{index=4}
| Fee category | What the response must include | Common scope gap that causes surprises | RFP requirement line |
|---|---|---|---|
One-time install and activation |
Itemized NRC list with quantities and unit rates | “Install included” but later charged for handoff gear or turn-up | All one-time fees must be listed by name and amount |
Construction and make-ready |
NTE estimate, assumptions, and triggers | Build cost appears after survey when permits or lateral needed | No “TBD construction” responses allowed |
Cross-connects and MMR fees |
Monthly and one-time charges, who bills them | DC facility bills cross-connect separately from carrier quote | State whether cross-connect is included, excluded, or pass-through |
Equipment and CPE |
Included or rented, model class, replacement terms | Managed router “optional” becomes required for SLA support | Any equipment fee must be disclosed as MRC or NRC |
Taxes, fees, and surcharges |
Pass-through categories and estimate method | Regulatory recovery and similar line items inflate bill | Describe surcharge categories and how they are calculated |
Term, renewals, early termination |
Term options and ETF schedule | ETF based on remaining MRC plus install clawback | Provide ETF calculation formula and examples |
Price increases |
Annual escalator rules and notice period | “Standard increase” language without a cap | Disclose escalator percent and applicable charges |
- Physical handoff: copper, single-mode fiber, or multi-mode fiber; connector type if known.
- Interface speed: 1G, 10G, 100G, and whether the service rate is shaped or true line rate.
- Ethernet attributes: define CIR/EIR, burst behavior, and UNI characteristics for ethernet services. :contentReference[oaicite:5]{index=5}
- Demarc location: suite, MPOE, or MMR; include a simple diagram in the response for each site.
Require bidders to describe physical route diversity in plain language. Avoid vague phrases like “diverse where available.” The response should name whether the secondary path is truly physically diverse or shares common conduit, common building entry, or common POP.
- 🟦BGP support, IPv4/IPv6 allocation, and any charges for additional IP space
- 🟦DDoS mitigation options and whether they are included or priced as add-ons
- 🟦Managed router expectations: who owns config, who patches, replacement SLA
- 🟦Customer portal access: ticketing, circuit stats, billing detail availability
- Survey complete with documented demarc plan and building access notes.
- Construction decision with a formal NTE special construction quote if applicable.
- Install ready with handoff confirmed and test plan scheduled.
- Acceptance test that defines pass criteria: throughput, packet loss, latency targets if provided, and failover behavior if applicable.
- Availability: percentage, measurement window, and exclusions.
- MTTR: definition, clock start, and clock stop conditions.
- Latency and packet loss: measurement points and reporting access.
- Credits: exact credit table and claim window.
- 🟩NOC phone and ticketing channels
- 🟩Severity definitions and response targets
- 🟩Named escalation contacts for chronic issues
A simple way to compare vendors is to normalize to first-year cost and include the typical “surprise” line items: NRC, special construction, and estimated surcharges.
- ✅Site-by-site MRC, itemized NRC, and construction NTE with triggers
- ✅Demarc plan and handoff details, including any meet-me room dependencies
- ✅Route diversity statement that names shared risk points
- ✅SLA table, credit table, and escalation path
- ✅Term options, ETF formula, and price increase rules
- ✅Taxes/fees/surcharges disclosure method
The strongest RFPs do not demand the lowest price. They demand the clearest scope, the most comparable performance commitments, and the fewest unknowns left for “after the survey.” That discipline is what prevents scope gaps, keeps installs on schedule, and makes vendor comparisons defensible.
