Mid-market SLED teams already know an RFP is a Request for Proposal. The decision-changing definition is this: an RFP is a formal, scored buying process. A public buyer uses it to compare qualified vendors against published criteria and defend the award. The RFP Success® Company treats the document as the evaluator’s scoring map, because that is where experienced bidders gain or lose ground.
If your team already bids on State, Local, and Education (SLED) opportunities, this guide will sharpen the shared definition behind your process. It covers how an RFP differs from an RFQ and an RFI, what is inside one, how the SLED process runs, and where established service-based teams turn a compliant response into a scoreable one.
76%+ Client Win Rate · 92% Down-Select Rate · $500M+ in Client Wins · Lisa Rehurek: 30+ Years Across Responding to, Developing, and Evaluating RFPs
What Is an RFP?
An RFP, or Request for Proposal, is a formal, scored procurement process. A SLED buyer defines the need, publishes requirements and evaluation criteria, and asks qualified vendors to propose a solution. For an experienced bidder, the document is both the opportunity and the scoring map: it shows what evaluators must compare and what the winning response must make easy to find.
Most definitions stop at “a document that invites proposals.” That is accurate and not very useful, because it describes the paper without describing the purpose. The purpose of an RFP is comparison. A state agency, a county, a school district, or a public university has a need it cannot meet in-house, a budget it has to spend in the open, and a duty to choose fairly and prove it chose fairly. The RFP is how it does all three at once.
That last part is the part vendors miss. Every section of an RFP exists to help someone score you. The scope of work tells the panel what to measure. The evaluation criteria tell the panel how to measure it. The submission rules tell the panel who to disqualify before scoring even starts. When you read an RFP as a list of things to write, you write a lot and win a little. When you read it as a scoring instrument, you write exactly what earns points.
After 30+ years across responding to, developing, and evaluating RFPs, RFP-expert Lisa Rehurek will tell you the document is the easy half. Even experienced teams can slip into reading the RFP cover to cover and answering it in order. The strongest teams start with the evaluation criteria, align the pursuit strategy to the scoring model, and work backward from how the response will be judged.
What Does RFP Stand For?
RFP stands for Request for Proposal. It is a buyer’s formal, written request asking vendors to propose how they would solve a defined need, on terms and a timeline the buyer sets, so the buyer can compare complete solutions rather than just prices.
The word that matters in Request for Proposal is “proposal.” A proposal is not a price and it is not a brochure. It is your argument for why your approach is the one the agency should pick, written to the buyer’s requirements and scored against them. That is what separates an RFP from its two cousins, which get mixed up constantly.
You will also hear “RFP” used loosely to mean the whole pursuit, the document, the questions, the deadline, the submission, and the wait. In SLED, it pays to be precise, because the document is governed by rules and the rules are scoreable. Treating the RFP as a casual ask is how a qualified team gets ruled non-responsive over a formatting miss it never saw coming.
RFP vs RFQ vs RFI: What Is the Difference?
An RFI (Request for Information) gathers market and capability information early, before the buyer knows exactly what it wants. An RFQ (Request for Quote) asks for pricing on a need that is already clearly defined. An RFP (Request for Proposal) asks vendors to propose a complete solution and scores them on more than price, including approach, experience, and risk.
The three documents map to three different moments in a buyer’s decision, and knowing which one you are looking at tells you how to respond.
| Document | What the buyer is doing | What they want from you | How you are judged |
| RFI (Request for Information) | Exploring the market, not ready to buy | Capabilities, options, and education | Usually not scored; shapes the future RFP |
| RFQ (Request for Quote) | Knows exactly what it needs | A price on a defined spec | Mostly on price |
| RFP (Request for Proposal) | Needs a solution to a complex problem | A complete, persuasive proposed approach | On weighted criteria, price plus much more |
The practical takeaway: if you respond to an RFP as if it were an RFQ, all price and specs and no proposed approach, you lose to a team that understood it was being scored on its thinking. And if an RFI lands in your inbox, treat it as a head start. The buyer is telling you what it is about to buy, often months before the RFP drops, which is the single best moment to influence the requirements in your favor.
What Is Inside an RFP?
A typical RFP contains a scope of work, evaluation criteria and their weights, submission instructions and format rules, key deadlines, and a list of required documents. The evaluation criteria are the most important part to read first, because they tell you exactly how every page you write will be scored.
RFPs vary by agency, but the bones are consistent. Here is what you will find, in the order most teams read it, and the order you should read it instead.
Most teams read the scope of work first, because it is the longest and feels like the heart of the project. Read the evaluation criteria first instead. They are usually a short section, sometimes a single table, and they are the only part that tells you how points are awarded. If technical approach is worth 40 percent and past performance is worth 10, you now know where to spend your best writing. Skip that step and you will pour effort into a section worth almost nothing.
After the criteria, read the submission instructions and the compliance requirements, the page limits, the format, the required forms, the deadline, and the delivery method. In SLED procurement these are often a pass-or-fail gate. A missed attachment or a proposal that runs three pages over the limit can remove you before a single point is scored, no matter how strong the work is. The Scrambler, the team responding in a last-minute fire drill, loses more contracts to compliance misses than to weak content, and never finds out, because a disqualified proposal does not get a debrief.
Only then read the scope of work in detail, and read it asking one question on every line: how would I prove this, and how would a panel score my proof? That question is also the heart of the go/no-go decision, the discipline of deciding which RFPs are actually worth pursuing before you spend a single hour responding. Not every RFP you can answer is one you should.
“Read the evaluation criteria first. They are the only part that tells you how you will be scored.”
What Does the SLED RFP Process Look Like?
In SLED procurement, the agency defines a need and publishes the RFP with its criteria and weights, vendors submit a complete proposal by a hard deadline, an evaluation panel scores each proposal factor by factor, and the highest-scoring responsive proposal, with price factored in, wins. The weights are usually published in advance and cannot be changed after proposals arrive.
State, Local, and Education buyers run on their own rules and their own calendars, which is exactly why this market rewards specialists. There is no single federal-style rulebook across SLED. A school district, a state department, and a city all procure differently, often aligned to their own fiscal years. But the spine of the process is recognizable everywhere. Use the state government RFP guide for the launch-state breakdown and the pursuit patterns that repeat across SLED.
The agency identifies a need and writes the RFP, including the criteria and weights. It publishes the solicitation, usually openly, and sets a window for written questions. This question window is a quiet advantage most vendors waste. A well-placed question can clarify a requirement or surface an assumption that helps you score, and the answers are shared with every bidder, so they become part of the official record.
Vendors then submit by a hard deadline. Late is not a category in public procurement. After the deadline, the evaluation panel scores. Each evaluator reads against the published criteria, assigns points per factor, and writes a short rationale, because in SLED, scores are auditable and debriefable. The panel combines the scores, applies the weights, factors in price, and ranks the proposals. The top responsive proposal wins the award, and losing bidders can usually request a debrief.
That is the machine. The reason qualified teams keep losing inside it is not that the machine is unfair. It is that they wrote for themselves instead of for the people running it. For the full walkthrough of the SLED process from go/no-go to submission, see our guide on how to respond to an RFP, and for state-by-state specifics, the state government RFP guide.
How Do Service-Based Businesses Win an RFP?
Service-based businesses win RFPs by reading the evaluation criteria first, answering every requirement in the buyer’s language, and writing for the person scoring the page instead of about themselves. Meeting the requirements is the starting line, not the finish line. Evaluators award points for showing them what they get, not for everything you can do.
We review proposals every week from service-based businesses that are fully qualified to win and do not. The work is real. The experience is real. And the proposal reads like a company talking about itself.
The single most important thing we teach fits on a bumper sticker: IT IS NOT ABOUT YOU. The evaluator does not have a scoring box for how proud you are of your company. They have a scoring box for whether you solved their problem in a way they can defend. The fix is to take every claim about yourself and finish the thought from the buyer’s side of the table. “We have done this 500 times” is about you. “Your team spends less time managing us because we have run this exact transition 500 times” is scoreable, because it tells the evaluator what they get.
That discipline is the whole point of the 4×4 Framework™, the methodology behind our 76%+ client win rate across $500M+ in client wins, and the D.A.R.E. Method, the writing system inside it that earns points on both the explicit scorecard items and the silent ones the RFP never spells out. None of it is a talent some teams are born with. It is a process, applied consistently.
When you are ready to apply the process, use the Complete Guide to RFP Response and the RFP evaluation criteria guide. Both sit inside the wider library on how to win more RFPs.
If your team needs a stronger pursuit system, a Play to Win Consult builds the strategy, roles, and process behind repeatable RFP work. If you have two or three past proposals that kept coming up short, an RFP Success® Mastery Audit has the Win Strategist team review them the way an evaluation panel would, so you can see where the points went before you bid again.
Case in Point: RTA Fleet
When RTA Fleet brought us three past proposals, the company was reaching the finalist round on 50% of its pursuits. We read the submissions through the evaluator’s lens and found strong capability but weak scoreability. After working the evidence and perspective back through the evaluator’s lens, its finalist rate moved to 80% and its scored responses gained more than 30 points inside one engagement cycle. The revised response made its capability easier for evaluators to find and score.
“Anyone can help you submit a proposal. Very few can help you win one. We don’t measure success by submission. We measure it by win rate.” : Lisa Rehurek, Founder, The RFP Success® Company
Keep Reading
- The Complete Guide to RFP Response : the full SLED process from go/no-go to submission
- The Go/No-Go Decision Framework : how to decide which RFPs are worth pursuing
- The State Government RFP Guide : how state-level procurement actually works
- The 4×4 Framework™ : the methodology behind a 76%+ win rate
- The D.A.R.E. Method : the writing system that earns points on the explicit and the silent criteria
