Understanding the Evaluation Criteria

11.1 How Stated Evaluation Criteria Translate Into Pricing Strategy

Evaluation criteria: the stated factors, subfactors, standards, and price evaluation rules the government will use to assess proposals and make an award. In PTW, evaluation criteria are not merely compliance instructions. They are pricing signals. They indicate whether the customer is likely to reward differentiation, punish risk, scrutinize realism, or compress the competition toward the lowest acceptable price.

The PTW team should start by separating what the solicitation says from what it implies. A solicitation may state that technical factors are more important than price, but if requirements are prescriptive, page limits are tight, scoring is coarse, and the price evaluation is simple, price may become the practical discriminator. Conversely, if the work is mission-critical and technical risk is complex, the customer may pay a premium for a proposal that clearly reduces risk.

Evaluation criteria translate into pricing strategy through four tests. Visibility: will the customer see and credit the differences we are pricing? Weight: how much will those differences matter relative to price? Defensibility: can the source selection authority justify paying more for those differences? Comparability: are competitors likely to offer similar strengths at lower prices?

Visibility is the first test. A contractor may invest in a superior tool, deeper staffing bench, or more robust management process, but if the criteria do not allow the customer to recognize that advantage, the investment may not support a premium. PTW should challenge every major cost driver by asking whether it creates an evaluated strength or only an internal belief in superiority.

Weight and defensibility are the next tests. Some criteria are explicitly weighted; others are listed in order of importance or described qualitatively. The PTW team should determine whether technical strengths can overcome a price gap, and if so, how large a gap appears reasonable. A premium price must also be defensible in the award record. General claims of quality, innovation, or customer focus are weak support. Specific reductions in transition risk, measurable performance improvements, stronger key personnel, proven staffing availability, or lower cost of failure are stronger support.

Comparability completes the analysis. A bidder may be excellent, but if several competitors are also excellent, price becomes more important. Customers pay premiums for meaningful differences among offers, not for excellence in the abstract. PTW must ask whether the company’s strengths are unique, rare, or merely expected. When technical proposals are likely to cluster, the winning price usually moves downward.

11.2 Lowest Price Technically Acceptable vs. Best-Value Trade-Off

Lowest Price Technically Acceptable and best-value trade-off represent different pricing worlds. Confusing them is one of the most expensive mistakes in government contracting. The contractor that brings a premium best-value solution into an LPTA competition often loses cleanly. The contractor that brings a thin LPTA-style solution into a true best-value trade-off may lose because the customer perceives unnecessary risk. PTW must identify not only the stated method, but also how the method is likely to behave in practice.

Lowest Price Technically Acceptable: an evaluation approach in which the government determines whether proposals meet stated technical acceptability standards and then awards to the lowest-priced acceptable offer. The pricing strategy is to meet the requirements convincingly at the lowest responsible evaluated price. Added features that do not improve acceptability usually do not create award value. The critical PTW question is, “What is the minimum credible solution that will be found acceptable and executable?”

In LPTA, overbuilding is a common failure. Capture and solution teams may add senior staff, enhanced tools, extra management layers, and transition safeguards because those elements make the proposal feel stronger. If the customer does not evaluate those additions beyond acceptability, the company has increased price without increasing win probability. PTW should push the team to distinguish must-have requirements from nice-to-have features. The solution should be compliant, credible, and low risk enough to pass, but not loaded with unevaluated premium.

LPTA does not mean reckless underpricing. A low price can create concern if it suggests misunderstanding, unrealistic staffing, weak professional compensation, or unacceptable performance risk. The bidder must still persuade the customer that the price is executable. The PTW range should therefore estimate the lowest credible evaluated price, not the lowest imaginable price.

Best-value trade-off: an evaluation approach in which the government may select a higher-priced offer if the non-price advantages are worth the additional cost. The pricing strategy is to align price with evaluated value. The bidder may pursue a premium, but the premium must be supported by strengths that matter to the customer and can be documented in the award record. The critical PTW question is, “How much premium will the customer pay for our specific advantages?”

Best value is not a license to price freely. Many best-value procurements become price-sensitive when proposals are technically close. If all serious bidders receive similar ratings, price often dominates the final decision. PTW should therefore estimate both the premium scenario and the parity scenario. In the premium scenario, the company earns meaningful technical separation. In the parity scenario, the customer views proposals as close and selects the lower price.

Some procurements sit between LPTA and best value. They may be formally best value but include pass/fail technical gates, standardized labor categories, limited narrative space, and a strong price factor. Others may be formally LPTA but include acceptability standards demanding enough to eliminate weak low-price bidders. PTW should label the practical behavior, not just the legal category.

11.3 Technical Superiority, Risk Ratings, and Price Premium Tolerance

Technical superiority matters only when it is recognized, differentiated, and worth paying for. Contractors often assume that because their solution is better, the customer will pay more. PTW requires a harder test. What exactly is superior? Will evaluators score it as a strength? Does it reduce a risk the customer cares about? How much price difference can the source selection authority defend?

Technical superiority: an evaluated advantage that gives the customer more capability, lower risk, better performance, faster outcomes, stronger staffing, or greater confidence than competing offers. The word “evaluated” is essential. Internal superiority does not support premium pricing unless the evaluation framework allows the government to credit it.

Risk ratings are often the practical link between technical superiority and price. A superior solution may justify a premium because it reduces transition risk, delivery risk, staffing risk, integration risk, security risk, or mission risk. Conversely, a low-priced proposal may lose if the customer assigns higher risk and decides the savings are not worth the exposure. PTW should therefore model not only price differences, but also risk-adjusted award logic.

Price premium tolerance: the amount above the low-price or market price the customer is likely to pay for a higher-rated or lower-risk offer. Premium tolerance is not fixed. It depends on mission criticality, budget flexibility, evaluation criteria, technical separation, incumbent performance, competitive alternatives, and customer history. A five percent premium may be acceptable in one procurement and fatal in another. A fifteen percent premium may be defensible only when the technical gap is large and the consequences of failure are material.

PTW should estimate premium tolerance using evidence, not optimism. Relevant evidence includes prior premium awards, debriefs explaining trade-offs, protest decisions describing award rationale, customer statements about mission risk, budget signals, and the structure of evaluation factors. If the customer has repeatedly declined premiums when technical differences were modest, the team should not assume this procurement will be different without strong evidence.

The proposal must create the premium. A company cannot simply choose a higher price and hope the customer recognizes value. The technical volume must show why the solution is materially better, how the advantage maps to evaluation criteria, and why the difference matters operationally. If the company bids a premium for staffing certainty, it should demonstrate recruiting pipelines, named personnel, retention plans, compensation realism, and transition controls.

Risk ratings can also constrain aggressive pricing. A low-price strategy may be appropriate, but only if the solution remains credible. If evaluators believe the staffing is too thin, the labor mix unrealistic, or the transition underfunded, the low price may produce weakness rather than advantage. PTW should examine the price-risk frontier: how low can the company bid before the offer begins to look risky?

11.4 Past Performance, Staffing, Management Approach, and Transition Risk

Several evaluation factors are especially important in PTW because they connect directly to price and risk: past performance, staffing, management approach, and transition. These factors often determine whether a customer sees a low price as attractive or dangerous.

Past performance: evidence that the bidder has successfully performed similar work for similar customers under similar conditions. Strong past performance can support premium pricing when it reduces customer uncertainty. However, it must be relevant. A broad reputation may matter less than recent, comparable work at the right scale, mission, and contract type. If competitors also have strong relevant records, past performance may not support much premium.

Past performance can also help challengers overcome incumbent advantage. A challenger with highly relevant success elsewhere may persuade the customer that transition risk is manageable. If that challenger also offers a lower price, the incumbent’s premium tolerance may shrink. For an incumbent, past performance can defend continuity, but only if the customer is satisfied and the price remains affordable.

Staffing: the proposed labor mix, key personnel, recruiting approach, retention plan, compensation strategy, and staffing availability. Staffing is one of the largest cost drivers in services bids and one of the most visible risk indicators. A senior-heavy model may reduce risk but increase price. A lean model may reduce price but raise concerns about coverage, quality, or retention.

Professional compensation is often central. If the solicitation evaluates compensation realism or staffing retention, a bidder cannot simply lower salaries to reduce price without creating risk. Conversely, if the customer provides fixed labor categories and estimated hours but does not scrutinize compensation deeply, rate competitiveness may become decisive.

Management approach: the proposed structure for governing performance, managing risk, controlling quality, communicating with the customer, and improving delivery. Management approach can justify price when it clearly reduces operational risk or improves outcomes. But it can also become a source of unnecessary cost. Extra program management layers, governance forums, quality roles, and reporting processes may look impressive but may not be worth a premium if the evaluation does not reward them.

Transition risk: the possibility that performance will degrade during the move from the incumbent or current state to the new contract. Transition risk can be one of the strongest premium drivers. Customers may pay for continuity when mission disruption would be costly. Incumbents often have an advantage because they avoid many transition costs and retain institutional knowledge. Challengers can reduce transition risk through incumbent staff capture, realistic phase-in plans, proven onboarding methods, and strong key personnel.

Transition can cut both ways. If the customer is dissatisfied with the incumbent, it may accept transition risk to obtain better performance or lower cost. If the customer is satisfied but budget constrained, it may demand that the incumbent reduce price while preserving continuity. PTW should assess the customer’s pain, risk tolerance, and affordability pressure before assigning transition value.

11.5 Checklist: Evaluation Criteria Implications for PTW

The following checklist should be used immediately after reviewing the draft or final solicitation. It helps the PTW team convert evaluation language into pricing implications. The checklist should be completed jointly by capture, PTW, solution, pricing, proposal, contracts, and finance. The purpose is to identify what the customer will reward, what it will ignore, and what price posture the evaluation method supports.

• Evaluation method: Is the procurement LPTA, best-value trade-off, cost-realism based, technically acceptable with price pressure, or ambiguous in practical behavior?
• Factor weighting: How important is price relative to technical, past performance, management, staffing, and risk factors?
• Scoring visibility: Which solution features can evaluators actually see, score, and document as strengths?
• Premium support: Which evaluated strengths could justify a higher price, and how large a premium appears defensible?
• Price discriminator risk: Are competitors likely to be technically similar, making price the practical discriminator?
• Acceptability threshold: Under LPTA or pass/fail factors, what is the minimum credible solution that will pass without unnecessary cost?
• Cost realism: Will the government evaluate whether labor mix, hours, compensation, or total cost are realistic?
• Staffing implications: Does the evaluation reward seniority, key personnel, retention, compensation realism, fill rates, or incumbent staff capture?
• Management implications: Does the proposed management structure create evaluated value or unevaluated overhead?
• Transition implications: Is transition risk a major award factor, and who has the strongest credible transition story?
• Past performance implications: Does the company have meaningfully stronger, equally strong, or weaker relevant past performance than likely competitors?
• Risk-rating implications: How low can price go before the solution appears risky, thin, or unrealistic?
• Customer history: Has this customer previously paid premiums, selected low price, retained incumbents, or rejected higher-priced technical strengths?
• Scenario needs: What PTW scenarios are required: low-price acceptable, best-value premium, incumbent retention, challenger disruption, or cost-realism adjustment?
• Bid action: What must change in the solution, staffing, teaming, price, or proposal narrative to align with the evaluation criteria?

The checklist should produce a short evaluation implications memo. That memo should state the practical award logic, likely premium tolerance, key evaluated cost drivers, risks of overbuilding, risks of underpricing, and required PTW scenarios. The value is in interpretation, not restatement.

A strong memo might say: “Although the solicitation says technical factors are more important than price, the requirements are prescriptive and most serious bidders are likely to be rated acceptable or good. Price is likely to become decisive unless we create clear transition-risk separation.” That conclusion gives the team a usable pricing strategy.

Evaluation criteria should shape the bid before the final price review. If the criteria do not reward a feature, the team should question whether it belongs in the solution. If the criteria reward transition certainty, the team should invest in proof, not slogans. If the criteria emphasize affordability, the team should design for cost reduction early.

PTW is ultimately about predicting the evaluated competition, not the internal competition the bidder imagines. Evaluation criteria define that competition. They show what the customer can compare, credit, defend, and award. A contractor that reads them strategically can avoid submitting an expensive solution the customer will not reward or a cheap solution the customer will not trust. The right price fits the evaluation logic, customer risk tolerance, competitive field, and company’s ability to deliver.