Polokwane, Limpopo
abisaiinnovations.co.za
+27 72 952 2927
abisaiinnovations.co.za
+27 72 952 2927
We built a system that took RDP contractors from manual to digital. Here is what that means.
RDP housing is a government programme that builds subsidised homes for qualifying South African citizens. The government provides the funding. Private contractors are appointed to construct the homes. In Limpopo, these projects are administered by COGHSTA — the Department of Cooperative Governance, Human Settlements and Traditional Affairs — and range from a few dozen units to several hundred, with contract values typically between R8 million and R54 million.
The way it works: the contractor builds the homes in stages. A provincial inspector from COGHSTA reviews each completed stage before work proceeds to the next one. Once a milestone is approved, the contractor submits a claim pack to trigger payment. That pack must be correct, complete, and submitted in the correct sequence. If a document is missing, a signature is absent, or a submission falls outside the required format, payment is delayed — sometimes by weeks.
The project has layers. A main contractor leads the build. Subcontractor teams — bricklayers, plumbers, electricians, roofers — work across multiple units simultaneously. Materials are ordered and delivered across months. Labour shifts daily. COGHSTA inspects on its own schedule. And throughout all of this, the contractor is expected to maintain accurate records, manage cashflow, comply with health and safety requirements, and submit reports on demand.
For a contractor managing 80 units across a single site, that is hundreds of moving parts — most of them coordinated through handwritten ledgers, WhatsApp voice notes, printed spreadsheets, and filing cabinets.
Every RDP contractor we spoke to was dealing with the same five problems. They showed up in different combinations, but they were always the same five.
Submissions. Preparing a milestone submission for COGHSTA was a full-time job on its own. Documents from multiple sources had to be collated, formatted, signed, and packaged correctly. Any gap in the pack meant the submission was rejected and the timeline reset. Contractors were spending days — sometimes weeks — compiling paperwork that should take hours.
Payments. Because payment is tied to milestone approval, any delay in submission is a direct delay in cash. Contractors were carrying the cost of completed work for 30, 60, sometimes 90 days while waiting for approvals to clear. Meanwhile, subcontractors were waiting to be paid. Some were walking off site.
Procurement. Materials were ordered verbally or over WhatsApp. There was no system connecting what was ordered to what was delivered, what was used, and what remained. Contractors were losing money to ordering errors, supplier disputes, and materials that disappeared on site — with no paper trail to trace what happened.
Site visibility. On a large site, the contractor can’t be everywhere. Foremen gave verbal updates by phone. There was no record of daily progress, no way to know in real time which units were ahead or behind, and no documented evidence of what was done and when — until COGHSTA asked for it.
Risk. When a subcontractor’s scope changed, it was settled verbally. When a client requested an addition, it was agreed on site. When a dispute arose later about what was agreed, there was nothing in writing. The contractor absorbed the cost.
BuildTrack is a purpose-built system for RDP project management. It replaced each of those five manual processes with a digital one.
Submissions are now assembled inside the system. The contractor uploads inspection reports, photos, and compliance documents as work is completed — not in a last-minute scramble before a deadline. When a milestone is ready, the claim pack is generated automatically from everything already captured. What used to take days now takes minutes, and the pack leaves with nothing missing.
Payments are tracked against milestones. The system shows the current approval status of every submission and flags outstanding documents before a pack is sent. Contractors know exactly where they stand in the payment queue and what is needed to clear the next milestone.
Procurement is connected to the job. Every material order is captured against a project code, a quantity, and a cost. The system tracks what was ordered, what was delivered, and what was paid for. When a supplier invoice arrives, it is matched against the original purchase order. Nothing gets approved without a record.
Site visibility is handled through daily digital check-ins. Foremen submit progress updates directly from site. The contractor sees a live status of every unit — stage completed, what remains outstanding, which teams are where. When COGHSTA asks for a progress report, the data is already there.
Risk is managed through the document layer. Every scope change is captured as a formal variation before work proceeds. Every subcontractor engagement has a written record. Every site instruction is logged with a date and a signature. If a dispute arises, the contractor has the evidence.
The first question we always get is: why not use an existing project management tool?
The short answer is that generic tools solve generic problems. An RDP project under COGHSTA has a specific document structure, a specific submission sequence, and specific compliance requirements that a generic tool does not know about and cannot accommodate.
A standard project management platform will let you create tasks and track deadlines. It will not generate a COGHSTA-compliant claim pack. It will not connect procurement to a job code. It will not flag a missing health and safety certificate before a submission is rejected. It does not know what a G4 certificate is or where it belongs in a milestone pack.
Generic SaaS tools are built for the broadest possible market. RDP contractors in Limpopo are not the broadest possible market. They are a specific group doing specific work under specific government requirements. The system that serves them has to be built around that — not around a software company’s total addressable market.
That is what BuildTrack is. Not a template dropped in from somewhere else. A system built around how this work actually runs.