Vendor proposals become comparable only after four gates are normalized. The evaluation should expose differences in compliance, scope, evidence and commercial risk before totals, rankings or prices are treated as decision-ready.
Proposal-normalization gates
- Requirement gate: does the offer meet every mandatory technical, safety, data, legal and operating condition?
- Scope gate: are design, site works, interfaces, commissioning, service, replacement and exit assigned to a named party?
- Evidence gate: are performance, delivery, security and support claims backed by relevant proof rather than marketing language?
- Commercial gate: are price, escalation, assumptions, exceptions, warranties, liabilities and remedies on a common boundary?
A failed mandatory gate cannot be repaired by a high weighted score. A higher-priced offer should be selected only when the evidenced additional value merits the additional cost and the tradeoff is documented.
Before proposals arrive
Define the requirement and decision rule
State the outcome, operating conditions, interfaces, minimum performance, site constraints, delivery date, data needs, acceptance tests and commercial boundary. Separate requirements that are mandatory from factors that can be traded.
Evaluation factors should represent the areas that matter to the decision and distinguish meaningfully between competing proposals. Set the factors, weights, gates and scoring definitions before final proposals are reviewed where practical.
Issue a common response structure
Ask vendors to respond in the same order and units. A useful response schedule may cover:
- compliance with each requirement and identified exceptions;
- technical approach, design assumptions and performance evidence;
- site, utility, integration and customer dependencies;
- delivery plan, milestones, resources and subcontractors;
- commissioning, acceptance, training and documentation;
- service, maintenance, support, warranty and spare parts;
- data ownership, access, security, retention and portability;
- price schedule, validity, escalation, options, exclusions and allowances;
- contract departures, liability, guarantees and remedies;
- references for comparable operating conditions.
1. Check compliance before scoring preferences
Create a compliance matrix that records compliant, partially compliant, non-compliant and unclear responses. A mandatory failure should not be hidden inside an average weighted score.
Clarify whether a stated compliance depends on an assumption, customer action, future design decision or third-party approval. “Compliant subject to survey” is different from demonstrated compliance.
2. Normalize scope and commercial boundary
Build a side-by-side scope table. Identify who supplies and pays for design, permits, civil works, electrical upgrades, communications, integration, commissioning, training, maintenance, software, data, consumables, replacement and decommissioning.
For every exclusion or allowance, estimate the purchaser’s likely cost or preserve it as an unresolved exposure. Do not silently add an estimated adjustment to a proposal without recording the basis and uncertainty.
| Comparison layer | Normalize | Record separately |
|---|---|---|
| Compliance | Mandatory requirement, test and evidence standard | Exceptions, dependencies and unresolved interpretations |
| Technical scope | Capacity, performance boundary, interfaces, site work and owner-furnished items | Optional capability and material design differences |
| Delivery | Milestones, resources, subcontractors, approvals and acceptance | Lead-time risk, assumptions and recovery plans |
| Service and lifecycle | Warranty, maintenance, software, data, replacement and exit | Proprietary dependency and end-of-support exposure |
| Commercial | Price basis, escalation, taxes, allowances, payment and TCO period | Contract departures, risk transfer and contingent cost |
3. Evaluate evidence, not adjectives
A proposal claim should be linked to evidence appropriate to the decision. Depending on the criterion, evidence may include:
- certified test results or recognized standards;
- calculations with stated inputs and boundary;
- site survey findings and design documents;
- reference projects with comparable duty cycle and conditions;
- service-level commitments and support locations;
- warranty and performance-guarantee wording;
- cybersecurity architecture and control evidence;
- financial capacity and supply-chain information;
- implementation schedules, named roles and resource plans.
Record evidence confidence separately from the score. A high score supported only by a future promise should trigger clarification, a condition or a contractual commitment.
4. Use a controlled scoring method
A five-point scale is usually sufficient when each material factor has defined anchors. For example:
- 1 — materially below requirement: important gap, weak evidence or unacceptable limitation.
- 2 — weak: partial fit with significant qualifications or delivery uncertainty.
- 3 — acceptable: meets the requirement with manageable limitations.
- 4 — strong: exceeds the requirement in a relevant and evidenced way.
- 5 — leading fit: clearly superior evidence or capability that creates material decision value.
Avoid scoring every small line independently. Too many factors create false precision and encourage double counting. Use subfactors only where they help explain a material distinction.
| Evaluation type | Use it for | Do not use it for |
|---|---|---|
| Mandatory gate | Safety, legal, technical, security, data, capacity or deliverability conditions that cannot be traded away | Creating an average score that hides a material failure |
| Weighted criterion | Relevant differences in quality, usability, support, implementation, resilience or value | Restating the same advantage under several headings |
| Price or TCO | Comparable cost on the required scope and analysis period | Rewarding omissions, owner costs or unpriced exclusions |
| Evidence confidence | Distinguishing demonstrated, committed, modeled and roadmap claims | Replacing the technical or commercial score without explanation |
| Tradeoff record | Explaining why additional evidenced value does or does not merit additional cost | Using the weighted total as the whole decision |
5. Compare whole-life cost
Normalize price to a common scope and analysis period. Include the purchaser’s costs as well as vendor charges. Use Total Cost of Ownership for Energy Technology and the TCO worksheet.
Check price validity, escalation, foreign-exchange exposure, usage limits, subscription tiers, minimum terms, optional services, indexation, taxes, payment milestones, retention, financing and contract-exit charges.
6. Review risk allocation and contractability
A technical strength has limited value if the proposal will not convert into an enforceable obligation. Compare:
- design responsibility and interface ownership;
- site-condition and utility risk;
- schedule commitment and relief events;
- performance guarantees and calculation methods;
- acceptance criteria, testing and rejection rights;
- warranty coverage, exclusions and remedy;
- service response, parts availability and end-of-support;
- data rights, cybersecurity obligations and exit assistance;
- liability caps, indemnities, insurance and consequential-loss treatment;
- change control, termination and transition.
Legal review should focus on the requirements and risks that materially influenced evaluation. A proposal should not receive evaluation credit for a commitment the supplier refuses to include in the contract.
7. Use clarifications consistently
Clarifications should resolve ambiguity, confirm assumptions and complete the record. Give competing vendors equivalent information and opportunity where required by the applicable process. Keep written records of questions and responses.
Do not use clarifications to redesign the requirement for one vendor or allow an uncontrolled proposal rewrite. The permitted boundary depends on the organization and jurisdiction.
8. Conduct due diligence
Before award, verify the matters most likely to change delivery confidence. This may include references, financial standing, insurance, product certification, key personnel, subcontractors, supply chain, cybersecurity, litigation, safety history, factory capacity, service coverage and ownership of intellectual property.
Reference checks are most useful when they ask about comparable conditions, implementation problems, change orders, support response, actual performance and what the customer would do differently.
9. Document the tradeoff
The selected proposal does not always need the lowest evaluated price. A higher-priced option may provide better value where evidenced differences in performance, delivery, resilience, support or risk justify the additional cost.
The decision record should identify the important differences, explain how price and non-price factors were balanced, state unresolved conditions and show why the recommendation follows from the published method.
10. Preserve an evaluation file
- approved requirement and evaluation method;
- conflict-of-interest declarations;
- proposals and revisions;
- compliance and clarification records;
- individual and consensus evaluations;
- TCO normalization and assumptions;
- due-diligence evidence;
- legal and commercial departures;
- decision and approval record.
Common comparison failures
- Scoring before confirming mandatory compliance.
- Comparing headline price instead of normalized scope and TCO.
- Giving credit for unverified marketing claims.
- Allowing the favored vendor to define the evaluation criteria.
- Double-counting the same advantage under several factors.
- Treating every numeric difference as meaningful despite weak evidence.
- Ignoring contract exceptions until after selection.
- Changing criteria or weights after seeing the proposals.
- Failing to document why a higher-priced proposal creates enough additional value.
Use the tools
Apply the Comparison Methodology, Universal Vendor Comparison Worksheet and Technology Evaluation Scorecard. Continue to Technology Procurement Process for the full sequence.
Complete the clarification and decision record
- Resolve ambiguous compliance, assumptions, exclusions and customer dependencies consistently.
- Verify the evidence that materially affects ranking, cost or delivery confidence.
- Recalculate scope-adjusted TCO after clarifications and negotiated changes.
- Record contract departures, residual risk, due diligence and approval conditions.
- Explain why the selected value and risk position merits its evaluated cost.
Use the Universal Vendor Comparison Worksheet for the working record. The wider Technology Procurement Process places evaluation inside governance, contracting, implementation and acceptance.
Sources and evidence
Primary and authoritative references used for this page are listed below. Recheck current rules, rates, source editions and organizational requirements before a live decision.
- FAR 15.304 — Evaluation Factors and Significant Subfactors — Acquisition.gov
- FAR 15.101-1 — Tradeoff Process — Acquisition.gov
- FAR 15.305 — Proposal Evaluation — Acquisition.gov
- Cost Estimating and Assessment Guide — U.S. Government Accountability Office
- EMIS Planning and Procurement — U.S. Department of Energy FEMP
- Building Life Cycle Cost Programs — U.S. Department of Energy FEMP
- FAR 15.306 — Exchanges with Offerors — Acquisition.gov
- FAR 15.308 — Source Selection Decision — Acquisition.gov
- Project Control authority: approved page map, complete page criteria, contextual-linking rules and layout matrix.
The FAR pages are current US federal acquisition references and were verified against FAC 2026-01, effective 13 March 2026. They illustrate transparent planning, evaluation and tradeoff controls; they do not govern every private, non-US or non-federal procurement.
Reviewed and updated 29 June 2026. Recheck when financial methods, procurement rules, official guidance, discount and escalation inputs, organizational governance or the page’s material claims change. Organizational author: Future Green Technology, published by Zenith Star Media.