A tender pack is both a request for an offer and a rulebook for how that offer will be evaluated. Reading it sequentially from page one is useful, but bid/no-bid decisions become faster when the document is also analysed by function: qualification, scope, evidence, price, risk and submission mechanics.
Start with the procurement summary
Record the issuing institution, tender number, description, closing date and time, compulsory briefing requirements, submission method, validity period and contact procedure for clarification. These facts become the top of the bid-control sheet.
A compulsory event or a missed closing rule can make every later hour of bid preparation irrelevant, so identify these first.
Find the non-negotiable gates
Search the document for language such as mandatory, compulsory, must, shall, minimum, disqualified, non-responsive and required. Then read the surrounding clause rather than extracting isolated words.
Convert each gate into a yes/no test. If the bidder cannot satisfy a genuine mandatory condition by the permitted time, escalate the issue before further bid effort is spent.
Read the evaluation method as a separate document
Determine whether the procurement uses separate stages such as administrative compliance, technical or functionality scoring, price and preference evaluation, due diligence, presentations, samples or demonstrations. The order matters because later strengths cannot normally rescue an earlier failed gate.
Where functionality is scored, build an internal scoring model and identify exactly what evidence earns each score. Our guide on mandatory requirements, functionality and preference points explains the distinction.
Convert the scope into deliverable lines
Break the scope into products, services, quantities, sites, milestones, outputs and acceptance evidence. Do not rely only on the tender's headings. A single paragraph may contain several obligations.
For each deliverable, identify who will perform it, what input is required, what it costs, what can delay it and how completion will be accepted.
Read annexures, drawings and pricing schedules together
The narrative specification may say one thing while the bill of quantities reveals the real scale. Drawings may introduce interfaces not obvious from the main document. Pricing schedules may require packaging, installation, training or support that a supplier could miss if it reads only the technical section.
Reconcile these sources before approaching suppliers for quotations.
Identify what the buyer will verify
List every claim that needs evidence: years of experience, completed projects, staff qualifications, professional registrations, manufacturer appointments, financial capacity, equipment, facilities, methodology, delivery capability and references.
Then locate the prescribed form of evidence. A generic company profile is rarely a substitute for a reference letter, CV, certificate, purchase order or signed schedule where the tender specifies one.
Read the contract conditions before pricing
Commercial risk often sits outside the pricing table. Review payment terms, retention, performance security, penalties, insurance, warranties, defects obligations, confidentiality, intellectual property, data requirements, termination, escalation and variation rules.
The bid price should reflect the actual obligation. A contract that requires the supplier to finance six months of delivery has a different economic profile from one with mobilisation and milestone payments.
Create a clarification register
Do not resolve ambiguity by silently choosing the interpretation that produces the easiest price. Record unclear quantities, inconsistent specifications, missing drawings, uncertain site conditions and contradictory dates. Submit questions through the procurement channel and before the clarification deadline where one is stated.
Store all issued clarifications and addenda with the tender pack and update the bid-control register immediately.
Perform a bid/no-bid assessment
Before committing significant resources, assess:
- Can every mandatory gate be met?
- Is the required experience genuinely available and provable?
- Can the technical scope be delivered within the stated period?
- Are suppliers, specialists and manufacturers available?
- Can the company finance delivery on the proposed payment terms?
- Is the likely functionality score competitive?
- Does the expected margin justify the bid effort and risk?
- Are there contractual obligations the business should not accept?
Read for the evaluator, not only for the bidder
The final pass should ask how an evaluator will locate the answer to each criterion. A well-structured response mirrors the tender's logic, uses consistent terminology and makes evidence easy to verify.
African Resolve Holdings treats the tender pack as a requirements specification: obligations are extracted, owners are assigned, evidence is mapped and commercial assumptions are made explicit before submission.