The system behind the record

Yes. Transnet and Lesedi Nuclear Services use Tractivity in South Africa. The platform is cloud-based and browser-based, there is no local software to install for administrators or for the public, and onboarding and support are delivered remotely by the UK team across the South African working day.

In a Tractivity deployment you are the responsible party and Tractivity is the operator. Section 20 of POPIA requires an operator to process only with your knowledge or authorisation and to treat the information as confidential, and section 21 requires a written contract covering the section 19 security measures and immediate breach notification to you. The platform was built to UK GDPR, which shares most of POPIA’s architecture, and the field-level controls POPIA sections 26 to 33 require for special personal information operate at project, module and record level. Full detail is on our POPIA page.

Yes. The register of interested and affected parties, the notice programme with proof of service per recipient, dated site notice photographs, newspaper tear-sheets, attendance registers, minutes, written comments and the comments and responses report are all held against the project and the parties they relate to, and export to Word, Excel and PDF. The same structures serve water use licence participation under Regulations 17 to 19, Social and Labour Plan consultation under the MPRDA Regulations, and SPLUMA land development applications.

Municipalities and metros running IDP, budget and ward committee participation. Water boards, catchment management agencies and water user associations. Mining and energy operators with SLP, licence and community obligations. State-owned companies with corridor, servitude and access consultation. And the environmental and social consultancies and registered EAPs who run public participation as a service line for all of them.

Tractivity runs on Microsoft Azure, with UK data residency by default and European, United States and other regions available. There is no general data localisation requirement in South African law, but the National Policy on Data and Cloud pushes residency in policy terms and state-owned enterprises increasingly write in-country hosting into ICT tenders. If in-country hosting is a requirement of your tender, raise it at the outset so the available options for your deployment can be confirmed in writing.

Yes, and it is worth being straight about what that involves. We hold a UK G-Cloud listing and Government Commercial Agency supplier status, which signals that we have been through public sector assurance before, plus ISO 27001:2022 and Cyber Essentials Plus. What we work through with you is Central Supplier Database registration, tax clearance and B-BBEE status. A foreign vendor with no South African entity scores nothing on B-BBEE, and where that weighting is material a South African partner or reseller arrangement is usually the answer.

Yes. Notices, background information documents, comment forms and executive summaries are held in multiple language versions against one record, and the version each party received is tracked. That matters for section 18(2) of the Municipal Systems Act, which requires communication in the official languages the council determines, and for MPRDA Regulation 46A, which asks for two languages within 30 days.

Yes. Stakeholder mapping by location uses Google Maps with a Land Parcels module, so a corridor, a mining right area, a catchment or a ward can be read geographically. Filter by section, ward, municipality or party type, and see which stretch or which area is generating the grievances.

Four to six weeks on average from contract signed to launch, covering planning calls, system set-up, configuration, data import, checks and end-user training. That includes a minimum of 20 hours of onboarding and two 1.5-hour online training sessions with a dedicated Client Success Manager. It is an average rather than a guarantee, and it depends as much on how quickly your data is supplied as on us.