How to Read Public-Sector RFP Evaluation Criteria

Read public-sector RFP evaluation criteria as the buyer's disclosed decision model, not as background material. First separate requirements that determine whether your offer can be evaluated at all from factors that distinguish one acceptable proposal from another. Then record every factor, subfactor, weight, and statement of relative importance; connect each one to the response section the buyer requested; and identify the proof an evaluator can actually credit. If the solicitation gives relative importance but not a point formula, do not invent one. FAR 15.305 permits several federal rating methods, while the City of Austin's standard RFP instructions illustrate a municipal model combining minimum responsiveness, pass/fail submittals, and weighted factors. The solicitation in front of you remains the controlling source.

Start with three different kinds of criteria

Teams often call everything in an RFP a “scoring criterion.” That blurs three different decisions.

Criterion type	Question it answers	Typical treatment	Bid-team response
Responsiveness	Did the offer follow the material submission rules?	Pass/fail or initial screen	Complete every required submittal and follow delivery instructions
Responsibility or minimum qualification	Can this offeror perform?	Pass/fail, eligibility review, or separate determination	Provide the requested licenses, experience, capacity, and attestations
Evaluated factor	How does this acceptable proposal compare with others?	Weight, points, rank, adjective, color, or tradeoff	Put specific, relevant proof where the evaluator is told to look

The City of Austin's standard RFP instructions illustrate this separation. A proposal must first be minimally responsive. Submittals not identified as evaluation factors may be reviewed on a pass/fail basis, while the listed factors and their weights are used to differentiate proposals and identify best value. The same document warns that the City may evaluate without clarification, so the proposal should stand on its submitted contents. See the City's standard RFP instructions.

This is why a beautifully written technical response does not by itself satisfy a missing required form, and why a complete administrative package does not by itself earn a high technical rating. Whether a defect can be clarified, corrected, or waived depends on the governing rules and the facts.

Build an evaluation map before outlining the response

Create one row for every factor and significant subfactor. Do not begin with your usual proposal template. Begin with the buyer's vocabulary and requested organization.

Recommended columns are:

• factor or subfactor exactly as stated;
• source document, section, and page;
• responsiveness gate, minimum qualification, or scored factor;
• weight, points, rank, or stated relative importance;
• required response volume, form, or section;
• proof the buyer requests or can reasonably evaluate;
• response owner and reviewer;
• open question or assumption; and
• current status.

For federal negotiated acquisitions, FAR 15.204-5 separates Section L, which guides proposal preparation, from Section M, which identifies significant evaluation factors and their relative importance. That is a useful reading pattern even when a state or local RFP uses different section names, but FAR is not state or local law. Read FAR 15.204-5.

The practical move is to reconcile instructions and evaluation. If the evaluation factor is “project approach,” find the exact submittal that must carry that approach, its page limit, requested topics, and any mandatory format. If past performance is evaluated, capture what the buyer considers relevant and what records or references it requests. Never assume evaluators will search another volume for proof that belongs in the evaluated response.

Interpret weights without overreading them

A disclosed percentage is useful, but it is not the entire award decision. A factor worth 30 percent deserves proportionate planning attention, yet a five-percent factor may still contain a mandatory condition. Likewise, the absence of numerical weights does not mean all factors are equal.

Under FAR 15.304, federal evaluation factors must represent important areas, support meaningful comparison, and have their relative importance stated. The regulation also says the rating method need not be disclosed. FAR 15.305 allows numerical weights, adjectival or color ratings, ordinal rankings, or combinations of methods.

Use this hierarchy:

1. Follow an express point or percentage allocation when the solicitation provides one.
2. Follow an express order of importance when factors are ranked.
3. Follow statements such as “technical factors combined are more important than price.”
4. If the document is silent or inconsistent, log the ambiguity for the authorized question process rather than manufacturing a formula.

“Best value” also does not mean “price does not matter.” It describes the buyer's stated award approach. The tradeoff may favor a higher-priced proposal, may place price and technical merit on roughly equal footing, or may operate differently under the applicable procurement method. Repeat the solicitation's language instead of announcing a universal rule.

Match every factor to evidence

Evaluators can credit what the response demonstrates within the rules of the competition. Replace generic claims with evidence that answers the factor.

For example:

• For experience, identify comparable scope, buyer type, period, and result.
• For key personnel, connect named qualifications to the exact work they will perform.
• For methodology, show steps, controls, owners, outputs, and how the approach addresses the stated risk.
• For schedule, connect milestones to dependencies and required completion dates.
• For past performance, follow the buyer's definition of relevance rather than choosing only the largest contracts.

Texas agencies may use vendor performance as a best-value consideration when the solicitation says it may be considered; the Texas Comptroller's VPTS guidance explains that the IFB or RFP must contain that statement. That is a reminder to search for agency-specific performance language instead of assuming past performance is always scored the same way.

Run a score-first review

Before final production, give reviewers only the solicitation, evaluation map, and proposal. Ask them to work factor by factor.

• Can the reviewer find the response in the required location?
• Does the response answer every element of the factor and subfactor?
• Is the strongest claim supported by concrete evidence?
• Does the proposal take an unstated exception or rely on an assumption?
• Is a pass/fail item being mistaken for a scored strength?
• Does the draft spend disproportionate space on a low-priority topic while a major factor remains thin?

Keep this buyer-side review separate from your company's go/no-go decision framework. Your internal pursuit score asks whether the opportunity deserves resources. The evaluation map asks how this buyer says it will compare acceptable offers. Both can inform a bid check, but they answer different questions.

How GreenLight applies this

GreenLight can organize detected response requirements into a package inventory that preserves their sources and distinguishes ready, missing, and review states. It can also apply an organization's documented qualification rules and gaps to support a human go/no-go decision.

Those capabilities do not reveal an undisclosed scoring formula, predict an award, or replace the evaluation instructions. Automated extraction can miss a requirement. Users must compare the inventory with the current solicitation, decide how to answer each factor, and make the final pursuit and submission judgments themselves. Use the public-sector RFP compliance-matrix guide to plan requirement coverage, then use the requirement-traceability process to audit that coverage through final files and review decisions.

Evaluation-criteria checklist

• Confirm the current solicitation and every addendum are in the review set.
• Separate responsiveness, minimum qualification, and scored factors.
• Capture every factor, subfactor, weight, and relative-importance statement.
• Connect each factor to its required response location and format.
• Assign an owner and specific proof for every evaluated element.
• Log ambiguities for the authorized Q&A channel.
• Review the proposal only against disclosed criteria.
• Recheck the map whenever the buyer issues an addendum.

Sources

• City of Austin — RFP 1100 MMH3031 Standard Solicitation Instructions
• Acquisition.gov — FAR 15.204-5, Part IV: Representations and Instructions
• Acquisition.gov — FAR 15.304, Evaluation Factors and Significant Subfactors
• Acquisition.gov — FAR 15.305, Proposal Evaluation
• Texas Comptroller — Vendor Performance Tracking System Guidance

Research reviewed August 18, 2026. The municipal and state examples illustrate specific buyer rules; they do not establish a universal public-sector scoring method.

Frequently asked questions

Are all RFP requirements scored?

No. Some requirements determine responsiveness or minimum eligibility and may be reviewed on a pass/fail basis. Other factors distinguish among proposals that survive that screen. Label the treatment from the solicitation instead of assuming every requirement earns points.

What if the RFP lists factors but does not show points?

Capture any stated order or relative importance and plan to that disclosure. Do not create a point formula and present it as the buyer's method. If the documents conflict or the relative importance is genuinely unclear, ask through the authorized Q&A process before the deadline.

Should proposal page count follow the scoring weights exactly?

Not mechanically. Weights should influence effort, proof, and review attention, but page limits, required topics, complexity, and pass/fail obligations also matter. The goal is complete, easy-to-find evidence proportional to the buyer's stated priorities, not a page-allocation equation.