The challenge: a tender closing in under two days
A client in the security services sector came to us against a hard deadline: a tender closing in under two days required a valid, upgraded CIDB grading and a full compliance pack, and their existing grading no longer covered the contract value they were bidding for. Normally, upgrading a CIDB grading and assembling a complete tender-ready compliance pack is measured in weeks, not days — this is the story of how we compressed it.
Triage: one checklist for every document
The first afternoon was pure triage. We built a single checklist covering every document the tender actually required — CIDB grading certificate, tax clearance/tax compliance status PIN, B-BBEE certificate, CSD registration, proof of good standing with COIDA, and the technical/financial capability evidence CIDB needs for a grading upgrade — and marked each one as 'already valid,' 'needs renewal,' or 'missing entirely.' That single list was what let us parallelise the next 36 hours instead of working through requirements one at a time.
The CIDB upgrade: evidence is the bottleneck
For the CIDB upgrade specifically, the bottleneck is almost always the supporting evidence, not the application form itself — proof of similar completed contracts, financial statements matching the grading band being applied for, and a registered professional's sign-off where the grading requires one. We worked directly with the client's accountant and a registered CIDB-recognised professional in parallel with lodging the application, rather than waiting for each document before starting the next step, since CIDB's own processing queue was the one part of the timeline we could not compress.
CSD, SARS and tax compliance checks
In parallel, we handled the pieces that were genuinely ours to move quickly: confirming CSD registration was current and all supplier information matched exactly across CSD, SARS, and the tender documents (a mismatch here is one of the most common reasons compliant bids get disqualified on a technicality), and re-confirming tax compliance status through SARS eFiling rather than assuming an old tax clearance certificate would still be accepted.
Automating the final checks with Make.com
Where this became genuinely automated rather than just fast manual work: we set up a Make.com scenario that cross-checked every document against its expiry date and against the specific tender's stated requirements, flagging any mismatch immediately rather than relying on a final manual review the night before submission — the kind of check that's easy to skip under time pressure and expensive to get wrong.
The outcome
The tender was submitted six hours before the deadline, with every document verified and matching. The upgraded CIDB grading also stayed valid for the client's next three tenders that year, which is the part of a compliance sprint that's easy to undervalue in the moment: the work doesn't just solve today's deadline, it removes the same bottleneck from reappearing on the next one.
What makes a compliance sprint work
Compliance sprints like this one work because the coordination is centralised — one checklist, one point of contact chasing every party in parallel — rather than because any single step was done unusually fast. If you're facing a tender deadline against an expired or insufficient grading, the honest first question is whether there's still enough runway to do this properly; if there is, this is exactly the kind of sprint that makes the difference.