How to plan a lowest-price compliant tender bid

Decision rule

Prove that extra quality receives no tradeoff credit

Build an award-mechanics sheet from the tender notice, instructions, criteria, scoring method, pricing schedule, contract, amendments and authoritative answers. Separate conditions of participation from tender acceptability. List procedural requirements such as deadline, signature, format and mandatory forms. List technical thresholds and their pass evidence. Then record how evaluated price is calculated and whether acceptable tenders are ranked on any non-price dimension. Do not infer “lowest compliant” from a headline when the detailed method still scores quality.

A pure method needs a binary path: the offer passes all relevant gates, after which the lowest evaluated price wins, subject to the procurement’s other rules. FAR 15.101-2 is a specific US federal model: it says LPTA award uses the lowest evaluated price among proposals meeting the acceptability standards, does not permit tradeoffs and does not rank the acceptable technical proposals. UK Procurement Act guidance recognises that price can be the sole criterion while also noting this is unlikely to suit most contracts. These sources do not define every tender called “lowest price.” The issued assessment method does.

Mark unclear mechanics for clarification before changing the solution. Ask which options enter price, how discounts or taxes are treated, whether a technical response is ranked or only passed, what a tie-break does and whether failure under one criterion stops evaluation. Keep internal win themes out of the rule. The strategy begins only after the team can reproduce the evaluator’s path from received submission to acceptable set to winning price.

Offer design

Find the minimum complete delivery model, not the weakest response

Trace every mandatory outcome, deliverable, volume, service level, control and contractual duty into the solution. For each, record the delivery activity, resource, input, dependency, acceptance evidence, cost element and price line. This establishes the floor. Minimum does not mean vague, understaffed or barely described. It means no cost remains unless it supports a requirement, manages a retained risk or enables the contracted operating model. A short technical answer still needs enough evidence for a pass.

Distinguish specification from habit. A standard company feature may be valuable but unnecessary for this contract; a familiar review layer may duplicate a buyer control. Remove or simplify it only after solution, risk, security and contract owners agree it is not required. Conversely, do not classify an inconvenient obligation as optional because the evaluation question does not mention it. Contract schedules, security appendices and service requirements can create costs even when they are not separately scored.

Make buyer inputs and third-party work explicit. A lower-cost design may rely on buyer-provided premises, data preparation, licenses, integration or first-line support. Use that allocation only when the tender supports it and the price, plan and contract say the same thing. If the lowest solution shifts workload the buyer expected the supplier to carry, it is not an optimisation; it is an undisclosed scope qualification. Where alternatives are permitted, keep the compliant base offer separate from optional enhancements.

• Map every obligation to work, resource, evidence and price.
• Remove cost only after confirming the related scope is not required.
• Preserve enough proof for each binary pass decision.
• Disclose supported buyer inputs without transferring hidden work.
• Separate permitted options from the compliant base.

Pass evidence

Make every threshold easy to verify once

Create one acceptability record per gate with the exact requirement, consequence, source, response location, evidence, owner and verifier. Lead each answer with an unambiguous statement of conformance and scope. Follow with the minimum mechanism and proof needed for the evaluator to verify it. Do not assume a certification in an appendix will be found, or that a strong answer under one criterion cures a missing declaration under another. Binary evaluation rewards completeness, not rhetorical force.

Use precise evidence. If a required capacity is 10,000 transactions per hour, provide the tested configuration, workload definition, result and applicability to the proposed setup. If a named credential is mandatory, identify the holder, validity and proposed role. If an implementation plan must contain five elements, show all five in visible headings. Avoid exceeding a threshold with an expensive commitment unless the extra level reduces a retained delivery risk or costs less overall. In a true LPTA method, an evaluator cannot rank the surplus technical merit.

Run independent red-team checking against the exact binary rule and final rendered artifacts. The reviewer must classify each item pass, fail or unresolved and cite the evidence. “Likely pass” is not a release state. Resolve inconsistencies between narrative, forms, price and contract because one can invalidate another. Treat portal fields, file limits, signatures and required blanks as part of acceptability. An excellent cost model cannot rescue a late or procedurally defective submission.

Price integrity

Reduce the evaluated price without creating an unperformable contract

Reproduce the evaluated basket independently. Include stated quantities, base and option periods, one-time charges, usage lines, discounts, inflation, currency and tax exactly as the method requires. Keep evaluated price, expected revenue, cash and total delivery cost in separate views. A synthetic basket may reward a rate pattern that is unattractive under likely demand. Decision-makers need both the competition result and the contract economics before approving the structure.

Reduce price through traceable levers: narrower permitted scope, standard configuration, delivery sequence, location mix, role design, automation, subcontract choice, purchasing terms, risk treatment and margin authority. Document what changes, why the minimum still passes, which dependency shifts and what evidence supports the productivity assumption. Do not use unspecified future change control, unpaid overtime or an implausible hiring plan as a cost lever. Challenge optimism with low, expected and high credible cases.

Avoid moving price from highly weighted or estimated lines into options or low-quantity lines without regard to contract use. FAR 15.404-1 requires analysis of separately priced line items for unbalanced pricing and permits rejection where imbalance creates unacceptable risk in its federal context. UK guidance also describes a process for examining an abnormally low tender before it may be disregarded. A low price can come from efficiency, but the bidder should be ready to explain the operating basis, scope, cost and authority without reconstructing the bid after submission.

At final approval, reconcile technical pass, staffing, schedule, third-party quotes, volume, service credits, liabilities, indexation, cash, line-item allocation and margin. Run a delivery-signature review in which the accountable executive confirms that the organisation can perform the proposed contract at the submitted price. The objective is not a premium proposal disguised as low cost or a cheap tender dependent on later recovery. It is the lowest evaluated price the organisation can defend and deliver while meeting every published gate.

• Separate evaluated price from expected contract economics.
• Tie every cost reduction to a permitted delivery change.
• Stress-test volume, productivity, cash and option assumptions.
• Review line-item balance and abnormally low price exposure.
• Obtain accountable approval for performance at the submitted price.