Public Comment Submission

1. Introduction

We welcome the opportunity to submit comment on the draft City of Cape Town Short-Term Letting By-Law. Short-term letting has become an important part of the Cape Town tourism ecosystem — providing accommodation capacity, supporting tourism growth, and enabling many property owners to participate in the tourism economy.

This submission was made in a personal capacity by a strategist working in the short-term rental industry, drawing on hospitality and short-term rental industry experience since the year 2000 across multiple international markets where comparable legislation has been introduced. It engages directly with the draft By-Law and the accompanying Frequently Asked Questions document (updated August 2026).

2. General Support for the Draft By-Law

We support the By-Law's core intent and design choices, and want to acknowledge specifically what the City has done well:

• Balanced approach. The City has explicitly chosen to differentiate between commercial-scale short-term letting operations and primary residences that undertake occasional letting — rather than the outright caps or bans imposed in cities like Barcelona, Amsterdam, Paris and New York (FAQ §22, §23). This is the right posture for a tourism-dependent economy.
• Formal registration mechanism. The current framework does not have a mechanism for a compliant short-term rental operator to register as such. Confirmed in person at the City's Business Licence Department (16 July 2026): there is no STR-specific business licence. The By-Law addresses this gap directly.
• Data-driven classification. Requiring booking platforms to share availability and occupancy data (FAQ §13, §14) creates an objective basis for classification that does not rely on operator self-declaration alone.
• Rolling 365-day assessment. Assessing property use on any rolling 365-day period (FAQ §11) forecloses the simple "close for one season to drop below the threshold" workaround. This is a considered improvement over static annual-window frameworks.
• Grace period and non-retrospective application. The 1 July 2027 effective date and non-retrospective treatment (FAQ §7, §18) give operators time to understand, register and comply.
• Zoning left unchanged. Confirming that the Municipal Planning By-Law already permits short-term letting (FAQ §20) removes a significant compliance hurdle for existing operators.
• HOA / body corporate autonomy preserved (FAQ §21). This appropriately respects the layered governance of sectional title complexes.

4. Structural Considerations Around the Availability-Based Threshold

The reliance on availability as the primary classification input, and the associated definitions and mechanisms in the draft By-Law, introduce a set of structural characteristics worth surfacing at the public-participation stage so that the framework may be refined before enactment. This section sets out thirteen considerations, working from definitional through behavioural to structural, and closing with the second-order economic effects the mechanism is likely to produce and the national tax-integrity risk it opens.

4.1 Definitional gap — no day thresholds distinguishing short, medium and long

The By-Law relies on distinctions between short-term letting and "medium- or long-term" letting (FAQ §3), and between commercial short-term letting and part-time letting of a primary residence (FAQ §5, §6). These distinctions are functional but unquantified. Specifically:

• There is no day-count threshold defining where short-term ends and medium-term begins.
• Medium-term and long-term are grouped together in the FAQ (§3) without further differentiation, and neither is defined in days.
• The terms "transient guests", "temporary basis" and "continuous and extended period" are used but not quantified.
• The qualifier "primary place of residence" is central to the exclusion of long-term rentals from commercial classification, but the evidence standard for establishing primary residence is not stated.

Comparable jurisdictions apply explicit day thresholds — for example New York City and Barcelona set the boundary at around 30 days; Amsterdam applies both a 30-day per-booking limit and a 30-night annual cap for primary residences; Paris applies a 120-day annual cap for primary-residence letting; London operates a 90-night annual limit. The FAQ's illustrative example (§10) referring to "an entire home rented out as a long-term rental" as remaining residential presupposes a working definition of "long-term" that the By-Law does not yet supply.

Without published day thresholds and documentation standards, operators, the City, booking platforms and dispute forums will interpret the boundaries differently, producing inconsistent enforcement, classification disputes and unnecessary legal challenge exposure. We recommend publishing explicit day thresholds and evidence requirements alongside the final By-Law.

Illustrative case — the 32-day Airbnb booking

Consider an operator whose property receives a single 32-night booking through a booking platform. On the platform's side, this booking is recorded as 32 nights booked; the platform applies its own long-term-stay pricing conventions but does not verify guest intent, primary-residence status, or lease qualification. In the data feed to the City envisaged under the By-Law, those 32 nights appear as 32 nights of listed availability that were booked. Under FAQ §9 (which measures availability rather than booked-vs-unbooked), the 32 days add to the property's rolling 365-day availability count. The only route to exclusion is FAQ §3 — treatment as a long-term lease with the property as the tenant's primary place of residence — but neither the qualifying day threshold nor the evidence standard is defined. The operator would therefore need to submit case-specific documentation for classification review, and the City would need to adjudicate each such case individually. Since the R3 million enforcement budget under Budget 2026/27 Annexure 16 has to cover the full scope of By-Law enforcement, an unknown volume of case-by-case classification reviews for mid-length bookings represents a material budget-and-capacity risk. Published day thresholds and evidence standards would substantially reduce this administrative load.

4.2 Availability is a controlled and adjustable variable

Availability, unlike actual bookings or revenue, reflects operator intent — and that intent can be redirected in response to the classification framework itself. The rolling 365-day assessment (FAQ §11) has appropriately foreclosed the simplest form of the seasonal-close workaround at the arithmetic level. The math is instructive: closing for exactly six months in Cape Town's low season (approximately April to September) produces an availability figure of 182 / 365 = 49.9%, which sits so close to the 50% threshold that any partial-property listing, calendar-sync error, single missed calendar block or accidental off-peak listing tips the property into commercial classification. To sit reliably below 50% by seasonal closure alone, an operator would need to close for more than six months (for example a five-months-open / seven-months-closed pattern, yielding 151 / 365 = 41.4%), which entails a meaningful loss of revenue and is therefore self-limiting.

However, three more fundamental behavioural responses remain available and are not addressed by the rolling assessment. All three cluster around 41 – 43% availability (safely under 50%) but with materially different revenue-trade profiles.

4.3 Behavioural Response 1 — Alternative-let switching (the dominant remaining vulnerability)

The By-Law's explicit exclusion of properties on long-term leases from commercial classification (FAQ §3, §10) creates a legitimate route for operators to move a property between letting modes across the year without triggering commercial classification. A concrete illustration:

• Property operated as an STR during the five-month peak season (1 November to 31 March) — 151 days available.
• Property converted to a six-month lease covering the low season (1 April to 30 September) — treated as a long-term rental per FAQ §3 and excluded from the availability calculation.
• STR availability calculation: 151 / 365 = 41.4% — safely below the 50% threshold on a rolling 365-day basis.
• The property is commercially active year-round via two different letting modes, without meaningful revenue loss, while remaining classified as residential.

This is not a theoretical scenario. Cape Town's strong seasonality and the growing mid-term / medium-term rental market make it a natural operating pattern, and the By-Law appropriately preserves the primary-residence protection that enables it. It is therefore the workaround with the strongest revenue economics — and the response the framework will most reliably produce.

4.4 Behavioural Response 2 — Weekend-only operating pattern

A property listed as available only Friday, Saturday and Sunday every week of the year produces:

• 3 available days × 52 weeks = 156 days available per year
• 156 / 365 = 42.7% availability — safely below the 50% threshold with a ~7 percentage-point margin

This is significant because Fridays through Sundays are also Cape Town's highest-demand STR nights across all seasons. An operator adopting a weekend-only pattern captures the majority of the commercial revenue potential (weekend ADRs typically carry a 25–40% premium over weekdays; occupancy on available weekend nights blends to approximately 65–75% annually) while sacrificing only the mid-week nights that already carry lower demand and lower rates. The revenue trade-off is modest; the classification protection is meaningful and reliable.

4.5 Behavioural Response 3 — Cross-platform and partial-property availability strategy

Because the 50% assessment is against listed availability on booking platforms (FAQ §8, §9), operators can adjust the number of nights listed as "available" and the number of bedrooms exposed on any given platform independently of their underlying commercial intent. A multi-bedroom property that is fully commercially operated can list only a subset of bedrooms on booking platforms, keeping platform-visible availability below the threshold, while the balance of the property is let via direct-booking channels or through relationships not visible to platform data feeds. This response is particularly relevant for larger properties (four or more bedrooms) where partial-listing strategies are operationally feasible.

4.6 The intent-versus-mechanism disconnect

The three viable behavioural responses above share a common characteristic that the drafters may not have fully considered: all three keep operators active during the summer peak season, which is precisely when the community-impact concerns the By-Law is understood to address are at their most acute.

Neighbour complaints, noise, overcrowding, parking pressure, waste generation and infrastructure strain from short-term letting are overwhelmingly a summer phenomenon in Cape Town, concentrated in the October to March peak. The winter low-season months (April to September) generate materially fewer complaints and less infrastructure pressure because tourist numbers are lower and properties are generally less intensively used regardless of classification.

Yet the three workarounds all direct operators to:

• Concentrate operations in the peak-nuisance months (weekend-only, seasonal close, lease switch)
• Reduce operations exactly in the low-nuisance months (winter close, winter lease conversion)
• Preserve commercial activity year-round in ways invisible to the classification metric

The result is that the classification framework will systematically identify a subset of operators for rate reclassification while leaving the underlying community-impact concerns largely unchanged. A property that operates only in peak season under the lease-switch model contributes the same peak-season community impact as one that operates year-round and is classified as commercial, yet the two are treated differently under the framework. This asymmetry between the framework's classification and the harm it is understood to address is worth surfacing so that the City may consider whether classification alone can achieve the outcomes it seeks, or whether complementary instruments are required.

There is a related second-order effect on enforcement capacity. Where the R3 million enforcement budget under Budget 2026/27 Annexure 16 is drawn heavily into classification review and dispute adjudication, the same budget is not available for neighbour-complaint response. Residents affected by summer nuisance who report a specific property to the City may find complaint response degraded because enforcement resources are consumed by the classification framework itself. The framework thus risks a paradox where its own operational load undermines the community-protection outcome it is meant to deliver.

4.7 The rate mechanism uses valuation as a proxy for commercial output — but valuation and output diverge sharply

A more fundamental structural point warrants attention: the rates system uses municipal property valuation as its proxy for the property's commercial capacity. However, valuation and commercial output are only loosely correlated, particularly among properties in the same size and location bracket.

Consider two identical two-bedroom apartments in the same building. Both are 90 m² with the same view, floor plan and municipal valuation of R5,000,000. Apartment A has a standard fit-out. Apartment B has been upgraded to include a jacuzzi and premium furnishings.

The jacuzzi generates approximately 100 times more incremental revenue than incremental rates. Even more dramatically, the same disparity applies to differences in interior design, listing photography quality, review score, response rate, direct-booking channel maturity, seasonal pricing sophistication, or any other operator-controlled quality dimension. None of these commercial-capacity differentiators are visible in the valuation roll, and therefore none of them are reflected in the rates a property pays.

The consequence is that two identical-valuation, identical-classification properties can generate materially different commercial revenues while paying identical rates — and, conversely, two properties with materially different commercial outputs can pay identical rates while contributing very differently to the accommodation market. The "level playing field" objective the FAQ articulates (§4, §6) is difficult to achieve using a classification mechanism whose underlying rate signal does not track the commercial output it is intended to level.

We do not use this observation to argue against the classification approach — the valuation-based mechanism has clear administrative advantages and is the natural starting point for a framework of this scale. But measures that reflect actual commercial output would more fairly distinguish operators than valuation alone. Revenue, ADR, occupancy patterns, cross-platform listing activity and property-performance data are already being generated by every commercially-operating STR in Cape Town and will be flowing to the City through the very data-sharing framework the By-Law is establishing. Using that data — either as a complement to the valuation-based classification, as a secondary indicator for boundary cases and dispute resolution, or as the basis of a differentiated commercial rate structure over time — would produce classification outcomes better aligned with the economic substance the By-Law is intended to address. The infrastructure the City is building supports this evolution; the design decisions taken now will determine how readily it can be adopted.

4.8 The evidentiary standard for lease qualification

FAQ §3 excludes properties on "lease or rental agreement…for a continuous and extended period as their primary place of residence" from commercial short-term letting classification. The exclusion depends on two factual gates: qualifying lease documentation, and the tenant's primary-residence status. The By-Law does not specify what documentary form constitutes a qualifying lease, what elements the lease agreement must contain, or what evidence establishes primary residence.

In practical operational terms this creates a documentary gap that will affect classification outcomes in three ways:

First — the paperwork threshold is low. Under SA property law, a lease requires only identification of the parties, identification of the property, agreed consideration, a stated duration, and signature. Any operator organised enough to run a bookkeeping process can incorporate lease-agreement language into standard guest-arrival documentation. Whether such documentation ultimately qualifies for the FAQ §3 exclusion depends entirely on how strictly the City interprets and enforces the "primary place of residence" test — a factual determination that requires case-by-case evidence.

Second — the burden of proof is asymmetric in favour of the operator. Under the current framework wording, an operator claiming the exclusion produces documentation. The City would then need to gather independent evidence — evidence of the guest's other residence, tax residency, prior address, contemporaneous residency arrangements — to contest primary-residence status. Because the operator controls the documentation and the guest is often unavailable or uncooperative once the stay is complete, the evidentiary burden falls disproportionately on the City.

Third — enforcement-economics exposure. Even where a documented "lease" would ultimately fail the primary-residence test on challenge, the process of mounting that challenge consumes enforcement resources. If a meaningful proportion of contested classifications require case-by-case adjudication, the R3 million enforcement budget under Budget 2026/27 Annexure 16 is exposed to a caseload the City has no visibility into at this stage. The mechanism does not need to succeed for the framework to be affected; it only needs to require adjudication.

We do not raise this to expose a workaround. The vulnerability is inherent in any framework whose classification exclusion depends on a factual test applied to a large volume of transient occupancies. We raise it because the framework would materially benefit from an explicit, published evidentiary standard that removes interpretive ambiguity at the front end rather than at case-by-case audit. Elements the City may wish to include:

• A minimum lease duration threshold (aligned with the day thresholds referenced in §4.1)
• Required elements of a qualifying lease agreement (parties, property, consideration, duration, primary-residence declaration, and guest signature acknowledging that declaration)
• Required contemporaneous supporting evidence of the tenant's primary-residence status (evidence of prior address, evidence of contemporaneous change of address, cross-check against SA tax residency where applicable)
• A self-declaration mechanism at the point of booking so that classification is resolved contemporaneously rather than reconstructed on audit
• A defined penalty framework for false or misleading declarations, providing meaningful deterrent to speculative classification
• An aggregate audit / sampling approach for the general run of bookings, so that verification is proportionate to enforcement capacity rather than universal

A published evidentiary standard would give bona-fide long-term operators clear guidance on how to document their stays, give the City a defensible basis for classification decisions at scale, and prevent the framework from producing inconsistent outcomes across similarly-situated properties.

Additional consideration — interaction with the Rental Housing Act

The evidentiary standard for lease qualification also intersects with the Rental Housing Act, 1999 (Act 50 of 1999), which regulates residential leases in South Africa and confers significant statutory protections on residential tenants, including deposit-handling requirements, quiet enjoyment, formal eviction procedures, and prohibitions on unfair practices. An operator whose documentation is formally structured as a residential lease may inadvertently place the guest within the RHA's protective scope — with the consequence that the guest becomes a "tenant" who cannot be summarily removed, whose deposit must be handled under statutory rules, and whose displacement requires compliance with the Act's eviction procedures. This creates a legal-risk dimension the By-Law does not currently signal, and reinforces the importance of publishing a defined boundary between lease-qualified occupancy for classification purposes and residential tenancy under the RHA. Both bona-fide long-term operators and the City itself benefit from that boundary being explicit rather than tested through litigation.

Additional consideration — evidence perishes with time

Primary-residence status is a factual snapshot at a specific point in time, but guest circumstances shift constantly. Digital nomads relocate frequently; corporate assignments end; medical treatments conclude; students complete academic terms; personal circumstances change. A guest whose primary residence genuinely was a property for the duration of their stay may have moved on within weeks; the address associated with that stay may no longer function as their residence at all, and the guest may be unreachable through the contact details they used at booking. Retrospective proof of primary residence six to twelve months after a stay — which is the practical window in which classification review would occur — is often not possible even where the underlying facts would have supported the exclusion. The framework therefore requires contemporaneous evidence capture at the point of booking rather than reconstruction at the point of dispute; otherwise the enforcement mechanism will produce arbitrary outcomes correlated with operator record-keeping quality rather than with the underlying facts.

4.9 Small-operator economies-of-scale burden

A related but distinct structural point: the commercial rate applies at a single rate-in-the-rand regardless of operating scale. This assumes that a five-bedroom villa reclassified as commercial can absorb commercial rates on the same economic basis as a 100-room hotel that has always operated commercially. The two are not economically equivalent.

Working through the numbers on a small-scale villa:

• Four-bedroom Cape Town villa, R5,000,000 valuation, ~R2,000,000 annual STR revenue at 60% occupancy, typical net margin ~5% before rates
• Residential rates: (R5,000,000 − R450,000) × 0.006428 = R29,247 / year (approximately 1.5% of revenue)
• Commercial rates: R5,000,000 × 0.015106 = R75,530 / year (approximately 3.8% of revenue)
• Increase on reclassification: R46,283 / year — approximately 46% of the villa's annual net profit at typical margins

For a large hotel that has always operated as commercial accommodation, comparable commercial rates have been priced into the ADR and business model from the outset — the room count spreads the fixed rates cost across a much larger revenue base, and the operating platform (staff, F&B, MICE, spa) diversifies the revenue mix. A small STR operator has none of these absorption mechanisms and cannot readily increase ADR by 2 – 4 percentage points to offset the rates increase without competitive impact from other accommodation options.

The consequence is that commercial reclassification, while nominally applying an "equal rate" to comparable commercial activity, imposes materially unequal economic burdens across the range of operators the By-Law will identify. We respectfully suggest the City may wish to consider whether a differentiated approach — for example a small-operator commercial category, a graduated rate-in-the-rand based on room count or annual revenue, or a rebate mechanism for operators below a defined scale threshold — could achieve the "level playing field" objective more equitably than a single commercial rate applied across all scales.

4.10 Rental arbitrage — classification obligation in owner-lessee-sublet arrangements

A significant proportion of Cape Town short-term letting activity is conducted not by the property owner directly but by a primary tenant who leases the property from the owner on a long-term residential basis and then sublets it on booking platforms. This arrangement is known in the industry as "rental arbitrage": the owner receives a fixed monthly rent from the primary tenant; the primary tenant operates the STR business, engages with booking platforms, manages guests, and captures the STR revenue.

The By-Law's registration and classification framework does not clearly address the multi-party structure this creates:

• The owner is legally the property-rates ratepayer and would bear any rates reclassification consequences, but has no operational involvement in the STR activity and often has no visibility into it beyond the terms of the primary lease.
• The primary tenant / STR operator captures the STR revenue and controls the platform activity, but is not the ratepayer and may not appear anywhere in the property-rates records.
• The FAQ §3 exclusion technically applies because the property is rented "under a lease…as their primary place of residence" — the tenant's use of the property as their primary residence qualifies. But the tenant's primary-residence activity coexists with commercial STR sub-letting, and the exclusion was not designed with that coexistence in view.

This structural ambiguity produces three concrete consequences that the framework does not currently address. First, the owner may be reclassified as commercial for rates purposes without ever having conducted or benefited from commercial STR activity, and without effective recourse because the platform activity is not their own. Second, the primary-lease agreement between owner and tenant may not include express STR permission or prohibition clauses, exposing the owner to legal, insurance and commercial risk they may not have consented to. Third, enforcement action against the party actually conducting the STR activity — the primary tenant — is not clearly authorised by the current framework, which addresses "owner" and "operator" as if they were the same party.

We recommend the framework explicitly address the owner-lessee-sublet chain by clarifying which party bears the registration and classification obligation where they are different; whether primary-lease agreements should be required to include express STR permission or prohibition clauses; whether enforcement action attaches to the party operating the platform account rather than the property owner; and how the FAQ §3 exclusion is intended to apply where a tenant's genuine primary-residence use coexists with commercial STR sub-letting.

4.11 Ownership transfer — classification continuity

When a property changes hands during the assessment period, the rolling 365-day availability metric raises questions the framework does not currently address:

• Does the previous owner's classification status transfer with the property, or does the new owner begin with a clean rolling assessment window?
• Does the previous owner's registration number transfer to the new owner, or is it cancelled and reissued?
• If the new owner intends to occupy the property as their primary residence, are they immediately reclassified as residential, or does the previous owner's twelve months of availability history continue to apply during a transition period?
• Are prospective purchasers entitled to disclosure of the property's current classification status and rolling-assessment history as part of the sale process?
• How are commercial-classification rate liabilities apportioned in the sale process — do they attach to the property (successor liability) or to the previous owner personally?

These questions have material implications for property transactions, particularly in areas where STR activity is prevalent. A prospective purchaser buying what they believe is a residential property may inherit a commercial-classification status with associated rate liability accrued over the previous owner's twelve-month operating window. Conversely, an owner-occupier selling to a commercial STR operator may unknowingly enable circumvention of the classification framework if the new owner's operating pattern is not connected to the property's classification history.

We recommend the framework publish clear treatment of ownership transfer, including rolling-assessment reset rules for new owners with genuinely different use intent; registration number continuity or reissuance procedures; classification-history disclosure requirements in the sale process; and apportionment rules for any accrued rate liability at the point of transfer.

4.12 Second-order effects — property-use shift and informal employment

The rates-reclassification mechanism will produce economic effects beyond the immediate rates impact on classified properties. Two of these effects are worth surfacing for the City's consideration, one positive and one negative.

Positive — property-use shift toward long-term rental supply. Small-scale STR operators who cannot absorb the commercial rates increase (see §4.9) will, at the margin, exit STR operation and convert their properties to long-term residential rental or place them on the market for sale. This produces a net addition to Cape Town's long-term rental housing supply at a time when housing affordability is under strain. Even a modest exit rate — for illustration, 10 to 25% of currently-commercial STR properties — would produce a meaningful supply contribution to the long-term rental market, particularly in higher-value areas where STR activity is concentrated.

Negative — informal employment displacement. The STR sector supports a significant informal employment base in Cape Town: cleaning staff, gardeners, laundry operators, maintenance contractors, key-handover and co-host services, and an adjacent supply chain of linen suppliers, cleaning-product retailers and small independent tour operators. These positions are frequently held by workers with limited formal education for whom alternative employment pathways are constrained. STR-generated work also tends to be higher-frequency (per-turnover) than long-term rental support (typically once or twice per month per property), so the displacement effect on aggregate informal-employment hours is disproportionate to the number of properties that exit.

A rough scale check: if an average commercially-operating STR sustains approximately 0.5 to 1 full-time-equivalent of informal work across cleaning, maintenance, gardening and support services, and if 15 to 20% of the estimated ~7,500 commercially-classified Cape Town STR properties exit the market post-reclassification, the employment displacement could reach 500 to 1,500 informal jobs. This is a first-order impact concentrated among workers who benefit most from the low-barrier-to-entry pathways the STR sector has created.

Neither of these effects is captured in the By-Law's stated objectives (rates fairness and improved compliance), and both flow directly from the mechanism. We do not raise them to argue against the reclassification approach — the fairness objective is legitimate and no by-law can be expected to internalise every downstream economic effect. We raise them because acknowledging them at the framework-design stage allows the City to shape the outcome deliberately rather than reactively:

• The property-use-shift effect argues for the By-Law being coordinated with Cape Town's broader housing strategy, so that the additional long-term rental supply flowing into the market is captured productively — for example through affordable-rental incentives, first-time-buyer support for former STR properties, or targeted engagement with rental-agent networks to absorb the new stock efficiently.
• The employment-displacement effect may warrant a modest transition-support programme — transition-assistance information for displaced workers, coordination with hotel and hospitality-training partners to absorb some of the displaced labour into the formal sector, or targeted skills-upgrade support delivered through existing City workforce-development channels.
• Both effects benefit from transparent communication in the City's roll-out of the By-Law, so that operators, workers and community stakeholders can anticipate and plan for the transition rather than experience it as a shock.

The framework is likely to produce these effects whether they are anticipated or not. Anticipating them turns two significant externalities from unmanaged consequences into deliberately-shaped outcomes aligned with the City's broader social and economic objectives.

4.13 The cash-economy incentive and national tax-integrity risk

Because the classification mechanism relies on platform-listed availability, and because most short-term rental demand is weekend-concentrated (see §4.4), the mechanism creates a specific and predictable incentive to move marginal nights off-platform and into cash. This is arguably the framework's most consequential unintended effect, because it reaches beyond the By-Law's own scope into national tax administration.

The operational flow is straightforward. An owner opens their booking-platform calendar for Friday to Sunday only (achieving the ~42.7% availability that safely stays below the classification threshold per §4.4). A guest books their weekend stay. Through the platform's own messaging flow, the operator now has the guest's contact details — name, phone number, WhatsApp handle. When the guest asks about extending the stay into Monday or Tuesday, the operator responds that the property is "closed" on the platform for those nights but is available to be booked directly, in cash. Those additional nights are neither listed on any booking platform nor visible to the platform data feed the City will receive under the By-Law. The revenue is neither declared to SARS nor visible to the City.

This is not a hypothetical scenario. The same dynamic played out at scale in parts of Southern Europe — Greece being the most cited example — where cash-only accommodation channels emerged as tax-avoidance vehicles once formal reporting attached to specific booking channels. The lesson from that experience is durable: when a regulatory mechanism defines its data source narrowly (in this case: platform-listed availability), commercial activity flows into the channels the mechanism does not see.

The consequences compound in four directions:

• City rates integrity is weakened. The very data the By-Law will rely on becomes a progressively worse proxy for actual commercial activity as revenue moves off-platform. The classification framework operates on data that is systematically understating real operator behaviour.
• SARS revenue is undermined. Cash payments for accommodation nights are not automatically reported and are much harder to identify through the third-party data flows SARS uses for tax administration. A framework that inadvertently expands the cash economy expands the SARS collection gap.
• The consumer-protection story is undercut. A guest paying cash for nights off-platform has no platform-mediated dispute mechanism and no consumer-protection recourse. This directly undercuts the trust argument the reframed By-Law would rest on (see §3.4).
• Compliant operators are competitively disadvantaged. Operators who report all revenue transparently pay full commercial rates and full tax; operators who structure activity through the cash channel avoid both. This is the opposite of the "level playing field" the By-Law is meant to establish.

We recommend the framework be designed with coordination with SARS from the outset — visibility into off-platform income, intergovernmental data-sharing arrangements, and design choices that make on-platform bookings materially preferable to off-platform cash arrangements (verified-operator trust signals, platform-integrated compliance certifications, and dispute-resolution mechanisms tied to on-platform booking history). The mechanism should be designed so that compliance is the path of least resistance for the operator, not the path of least commercial return.

5. Practical Implementation Considerations

The following operational scenarios may benefit from explicit treatment in the final By-Law, in the accompanying regulations, or in published operational guidance:

• Multi-platform listings. A single property may be listed simultaneously on multiple platforms (Airbnb, Booking.com, Vrbo, direct booking sites). How will aggregate availability be calculated where the same nights are listed across multiple platforms — additive, or deduplicated to the true available-night set?
• Multi-listing properties. A three-bedroom property may be listed as three separate one-bedroom listings across one or more platforms. How will these be aggregated back to the same physical property for classification purposes?
• Portfolio operators and property managers. Operators managing tens or hundreds of properties (professional property management companies) will require a batch registration and reporting mechanism. Individual per-property manual registration is not scalable at portfolio level.
• Sectional title and body corporate scenarios. Where a body corporate or HOA has its own STR rules, coordination between those rules and the City's registration system will benefit from clear guidance.
• Classification disputes. A mechanism for operators to contest a classification determination — whether through internal municipal review, formal appeal, or independent third-party assessment — should be built into the framework, not left to develop reactively.
• Direct-booking operators. Properties booked directly (not via platform) still fall within the scope. The framework should account for direct-booking operators via alternative registration and reporting arrangements.

6. Registration System Design Considerations

To maximise voluntary compliance and minimise operational friction, we suggest the registration system be designed with the following characteristics:

• Simple. Minimal information collection at registration (property address, contact, capacity). Additional detail collected only where classification is contested or a complaint-driven investigation is triggered.
• Free or low-cost. A registration fee acts as a compliance disincentive; the value of the registration system is in the aggregate compliance it produces, not in fee income.
• Batch-capable. Portfolio operators must be able to register properties in bulk via CSV import, an operator dashboard, or an API.
• API-first for platforms. Booking platforms should be able to submit availability data via automated feed rather than manual monthly submission.
• Operator-visible. Operators should be able to see their current rolling 365-day availability position, the projected date at which they would cross the classification threshold at their current pace, and the classification determination the City currently holds for their property. Transparency drives voluntary compliance far more effectively than reactive enforcement.
• Voluntary early registration. Allow operators to register voluntarily ahead of the 1 July 2027 effective date, and to receive a provisional classification, so they can plan.

7. Data Sharing Framework Considerations

The By-Law's requirement for platform-to-City data sharing (FAQ §13, §14) is the enforcement mechanism that gives the framework teeth. Several considerations warrant attention:

7.1 Foundational framework considerations

• POPIA compliance. What personal data will be shared (operator contact, guest details, booking values)? How will retention, purpose limitation, and access controls be documented?
• Data schema standardisation. Different platforms structure their data differently. A published City data schema will reduce compliance friction and produce cleaner data.
• Submission cadence. Daily, weekly, monthly? A published cadence with reasonable lead time helps platforms build accurate compliance workflows.
• Data-integrity mechanism. How will the City verify platform-submitted data is accurate and complete? Will there be periodic audit, reconciliation, or cross-source verification?
• Reciprocal operator transparency. Operators should be able to see the data platforms have submitted about their property — for accuracy verification and to build operator confidence in the system.
• Sanction and correction path. Where data errors are identified, a clear correction and re-classification path should be available without penalty for good-faith reporting.

7.2 What "available" means across booking-platform states

Booking platforms distinguish between a range of availability states that are handled differently by each platform and that will produce different data feeds to the City:

Without published definitions, operators, platforms and the City will interpret these differently. An operator who calendar-blocks 200 nights of the year may reasonably believe those nights are "unavailable" and drop out of the 50% calculation; the City's data feed may or may not treat them the same way. A property let entirely off-platform for part of the year will show as zero availability during that period from the platform data feed but may still be commercially operating.

We recommend the By-Law's regulations or accompanying operational guidance publish explicit definitions of "available" across each platform state, together with the treatment of properties operating outside platform channels.

7.3 The mid-length booking classification problem

As set out in Section 4.1 (illustrative case), platform data alone cannot determine whether a 30+ night booking qualifies as a short-term stay counted toward availability, or a long-term lease excluded per FAQ §3. Booking platforms record such stays as bookings without verifying the guest's primary-residence status or the qualifying lease documentation. Without a published day threshold and evidence standard, every mid-length booking becomes a potential classification review. We recommend the framework include:

• A published day threshold for lease qualification (aligned with SA legal precedent and international benchmarks)
• A defined documentation standard for demonstrating primary-residence occupancy where the day threshold alone is not sufficient
• An operator-facing self-declaration mechanism at the point of booking, so that documentation is captured contemporaneously rather than reconstructed on request
• A streamlined classification-review process for cases genuinely on the boundary, so that the volume of contested classifications does not overwhelm the R3 million enforcement budget under Annexure 16

7.4 Direct-booking and off-platform channels

The By-Law's platform-data-sharing mechanism does not directly address properties booked outside major booking platforms — through direct websites, WhatsApp channels, agent networks, or repeat-guest relationships. A registered operator who conducts a growing share of business via direct booking will over time become progressively less visible to the framework's classification data. We recommend the registration system require operators to self-declare direct-booking activity, and that the framework include a proportionate audit mechanism to verify aggregate consistency between self-declared activity and platform-observed activity.

7.5 Billing-cycle and data-cycle lag — the operational implementation bottleneck

Under the mechanism as designed, the City will need booking platforms to provide regular reports of past-period occupancy and availability data — realistically on a monthly cycle, since platforms internally account in monthly windows. This creates three operational realities the By-Law does not currently address, and which together represent the framework's most concentrated implementation risk.

Data lag is inherent. Platform data is unavoidably backward-looking. A property's classification for a given month can only be determined once the platform has closed and reported that month's activity. The City's rates billing cycle therefore always operates on lagged data — typically a month or two behind actual operator activity. This is manageable in principle but requires explicit definition: when will operators be notified of a classification change? What is the intended lag between operating activity and the rates bill reflecting it? What happens when a platform delivers its monthly report late, or with partial data, or with data that requires correction? These are operational questions with material consequences for both operator experience and City cash-flow certainty.

Query volume from operator disputes will be substantial. When a rates bill arrives reflecting commercial classification, an operator who disputes the underlying availability figure has a natural incentive to challenge — "my availability was not X in that period; here is my calendar and my booking record". Every such dispute requires the City to open a classification review file, pull the platform data feed for that property for that period, cross-reference operator-supplied records, and either sustain or vary the classification. Applied across the estimated 25,000 to 30,000 short-term rental listings in Cape Town, even a modest per-operator dispute rate — say 5 to 10% of classified properties in a given cycle — produces a substantial ongoing case volume.

Training and expertise burden on the City is specialist. Adjudicating these disputes requires City staff who understand: booking platform data structures across multiple platforms; the distinction between listed availability, calendar-blocked availability, booked availability, and closed-to-arrival treatment; how partial-property listings aggregate to the physical property; how off-platform and direct bookings interact with platform-reported figures; and the evidentiary standards discussed in §4.8. This is a specialist skill set distinct from the general municipal rates administration workforce, and one that would need to be built and maintained on an ongoing basis.

The three items compound. Data lag creates timing gaps that generate operator queries; a rising query volume increases dispute caseload; adjudication load requires trained staff; staffing constraints extend resolution times; extended resolution times further increase operator frustration and query volume. Without deliberate operational design, this feedback loop can absorb a materially larger share of the R3 million enforcement budget than the framework's designers may currently be modelling. It is a foreseeable bottleneck that becomes very difficult to unwind once the framework is operational and disputes have accumulated.

We recommend the operational design of the framework — the platform reporting cadence, the billing-cycle-to-data-cycle relationship, the dispute review process, and the staffing model to support all three — be published alongside the final By-Law and its regulations. The framework's operational architecture would benefit from being designed with input from operators, platforms and industry practitioners who have seen how comparable mechanisms have or have not worked internationally. Alternative operational approaches exist that would substantially reduce this administrative load; we would welcome the opportunity to discuss these with the City.

8. Beyond Rates Classification — The Wider Compliance Landscape

The draft By-Law addresses rates classification and registration comprehensively. Short-term rental operator compliance in Cape Town, however, spans many other dimensions the By-Law appropriately does not attempt to cover — but which remain live risks for guests, neighbours and the broader tourism sector:

• Life safety — fire safety fittings, gas safety certificates, medical readiness (first aid kits, emergency numbers), child safety fittings, pool safety per SANS 10134.
• Insurance — standard household policies typically void on commercial letting; operators often do not know they are exposed until a claim is refused.
• Maintenance and inspection records — the compliance certificates a hotel produces on demand (fire extinguisher service, pest control, electrical COC, gas COC, pool safety, HVAC, structural, roof) apply equally to STR properties but are rarely maintained.
• Community impact protections beyond rates — noise monitoring, occupancy caps per bedroom, 24/7 local contact requirement, complaint response SLAs.
• Listing accuracy and claim integrity — disability access claims, green / sustainability claims, amenity accuracy. False claims cause real consumer harm and undermine honest operators.
• Biohazard protocol — blood-contaminated linen destruction rather than bleach-and-reuse (a live public health issue currently absent from STR sector norms; hotels and hospitals already have proper protocols).
• Health and hygiene beyond municipal minimum — industrial laundry standards, cleaner training and PPE, sharps disposal.

We have set out a full 13-pillar wishlist covering these dimensions in a companion document titled "A Practical Code of Good Practice for Short-Term Rentals in South Africa", which we would be pleased to share with the City or with any interested department. These dimensions form a natural component of the repositioned business-compliance framing set out in Section 3 above.

Registration is a necessary first step. A registered listing without smoke detectors, biohazard protocol, valid STR-endorsed insurance and a maintenance log remains a preventable-harm risk to guests and neighbours. The infrastructure the City is building (registration numbers, platform data pipeline, enforcement funding under Budget 2026/27 Annexure 16) is the same infrastructure a comprehensive Code of Good Practice would run on. We respectfully suggest that as the By-Law is implemented, the City may wish to consider laying the foundation for a companion Code of Good Practice covering these wider dimensions — either as a City instrument, in partnership with industry bodies, or via endorsement of a voluntary industry standard.

9. Summary of Recommendations

1. Retain the draft By-Law's rates-classification mechanism, registration requirement, and platform data-sharing framework substantively as drafted.
2. Reposition the By-Law's public framing as the first component of a comprehensive short-term rental business-compliance framework — where rates classification is one natural consequence of legitimate commercial operation, alongside registration, safety compliance, insurance, maintenance records, and adherence to a Code of Good Practice. Support this reframing with a visible revenue-recycling compact — articulating how the rates and registration revenue generated under the By-Law is reinvested in tourism marketing, destination safety, small-operator compliance support, and adjacent industry-stimulus outcomes. Together, these two moves change nothing about the mechanism, but materially improve compliance economics, public reception, enforcement dynamics, and industry / platform buy-in (see Section 3, especially §3.7).
3. Publish explicit day thresholds distinguishing short-term, medium-term and long-term letting, together with evidence standards for lease qualification and primary-residence occupancy. Without these, every mid-length booking becomes a potential classification dispute and the R3 million enforcement budget carries unquantified case-load risk.
4. Publish a defined evidentiary standard for qualifying lease documentation under FAQ §3, including required lease-agreement elements, contemporaneous supporting evidence of primary-residence status, a point-of-booking self-declaration mechanism with meaningful penalties for false declaration, and an aggregate audit approach proportionate to enforcement capacity. Include an explicit boundary against inadvertent activation of the Rental Housing Act's residential-tenancy protections. This is the single most effective way to prevent classification bottleneck and to give bona-fide long-term operators clarity on how to document their stays.
5. Publish operational definitions of what constitutes "available" across each booking-platform state (listed, booked, owner-blocked, closed-to-arrival, delisted, off-platform), so that operators, platforms and the City interpret the classification metric consistently.
6. Add multi-indicator support to the availability-based classification. Availability alone is a proxy for commercial capacity; measures that more directly reflect commercial output (revenue, ADR, occupancy patterns, cross-platform listing activity) would produce a fairer and more robust classification outcome, particularly for boundary cases and dispute resolution.
7. Consider a differentiated commercial rate for small-scale operators. A single commercial rate-in-the-rand applied across all scales imposes materially unequal economic burdens on small STR operators (four to six bedrooms, single-property operators) relative to large commercial accommodation providers whose economies of scale and revenue diversification absorb the same nominal rate readily.
8. Design the registration system to be simple, free (or minimal-fee), batch-capable, API-first, and operator-visible, with voluntary early registration and a live view of the operator's rolling 365-day availability position.
9. Publish the full data-sharing and operational-implementation framework — schema, cadence, integrity mechanism, POPIA compliance framework, off-platform / direct-booking treatment, billing-cycle-to-data-cycle relationship, dispute-review process, and staffing / expertise model to sustain adjudication at scale — alongside the By-Law's regulations, so that platforms, operators and the City itself have a shared operational picture from day one and the foreseeable data-lag / dispute-volume / expertise feedback loop (see §7.5) is deliberately managed rather than reactively absorbed.
10. Address the multi-platform, multi-listing, portfolio, sectional-title, classification-dispute and direct-booking scenarios explicitly in the final By-Law or accompanying regulations.
11. Consider laying foundation for a companion Code of Good Practice covering the compliance dimensions the By-Law is silent on — life safety, insurance, maintenance records, community impact, listing accuracy, biohazard protocol, health and hygiene. The infrastructure the By-Law is establishing (registration numbers, platform data pipeline, enforcement funding) is well suited to supporting a broader compliance framework over time. This directly supports the repositioning recommended in Recommendation 2.
12. Clarify classification obligation in owner-lessee-sublet arrangements (rental arbitrage). Specify which party bears the registration, classification and rate-liability obligation where owner and STR operator are different; consider requiring express STR permission or prohibition clauses in primary residential leases; align enforcement action with the party actually operating the booking-platform account rather than defaulting to the property owner.
13. Publish ownership-transfer treatment — rolling-assessment reset rules for new owners with genuinely different use intent, registration continuity or reissuance procedures, classification-history disclosure requirements in the sale process, and apportionment rules for accrued rate liability at transfer.
14. Anticipate and coordinate second-order effects. The reclassification mechanism will produce two significant economic effects the By-Law itself does not address: a positive shift of small-scale STR properties toward long-term rental supply (opportunity for the City's housing strategy) and a negative displacement of informal STR-dependent employment (transition risk for low-education workers). Acknowledge both explicitly in roll-out communications; coordinate the property-use-shift effect with Cape Town's broader housing strategy so the new supply is captured productively; provide transition-assistance information and consider partnerships with hospitality-training providers to absorb displaced labour.
15. Coordinate with SARS on tax-integrity implications and design against the cash-economy incentive (see §4.13). The classification mechanism, by relying on platform-listed availability, inadvertently creates an incentive for marginal nights to move off-platform and into cash — a pattern documented at scale in comparable international frameworks (Greece being the most cited example). Coordinate with SARS on off-platform income visibility, adopt design choices that make on-platform bookings materially preferable to off-platform cash arrangements (verified-operator trust signals, platform-integrated compliance certifications, dispute-resolution mechanisms tied to on-platform booking history), and structure intergovernmental data-sharing arrangements that reduce the visibility gap between what the platforms report and what is actually being paid.
16. Engage industry stakeholders (operators, property managers, platforms) in the technical design of the registration platform, the data-sharing framework, and the classification-review process, so that operational realities are built in from day one and administrative bottlenecks are minimised.

10. Conclusion & Engagement Request

We support the City's approach and recognise the difficult balance the draft By-Law strikes between formalising a growing sector, preserving the tourism economy that depends on it, and ensuring fair treatment relative to hotels and guesthouses. The framework is a considered improvement over comparable international approaches, particularly in its rolling assessment window and its explicit protection of primary-residence occasional letting.

We appreciate the opportunity to provide input and look forward to continued engagement as the By-Law progresses toward adoption and implementation. We would welcome an opportunity to discuss any of the observations above in more detail with the responsible team.