Lodging a South African tender bid and proving it arrived
How a South African business lodges a bid pack by e-mail from Achekam, what delivery records show, and why a colleague checks the acknowledgement.
By Achekam · · 4 min read · For Running a business businesses in South Africa
A tender can be lost before anyone reads it. The bid pack goes to the wrong address, arrives a minute after the closing time, is missing the returnable schedule that was saved in someone's downloads folder, or simply never lands, and nobody notices until the award is published. Weeks of pricing and writing are gone.
Lodgement deserves the same discipline as the pricing. This article explains how a South African business lodges a bid pack by e-mail from Achekam's tender tools, what evidence Achekam keeps, and the checks that remain with your own people.
Sending only to the address the tender prescribes
Every tender tells bidders how to submit: by hand into a tender box, through an electronic portal, or by e-mail to a named address. Only the method the tender prescribes counts.
Where a tender prescribes e-mail, Achekam can e-mail the bid pack from the tender's Submission Pack to the address the tender gives. Read that address from the tender document itself, not from an old bid to the same buyer or from a colleague's memory: departments change addresses between tenders, and a pack sent to last year's mailbox has not been lodged.
If the tender prescribes hand delivery or a portal, Achekam's e-mail is not a substitute. Use it to assemble and check the pack, then lodge it the way the buyer asked.
Many public-sector bids begin on the National Treasury's eTenders portal, where advertised, awarded and cancelled tenders from organs of state in every sphere of government are published. Achekam's tender scout reads live adverts from the eTenders public data feed and from any public RSS or Atom feed you add, and staff can also enter a tender by hand with its documents.
A person confirms before the pack goes
Achekam sends the bid pack only once a person has confirmed it. Nothing leaves on a timer or a rule.
Treat that confirmation as a sign-off, not a click. Before confirming, the person should check:
- the recipient address against the tender document;
- the tender number and description in the subject line;
- that every returnable document and schedule is attached and signed where required;
- the file sizes and formats against any limits the buyer sets;
- the time left before closing, with enough margin for a slow mailbox.
The bid itself should already have passed your internal approval. Achekam requires a reason for every bid or no-bid decision, and a decision to bid on a tender of R5 million or more must name an active partner as approver. Be aware that the R5 million threshold is fixed in the code: the Tender Settings show a default of R1,000,000 that nothing reads, and several other Tender Settings tabs save values that nothing in Achekam uses. Do not rely on a setting you have changed there.
Delivery and download records
Once the pack is sent, Achekam records its delivery, and records downloads of the pack. That gives you evidence of when the e-mail left and when the files were opened, which is far better than "I'm sure I sent it".
Delivery evidence is not acceptance. A record that the e-mail was delivered shows your side of the transaction. It does not show that the buyer's tender mailbox accepted it, that it was not quarantined as too large, or that it was logged as received before the closing time.
A colleague verifies lodgement against the buyer's acknowledgement
For that reason, Achekam leaves the final check to a person: a colleague verifies lodgement against the buyer's acknowledgement. The acknowledgement may be an automatic reply, a receipt number from the buyer's system, or a confirmation e-mail from the procurement office.
Make the colleague someone who did not send the pack. They should confirm:
- the acknowledgement refers to this tender number;
- its time is before the closing time;
- it lists, or at least does not contradict, the documents you sent.
If no acknowledgement arrives, phone the contact person named in the tender while there is still time to resend. A missing acknowledgement discovered after closing cannot be fixed.
Tracking every bid's stage and overdue milestones
The Delivery Tracker lists every tender being prepared, with its owner, stage and any overdue milestones, and bid hours come from timesheets. Use it at a short weekly meeting: which bids close this week, who owns each one, and which milestones have slipped.
For lodgement in particular, add a milestone ahead of the closing date for "pack complete and checked". A bid that reaches its last day with this milestone open is a bid at risk, and the tracker will show it as overdue.
Sections still marked ready for review
If you use the Response Studio, AI drafts a bid section only from your approved capabilities, verified references and the buyer's documents, and saves nothing if the draft claims something those records do not support. A saved draft is marked "ready for review".
That label matters at lodgement time. No rule was found that blocks submitting a section that has not been reviewed. Before the pack is confirmed, check that every drafted section has been read and approved by a person, and remove the "ready for review" sections that nobody signed off. A buyer evaluates what you sent, not what you meant to check.
How the price side of a bid is built is covered in bid pricing and the bill of quantities, and how tenders are found and matched in the first place is in the tender scout and its match rules. For your next bid, name the person who will confirm the pack and the colleague who will check the acknowledgement on the day you decide to bid, not on closing day.
General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.
