Platform in Practice

Real Scenarios.
Real Municipal Outcomes.

Six scenarios showing how MCMP's compliance pathways work in practice — from the first application through inspection, certificate issuance, and annual renewal. Each anchored to the specific South African legislation it enforces.

Business Licence (BL) OCC Certificate Food Health (CoA) Spaza Shop Liquor Licence Renewal Fast-Track SCM Pre-Qualification
BL

Business Licensing — Non-Public Facing, No Direct Transact, Office-Based Operations

Municipal Business Operating Licence · 4-Tier Graduated Framework · OHSA-Aligned

Scenario

A 45-person consulting firm applies for a business licence in a local municipality. Their premises is a registered office — staff only, no clients visiting, no public sales floor. A separate branch with 4 staff works from a home office under the same business registration.

The Challenge

  • Manual process had no mechanism to distinguish office-only premises from public-facing operations — the wrong certificate type was routinely issued
  • No graduated compliance depth — a 45-person firm was processed identically to a sole trader, leaving the municipality legally exposed under OHSA
  • Paper checklists did not include SANS 10400-S sanitary facility ratios — inspectors had no basis for verification
  • Home office branch had never been assessed for zoning compliance under SPLUMA
  • Licence processing took 60+ days with no SLA tracking

The MCMP Response

  • Client-visit flag at intake — "Do clients or members of the public visit this premises?" — routes correctly to BL (office) vs OCC (public-facing). Both branches processed under the same application
  • Tier auto-assignment — 45-staff branch classified as BL Tier 3 (Medium Office 21–50); 4-staff branch classified as BL Tier 1 (Micro)
  • OHSA modules triggered automatically — H&S Representative appointment, written OHS policy, fire evacuation plan, EMS risk assessment — all required at 45 staff per OHSA Section 17
  • Sanitary facility calculator — SANS 10400-S ratios auto-calculated from declared male/female split; inspector verifies on-site at Tier 3
  • Tier 1 (home office) — documentation-only, no inspection required, SPLUMA zoning check confirms home occupation compliance
  • Both licences issued within 21 days; renewal tracked annually per band
4 Tiers
Micro · Small · Medium · Corporate — each with OHSA-calibrated compliance depth
21 Days
Processing time vs 60+ days on paper — correct certificate type, first time
OHSA s.17
H&S Representative requirement auto-triggered at 21+ staff — OHSA compliance confirmed before licence issues
Legal Authority Municipal Systems Act 32 of 2000 · Businesses Act 71 of 1991 (as amended) · Occupational Health and Safety Act 85 of 1993 (Sections 7, 17, 19) · SANS 10400-S (Sanitation ratios) · SPLUMA 16 of 2013 (Zoning — home occupation)
OCC

Operational Compliance Certificate — Public-Facing Premises at Scale

Certificate of Operational Compliance · SPLUMA Land Use Test · Multi-Branch Management

Scenario

A hardware retail chain with 12 branches across a metropolitan municipality applies for OCC certificates. Premises vary from small stores to a large warehouse-attached flagship. Each branch has a different inspection profile — fire loading, access, floor area, public throughput.

The Challenge

  • Manual process produced inconsistent inspection depth across branches — the same business type was assessed differently by different inspectors
  • No central certificate registry — the municipality could not confirm which branches held valid OCCs and which had expired
  • Warehouse-attached flagship had never been assessed for fire loading, rack storage compliance, or structural floor rating
  • Zoning changes on two branches had not triggered re-assessment — a SPLUMA violation the municipality was unaware of
  • No QR verification on physical certificates — certificates could not be authenticated

The MCMP Response

  • Public engagement test applied at intake — "Do members of the public physically enter to purchase?" — all 12 retail branches confirmed as OCC. Warehouse-attached flagship routed to OCC warehouse variant with specialist module set
  • Parallel departmental review — zoning (SPLUMA), fire safety (NBR Act), health & hygiene, and building/structural departments review simultaneously per branch — not sequentially
  • Warehouse specialist modules — fire load assessment (rack storage), structural floor rating, forklift operations zone compliance, environmental waste management — applied automatically to flagship
  • SPLUMA zoning check — flags two branches with land use changes for re-assessment before certificate issuance
  • QR-coded digital certificates — every OCC carries a unique QR code verifiable at the MCMP portal, confirming authenticity and current validity status in real time
  • All 12 OCCs issued from a single application session; renewal tracked centrally with 60/30-day automated notifications
12 Branches
Managed in a single application — consistent inspection depth across all premises
QR Verified
Every certificate authenticated in real time — no paper forgery risk
SPLUMA
Zoning violations identified before certificate issuance — municipality legally protected
Legal Authority Municipal Systems Act 32 of 2000 · SPLUMA 16 of 2013 (Sections 42 — land use scheme enforcement) · National Building Regulations and Building Standards Act 103 of 1977 · Occupational Health and Safety Act 85 of 1993 · Municipal Business Compliance Bylaws
CoA

Certificate of Acceptability — Food Health, Auto-Resolved by Business Type

Regulation R638 · 10 CoA Sub-Types · Dynamic Compliance Engine Auto-Resolution

Scenario

A food court development opens with eight operators: a restaurant, a bakery, a butchery, a catering company, a food truck, a cold storage facility, a hotel kitchen, and a market hawker stall. Each requires a different Certificate of Acceptability under Regulation R638. The municipality's environmental health division must inspect and certify all eight — each with different compliance requirements.

The Challenge

  • Applicants had no way to know which CoA sub-type applied to their business — they were asked to select from a list they didn't understand
  • Paper checklists were generic — inspectors applied the same R638 checklist regardless of business type, missing cold chain requirements for the butchery and HACCP obligations for the food manufacturer
  • The hotel kitchen required both a CoA (food service) and a Health Certificate (accommodation establishment) — the paper process had no mechanism to issue dual certificates
  • The food truck's CoA required a vehicle registration section — paper certificates had no structured vehicle listing
  • No expiry tracking — three operators had been trading on expired CoAs for months

The MCMP Response

  • DCE auto-resolves CoA sub-type — applicant selects their business type in plain language. The system maps to the correct certificate: restaurant → coa_restaurant, butchery → coa_butchery (with cold chain ≤4°C chilled / ≤−12°C frozen requirements), bakery → coa_bakery, food truck → coa_hawker (with vehicle registration section), catering → coa_catering (food handler training required)
  • Cold storage — auto-routed to coa_cold_storage: HACCP plan required, temperature records per zone (12-month retention), stock movement register
  • Hotel kitchen — sells_food = true AND accommodation business type triggers coa_accommodation automatically, noting that a separate Health Certificate (NHA R1229) is also required
  • Business-type-specific inspection checklists — each inspector arrives with R638 requirements calibrated to the specific sub-type, not a generic list
  • All certificates digitally issued with expiry dates tracked and renewal notifications automated at 60 and 30 days
10 Sub-Types
Auto-resolved by DCE — applicant never selects a sub-type they don't understand
R638
Every certificate issued with the correct Regulation R638 clauses for the specific business type
Zero Expired
Automated renewal tracking — no operator trades on an expired certificate without the municipality knowing
Legal Authority Regulation R638 of 22 June 2018 (GN No. 41730) · Foodstuffs, Cosmetics and Disinfectants Act 54 of 1972 · National Health Act 61 of 2003 (Notice R1229 — Health Certificate) · SANS 10049 (Food manufacturing prerequisites)
SPZ

Spaza Shop Registration & Periodic Inspection — From Invisible to Governed

Risk-Based Classification · Scheduled Periodic Inspection · SEDFA-Linked Registration

Scenario

A metropolitan municipality estimates 3,000+ spaza shops operating across its township, peri-urban, and suburban areas. A significant proportion are owned and operated by foreign nationals — some undocumented. The majority trade without valid registrations or health certificates. Following the 2024/2025 food contamination crisis, the municipality must establish systematic compliance governance.

The Challenge

  • No reliable record of how many shops were operating, where they were located, or who owned them — the municipality was managing a sector it could not see
  • Reactive inspection only — health inspectors responded to complaints and crises, not a schedule. Inspections triggered by a death are not compliance management
  • Undocumented operators were invisible to the registration system — and therefore invisible to enforcement
  • No mechanism to flag shops selling high-risk products (raw meat, dairy, cooked food) for more frequent inspection than shops selling dry goods
  • Enforcement actions were legally weak — no digital audit trail, no formal notice system, no court-ready records

The MCMP Response

  • Digital registration linked to SEDFA framework — ownership validation, ID/permit verification at submission. Undocumented operators cannot complete registration; the system creates a visible compliance boundary
  • Risk-based classification — shops classified by product type, storage conditions, and foot traffic. High-risk (raw meat, dairy, cooked food) assigned monthly inspection cycles; lower-risk assigned quarterly
  • Scheduled periodic inspection — inspectors receive GPS-routed daily assignments. Each inspection uses a digital checklist specific to spaza/tuck shop compliance under the National Health Act. Photos captured as evidence on-site
  • Real-time compliance status — the municipality knows at any moment how many shops are registered, compliant, overdue for inspection, and under active enforcement
  • Structured enforcement — failed inspections trigger formal notices under the Municipal Systems Act, with defined response deadlines, re-inspection scheduling, and — where required — closure proceedings backed by a full digital audit trail
3,000+
Shops registered and visible — from invisible to fully governed in a single onboarding cycle
Periodic
Inspection by schedule — not by crisis. Prevention, not response
MSA s.102
Enforcement actions court-ready — digital audit trail, formal notices, legally defensible records
Legal Authority National Health Act 61 of 2003 · Municipal Systems Act 32 of 2000 (Section 102 — enforcement powers) · Regulation R638/2018 (food premises) · Consumer Protection Act 68 of 2008 · Municipal Environmental Health Bylaws
LIC

Liquor Licensing — Provincial Track, Digitised End-to-End

Liquor Licence Application Docs · Provincial Submission Package · Inspection & Certificate Registry

Scenario

A tavern owner in a local municipality applies for a liquor licence. The application must follow the provincial track — application documentation, police clearance, zoning confirmation, public notice compliance, and an on-site inspection — before a licence can be recommended to the provincial liquor board. The municipality is the first point of compliance assessment.

The Challenge

  • Provincial application documentation was collected manually — incomplete sets were only discovered late in the process, causing significant delays and re-submissions
  • The municipal compliance assessment had no structured workflow — different officials applied different standards, and there was no audit trail of who had approved what
  • Inspection reports were handwritten and stored in physical files — they could not be retrieved, verified, or submitted electronically to the provincial board
  • Public notice compliance was self-declared by the applicant — the municipality had no mechanism to verify the 21-day notice period had been observed
  • Licence renewals were not tracked — taverns operated on expired licences for extended periods without the municipality's knowledge
  • No systematic mechanism existed to verify statutory distance requirements — whether a proposed outlet was within the prohibited radius of a school, church, mosque, or other protected place was left to manual estimation, exposing approvals to legal challenge at the board
  • Proliferation of licensed premises in an area — a standing ground for refusal under provincial liquor legislation — was never formally assessed at the municipal stage

The MCMP Response

  • Structured digital application intake — the intake form collects all required provincial application documentation at submission. Incomplete applications are blocked with specific guidance on missing items — not discovered weeks later
  • Structured municipal compliance workflow — zoning assessment, public notice period tracking, police clearance verification, and on-site inspection assigned sequentially with SLA deadlines and auto-escalation
  • Proximity scan — 500m restricted zone — at application stage, MCMP automatically maps every church, mosque, school, and place of learning within 500m of the proposed premises. The scan is documented, reproducible, and included in the provincial submission package — replacing officer estimation with verifiable spatial intelligence
  • Proliferation analysis — 1km radius — a density scan of all existing licensed premises within a 1km zone is generated and attached to the application. The board receives a documented proliferation picture alongside the application, not a blank
  • Digital inspection report — inspector completes structured digital checklist on-site. Report submitted instantly to the system, available immediately to supervisors and the applicant
  • Provincial submission package generated automatically — all compliance documentation compiled into a structured PDF package ready for provincial liquor board submission, including the proximity scan and proliferation analysis, with a complete audit trail of the municipal assessment
  • Licence issued digitally with QR verification; expiry tracked with automated renewal reminders at 60 and 30 days before lapse
Complete
Application docs complete at intake — no missing items discovered weeks into the process
500m Scan
Every restricted place mapped automatically — churches, mosques, schools, places of learning
1km Zone
Proliferation density documented and included in the provincial submission package
QR Verified
Every licence authenticated in real time — enforcer can verify at the door
Legal Authority Liquor Act 59 of 2003 · Applicable Provincial Liquor Act (Free State Liquor Act / Western Cape Liquor Act etc.) · Municipal Systems Act 32 of 2000 · Municipal Liquor Trading Bylaws
RNW

Renewal Fast-Track — Cross-Cutting Revenue Recovery Across All Pathways

Pre-Populated from Active Licence · Municipal Account Validated in Real Time · MFMA Section 64 Aligned

Scenario

A local municipality has 8,000 active compliance certificates and licences across all pathways — BL, OCC, CoA, spaza, liquor, and informal trading. Annual renewals represent the largest single component of own-source compliance revenue. With no tracking system, renewals were missed, revenue was lost, and lapsed certificates went undetected and unenforced.

The Challenge

  • No systematic expiry tracking — renewal dates existed only in paper files that no one actively monitored
  • Businesses were not notified of upcoming renewals — many operators only discovered their licence had lapsed when an inspector arrived or a complaint was lodged
  • Renewal applications required applicants to re-submit all their documentation from scratch — the same information the municipality already held
  • Revenue from renewals was chronically under-collected — MFMA Section 64 (effective revenue collection) was not being met
  • The municipality had no way to distinguish businesses that had legitimately renewed from those operating on lapsed certificates — enforcement was blind

The MCMP Response

  • Cross-cutting renewal module — one screen surfaces every active licence held by the applicant across all pathways. A multi-site operator sees all their premises and licence types in a single view
  • Automated renewal notifications — sent to the licensee at 60, 30, and 14 days before expiry across all certificate types, reducing missed renewals to near zero
  • Pre-populated from original application — business name, type, address, municipality, and property details all carried forward. The applicant confirms, not re-enters
  • Municipal account validation in real time — the system confirms the municipal account is active and in good standing before the renewal can proceed, directly enforcing the municipality's billing relationship
  • Revenue at point of confirmation — renewal fee collected electronically at the moment of submission, not when an applicant remembers to come in and pay. MFMA Section 64 compliance is built into the workflow
  • Expired licences that are not renewed automatically flag for enforcement, closing the gap between compliance knowledge and enforcement action
8,000
Active licences tracked centrally — expiry dates monitored automatically across all pathway types
Minutes
Renewal completion time — pre-populated, account-validated, fee collected at confirmation
MFMA s.64
Revenue collected at point of confirmation — effective collection, not deferred collection
Legal Authority Municipal Finance Management Act 56 of 2003 (Section 64 — effective revenue collection; Section 71 — monthly reporting) · Municipal Systems Act 32 of 2000 · Applicable pathway-specific legislation per licence type
SCM

Supplier Pre-Qualification — MCMP Certificate as SCM Compliance Credential

Local Supplier Preference Verification · GPS-Inspected Physical Presence · AGSA-Defensible Audit Trail

Scenario

A municipality's SCM unit is evaluating bids on a local services contract that awards 20 preference points to suppliers with a confirmed local business presence. Current practice: accept a registered address on the CSD profile. The SCM director, anticipating AG scrutiny, wants a verified and documented basis for every preference point award. The municipality adds a single clause to its SCM policy — suppliers claiming local preference points must hold a valid MCMP compliance certificate, confirming a GPS-inspected, officer-verified physical premises within the jurisdictional boundary at the time of tender submission.

The Challenge

  • Local preference points awarded on self-declared addresses — no physical verification step exists between a supplier's declaration and the award of preference points
  • National supplier databases confirm company registration and tax compliance, but cannot confirm that a declared local address reflects a genuine, operational business premises within the jurisdiction
  • Fronting and address fraud: suppliers based outside the jurisdiction register a local address using a serviced office or bogus lease agreement, claim preference points, and compete with an artificial scoring advantage against genuinely local businesses
  • When the Auditor-General reviewed preference point awards, the municipality could not produce documented evidence that local presence had been verified — only that it had been declared
  • The licensing function and the SCM procurement function operated in complete isolation — a business could hold a compliance certificate and a CSD profile with no connection between them

The MCMP Response

  • One SCM policy clause — the municipality mandates that all suppliers claiming local geographic preference must hold a valid MCMP compliance certificate. No new system required — one addition to the SCM policy under MFMA Section 111 closes the verification gap
  • GPS-verified physical presence — every MCMP-certificated business has had its physical premises confirmed on-site by a trained compliance officer, with GPS coordinates on record. A serviced address or bogus lease cannot pass physical inspection — no certificate, no preference points
  • Live identity confirmation — DHA identity verification and CIPC company registration confirmation are built into every MCMP application. The certified supplier is who they say they are, and their company is legitimately registered at the time of application
  • Ward-level local positioning — MCMP positions every certified business within the ward structure of the municipality, providing the most granular geographic confirmation available for local preference scoring
  • QR-verified, AG-ready certificate — the MCMP compliance certificate carries a QR code traceable to the full inspection record, identity verification result, and compliance history. Every preference point award backed by an MCMP certificate is documentable and audit-defensible from day one
Zero
Unverified preference claims — every MCMP-certificated supplier has a GPS-confirmed, officer-inspected physical premises on record
1 Clause
One SCM policy addition is all it takes — no new legislation, no new procurement system required
AG Ready
QR-verified certificate traceable to inspection record, DHA identity, and CIPC registration — audit-defensible evidence on every preference award
Legal Authority Municipal Finance Management Act 56 of 2003 (Section 111 — SCM policy authority) · Preferential Procurement Policy Framework Act 5 of 2000 · Preferential Procurement Regulations 2022 · Municipal Systems Act 32 of 2000 (Section 2 — local economic development mandate) · Municipal SCM Policy

See these pathways
running live.

Book a 45-minute MCMP demonstration. Walk through any of these seven scenarios — live, on a working system, with real data.

Book a Demo Send an Enquiry
Book an MCMP Platform Demo — Bopaki Group
Loading calendar...

Calendar not loading? Open directly →

Chat with us