Best-value construction RFPs: match proposal effort to the stated evaluation basis

Use the solicitation's evaluation basis to connect construction proposal evidence, estimating assumptions, ownership and pursuit decisions.

Guide5 min read

Published

Tower crane above steel reinforcement

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.

Book a demo
On this page
  1. Identify the selection basis before allocating proposal work
  2. Turn each instruction into a readiness record
  3. Work the handoff from technical promise to trade carry
  4. Set a pursuit gate and close the loop

Before a GC or CM preconstruction lead commits estimating and design-partner capacity to a best-value RFP, identify how that particular owner will evaluate proposals. Then match each submission instruction and evaluation factor to proof the team can actually provide, its price assumptions and a responsible reviewer. The words “best value” alone do not establish that stronger technical features can offset a higher price.

Make the first pursuit decision on the documents and the team's ability to respond, not on an invented score or prediction of competitors. If a required reference, key person or price basis cannot be substantiated in time, resolve that gap or decline the pursuit.

Identify the selection basis before allocating proposal work

Start with the issued RFP, attachments and amendments. Record the solicitation identifier, issue and amendment dates, submission deadline, applicable procurement provisions, evaluation factors, relative importance where stated, and the instructions for each proposal volume. Check whether the owner describes minimum acceptability, a tradeoff, or another selection approach. Note how price is to be submitted and evaluated, including any stated allowances, alternates or assumptions. If the documents conflict or are unclear, use the solicitation's question process and track the answer against the affected work.

The published federal rules illustrate why the distinction matters, but they are not a rule for every construction RFP. Under FAR 15.101-1, a tradeoff process permits price and nonprice tradeoffs; the solicitation states the relevant factors and their relative importance. A higher-priced proposal's perceived benefits must merit the additional cost. Under FAR 15.101-2, lowest price technically acceptable (LPTA) uses stated acceptability standards and the lowest evaluated price among acceptable proposals; nonprice factors are not ranked and tradeoffs are not permitted.

The published FAR overhaul model Part 15 also distinguishes tradeoff and LPTA and identifies other approaches. A model is not evidence that a particular agency adopted it. Check the provisions applicable to the procurement, any agency deviation, and the issued RFP and amendments. Do not assume that a numerical score, a premium for additional technical benefits, or an opportunity to negotiate follows from the label “best value.”

For pursuit planning, separate the delivery method from the evaluation basis. Knowing that the work is design-build or CMAR does not by itself tell the estimator how this owner will select the proposal. Similarly, keep eligibility separate from proposal evidence: a qualification review does not replace the evidence the RFP requests for an evaluated factor.

Turn each instruction into a readiness record

The following is a proposed working tool, not a prescribed government form. Create a row for every material submission instruction and factor, including price and any pass/fail requirement. Copy the actual RFP reference and wording into the working version; distinguish what the owner requires from the team's proposed response. If relative importance is stated, carry it into the record without inventing weights.

Solicitation basisMinimum acceptability or tradeoff factorRequired project evidenceTechnical and price assumptionPreparer / reviewerOpen question
RFP section and amendmentExact factor or threshold, if statedRequested proof and sourceScope, staffing or sequence carried in both volumesNamed owner / independent checkDecision, question owner and due date

A row is ready for review when the proof is available, the proposed language responds to the actual instruction, and the estimator can trace any promised work to a carry or an explicit, permissible qualification. A polished narrative is not evidence of a completed requirement. Conversely, a cost carry alone does not prove the technical submission includes the requested explanation.

Work the handoff from technical promise to trade carry

Consider this hypothetical solicitation: an owner asks for an occupied-building phasing plan and evaluates the proposed approach in a tradeoff. The GC proposes evening cutovers and temporary protection to maintain access. The pursuit lead assigns the superintendent to prepare the sequence and the estimator to check affected trade quotations, temporary protection and general conditions. The technical reviewer checks the narrative against the RFP; the estimate reviewer checks that the carry reflects the same sequence and duration.

If a subcontractor's quote excludes evening work, the team has an open scope and price question. Obtain a revised quote or make a documented estimate adjustment, then reconcile the schedule and technical narrative. If the proposed cutovers depend on owner access windows that the documents do not establish, submit a question under the stated process and assign an answer deadline before final pricing. Do not describe the assumption as an owner commitment.

The effort changes with the actual basis. If an RFP instead uses an acceptability threshold, the team should demonstrate the required threshold and price the compliant plan; it should not assume that additional features earn a tradeoff premium. If the RFP asks for similar-project records or named staff, identify the exact evidence requested, verify availability and obtain the responsible person's review. Do not add those items as universal requirements.

Set a pursuit gate and close the loop

At the initial gate, the pursuit lead should confirm the selection basis, required submissions and available capacity with estimating and any design partner. Mark each evidence item available, obtainable by a named date, or unavailable. Proceed when the team can assemble a compliant, internally consistent response within the available effort. Defer commitment while a material ambiguity can still be resolved; decline if essential proof or capacity cannot be secured in time. This is a resource decision, not a forecast of award.

Before submission, revisit the record against every amendment. Confirm that answers and revisions reached the technical and pricing owners, that changed scope is reflected in the relevant trade carry, and that exclusions and assumptions are handled as the RFP permits. The final reviewer should be able to move from each material instruction to its response and from each technical promise to its estimate basis, with unresolved issues visible to the decision maker.

ShareLinkedInX

Related reading

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

See Piper on your project

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.