How to Respond to an RFP: A Step-by-Step Guide for Vendors

An RFP response has to arrive complete and on time, and the buyer will usually score it against criteria set before you saw the document. This guide walks through the RFP response process from the vendor side, in the order you’ll do the work. For the proposal document itself, start from RFPhub’s free RFP response template.

Read the RFP and log the deadlines

Read the whole package, including every attachment, addendum and contract term, before deciding anything. Terms you can’t accept are cheaper to find before anyone starts writing. Then log these where the whole team can see them:

• Every date, including the question deadline and the proposal due date, time and time zone.
• Every mandatory requirement, usually worded “must” or “shall”. Missing one can get a proposal set aside before it’s scored.
• The submission rules: format, file names, page limits, volumes, forms and signatures.
• The evaluation criteria and weights, and how long your proposal must stay valid.

Decide whether to bid

Responding to an RFP properly takes time from sales, pre-sales, delivery, finance and legal. Make the bid/no-bid call early, with the people who would do the work, and record why.

Answer any intent-to-bid request by its date either way, and if you won’t bid, tell the named contact early.

Ask questions through the named contact

Send questions in writing to the named contact before the question deadline, citing the section or requirement ID. Ask about anything that changes your price or plan, such as missing volumes or unclear scope. Assume every answer goes to every bidder, and word your questions so they don’t reveal your approach.

Route everything through that contact while the RFP is open, even if you know others on the buying team. Under some public-sector rules, contact with anyone else can get a bid rejected.

Acknowledge every addendum the way the RFP asks, and revisit the bid decision if the scope changes.

Build a compliance matrix

A compliance matrix lists every requirement and instruction in the RFP, one per row, with the buyer’s ID and exact wording, an owner, a response code, where it’s answered and its status. Build it before anyone writes prose. It exposes gaps while there’s time to close them, and becomes your final check.

Keep the buyer’s wording, since a paraphrase can drop a condition, and add the submission rules as rows. Use the buyer’s compliance form if it supplies one. If not, the RFP response template has a matrix to fill in.

Plan back from the deadline

Name one proposal lead to own the schedule, and give each answer one owner. Work back from the due date, aim to submit at least a working day early, and protect review time, the first thing lost when drafting runs late.

This is an example only. RFPhub’s RFP process guide uses three to four weeks as an example response window for a mid-sized software RFP.

Write answers the buyer can score

Buyers running a structured process score proposals against criteria and weights set in advance, as RFPhub’s guide to RFP evaluation criteria explains. If the RFP publishes its weights, spend your effort in proportion.

• Answer the question in the first sentence, then say how, who and by when.
• Follow the RFP’s order, numbering and terms, so evaluators find each answer where they expect it.
• Back claims with evidence an evaluator can check, such as a reference of similar size.
• Promise only what you’d sign, because commitments in a proposal can end up in the contract.

Use response codes honestly

If the RFP asks for response codes, use its set, such as the six in RFPhub’s guide on how to write an RFP: standard, configuration, custom, third party, roadmap and not available. Pick the code that’s true for the edition you’ve priced. Buyers can test claims in demos and reference calls, and a must-have that isn’t really met can get a proposal set aside. If you can’t meet a requirement, say so and offer an alternative.

Price on the buyer’s form

Complete the buyer’s pricing sheet exactly as issued, with the same line items, units and contract term. Buyers often score total cost over the term, and a price that doesn’t fit their table is hard to compare.

• Price every line, rather than leaving costs such as data migration in the assumptions.
• If your pricing model doesn’t fit the form, fill it in as closely as you can and explain.
• Price options separately, and state renewal terms and how long prices are valid.
• If the RFP asks for a separate price volume, keep prices out of the technical proposal.

Write the executive summary and cover letter last

Write both once the answers and price are final, so every figure matches. The executive summary opens the proposal, and evaluators read it as part of your answer. Restate the buyer’s goals in the RFP’s own words, summarize your proposal and total price, and tie each reason to choose you to a criterion and the section that proves it.

The cover letter is a signed, one-page letter to the named contact. It names the RFP, acknowledges each addendum, confirms how long the proposal stays valid and points to any exceptions, without adding prices, terms or promises. The free RFP cover letter template has the structure and examples.

Review before you submit

Have each section checked by someone who didn’t write it.

• Compliance: walk the matrix line by line against the RFP and every addendum.
• Scoring: read the proposal as an evaluator would, and rewrite answers that are vague or unsupported.
• Pricing and legal: check the arithmetic, confirm totals match throughout, and review every exception and assumption.

Then look for leftovers, such as another customer’s name. The pre-submission checklist in the RFP response template has the full list.

Submit early, in the exact format

Submit exactly as the RFP instructs, from the portal or address to the file names, page limits, copies and volumes. Register and test any portal login well before the due date. Public buyers may require supplier registration first, and RFPhub’s state procurement portals directory shows where each US state posts solicitations.

Leave time for a failed upload or a signer who’s out of the office, and keep the confirmation of receipt. Late proposals are usually rejected, particularly in the public sector.

What happens after you submit

After scoring, the buyer may invite the leading vendors to further stages:

• Clarification questions. Answer in writing, on time and only what’s asked, without changing your offer unless invited to.
• Presentations, scripted demos and reference calls. Follow the buyer’s script and sample data exactly, bring the people who would deliver the project, and brief your references before they’re called.
• A proof of concept, if a demo can’t prove a requirement that matters. Agree the scope, success criteria and who pays in writing first; RFPhub’s proof of concept template shows the kind of plan involved.
• Negotiation on price, terms and the statement of work, possibly while a runner-up is still in the process.
• A debrief if you lose. Ask promptly, in writing, how your proposal scored against each criterion and where it fell short.

Public-sector RFPs

Public bodies, and organizations spending public or grant money, follow procurement rules that vary by country, state and agency. Read the solicitation closely and check with its named contact or your counsel.

• Deadlines are strict. In US federal negotiated acquisitions, FAR 15.208(b) says a proposal received after the exact time specified for receipt is “late” and won’t be considered, apart from narrow exceptions. Follow the format exactly too, including any prescribed forms.
• One contact. Under FAR 15.201(f), the contracting officer must be the focal point of any exchange with potential offerors once the solicitation is released.
• Debriefs. Under FAR 15.506(a)(1), an offeror whose written request reaches the agency within 3 days after it’s notified of the award must be debriefed. FAR 15.505(a)(1) lets an offeror excluded before award request a debriefing in writing within 3 days after receiving notice of the exclusion. Protest deadlines can be short too.

FAR references are to the text on acquisition.gov as of October 2026. The FAR is being rewritten under the Revolutionary FAR Overhaul, and many agencies have adopted a deviation based on the overhauled Part 15, which renumbers these rules (debriefings are at 15.206-2 and 15.301-1). Check which version your solicitation applies. State and local rules differ. This isn’t legal advice.

Frequently asked questions

How do you respond to an RFP?

Read the RFP, log every deadline and mandatory requirement, and decide whether to bid. If you bid, ask questions on time, build a compliance matrix, answer against the buyer’s scoring criteria and price on its form. Review, then submit early in the exact format requested.

How long does it take to respond to an RFP?

The buyer sets the deadline, so the work has to fit its window. RFPhub’s example window for a mid-sized software RFP is three to four weeks. Make the bid decision and build the compliance matrix in the first few days.

Should you respond to every RFP?

No. Bid when you can meet every must-have, deliver on the buyer’s timeline, accept the terms and win at a price that’s worth it. Otherwise, tell the buyer early that you won’t bid.

Can you contact the buyer while an RFP is open?

Only through the contact the RFP names, in writing, and assume every bidder will see the questions and answers. Under some public-sector rules, contacting anyone else can get a bid rejected.

What should you do if you lose an RFP?

Ask the buyer for a debrief promptly and in writing, including how your proposal scored against each criterion. In US federal negotiated acquisitions, the FAR sets a short deadline for the request.