RFPs and bid requests arrive by email, portal, and phone call. Miss a due date and the work goes to somebody else. Win the work and lose track of what was authorized, and the invoice gets questioned. A simple tracking habit covers both.
Short answer: A telecom RFP is a request from an ISP, prime or public agency asking contractors to price a defined scope of work. It lists the work, the units and the date the bid is due. You read it, price it in their terms, and send it in on time.
A telecom RFP is a request for proposal. An ISP, prime contractor, utility, municipality, or BEAD subgrantee sends it to ask contractors to price a defined scope of work, such as fiber placement, splicing, or drops, by a set due date.
You will also see RFQs and bid packages. An RFQ usually asks for prices on a scope that is already fixed. A bid package is the set of documents a customer sends with the request. The names vary by customer, but the job is the same: read what they want, price it in their terms, and get it in on time.
Expect the scope and maps, the rate codes and units (feet for cable and conduit, each for drops, splices, and locates), the schedule and due dates, and the insurance and documents the customer requires.
Read the documentation standards closely: photos, test results, and as-builts. The closeout package checklist shows what that paperwork looks like at the end of a job. Read the payment terms carefully too, since they decide how long you carry the cost of the work.
Fiber bids are often priced by the unit. The price sheet (also called a bid form or bid tab) lists each kind of work on its own line. Here is how to read one, line by line.
Example only. The lines below are made up for this guide. They do not come from a real bid. Prices are left blank on purpose: your prices come from your own costs.
| Line | Work | Unit | Est. qty | Your unit price | Line total |
|---|---|---|---|---|---|
| 1 | Directional bore, 2 inch conduit | LF (feet) | 4,200 | ___ | qty x price |
| 2 | Place 144-count fiber in conduit | LF | 4,500 | ___ | qty x price |
| 3 | Handhole, 17 x 30 inch, set and grade | EA (each) | 9 | ___ | qty x price |
| 4 | Splice closure, place and splice | EA | 3 | ___ | qty x price |
| 5 | Rock adder, bore in rock | LF | 300 | ___ | qty x price |
| 6 | Restore paved surface | SF (square feet) | 250 | ___ | qty x price |
| 7 | OTDR test, both directions | EA (per fiber) | 144 | ___ | qty x price |
Read it this way:
The test: could someone in your office read your priced sheet and know what each line covers, without calling the estimator? If not, write your assumptions on the bid.
Bids do not come from one place. Several of these places are public and free to search. Here is where to look, and what each place is good for.
State broadband offices. Each state and territory has a broadband office that runs its BEAD program. NTIA has approved all 56 BEAD final proposals (NTIA, Aug 25, 2026). Start with your state's BEAD page. Some states also run a contractor directory, like Minnesota. Get listed where you can.
BEAD subgrantee lists. The state does not hire your crew. The ISPs that won subgrants do. Some state broadband offices post the winners as a file you can download, called "Exhibit A, Subgrantees" (for example, Mississippi and Arkansas). That file is your call list. Get on each ISP's vendor list before it starts to build. The BEAD subcontractor guide covers what they ask for.
SAM.gov. This is where federal agencies post their bids. Anyone can search it for free at sam.gov/opportunities, with no account. Search by NAICS code 237130 (Power and Communication Line and Related Structures Construction) and by the states you can reach. With a free Login.gov account, you can save searches and follow changes to the bids you care about (SAM.gov).
School and library fiber bids (E-Rate). Schools and libraries that want E-Rate money must post a bid request, FCC Form 470, for at least 28 days. Some post an RFP with it, such as when state or local bid rules call for one. You can search and download these for free with USAC's Form 470 Download Tool (USAC).
Utility and co-op bid pages. Electric co-ops, power utilities and public utilities often post fiber and make-ready bids on their own procurement pages. Check the ones in your area every week, and register as a vendor where they let you.
State, city and county bid portals. State offices, DOTs, counties and cities post fiber and conduit work on their own bid pages. For example, New York's Empire State Development posts its open bids, broadband builds too, on its Requests for Proposals page. Sign up as a vendor so the notices come to you.
ISP and prime vendor portals. Once you are on an ISP's or a prime's vendor list, its bids come to you by email or in its portal. This is where repeat work lives.
No one list has every bid. So build your own, and keep it current:
That last step is the one that keeps a bid from slipping past you. Many contractors watch more than one of these places at once. That is why a single log matters more than any one source.
Before you price it, check that you have crews free in the window, that the codes fit your price book, and that you can meet the insurance limits and documents the customer asks for. Paperwork standards count too: photos, test results, and as-builts all take crew time, so price them into the unit rates. Customer documents are covered in contractor compliance tracking.
Send your questions by the questions due date. Price the work in the RFP's own codes and units, not your internal names. List your assumptions and exclusions so the customer knows what the price covers. Submit before the bid due date, then log it.
The customer, the project, the location, and where the request came from: the portal, the contact, or the email thread.
Questions due, bid due, expected award, and expected start. The bid due date is the one that loses work when it is missed.
The rate codes and quantities in the RFP's own units: feet for cable and conduit, each for drops, splices, and locates.
Reviewing, bidding, submitted, won, lost, or no bid, with the reason for the decision.
You can do all of this in a plain spreadsheet. Use one row for each RFP.
The awarded RFP or PO sets what you are authorized to bill. Keep the authorized codes and quantities where the office can see them for the life of the job.
Compare the tally to the authorized quantities before you send the invoice. If the crew did more than was authorized, get the change order approved before you bill it, not after.
Each customer has its own way to approve work. The path often looks like this.
First, the customer sets the scope. Next, a team reviews the bids that come in. Then the customer picks a bid and makes the award. Last, it can send a notice to proceed. That is the go to start work.
Steps can change by customer and by job. Read the RFP to see how this one works. If you are not sure, ask the customer before the questions deadline.
If your price book uses different names, map them once when you log the award, not on every invoice.
Feet for cable and conduit, each for drops, splices, and locates.
An approved change order adds to the authorized quantities. Keep it with the job, not in an email thread.
The log is only as current as the person who updates it. Update it the day an RFP arrives.
A request for proposal from an ISP, prime contractor, utility, or public agency asking contractors to price a defined scope of telecom work, such as fiber placement, splicing, or drops, by a set due date. It usually lists the rate codes, quantities, schedule, insurance, and documentation the customer expects.
One shared log with a row per RFP: customer, project, due date, scope, status, and the decision. A spreadsheet works if one person owns it and it is updated the day an RFP arrives.
Compare the tally to the authorized quantities before you send the invoice. If the work went over, get a change order approved first, or bill to the authorized quantity and note the difference.
Yes. Log the result and the reason if the customer gives one. Over time the log shows which customers, regions, and job types you win, and where your bids miss.
An RFP asks you to plan and price the work. An RFQ usually asks for a price on work that is already defined. An RFI asks for facts about your crew and what you can do; it is usually not a bid.
Look at state broadband office sites and BEAD subgrantee lists. Check ISP vendor portals and public bid boards too. Where alerts are offered, sign up so new ones come to you.
It depends on the scope and the dates the RFP sets. Check the due date and the questions deadline in the RFP itself.
It depends on the RFP and your state's BEAD rules. Some RFPs are open to subs and some go only through the subgrantee. Read who may respond in the RFP. If it's unclear, ask the issuer before the questions deadline.
An RFP tracker is one shared log with a row for each RFP. It shows who sent it, the project, the due date, the scope, the status and the decision. One person owns it and updates it the day an RFP lands. After the award, it also holds the codes and quantities the customer authorized.
Read each line left to right: the work, the unit (feet or each), the quantity, and your unit price. Unit price times quantity is the line total. Then check what each line covers. Is material in or out? Are rock, pavement or extra conduit on their own lines? Price every line the RFP asks for.
Check that you have crews free in the window. Check that the codes fit your price book. Check the insurance limits, the as-built format, the closeout list and the payment terms. Note the bid due date and the questions deadline. If something is unclear, ask the customer before the questions deadline.
Each customer has its own path. Often the customer sets the scope, a team reviews the bids, and the customer picks one and makes the award. Then it may send a notice to proceed. That is the go to start work. Read the RFP to see how this one works, and ask if it is not clear.
Once the work is won, the tally side is map to invoice. BEAD solicitations are covered in the BEAD subcontractor guide. For subs, see sub invoicing.
Get this coverage first in Google