How to Write an RFP: Structure, Questions and Scoring
How to write a request for proposal vendors want to answer: a section by section RFP outline, sharper questions, and a fair way to score the responses.

Most disappointing RFP responses are caused by the RFP. Ask "describe your reporting capabilities" and every vendor sends pages of marketing copy that cannot be compared. Ask "can a manager build a report of overdue invoices by customer without an administrator, and on which plan?" and the answers become short, specific and easy to score.
This guide covers the request for proposal (RFP) as a document: what goes in each section, how to write questions that get specific answers, how long it should be, why good vendors sometimes decline to bid, and how to score the responses fairly. If you need the wider process around it, such as building the team, running demos and checking references, see our vendor selection process guide.
What a good RFP does
A good RFP tells vendors enough to price accurately, forces comparable answers through one format and one pricing template, and tells vendors how they will be judged. Hawaii's State Procurement Office, for example, says an RFP should include an overview with background, schedule and how to submit questions; the specifications or statement of work; the evaluation and award criteria "and point value for each"; and exhibits, attachments and terms. A private business is not bound by those rules, but the structure works for the same reasons.
The RFP outline at a glance
Use this table as your template. Copy it into a document and fill in each section in order.
| Section | What it contains | Typical length for a small business RFP |
|---|---|---|
| 1. Cover letter and instructions | Purpose, single point of contact, deadline, how to submit, intent to respond date | Half a page |
| 2. Background | Who you are, what is broken today, what success looks like | Half a page to one page |
| 3. Scope of work | What is in and out of scope, volumes, systems, locations | One page |
| 4. Requirements as questions | Numbered questions grouped by topic, each marked gate, must have or nice to have | Two to five pages |
| 5. Response format and pricing template | Answer sheet, page limits, required attachments, pricing table | One page plus a spreadsheet |
| 6. Timeline | Issue date, question deadline, answers published, due date, demos, decision | A short table |
| 7. Evaluation method | Criteria, weights, gates, price scoring formula, next stages | Half a page |
| 8. Key terms | Contract terms you need, and how to flag exceptions | Half a page to one page |
| 9. Q&A process | How questions are asked and how answers are shared with all vendors | A short paragraph |
Step 1: Write the cover letter and instructions
Open with a short letter that says what you are buying, why, and what you want vendors to do next. Then give the practical instructions:
- One named contact for all questions; vendors should not contact other staff about the RFP.
- The submission deadline, with date, time, time zone and submission method.
- An intent to respond date, so you know early whether you will get enough bids.
- Confidentiality: what you will keep private, and a request that vendors mark confidential sections.
Step 2: Describe the background and the problem
Vendors propose better solutions when they understand the problem, not just the shopping list. In half a page, cover:
- What your organization does, its size and where it operates.
- How the work is done today, and which tools or providers are involved.
- What is going wrong and what it costs you, in time, errors or money.
- What success looks like 12 months after go live.
Keep it factual: "approvals are tracked in email and month end close takes eight working days" gives vendors something to work with; "we want a best in class solution" does not.
Step 3: Define the scope of work
The scope tells vendors exactly what they are pricing. List what is in scope (modules, services, data migration, training, integrations), what is out of scope, and the numbers that drive cost: users by type, transaction volumes, locations, entities and data history to migrate. If a number is uncertain, give a range and ask vendors to price both ends.
State constraints plainly: a fixed go live date, a budget range if you are willing to share one, systems that must remain in place, or regions where data must be stored. Late constraints force everyone to start again.
Step 4: Turn requirements into testable questions
This is the section that decides whether answers are useful. Every requirement becomes a numbered question that a vendor can answer specifically and you can verify later. Mark each one as a gate (pass or fail), a must have (scored) or a nice to have (tiebreaker). Our guide to choosing business software covers how to collect requirements in the first place.
Good vs bad RFP questions
| Weak question | Why it fails | Stronger question |
|---|---|---|
| Describe your reporting capabilities. | Invites marketing copy that cannot be compared | Can a non admin user build and save a report of overdue invoices by customer? Answer yes, yes with configuration, or no, and name the plan. |
| Do you integrate with our accounting system? | "Yes" covers anything from a native sync to a custom project | Is there a native, vendor maintained integration with [system]? Which records sync, in which direction, and how often? Is there an extra fee? |
| Is your platform secure? | Every vendor says yes | Which independent audit reports or certifications do you hold, with dates? Can you share the latest report under NDA? |
| Describe your implementation approach. | Produces a generic methodology | For a customer of our size, give the typical weeks to go live, the tasks your team does, the tasks we do, and the estimated internal hours we should plan for. |
| What support do you offer? | Answers list channels, not commitments | State support hours, response time targets by severity, and whether these are contractual on the quoted plan. |
| Is the product scalable? | Unmeasurable | What are the plan limits on users, records, storage and API calls, and what does it cost to exceed them? |
Rules for writing questions
- Ask one thing per question. Compound questions get partial answers.
- Give an answer scale where you can: standard, configurable, add on, roadmap (with date), not available. This makes scoring fast.
- Ask for evidence, such as a document, a screenshot or a reference customer, for anything that matters.
- Ask what it costs in the same question when a feature might be a paid extra.
- Avoid copying one product's feature names, which signals you have already chosen.
- Cut every question you will not score.
Step 5: Set the response format and pricing template
Comparable answers come from a fixed format, not from good intentions. Provide:
- An answer sheet, ideally a spreadsheet with one row per question, a column for the answer scale, a column for explanation (with a word limit) and a column for evidence references.
- Page limits for any narrative sections, such as an implementation plan.
- A list of required attachments, such as sample contract, service level agreement, security report and data processing agreement.
- A pricing template that every vendor must complete, broken down by year for at least three years: subscription or service fees by line, one time setup and migration, training, integrations, support tiers, and any usage based charges at your stated volumes. Ask for renewal increase caps and payment terms in the same template.
Without a template, every vendor prices on a different basis and you spend days rebuilding their numbers. Pricing on a common basis also feeds straight into a total cost of ownership comparison.
Step 6: Publish the timeline and the Q&A process
A simple table removes most back and forth:
| Milestone | Example timing |
|---|---|
| RFP issued | Day 0 |
| Intent to respond | Day 3 to 5 |
| Deadline for vendor questions | Day 7 to 10 |
| Answers published to all vendors | Day 10 to 12 |
| Proposals due | Day 15 to 21 |
| Shortlist and demos | Following one to two weeks |
| Decision | Date you can actually meet |
These timings are general practice for a modest purchase, not a rule. Complex services or large migrations need more response time.
For questions, use one rule: all questions go in writing to the named contact by the deadline, and every answer is shared with every vendor, without saying who asked. Public bodies handle this through written addenda; Hawaii's procurement guidance notes that vendor inquiries may require the RFP to be amended, corrected or clarified by addendum. If an answer changes the scope materially, extend the due date for everyone.
Step 7: Disclose how you will evaluate
State the criteria, the weights, the gates and how price will be scored. Hawaii's guidance calls for "the relative importance, expressed in terms of numerical scoring, of price and other evaluation criteria", and that transparency helps private buyers too: vendors stop padding sections you do not weight, and losing vendors find it easier to accept the outcome.
Say which requirements are gates, the category weights, the price scoring method, and what happens next (shortlist, demos, references, best and final offer). Also say that you may accept a proposal without further discussion, so vendors send their best terms first.
Step 8: State key terms and ask for exceptions
List the contract terms that matter to you, such as data ownership and export, security incident notification, service levels and credits, renewal caps, termination rights and liability. Then ask each vendor to list any exceptions to those terms in a separate section. Finding out in the proposal that a vendor will not accept your data return terms is much cheaper than finding out during contract review. Our SaaS contract checklist and vendor risk management guide list the terms worth including.
How long should an RFP be?
There is no official length. The right length is the shortest document that lets vendors price accurately and lets you score fairly. For most small and mid sized business purchases, a light RFP of a few pages plus a question spreadsheet of roughly 20 to 40 questions is a sensible starting point; that range is our practical guidance, not a published standard. Larger, riskier purchases justify more detail on scope and terms, not more generic questions.
Signs it is too long: copied questions nobody will score, repeated questions, and requirements every vendor already meets.
Why good vendors decline to bid
A low response rate usually tells you something about the RFP. Common reasons vendors walk away:
- The deal looks pre wired. Requirements that describe one product's features word for word signal that the winner is already chosen.
- Unclear scope or budget. If vendors cannot estimate the work, the cost of bidding outweighs the chance of winning.
- Effort out of proportion to the deal. A long questionnaire for a small contract is a poor investment for the vendor.
- Too little time, especially when the deadline falls over a holiday.
- Unacceptable terms stated as non negotiable, such as unlimited liability.
- No access to answers. Vendors who cannot ask questions guess, or skip the bid.
Ask vendors who decline why. Their answer often tells you how to fix the next RFP.
How to score RFP responses
Scoring is where a well written RFP pays off. Decide the scoring rules before the responses arrive, and write them down.
Define the scoring scale
Scores mean little unless every evaluator reads the scale the same way. Define each point:
| Score | Definition |
|---|---|
| 5 | Fully meets the requirement as standard on the quoted plan, with evidence; exceeds it in a way that matters to us |
| 4 | Fully meets the requirement, with evidence or configuration only |
| 3 | Mostly meets the requirement; minor gaps or a workaround we can accept |
| 2 | Partially meets the requirement; significant gaps, or depends on an add on or roadmap item |
| 1 | Barely addresses the requirement or the answer is unclear |
| 0 | Does not meet the requirement or no answer given |
Gates are scored pass or fail, separately from this scale.
Score independently first, then reach consensus
Each evaluator scores every proposal alone, against the written criteria, and writes a short note justifying each score. Then the group meets to agree a consensus score. The University of Oregon's procurement scoring guidance says evaluators must support ratings with narrative statements, and that "averaging individual scores to arrive at a decision is not a best practice"; instead, evaluators should meet after individual scoring to agree the strengths, weaknesses, risks and score for each factor. In the meeting, start with the items where scores differ most, and record the reason for each final score.
The same guidance warns against comparing proposals with one another rather than against the stated criteria, because that can bypass the criteria you published.
Keep price separate until quality is scored
Score the quality sections before evaluators see prices, so a cheap quote does not color the technical judgment. The Georgia Procurement Manual describes this approach: the issuing officer analyzes cost responses separately, and cost scores are not shared with the evaluation committee until the initial technical scoring is complete and clarifications are obtained.
Normalize prices with a stated formula
First, convert every quote to the same basis using your pricing template: same volumes, same term, all one time and recurring costs included. Then apply the price formula you published. The Georgia Procurement Manual describes a common ratio method: lowest price divided by the price of the proposal being scored, multiplied by the points available for cost. In its own example, with 300 cost points, a $50,000 proposal gets 300 points and a $55,000 proposal gets 272.7 points.
The ratio method rewards the lowest quote, so make sure you compare realistic multi year totals, not first year teasers. The Oregon guidance also warns about unrealistically low cost estimates, known as "buying in".
Handle non compliant answers consistently
Decide the rule before you read the responses:
- Missed gate or late submission: reject, as stated in the RFP.
- Missing pricing template or answers in the wrong format: ask for a corrected submission within a short deadline, or reject, but apply the same rule to every vendor.
- Vague answers such as "yes" or "available on request": score them low as written, or send a clarification question.
- Roadmap items: score only what exists today on the quoted plan.
Run a clarification round
Use written clarification questions to resolve ambiguity, not to let a vendor rewrite its proposal. Send each vendor its own list, set one deadline, and file the answers with the proposal. If you want improved prices or terms from a shortlist, issue a formal best and final offer request to every shortlisted vendor at the same time. Hawaii's guidance describes this step: shortlisted offerors get equal treatment, substantial oral clarifications must be confirmed in writing, and a vendor that does not submit a best and final offer is held to its previous offer.
Common RFP mistakes
| Mistake | Fix |
|---|---|
| Writing the RFP around one vendor's product | Describe outcomes and constraints, not features |
| Open ended "describe" questions | Ask specific questions with an answer scale and evidence |
| No pricing template | Require one template, broken down by year |
| Setting weights after reading responses | Publish weights in the RFP |
| Averaging scores without discussion | Score independently, then agree a consensus with written reasons |
| Answering one vendor's question privately | Share every answer with all vendors |
| Ignoring contract terms until the end | Ask for exceptions in the proposal |
After the RFP
Once you have a consensus ranking, move the top two or three vendors to scripted demos, references and negotiation, as described in our vendor selection process guide. Use the written commitments from the proposals in your SaaS pricing and renewal negotiation, then raise the order through your normal purchasing process. Keep the RFP, scoring notes and consensus record together for renewal time.
Frequently asked questions
What are the main sections of an RFP?
A cover letter and instructions, background on your organization and the problem, scope of work, requirements written as questions, response format and pricing template, timeline, evaluation method, key contract terms, and the Q&A process. Hawaii's State Procurement Office lists a similar set: an overview with background and schedule, specifications or statement of work, evaluation and award criteria with point values, and exhibits and terms.
How long should an RFP be?
As short as it can be while still letting vendors price accurately. For a typical small business software or service purchase, a light RFP of a few pages with 20 to 40 focused questions is usually enough. Length should come from requirements that change the decision, not from copied question banks.
Should I tell vendors how their proposals will be scored?
Yes. Publishing the evaluation criteria and weights tells vendors where to put their effort and makes the result easier to defend. Public bodies such as Hawaii's State Procurement Office require the RFP to state the evaluation criteria and their relative importance, and that is good practice for private buyers too.
How do you score price in an RFP?
A common method gives the lowest price the full price points and every other proposal a share based on the ratio of the lowest price to its price. The Georgia Procurement Manual writes this as lowest price divided by the proposal's price, multiplied by the points available for cost. Normalize every quote to the same volumes and term first.
Should evaluators average their scores?
Not as the final step. The University of Oregon's procurement guidance says averaging individual scores is not a best practice and recommends that evaluators score individually, then meet to agree a consensus score based on strengths, weaknesses and risks.
What should I do with a non compliant RFP response?
Decide the rule in advance and state it in the RFP. Missing a gate requirement or the deadline usually means the response is rejected; a minor omission, such as a missing form, can be fixed through a written clarification request offered on equal terms to every vendor in the same situation.
Sources
- Hawaii State Procurement Office: Procurement Wizard, Solicitation and Award, 4.4 Competitive Sealed Proposals (checked November 10, 2026)
- Georgia Procurement Manual: 5.6.3.2.2 RFP Cost Scoring (checked November 10, 2026)
- University of Oregon Purchasing and Contracting Services: Procurement Scoring (checked November 10, 2026)