# DESTINATION TSHWANE — WHERE WE MEET

Identity proposal for review · 19 September 2026

Executive proposition

## An identity for a place that holds many identities.

The proposed Destination Tshwane identity centres on meeting. Its geometric Y gives that idea a compact visual form: distinct approaches, a shared centre and a continuing path. “Where We Meet” states the same proposition in words.

The identity is designed to connect destination communications across culture, heritage, nature, knowledge, institutions and economic opportunity. The mark supplies continuity; individual stories retain their own imagery, voices and context.

Independent design proposal. This document does not claim City endorsement, trademark clearance, approved production standards or compliance with an unseen competition brief.

## 01 / The strategic case

Tshwane cannot be represented completely by a single attraction. The design challenge is to establish a recognisable organising idea broad enough for diverse places and communities, while giving it a consistent visual expression.

Meeting is proposed as that organising idea. Residents meet visitors; history meets contemporary life; research meets enterprise; city experiences meet natural environments. These are strategic interpretations, not claims that any one metaphor explains the destination’s name or geography.

### The promise

A destination where distinct journeys can share a point of encounter. The identity invites participation without demanding that every story look or sound the same.

### The audience

- **Residents:** a system that can include local stories and recognise contributions across the metro.
- **Visitors:** clear discovery, useful information and connections to real operators.
- **Partners:** consistent assets and practical rules for destinations, institutions, events and businesses.
- **Decision-makers:** a manageable identity that can work across channels and evolve through evidence.

## 02 / Why this form

### Distinct approaches

Purple and gold arms remain visibly different. Their relationship supports a proposition of connection with difference intact.

### The meeting space

The supplied artwork includes a light triangular element. It represents common ground: a place for dialogue, exchange and welcome. It must be described as a light element in this version, rather than an empty, transparent wedge.

### Convergence and continuation

The separate shapes gather around a common centre, reading together as a Y. The lower stem suggests continuation. The supplied mark and its new digital rendering retain visible separations; the rationale therefore does not claim the arms physically join or that a new colour forms at their intersection.

### Restraint has a purpose

The master mark provides a recognisable anchor. The Union Buildings, wildlife, jacarandas, communities and other place-specific subjects belong in the wider communication system, where their detail can remain meaningful and legible.

### Development narrative

Present the design journey as observation, exploration, reduction and resolution. Use actual dated sketches, image studies and source files to demonstrate it. Reconstructed studies must be labelled as new design-development studies; they should not be presented as an invented historical sequence.

## 03 / A disciplined identity system

| Element | Proposed rule | Production status |
| --- | --- | --- |
| Master mark | Preserve the established silhouette and the proportions between its parts. | Clean digital SVG reconstruction available; final master approval and print proofing pending. |
| Lockup | Align the geometric mark with Destination Tshwane / Where We Meet, retaining consistent spacing. | Live-text digital lockups implemented; supplied raster retained for reference. |
| Clear space | Start with one stem-width around the visible mark; measure against the final master. | Proposed rule, awaiting vector proof. |
| Minimum size | Judge legibility at 16, 24, 32, 48 and 64 px; develop a small-size master if needed. | Screen samples available. No final print minimum asserted. |
| Single colour | Maintain the same visual relationships in positive and reversed applications. | Clean single-colour SVG for digital use; final production approval pending. |
| Colour | Purple anchors the identity; gold highlights emphasis; cream supplies a quiet field. | Website values fixed; CMYK and spot colours require physical proofing. |
| Type | Native system typography for an iOS-inspired digital experience; monospaced small labels. | System font stack applied. Final fixed-font brand artwork remains a separate production deliverable. |
**Identity colours:** deep purple #231148, destination gold #C8841A, meeting cream #F6F1ED and ink #15102B. Digital surfaces also use a cool off-white #F7F5FA. Gold is used as a display accent or with dark text; body copy uses darker or lighter combinations for readability.

### Motion

Motion should describe approach and convergence. Keep transitions brief, provide a stable resting state and honour reduced-motion preferences. The page’s imagery changes only when selected; it does not force an autoplay sequence.

### Photography and representation

Commission and licence identifiable Tshwane places and real people with appropriate permissions. The updated proposal uses clearly labelled AI-generated concept photography for identity applications, family discovery and local enterprise. These scenes illustrate the intended experience; they do not document actual visitors, named operators, events or verified locations. The geometric identity masters remain separate from the illustrative print applications.

### Campaign language

- Master: **Where We Meet.**
- Culture: Where stories meet.
- Nature: Where city meets wild.
- Knowledge: Where ideas meet opportunity.

Campaign expressions sit beneath one master identity. Partner and regional variants should follow a governed naming and lockup system, rather than becoming unrelated logos.

## 04 / From identity to useful service

The working visitor layer demonstrates discovery, filtering, place details and a personal day plan. Four real destinations link to operator information. A visitor can add and remove places, change visit order and time allowances, keep the plan on their device, download it or share a link.

The planning companion accepts natural-language requests and follow-up edits for interests, named places, exclusions, pace, start time and a total time window. It shows its interpretation, preserves explicit place constraints and flags unsupported requests. It matches these preferences against the four-place collection. It evaluates visit combinations, reserves at least 30 minutes of free time, and offers an editable proposal with apply and undo. Wildlife visits remain standalone. This is a local rules-based planner, not a connected language model, live travel service or booking agent.

Opening hours, prices, transport and availability are confirmed by the operators. The demonstration does not issue tickets, process payments, confirm reservations or calculate live journeys. Its purpose is to make the destination easier to explore while establishing the requirements for a future service.

### Geographic integrity

Municipal administrative regions and visitor locations are distinct. This experience lists individual destinations and locality labels, rather than claiming to divide Tshwane into tourism districts. It does not equate a visitor-location list with the municipal region count. The unverified schematic map is not part of the proposal.

The green thread is a thematic nature narrative. It is not presented as a continuous Apies walking route to Dinokeng. Every journey requires its own access and transport check.

### Accessibility and mobile use

The experience uses native controls, keyboard focus indicators, named buttons, touch-sized actions, a collapsible mobile menu, persistent mobile navigation and reduced-motion support. The planner communicates empty states and estimate limitations. Broader assistive-technology testing remains part of production acceptance.

## 05 / The implementation case

| Stage | Work | Evidence to collect |
| --- | --- | --- |
| Identity validation | Vector refinement, reproduction proofs, resident and stakeholder review. | Recognition and comprehension tests; documented feedback; approved masters. |
| Visitor pilot | Validate listings with operators, test discovery and planning on phones. | Task completion, information accuracy, accessibility findings and partner feedback. |
| Partner service | Introduce authorised listing updates, operator hand-offs and content governance. | Listing freshness, operator participation and confirmed referral activity. |
| Transactional service | Integrate booking, payments, availability and support only with contracted operators. | Reconciliation, refunds, fulfilment, privacy and service support readiness. |
The economic case is a testable proposition: better discovery and clearer operator connections may support local visitation and spend. No unmeasured job, revenue or tourism uplift is asserted.

### Governance

A designated brand owner should maintain the master assets, approve partner variants and own the content review schedule. Community contributors and destination operators should help shape representation. Publication should require a named content owner, source and review date for each listing.


## 05A / Tourism opportunity with local benefit

The identity and website are jointly accountable for discoverability, useful operator referrals and evidence of local benefit. These are proposed pilot requirements, not achieved results.

| Goal | Identity requirement | Website requirement | Owner | Evidence |
|---|---|---|---|---|
| Make local businesses easier to find | A partner lockup, storefront and event templates that preserve each business’s own identity. | Verified operator profiles, direct enquiry links and fair discovery for small businesses. | Partner lead | Active local operators; qualified referrals per operator. |
| Make domestic outings affordable | Resident-facing campaigns with readable, itemised offers. | “Tours under R250 per person” filters verified prices and mandatory fees; show child pricing and transport exclusions. | Content lead | Price freshness; affordable-offer enquiries; operator-confirmed visits. |
| Spread visitor spend | Community-authored stories and consistent wayfinding to participating neighbourhood businesses. | Suggest relevant nearby guides, food and crafts alongside anchor attractions, with consent and practical travel checks. | Community + product leads | Distribution of referrals across participating areas; net receipts reported by local operators. |
| Encourage another visit | A reusable calendar identity for markets, culture and seasonal programmes. | “What’s happening today?” uses dated, reviewed events; remove expired listings and offer opt-in reminders. | Events editor | Fresh event coverage; repeat visits with consent; verified redemptions. |
| Turn a short visit into a longer stay | Partner materials for hotels, conferences and business-event hosts. | Offer optional evening or next-day extensions through accommodation and tour partners. | Partnerships lead | Partner-confirmed extra nights and bookings; no inference from clicks. |
| Make family planning easier | Clear icons, legible signs and welcoming imagery created with participating communities. | Family results show age guidance, total party cost, facilities and operator-confirmed access information. | Visitor experience lead | Successful family enquiries; task completion; complaints and resolution time. |

Propose free basic listings and assisted onboarding, fair discovery, clearly labelled sponsorship, community consent and paid contributions. Partner marks do not imply official accreditation. Every promoted offer needs a verified operator, content owner, review date, price scope and validity.

Measure discovery, referrals, visits and money received separately. Use agreed aggregated operator records, net of cancellations and refunds. Report data coverage; never infer sales from clicks or extrapolate pilot results to the whole city. Record a pre-pilot baseline and compare periods or phased rollout where practical. No job or revenue uplift is asserted.

Pilot: days 1–30 establish owners, partners, permissions and baseline; days 31–60 test bounded affordable/family/event journeys with verified records; days 61–90 evaluate outcomes and expand only with evidence. Proposed gates: every listing has an owner/contact/review date; no unverified price or expired event qualifies for targeted results. Numerical outcome targets are agreed after baseline collection.

Strategic context: [South African Government tourism overview](https://www.gov.za/about-sa/tourism). Local mechanisms are recommendations, not government-mandated standards.

The website proposal distinguishes working four-place discovery and day planning from proposed live events, price/family filters, onboarding, referral analytics and booking integrations.

## 06 / Production status (27 September 2026)

| Requirement | Current status | Next action on adoption |
| --- | --- | --- |
| Strategic proposition and rationale | Prepared | Refine with the City and tourism partners. |
| Web demonstration | Implemented and tested (542 automated checks) | Review on the final judging devices. |
| Canonical master | Verified against the original artwork (97.9% overlap); one reconstruction error corrected; geometry locked | Proof in print; register the master. |
| Logo suite | Every lockup in full colour, black, white and greyscale as SVG, PDF, EPS, PNG and JPEG | Press proofs; embroidery and signage samples. |
| Standards | Colour (HEX, RGB, FOGRA39 CMYK, greyscale, contrast), typography roles, clearspace, minimum sizes, incorrect use | Match Pantone physically; test on real stock. |
| Application system | 70 production artboards: stationery, tourism collateral, wayfinding, transport, 30 Years, campaign and scale test | Fit to real fleets, sites and suppliers; survey sign messages on site. |
| Design development evidence | New explanatory studies, September 2026, labelled as such | Keep the record open as the system develops. |
| Image provenance | Concept imagery labelled; images with AI-drawn brand marks retired | Commission and license real photography. |
| Name and trademark clearance | Not established | Complete clearance and the City’s adoption process. |

## 07 / Source and asset record

Existing artwork and source were recovered from [destinationtshwane.online](https://destinationtshwane.online/) on 19 September 2026. The supplied identity rationale dated 8 September 2026 informed the strategic structure. This revision reconciles that rationale with the actual recovered artwork.

- [SANBI — Pretoria National Botanical Garden](https://www.sanbi.org/gardens/pretoria/)
- [Freedom Park — official visitor information](https://www.freedompark.co.za/)
- [Voortrekker Monument — official visitor information](https://vtm.org.za/)
- [Dinokeng Game Reserve — official visitor information](https://www.dinokengreserve.co.za/)

Operator pages were checked on 19 September 2026. Suggested visit durations are editorial planning allowances, not operator commitments.

## 08 / Making of the Y: evidence record

The identity proposal’s case-study chapter (identity.html#making) separates evidence, measurement, interpretation and design decision. Sequence: Tshwane → place → connection → convergence → meeting → abstraction → the Y → where we meet, then the living destination system. Its studies are new explanatory design studies made in September 2026, not historical sketches.

The geography supplied the behaviour. Design supplied the discipline.

### Factual sources

| Statement or data | Source | Date |
| --- | --- | --- |
| River junction, names and relationship: Moretele from the south, Pienaarsrivier from the east, Moretele continuing west; junction 25.1736127°S, 28.1104284°E | OpenStreetMap contributors (ODbL): ways 442829249, 442829261, 442829251; node 4404800716. File: assets/junction-waterways.geojson | Retrieved 19 Sep 2026 |
| General directions 168°, 90°, 289°; 78° between approaches; continuing path 20° off straight-through; 129° design rotation | Derived from the OSM geometry by scripts/build-making-of-y.mjs. Method and values: assets/junction-measurements.json | Computed 24 Sep 2026 |
| Flag construction: the band’s centre lines converge in the centre and continue horizontally | Constitution of the Republic of South Africa, 1996, Schedule 1 — https://www.gov.za/documents/constitution/constitution-republic-south-africa-1996-schedule-1-national-flag-07-feb-1997 | Checked 24 Sep 2026 |
| Flag reading as “convergence of diverse elements … taking the road ahead in unity”; “no universal symbolism should be attached to any of the colours” | South African Government, National flag — https://www.gov.za/about-sa/national-flag | Checked 24 Sep 2026 |
| Language shares in the City of Tshwane | Statistics South Africa, City of Tshwane profile, Census 2011 — https://www.statssa.gov.za/?page_id=1021&id=city-of-tshwane-municipality | Checked 24 Sep 2026 |
| Mark geometry: arms ≈43° from vertical (≈86° apart), arm width 73–75, stem 76, gaps about 18–24 units | Measured on the canonical master brand/master/tshwane-y-master.svg (500 × 565 units), verified against the original artwork: overlap 97.9%, largest deviation 2.2 units | Measured 27 Sep 2026 |

### Fact, interpretation and proposal

| Class | Statement |
| --- | --- |
| Fact | OpenStreetMap maps Moretele approaching from the south, Pienaarsrivier from the east and Moretele continuing west at 25.1736127°S, 28.1104284°E. |
| Fact | Schedule 1 describes the flag’s Y-shaped band with centre lines that converge and continue horizontally. |
| Fact | Census 2011 records eleven spoken languages and Sign Language in the City of Tshwane. |
| Measurement | Bearings of 168°, 90° and 289°, an approach angle of about 78° and a 20° offset, derived from open community map data with a stated method. |
| Measurement | Mark proportions and clearances, taken from the digital reconstruction. |
| Interpretation | “Tshwane is a city of convergence” and its lines: people, languages, government, nature and city, South Africa and the world. |
| Interpretation | The Government’s own reading of the flag as convergence, quoted, not extended to colours. |
| Interpretation | KOPANO (union, gathering, coming together) as conceptual reference only; confirm usage with a language specialist before publication. |
| Interpretation | The junction as local evidence of the behaviour of meeting. |
| Proposal | The 129° rotation, balancing to about 86°, straightening by 20° and the upright Y. |
| Proposal | Nine new explanatory design studies, dated September 2026. |
| Correction | One reconstruction error in the gold arm’s inner edge corrected to match the original artwork. No other change: the approved geometry is locked. |
| Proposal | Lockups, app icon, vertical applications, the arrow derived from the Y, and the six visitor questions as platform capabilities. |
| Not claimed | That Tshwane means “rivers”, or any etymology; which municipality the junction lies in; that the mark traces the rivers; that the mark redraws the flag; meanings for flag or brand colours; a historical design sequence; surveyed hydrology. |

Map data © OpenStreetMap contributors, ODbL. Open community data, not official surveyed hydrology. The Tshwane mark is not a redraw of the South African flag.