A tender is a formal request for competing supplier offers. The buyer publishes or distributes requirements, eligibility conditions, evaluation criteria, contract terms, deadlines and submission instructions, then evaluates compliant bids to select one or more suppliers.
A tender is not merely a sales lead with a deadline. Formal gates, attachments, amendments, price schedules, signatures and portal actions can determine whether the offer is evaluated at all. Teams that start writing from the notice or summary before assembling the complete package risk solving the wrong requirement.
Tender success begins with document control and honest qualification. A supplier should reconstruct the governing package, prove every mandatory gate, decide whether the economics and evidence support a bid, then build a response that an evaluator can verify quickly.
Lifecycle
The tender process starts before the response document
A typical process moves from buyer planning and market engagement to publication, clarification, submission, evaluation, award and contract. Depending on jurisdiction and procedure, there may be prequalification, dialogue, presentations, negotiation, standstill or a challenge period. Private buyers can use similar documents with more procedural discretion.
For suppliers, the operational lifecycle is discovery, package reconstruction, qualification, decision, response planning, production, review, submission and outcome learning. Each stage creates a controlled artifact. Skipping qualification or compliance control does not save time; it moves uncertainty into expensive writing and executive review.
| Stage | Core question | Controlled output |
|---|---|---|
| Discovery | Is this potentially relevant? | Source link and basic metadata |
| Qualification | Can and should we bid? | Gate evidence and decision record |
| Production | How will we earn each score? | Compliant response and price |
| Submission | Was the approved bid received? | Final package and receipt |
| Learning | What changes next time? | Outcome and improvement record |
Public procurement
Public tenders add procedural duties and authoritative channels
Public procurement is governed by the applicable jurisdiction, procedure and buyer documents. Equal treatment, transparency and formal remedies can limit informal sales interaction once the process begins. Deadlines, approved communication channels and published clarification answers must be treated as operational controls, not administration.
Do not infer the rule from another tender. Thresholds, exclusion grounds, evidence timing, electronic signatures and portal requirements vary. The buyer’s current documents and applicable law are authoritative. When a condition has legal or material commercial effect, obtain qualified advice rather than relying on a general glossary.
- Use the official notice or portal as the source of record.
- Download all lots, annexes, forms and amendments.
- Track clarification answers as part of the governing package.
- Separate formal eligibility from scored quality.
- Never describe a bid as submitted without a valid receipt.
What good looks like
Useful outcomes from tender
- The complete and current tender package is under version control.
- Eligibility, mandatory requirements and submission mechanics are resolved early.
- The bid decision reflects evidence, capacity, economics and strategic value.
- Every material claim and attachment has an accountable owner.
- The final submission is compliant, approved and supported by receipt evidence.
Operating model
How to run the work
- 01
Reconstruct the authoritative package
Collect the notice, instructions, specifications, annexes, draft contract, price files, forms, questions and amendments from the authorized source. Record versions and deadlines. Treat a notification email or opportunity listing as discovery, not as the complete requirement.
- 02
Test mandatory gates before scoring fit
Extract eligibility, references, certifications, legal declarations, financial requirements, signatures, language and submission rules. Mark each as confirmed, failed or unresolved with its source clause. A high strategic fit cannot compensate for a mandatory condition the supplier cannot prove.
- 03
Make and govern the bid decision
Assess solution fit, evidence strength, buyer access, competitive position, delivery capacity, commercial return and pursuit cost. Assign owners and conditions to unresolved items. Approve bid, conditional bid or no-bid explicitly rather than letting drafting activity become the decision.
- 04
Produce, verify and submit
Build a compliance matrix, response plan, evidence set, pricing model and review schedule. Answer in the buyer’s structure and terminology. Complete content, legal, commercial and release reviews, then submit early enough to resolve portal or signature issues and preserve the final receipt.
Evaluation
Questions that change the decision
- Do the authoritative documents establish a mandatory condition the supplier cannot meet?
- Is there sufficient differentiated evidence to earn the available score?
- Can delivery and commercial owners support the proposed scope, schedule and risk?
- Which ambiguities need formal clarification before price or solution can be approved?
- Does expected value justify the full cost of pursuit and future delivery?
Failure modes
Where teams lose control
Working from an incomplete package misses requirements hidden in annexes or amendments.
An unsupported eligibility assumption can cause immediate exclusion.
Generic narrative makes evaluators search for proof and loses points.
Late pricing or contract review can expose an unviable deal after substantial effort.
Portal credentials, file limits or signature rules can block an otherwise finished bid.
Measurement
Measure the finished job
Measure the completed workflow, including review effort and exceptions. Output volume on its own is not evidence of a better process.
- authoritative documents and amendments captured
- mandatory gates confirmed before bid approval
- requirements mapped to owner, evidence and response
- planned reviews completed on time
- valid submission receipts retained
- win rate and contribution by opportunity fit
Questions
Common questions
What is a tender?
A tender is a formal competitive request in which a buyer defines requirements and rules, suppliers submit bids and the buyer evaluates those offers to award a contract or appoint suppliers.
What is the difference between a tender and an RFP?
Tender often describes the complete competitive procurement, while RFP describes a document asking for proposals. In practice the terms overlap. The actual procedure, eligibility, evaluation, contract and submission instructions determine what suppliers must do.
What documents are part of a tender?
The package may include the notice, instructions, specifications, evaluation criteria, contract, forms, price schedules, declarations, annexes, clarification answers and amendments. Suppliers should verify the complete current package at the authoritative source.
How should a supplier decide whether to bid?
Confirm mandatory gates first, then assess strategic fit, evidence, delivery capacity, competitive position, economics, risk and pursuit cost. Unknown conditions should have owners and deadlines; they should not be silently counted as positive.
About the author
Malcolm Ferguson
Malcolm writes from the buyer side about procurement, sourcing, due diligence and the evidence suppliers need to pass a serious evaluation.
Zelius
Managed tender intelligence and bid execution for teams that want the commercial outcome.
Suppliers, founders and commercial teams pursuing public or private opportunities. Start with the workflow, constraints and evidence you already have.
See Zelius→