Recurring and one-time cost
Separate MRC and NRC, currencies, terms, install charges, and any conditional components.
Practical RFP guide
Prepare a multi-site connectivity RFP that can become an executable workflow
A useful multi-site request does more than list addresses. It gives sourcing, suppliers, commercial teams, and delivery operations enough consistent context to compare options and carry the selected outcome into a governed quote and order.
Published by Trunkstar · Reviewed August 27, 2026
Requirement structure
Give every location a consistent commercial and technical record
Start with a stable site identifier and normalized address, then capture the requested product, capacity, access requirements, term, target dates, resilience needs, and any site-specific constraints.
Separate required fields from preferences. This makes incomplete records visible and prevents an optional request from being treated as a supplier disqualification rule.
- Customer and project identifier
- Stable site identifier and normalized address
- Product, capacity, term, and target date
- Access, resilience, and diversity requirements
- Site contacts, constraints, and notes
- Required versus preferred response fields
Supplier response model
Preserve the difference between automated, budgetary, and firm responses
Not every response has the same commercial certainty. Automated availability and budgetary pricing can support early comparison, while a firm-pricing request or negotiation may be required before the customer quote can be committed.
Record the source, status, validity, assumptions, supplier reference, and follow-up owner for every response so the comparison does not hide uncertainty.
Commercial comparison
Compare like with like before choosing a supplier mix
Coverage and exceptions
Show no-coverage, partial, manual-review, and alternative-product responses instead of dropping them silently.
Commercial confidence
Distinguish budgetary, firm, and negotiated prices and record validity or supplier assumptions.
Operational fit
Consider target delivery, product consistency, order process, and service ownership alongside price.
Quote governance
Turn the sourcing result into a controlled customer proposition
Apply customer price books, margin rules, commercial approvals, terms, and presentation only after supplier inputs have clear status. Keep selected and rejected alternatives connected to the project so later revisions do not restart the research.
When the customer accepts, carry the structured locations, products, suppliers, prices, terms, and references into ordering rather than re-keying the project.
Operational checklist
Plan ownership for gaps and changes before sending the RFP
Assign owners for invalid addresses, missing requirements, supplier follow-up, price negotiation, commercial review, and customer clarification. Set a common status model that distinguishes waiting, blocked, complete, rejected, and superseded work.
This makes the RFP a managed workflow rather than a spreadsheet that becomes outdated as soon as the first response arrives.
Frequently asked questions
Clear answers for connectivity teams
What information should a multi-site connectivity RFP include?
Include stable site identifiers, normalized addresses, product and capacity requirements, terms, target dates, access or resilience constraints, response fields, and the commercial context needed for comparison.
How should budgetary and firm supplier prices be handled?
Keep their status explicit. Budgetary prices can support early evaluation, while firm or negotiated prices should record their supplier reference, validity, assumptions, and approval context.
Can one RFP use multiple suppliers?
Yes. A multi-site RFP can compare and select different relevant suppliers or products by location while maintaining one customer and project context.
How does an RFP become an order?
The selected locations, products, suppliers, costs, customer prices, terms, and references should move from the governed quote into ordering without re-keying the accepted scope.
Keep exploring