Request for Proposal

Any applicant may use a request for proposal (RFP). An RFP is a formal bidding document that describes a project and desired services in detail to ensure an effective competitive bidding process. If you use an RFP, you must submit it with your FCC Form 465 (Request for Services Form). Service providers will use the RFP and information on the FCC Form 465 to submit a bid to provide services to your site.

You must submit an RFP if you are required to issue an RFP under applicable state, Tribal, or local procurement rules or regulations.

The RFP must include, at a minimum:

• sufficient information to enable an effective competitive bidding process, including a description of the applicant’s service needs and the scope of the project and network costs (if applicable);
• the period during which bids will be accepted; and
• the bid evaluation criteria, including the weight assigned to each criterion. Note: The weight percentages listed in the RFP must match the weight percentages provide on the FCC Form 465.

Sample RFPs and Checklist

Using a sample RFP will not guarantee approval of the RFP by USAC. You are responsible for reviewing related FCC rules and ensuring that your RFP meets program requirements.

• Large Project Scope RFP
• Medium Project Scope RFP
• Small Project Scope RFP

Use this printable checklist to ensure you include all required elements in your RFP.

Additional Requirements

• Neutral Language – Applicants must use general or neutral terms when describing their service needs. Applicants that include a particular service provider’s name, brand, product or service on the FCC Form 465 or RFP must also use the words “or equivalent” in the description, to avoid the appearance that the applicant has pre-selected the named service provider or intends to give the service provider preference in the bidding process.
• Information Required – The bid evaluation criteria must solicit sufficient information so that the criteria can be applied effectively.
• Changes to the RFP – If the applicant subsequently makes any changes to its RFP, it is responsible for ensuring that USAC has a current version of the RFP for website posting. Certain changes to RFPs may require an applicant to restart its competitive bidding process, including the 28-day requirement.

Recommendations

• Invoicing Procedures– The RFP should explain the FCC Form 469 invoicing process, including the selected service provider’s responsibility to sign, certify, and submit proper invoices and documentation for reimbursement by the invoice filing deadline
• Service Provider 498 ID Requirement – The RFP should explain that all service providers must either have an existing 498 ID or apply to obtain a 498 ID by completing an FCC Form 498 (Service Provider and Billed Entity Identification Number and General Contact Information Form).
• Service Level Agreement– The RFP should include whether the applicant is seeking services that include a service level agreement (SLA). Usually, an SLA will state when the network should be available, bandwidth required to support this connection, network latency standards, and required response times. These technical requirements are critical for a service provider to prepare an accurate pricing proposal, and for you to conduct an objective bid evaluation.
• Disqualifying Bids– The RFP should define the applicant’s standards for disqualification of service provider bids, including any services or equipment that do not meet the minimum project requirements.