The short version: the last week of a tender is a coordination problem wearing a writing problem’s clothes. Compliance comes first because compliance is the only thing that can disqualify you before anyone reads your solution, and on most scorecards it carries thirty to forty five percent against price at fifteen to twenty. The technical team builds the answer on top of their normal work, so it arrives late and thinner than it should be. The project office writes the methodology. Then somebody checks the pack under time pressure, and that check is the step most often skipped. Everything that makes the week survivable is preparation done months earlier: a live compliance folder, a real solution library, pre-templated governance, and reference letters written to travel.
I have sat next to the person who assembles tender responses for a living. Not once, and not as a consultant passing through. For years, in a business that lived or died on whether the pack reached the tender box before it closed.
This is what that last week actually looks like, in the order it happens. It includes the parts nobody puts in a process document.
What happens first in the last week?
Compliance comes first, always. It is the only part of a bid that can disqualify you before anyone reads your solution. The coordinator reads the tender briefing in full, then calls in a technical lead to confirm the company can respond to it at all, and only then starts assembling documents.
That second step matters more than it sounds. A technical lead who reads the document early stops you spending five days on a bid you were never equipped to win.
Why is every tender’s compliance pack different?
Only a handful of items are identical across every tender: your CIPC registration, your tax pin, your CSD registration. Everything else changes, and the differences are the trap.
One tender proves past experience through reference letters. The next one ignores reference letters entirely and wants OEM certification instead. A third asks for neither and wants proof of financial strength, which in practice means a credit line with a distributor large enough to buy the materials before the client pays you.
That last one is where smaller companies fall out. Government departments do not pay a deposit. If the tender requires two million rand of materials, you need somewhere to buy two million rand of materials on credit, and the letter proving it has to be in the pack. Even a business supplying something as ordinary as engine oil to a plant needs an account with a supplier willing to carry it.
The companies that handle this well do not assemble compliance at tender time. They keep a live folder that fills up in the normal course of doing business, so the coordinator fetches rather than chases.
What does the technical team have to produce?
Two things, and neither is optional. The solution itself, and the inputs to the project plan.
How much freedom they have depends entirely on how the tender was written. Some documents state only the problem in a background or context section. Others specify the answer down to brand level, naming Huawei servers or HPE Aruba by name. Most sit somewhere between. They ask for a backup solution and say nothing about what should run behind it.
Whatever the tender gives them, the technical team has to work out how many of each thing, configured how, and write it into a design document. Then they hand the project office a work breakdown, and a negotiation starts: the project office pushing for tighter durations, the technical team pushing for looser ones. That argument is healthy and it takes time nobody has budgeted.
The thing to hold on to is that all of this happens on top of their normal work. They are still in the field doing installations and servicing paying clients. A live client always outranks a possible one, so the tender gets done last, at speed, and the quality shows it.
What does the project office add?
A methodology statement, and it is a bigger document than most people expect. Tenders routinely ask how you will manage the project and how you will manage the change it causes, and the answer runs to several pages.
It covers the governance structure from steering committee down to the delivery team, the reporting rhythm, whether stand-ups are daily and meetings weekly or fortnightly, and what goes up to the project committee and when. Where the project changes how people work, it carries a change management plan and a training plan alongside.
When I ran the project office at Ndende, we pre-templated all of it. Governance, methodology, change management, training. The coordinator selected the relevant sections and edited them down instead of writing them again. That was a late discovery. For years we wrote them out again for every client, until we worked out that making them slightly more generic and trimming to fit saved an enormous amount of time. That single change took days out of every bid.
Who checks the pack before it goes?
In theory the coordinator runs a checklist. In practice, by the time the pack is assembled everyone is sprinting at the deadline, and the final check is the step most likely to be skipped.
That is a bad place to cut corners, because every hour of the week is wasted if one returnable is missing. The checklist is not long: CVs if the tender asked for them, specifications if it asked for them, proof of address, OEM letters, credit confirmation letters from distributors, the reference letters. Anything absent gets chased and added. Then the pack becomes a PDF and gets emailed, or it gets printed, packed and physically delivered to a tender box.
What goes wrong most often?
Starting late. Everything else on this list is a symptom of that one thing.
When work begins too late, the week becomes a flurry, and at that pace good enough beats nothing. Teams produce good enough work and submit it, and good enough loses to somebody who started on time.
The fix is libraries. Real, reusable solution components you select and adjust rather than build from scratch. The project office side of this is easy to do and we did it. The technical side is harder, and the reason is cultural. Technicians fixate on what is unique about each problem and underweight what is common across all of them, so their libraries stay thin and they rebuild from a blank page every time.
The trick that works, and should not have to
Our business development team communicated a false deadline to the technical teams. We took the real submission date and cut a few days off it, then treated the earlier date as if it were real.
It worked. Work arrived earlier, and there were fewer fights about it.
It is also not a strategy. People work out eventually that every date you give them is three days early, and once they do, the padding is gone and you have spent your credibility to buy it. The real answer is management discipline that enforces finishing before the deadline, which is harder than lying about the date and is the thing actually worth building.
What happens when the tender box is four hours away?
You improvise, and the improvisation is usually a person rather than a service. Head offices sit in one place and tenders come from everywhere, and some of them still require a physical pack in a physical box.
On the Mpumalanga Department of Health bid, an executive was meant to drive the pack down and something came up on the day. Couriers were too slow: a courier wants at least twenty four hours, and longer across provinces. So the team printed and packed the bid in Johannesburg, drove to the City Bug shuttle terminal, negotiated with the driver, and handed the pack over. The shuttle left at ten in the morning and was in Mpumalanga by two in the afternoon. One of our technicians met it, collected the pack, and walked it into the tender office at the Riverside complex.
We won that tender. It became the ICT modernisation programme across the province’s district hospitals, and it has since been delivered.
The detail worth noticing is why we could not email the files for the team on the ground to print. We had technicians in Mpumalanga, and no bid office. Printing, ordering and packaging a tender submission is its own skill, and asking a technician to do it under time pressure is how returnables go missing. The pack had to travel finished.
Why do reference letters cause so much trouble?
Because they expire, and because they are usually written too narrowly to reuse. A tender asks for three references dated within the last three months, and you cannot keep going back to the same client every quarter asking them to write you another one.
Even a fresh letter can be useless if the scope described in it is narrow enough to exclude the work you are now bidding for.
What we learned to do was change what the letter says. We send clients a template that keeps the focus off the detail of the work and on four things that travel to any tender:
- Industry, stated broadly. Public sector, mining, financial services.
- Capacity, meaning what you were. Main service provider, subcontractor, implementation partner.
- Project value, as a number. This is the single most reusable line in any reference letter, because it proves you have handled work of that size regardless of what the work was.
- Duration, with a start and an end.
Then one closing sentence that does the real work: a recommendation for similar services. Not for the exact scope described above, which narrows the letter to one tender. Similar services, which lets it travel.
Compare two real examples from our own file. One letter describes a firewall deployment in a single paragraph, then lists industry, capacity and project value, and recommends the company for similar services. Another describes a hyperconverged infrastructure deployment in loving technical detail. It names the storage platform and the backup software, and it carries no contract value at all. The first letter has been useful in a dozen bids. The second is useful in the one bid it was written for.
We also avoid dates in the body where we can, so the letter does not carry its own expiry. It is an imperfect fix. Some tenders want two years of history, some want the last twelve months, some insist on three to six months, and no letter satisfies all of them. A letter written around numbers that never change is still useful to far more bids than one written around a single scope of work.
One more thing, and it is the most commonly missed: put a named contact, a telephone number and an email address on the letter. Evaluators do call, and a reference nobody can verify carries very little weight.
What does a price do while you are waiting?
It moves, and you carry the risk. A distributor gives you pricing and holds it for thirty days. Government comes back in sixty, approves at the price you quoted, and by then the price you actually pay has changed.
We priced with a buffer of seven to fifteen percent. The band came from the historical movement in materials pricing rather than from a feeling. Outside genuine shocks, input costs move less sharply and less quickly than people assume, and a buffer in that range absorbs the normal case while leaving you competitive.
When the move exceeds the buffer you have two options and neither is good. A variation order, which government dislikes because open contracts create audit exposure, or a return to market, which is the painful one. Fixed price for the duration is what they prefer and usually what you get, which is exactly why the buffer has to be right at submission.
What actually decides who wins?
Price alone decides almost nothing except on straight supply and deliver tenders. Three things decide the rest, and price is the smallest of them.
On the scorecards we worked to, compliance carried thirty to forty five percent. Price carried fifteen to twenty percent. Everything in the middle was methodology, project management and the strength of the CVs.
Read that again, because it changes how you should spend the week. Compliance is worth more than double what price is worth, and compliance is the part that is entirely within your control and costs you nothing but organisation.
Beyond the scorecard sit credibility and relationship, which are not scored and are certainly present. And beneath all of it sits the rule that governs everything above: do nothing that eliminates you on a technicality, because a disqualified bid scores zero on every other line.
What it all comes down to
The last week of a tender is a coordination problem wearing a writing problem’s clothes. The documents are not hard. Getting five sets of busy people to produce their part, in the right order, before a date that cannot move, is hard.
Everything that makes it easier is preparation done earlier: a live compliance folder, a real solution library, pre-templated governance, reference letters written to travel, and a price with the right buffer already in it.
We have since built Landani around exactly that observation.
Questions people ask about tender submissions
How long before the closing date should you start a tender response?
Two weeks for a straightforward bid, and longer if you need documents from third parties. The binding constraint is rarely your own writing. It is reference letters, OEM authorisation letters and credit confirmations, all of which depend on somebody else’s diary.
What gets a tender disqualified in South Africa?
Missing or expired returnables, almost always. An out of date tax pin, a CSD registration that has lapsed, a reference letter older than the tender allows, an unsigned SBD form, or a missing OEM authorisation letter. A disqualified bid scores zero on every other line, however good the solution is.
What is a manufacturer’s authorisation form and when do you need one?
It is a letter from the OEM confirming you are an authorised partner permitted to bid their products for that specific tender. Tenders that name a brand almost always require one. They are issued per tender, with the tender number printed on them, so an old one is no use to you.
How much weight does price carry in a public tender?
Usually fifteen to twenty percent of the scorecard. Compliance typically carries thirty to forty five percent, and the band in between is methodology, project management approach and the strength of your CVs. Most companies spend their effort on the line worth the least.
Can you still submit a tender if the tender box is in another province?
Yes, and you will improvise. Couriers need at least twenty four hours and longer across provinces, so companies use intercity shuttle services, staff who happen to be travelling, or anyone local willing to walk a package into a building. Plan the delivery the day you decide to bid rather than the day before it closes.
How often do reference letters need to be renewed?
It depends on the tender, and that is the problem. Some accept two years of history, some want the last twelve months, and some insist on nothing older than three to six months. Ask clients to write letters that lean on contract value, capacity and duration, and to recommend you for similar services rather than the exact scope you delivered.