How to Write a Winning Technical Proposal for a Kenya Government Tender (Methodology, CVs, Work Plan)
You qualified. Your company profile passed. Your financial documents are in order.
You qualified. Your company profile passed. Your financial documents are in order.
The bid evaluation results come back and your score reads: Technical Proposal: 38/70. The winner scored 61/70.
This happens to hundreds of Kenyan SMEs every procurement cycle. The painful truth? It's almost never about the scope of work β it's about how you wrote about the scope of work.
This guide breaks down the technical proposal from the ground up: what evaluators look for, how to structure each section, how to write a methodology that actually scores, what makes CVs acceptable vs. outstanding, and how to build a work plan that gives evaluators confidence.
Before you write a single word, understand what you're writing for.
Under Kenya's PPADA 2015 framework, most tenders use a Quality and Cost Based Selection (QCBS) approach or Quality-Based Selection (QBS) for consultancies. Technical proposals are scored first, financial proposals only opened for technically responsive bidders.