Retain evidence for the contractor’s track record
The cidb grading guidance identifies award, completion and payment documents among the supporting records it considers. Use that guidance to plan your archive, then test retrieving a completed project’s evidence. The system’s document store does not itself establish a grading or verify a contractor’s registration.
Separate subcontract progress from payment status
On a sample Johannesburg refurbishment, measure a subcontract package, record a defect and prepare a progress valuation. Check that the outstanding defect, certified amount and recorded payment remain distinct. The contract determines how those records affect payment; a dashboard percentage should not make that decision.
What to bring to the demo
Bring a subcontract award, a progress certificate and a completion record. Retrieve them as a single project trail, then test whether the subcontractor can see its own work without seeing another package’s commercial information.
Official local reference
cidbUse the authority’s current guidance and your actual project contract to confirm applicable requirements.
Start with one real project
Bring a priced bill of quantities, a current drawing, a delivery note and a progress report. Ask the contractor, site supervisor and owner to follow the same work from estimate to inspection and recorded payment. Compare the result with the documents your team uses today.
Test each person’s permissions: site staff can report work without approving their own reports, and owners see agreed progress without receiving access to confidential rates. Try a direct link as well as the menu.
Confirm the fit before choosing
Confirm project currency, taxes, contract forms, product languages, exports and offline workflows during the demo. These guides explain how to evaluate software; they do not certify compliance or promise every local integration. BuildPanda records payment information; it does not hold or transfer funds.