To respond to a tender in South Africa, begin with the evaluation method in the actual bid documents. If they assess functionality, identify exactly what must be demonstrated and how the buyer says it will be considered. A large company profile is not a substitute for targeted evidence. The practical objective is to make each relevant claim understandable, supportable and easy to find in the required response.
Distinguish the guidance from your tender's rules
The National Treasury's Strategic Procurement Framework guide on evaluation and award criteria, updated in February 2024, distinguishes mandatory functionality requirements from other functionality criteria and provides weighted examples. Those examples are guidance for designing evaluations, not a universal score or threshold imposed on every South African bid. For your response, establish the actual criteria, weighting, threshold and evidence requirements from the current tender documents. Do not transfer an illustrative percentage from a general guide into a live competition.
Build an evidence map before writing a capability narrative
Our recommended method uses one row for each evaluation requirement. Record its reference, whether it is mandatory or scored under this tender, the requested proof and the precise response location. Where a criterion has several parts, check each part separately. A reference project might establish experience in a sector without proving a required contract duration or a particular technical role.
Give every evidence item a human owner who can explain its origin and relevance. That owner should confirm dates, scope, contracting entity and any limitations on disclosure. A project description copied from a marketing presentation may omit details essential to the evaluation, while adding a document of doubtful relevance can make the response harder to assess.
| Review field | What the team records | Risk it helps expose |
|---|---|---|
| Criterion reference | Exact requirement from this bid | Answering a different question |
| Evidence requested | Document type and required details | Using a narrative instead of specified proof |
| Claim supported | Activity, person, period or outcome | Overstating what the record demonstrates |
| Response location | Section, attachment and page | Leaving the evaluator to search |
Do not confuse completeness with strength
First ask whether the required information is present in the permitted form. Then ask whether it actually explains the proposed delivery. For example, naming a project manager is different from showing the person's relevant responsibilities and availability. A generic equipment list is different from demonstrating that the proposed resources can perform the requested work.
Use an internal reviewer who did not write the section. Ask them to locate the evidence without help and explain which part of the criterion it supports. If the reviewer must infer an important fact, clarify the response using accurate, permitted information. Do not fill gaps by inventing qualifications, project results, client approvals or commitments from partners.
A fictional example: experience exists, but the proof is incomplete
Imagine a Durban maintenance business whose draft lists several relevant contracts. The tender asks for specific details about comparable work, but the draft describes the company's general history instead. The reviewer maps the requested details against the underlying project records and identifies a missing completion date. The owner verifies that date and revises the relevant entry, rather than attaching an unrelated brochure. This is a fictional evidence-quality example, not a real tender outcome.
Where a requirement remains ambiguous, use the authorised clarification process. Keep the unresolved point visible in the bid decision. An optimistic internal score should never be treated as assurance that the buyer will reach the same conclusion or overlook a missing condition.
Connect evidence preparation to the broader bid
Read our guide to South African tender searches and bid readiness, then use the requirements and evidence matrix method. MyWiseDocs can support document analysis and response drafting; your team must validate the evidence and applicable requirements before submission.
Frequently asked questions
Is there one functionality threshold for every tender?
No single threshold is established by this article. Use the evaluation method stated in the actual bid documents and any applicable clarification. Illustrative figures in general guidance do not replace those instructions.
Can additional pages compensate for missing proof?
Not necessarily. Provide the requested information within the permitted format and limits. More material can obscure the answer, and an unrelated attachment does not establish a fact that the required evidence leaves unproven.
Does a high internal score guarantee eligibility or award?
No. Internal scoring is only a review exercise. The buyer applies its evaluation process, and separate administrative, technical and commercial requirements may still affect the outcome.