Turn tender evaluation criteria into a response strategy

Decision model

Translate a criterion into a decision the response can support

Begin after the evaluation model has been reconstructed from the current tender package. Copy the criterion, subcriteria, relative importance, score descriptors, threshold, response instruction and requested evidence into one strategy record. Then complete the sentence: “The evaluator must decide whether our proposed offer…” This converts a heading such as “implementation” into an assessed decision about feasibility, sequence, governance, resources, dependencies and date confidence. Preserve the buyer’s language; strategy should interpret the response obligation, not silently rewrite it.

Distinguish the minimum case, the credible strength case and unsupported ambition. The minimum case states what makes the response complete and admissible. The strength case identifies a specific quality the published method can recognize, such as a controlled transition path, lower operational exposure or evidence of relevant performance. Unsupported ambition is any intended rating that relies on hidden preferences, unavailable proof or an unauthorized commitment. It belongs in the gap log, not in the target score.

FAR 15.304 says evaluation factors should represent important areas and support meaningful comparison. FAR 15.305 describes assessment against the factors and subfactors in the solicitation. Those rules govern particular US federal procurements, not every tender, but they illustrate a useful discipline: the strategy earns differentiation inside the stated comparison, not beside it. UK guidance similarly anchors assessment in the published award criteria and methodology. The actual documents and applicable law always control.

Create a one-page strategy card for each material criterion. Record the buyer decision, pass condition, planned response position, offer choice, proof, owner, dependencies, red lines, response location and review test. Link every entry to its source. A card is complete only when a solution or commercial owner can explain what will be different in the offer and an evidence owner can show why the evaluator should believe it. A slogan and a high weight are not a strategy.

Offer design

Use scoring influence to make real offer choices before drafting

For every planned strength, ask what the offer must do differently. A higher implementation position might require a named mobilization lead, a verified dependency workshop before a fixed date, measurable exit criteria and a recovery route. A stronger service answer might require a particular support window, escalation authority and reporting commitment. If the only change is more enthusiastic prose, the score case is fragile. Make the choice in the solution, delivery or commercial baseline first, then write it.

Test tradeoffs explicitly. Additional resilience may increase cost and implementation effort. A faster transition may require earlier buyer access or narrower initial scope. A named senior team may improve credibility but constrain capacity. Record the buyer benefit, price effect, delivery risk, contract effect and condition for each option. Select one coherent configuration rather than promising every desirable quality in separate sections. The proposal, price schedule, implementation plan and draft contract must describe the same offer.

Do not treat every point as equally available. Some distinctions depend on evidence the bidder already has; others require an approved design decision; some cannot be closed honestly before submission. Estimate the decision value of closing each gap, the work required and the consequence of failure. A medium-weight criterion where one workshop can replace a generic answer with a credible method may deserve attention before a high-weight area already supported by strong reusable evidence.

Keep price and quality connected without claiming to know competitor bids. If an enhancement has an identified cost, test whether its plausible evaluated benefit justifies that cost under the published model and several transparent scenarios. If the evaluation uses qualitative judgement, use score ranges and switching conditions rather than decimal predictions. Strategy is a choice among supportable offer configurations, not a forecast disguised as mathematics.

• Name the operational choice behind every intended strength.
• Price the people, controls, tools and service levels that the choice requires.
• Record buyer dependencies and limits beside the commitment.
• Reject combinations that make the overall offer inconsistent.
• Use scenarios to choose an offer, not to invent a likely award.

Resource allocation

Spend scarce expert time where a credible improvement is possible

Create an evidence ladder for each criterion: direct verified performance under comparable conditions, independently issued assurance, controlled internal records, approved method with responsible owners, and unsupported assertion. Select evidence by applicability, not prestige. A famous client name does not prove performance if the bidder played a minor role or delivered different scope. Record entity, role, period, conditions, measure, source, approval and any limitation. The intended claim must not exceed what the evidence establishes.

Calculate priority from four factors rather than weight alone: evaluation influence, current evidence gap, dependency criticality and recovery feasibility. Add delivery or contractual consequence as a constraint. A heavily weighted answer with excellent current proof may need careful assembly but little invention. A smaller question that controls a threshold, creates a central architecture dependency or exposes an unpriced obligation may need immediate senior attention. Publish the rationale so resource allocation is not driven by the loudest section owner.

Give authors a decision brief, not just a page limit. It should contain the exact criterion, direct question, chosen offer, proof records, required components, prohibited claims, dependencies, buyer terms and review test. Subject-matter experts decide facts, methods and commitments; writers make those decisions clear. If an owner has not approved the method, label the text as a draft option. Polished language must never turn an unresolved proposal into an accidental promise.

Manage shared facts across criteria. A staffing ratio may affect method, capacity, price and mobilization. A recovery time may appear in resilience, service levels and contract schedules. Link those answers to one controlled decision record. When a late change occurs, the record reveals every affected section, evidence citation and approval. Without that linkage, locally optimized answers can collectively describe an offer that cannot exist.

Strategy review

Ask whether the rendered answer earns its planned position

Review against the criterion card, not against the author’s intention. In the exact response format, a reviewer must identify the direct answer, every requested component, the proposed method, accountable ownership, relevant proof, buyer consequence and material condition. Mark each item as found, weak, contradictory or absent. Do not award internal credit for a fact that exists elsewhere unless the tender permits the cross-reference and the response makes it precise.

Require reviewers to state the basis for any planned strength. “Compelling” is not a finding. A useful review note says that the response presents a dated transition sequence and named decision gates but lacks evidence that the proposed team has delivered comparable scope. The correction is then clear: add valid evidence, alter the team, narrow the claim or reduce the target position. This protects the bid from cosmetic editing that leaves the evaluated weakness untouched.

Run a cross-criterion review after individual sections. Reconcile dates, staffing, volumes, service levels, architecture, responsibilities, assumptions, price and contract positions. Check that a differentiator placed in one answer does not create an unapproved exception in another. Revisit the pursuit decision if a threshold becomes unattainable, a central strength loses its evidence or the price needed to support the strategy destroys the commercial case.

Freeze the accepted criterion cards with the response version and approval record. When an addendum, clarification, price decision or solution change arrives, identify the affected cards and reopen only the necessary decisions and reviews. The strategy remains a living control until submission. After the award decision, compare debrief evidence with the recorded hypotheses, not with retrospective stories, so the next bid learns which choices and proof actually helped.

• Review the buyer-visible response, not the source draft.
• Name the evidence behind every intended strength.
• Reduce the target when the proof cannot support it.
• Reconcile shared commitments across all criteria.
• Reopen strategy when material tender or offer inputs change.