Technical vs financial proposal: what evaluators actually score
Public buyers rarely award contracts on price alone. Most competitive tenders — whether published on TED, a national e-procurement portal, or a development bank's system — split your bid into two distinct packages: a technical proposal and a financial proposal. Understanding the difference between technical vs financial proposal scoring is one of the most practical things a bidder can learn, because it determines how you allocate drafting time, where you take risk, and how an evaluator's scoresheet actually adds up.
In short: the technical proposal scores your methodology, team, and capacity against fixed criteria; the financial proposal scores your price, often inside a sealed or digitally locked price envelope that is opened only after technical scoring closes. Under MEAT criteria (most economically advantageous tender), the two scores are combined using a published formula — commonly a weighted split such as 70/30 or 80/20 in favor of technical quality. Get the weighting wrong in your planning, and you risk over-investing in one section while under-resourcing the other.
What is the technical vs financial proposal split in practice?
Every tender dossier that uses MEAT-style evaluation separates the bid into two self-contained submissions, even if they are uploaded in the same portal session.
The technical proposal typically includes:
- Your proposed methodology and work plan
- Team CVs and role allocation
- Equipment, logistics, and subcontracting arrangements
- Quality assurance and risk mitigation measures
- References and past performance evidence
The financial proposal typically includes:
- Unit prices or lump-sum totals per lot
- Currency and tax treatment
- Payment schedule assumptions
- Price breakdown by cost category (labor, materials, overhead, margin)
Evaluators score these independently. A common procedural safeguard — used across many national e-GP systems and in World Bank-financed projects — is that the financial envelope stays closed until the technical panel finishes scoring and records its results. This prevents the price figure from anchoring or biasing technical judgment, which is a recognized integrity risk flagged in OECD procurement guidance.
If you are still assembling your file structure before this stage, our explainer on how to prepare tender documentation walks through the full folder map most authorities expect.
How do MEAT criteria combine technical and financial scores?
MEAT (most economically advantageous tender) is the evaluation logic behind most technical vs financial proposal splits in EU-regulated and many internationally financed tenders. It replaces "lowest price" with a composite score.
A typical formula looks like this:
Final Score = (Technical Score × Technical Weight) + (Financial Score × Financial Weight)
The financial score itself is usually normalized — the lowest compliant bid gets the maximum financial points, and other bids are scored proportionally lower as their price rises above that baseline.
| Weighting model | Technical weight | Financial weight | Common use case |
|---|---|---|---|
| Quality-focused | 80% | 20% | Complex consulting, design, R&D services |
| Balanced | 70% | 30% | Infrastructure works, IT systems |
| Standard MEAT | 60% | 40% | General supply and services contracts |
| Price-led | 30% | 70% | Commoditized goods, standard supplies |
| Lowest-price-compliant | Pass/fail | 100% | Simple, well-specified procurement |
These are illustrative patterns, not universal rules — the exact weighting is always stated in the specific notice or terms of reference, and you should never assume a default split applies. Always confirm it before drafting. For guidance on locating that information in the first place, see how to read a tender notice.
What do evaluators actually score in the methodology section?
The methodology section is usually the single highest-weighted sub-criterion inside the technical proposal, and it is where many otherwise-qualified bidders lose points unnecessarily — not because their approach is weak, but because the narrative does not map cleanly to the scoring grid.
Evaluators generally look for:
- A clear, sequenced work plan tied to the terms of reference, not a generic company brochure
- Evidence that you understand the specific risks of this contract, not procurement risk in general
- Named staff with roles matched to tasks, supported by CVs that demonstrate relevant experience
- A quality control mechanism — who checks what, and when, during execution
- A realistic timeline that aligns with the financial proposal's payment milestones
A frequent mistake is writing a methodology that reads well but does not reference the specific evaluation sub-criteria listed in the tender dossier. Many scoring panels work from a checklist; if your text does not visibly address each listed criterion, you may receive partial or zero marks for that line item even if the underlying capability exists elsewhere in your proposal.
How does the price envelope affect your financial proposal strategy?
Because the price envelope is often sealed independently and opened later, your financial proposal has to stand on its own — there is no opportunity to adjust price after seeing how competitors scored on technical merit.
This has a few practical implications:
- Price consistency matters. Figures in the financial proposal must match quantities and specifications in the technical proposal; mismatches are a common ground for clarification requests or disqualification.
- Currency and tax rules are strict. Many portals reject bids that do not follow the exact currency, VAT treatment, or rounding convention specified in the instructions to bidders.
- Abnormally low prices trigger scrutiny. Under EU procurement directives and comparable national rules, contracting authorities may request a detailed cost justification if your price falls well below the estimated contract value or the average of competing bids.
- Lump-sum vs unit-price format must match the template. Submitting a lump-sum total where the dossier requires itemized unit prices is a frequent compliance failure.
If bid security is required alongside your financial proposal, review bid bonds and tender guarantees explained before you finalize submission logistics, since bond amounts are often calculated as a percentage of your bid price.
What are the risks and limits of the technical vs financial proposal model?
No scoring model eliminates subjectivity or guarantees a particular outcome, and you should treat any claim otherwise with skepticism.
- Evaluation panels retain interpretive discretion within published criteria, which means two technically similar proposals can receive different scores depending on how clearly each addresses the stated sub-criteria.
- A strong technical score does not offset a non-compliant financial submission; most systems disqualify bids with formatting or currency errors in the price envelope regardless of technical merit.
- MEAT weightings can change between similar-looking tenders from the same authority, so past experience with one notice is not a reliable predictor for the next.
- Abnormally low financial offers can lead to additional scrutiny or rejection, even if the technical proposal scored well — see OECD and World Bank procurement integrity guidance for how this is typically handled.
- There is no guaranteed financing or guaranteed outcome tied to any particular scoring strategy; preparation reduces avoidable errors but does not remove competitive risk.
Practical checklist before you submit
Use this sequence to cross-check your technical vs financial proposal package before the submission deadline:
- Confirm the exact MEAT weighting (technical % vs financial %) stated in the specific notice
- Map each technical sub-criterion to a labeled section in your proposal, not a general narrative
- Verify that quantities, specifications, and timelines match between the technical and financial documents
- Confirm currency, tax treatment, and pricing format (lump-sum vs unit price) against the instructions to bidders
- Check that the financial envelope is submitted as a separate, correctly sealed or digitally segregated file where required
- Re-run your compliance pass against a documentation checklist before final upload
For a fuller compliance pass, our bid compliance checklist covers document-level requirements beyond the technical/financial split, and if you have not yet identified the right opportunities, how to find public tenders worldwide is a useful starting point.
Closing
Separating technical quality from financial price is designed to keep evaluation objective and auditable — but it also means your preparation workload is effectively doubled, with each half judged on different terms. Treating the methodology and the price envelope as two integrated but independently compliant documents is the core discipline behind a well-structured submission.
Leave your contacts for a consultation on tender selection and documentation preparation.
This material is for informational and educational purposes only. It is not legal, tax, or financial advice and it is not an official statement of any contracting authority. B2G Global Services Corp. is not a government agency. Outcomes in public procurement depend on published criteria, local law, and the bidder's own evidence. Readers should verify primary sources as of the action date.