Executive design review · Version 2.0

A destination is not a rendering.
It is a governed operating system.

This blueprint reorganizes CommonGround around the decisions required to responsibly validate, approve, finance, design, build and operate one exceptional nature-first flagship. It is a control plane—not a promise that land, approvals, capital or delivery are confirmed.

Review lens

01 · North star

Manage one connected guest experience—not a portfolio of attractions.

CommonGround succeeds only if nature, food, learning, craftsmanship, recreation and gathering reinforce one another across ordinary weekdays, difficult weather, winter evenings and peak community moments.

01

Nature carries the visit

Landscape quality, shade, habitat, water, trails and seasonal change must remain valuable even when no event or transaction occurs.

Design test: Would people still come if retail were closed?
02

Commerce supports belonging

Vendor economics matter, but the public realm cannot feel paywalled, over-programmed or organized around extraction.

Operating test: Is free everyday use protected?
03

Year-round means operationally credible

Snow storage, wind, drainage, darkness, heating strategy, maintenance, washrooms and accessible routes are first-order design inputs.

Delivery test: Does February work without theatre?
04

Evidence earns expansion

One flagship is phased through measurable demand, safe operations, community benefit and stewardship capacity—not optimism.

Governance test: What evidence unlocks the next layer?
GuestBelonging, beauty, ease
CommunityAccess, food, connection
VendorViable trade, fair terms
MunicipalityManaged impact, public value
StewardshipLandscape improves over time

02 · Decision architecture

Replace the implied timeline with evidence-based stage gates.

Dates should be outputs of due diligence, approvals and procurement. The board advances only when each gate has evidence, accountable ownership and an explicit no-go condition.

G0

Concept integrity

Vision, audience, experience principles, status language and governance charter.

Current foundation
G1

Demand validation

Resident, vendor, partner and seasonal programming evidence with bias controls.

In progress
G2

Site control

Qualified property, control structure, constraints register and exit rights.

Not achieved
G3

Feasibility

Planning, servicing, environmental, transportation, operating and capital cases.

Depends on site
G4

Entitlements

Municipal pathway, required studies, agency coordination and approval conditions.

Not started
G5

Capital close

Approved scope, contingencies, sources, uses, covenants and downside capacity.

Not started
G6

Delivery

Issued design, permits, procurement, commissioning and operational readiness.

Not started
G7

Operate & learn

Safe opening, service standards, measured outcomes and evidence-led expansion.

Future gate
Mandatory gate packetDecision requestedEvidence indexRisk movementCapital impactCommunity impactNamed ownerStop conditions

03 · Delivery readiness

Build a disciplined review system before making major commitments.

The current website explains purpose well but does not yet provide a complete decision-ready evidence structure. Blueprint 2.0 separates public enthusiasm from confidential diligence and requires every assumption to carry a source, sensitivity and owner.

Public-value capitalEligible grants, municipal or agency participation, conservation and infrastructure programs—only when qualified.
Patient aligned capitalMission-aligned equity, land partnerships and long-duration structures matched to the stewardship horizon.
Commercial capitalDebt or return-seeking capital sized only after resilient operating cash flow is evidenced.
Earned reinvestmentOperating surplus reinvested into landscape, maintenance, resilience and later phases.

Minimum decision-review package

  • Site control instrument and title/encumbrance review
  • Sources-and-uses model with escalation and owner contingency
  • Base, downside and severe-downside operating cases
  • Phased scope with independent cost validation
  • Working-capital and ramp-period assumptions
  • Insurance, tax, utility and lifecycle reserve assumptions
  • Vendor demand evidence separated from expressions of interest
  • Long-term obligation and continuity risk analysis
  • Community-benefit commitments with measurable cost
  • Data room index, version control and decision log

Core

Recurring place-based income

  • Vendor and maker occupancy
  • Food and beverage participation
  • Programs, workshops and memberships
  • Appropriately scaled parking or mobility services

Seasonal

Program-led income

  • Curated markets and festivals
  • Winter and shoulder-season experiences
  • Ticketed learning where free access remains protected
  • Destination partnerships

Aligned

Non-extractive support

  • Sponsorship and recognition
  • Philanthropic and community-giving programs
  • Grants tied to eligible public outcomes
  • Institutional programming partnerships

Guardrail

Do not underwrite

  • Unvalidated attendance
  • Unapproved grants
  • Uncontracted vendors or sponsors
  • Event revenue that compromises resident trust

04 · Municipal and regulatory strategy

Lead with a constraints map and public-value case—not a finished rendering.

The municipal experience should make review easier: one accountable contact, one assumptions register, clear stage language, complete study ownership and early acknowledgment of neighbourhood and infrastructure impacts.

1

Pre-consultation

Confirm planning pathway, agencies, complete-application requirements and decision authorities.

2

Constraints baseline

Natural heritage, source water, agriculture, archaeology, servicing, access, hazards and adjacent uses.

3

Concept options

Compare footprints and phasing against constraints before selecting a preferred plan.

4

Impact studies

Transportation, noise, light, stormwater, ecology, servicing, waste, emergency access and fiscal impact as required.

5

Public dialogue

Publish what changed, what cannot change, mitigation commitments and unresolved issues.

6

Entitlements

Track conditions, securities, agreements, agency clearances and expiry risk in one register.

7

Permits & inspection

Building, fire, health, accessibility, conservation, sign, occupancy and operational approvals.

Municipal value case

Present evidence against municipal priorities rather than generic economic-development language.

  • Local food-system resilience and entrepreneurship
  • Managed rural or edge-of-settlement tourism
  • Public realm, trails, habitat and education
  • Year-round community gathering capacity
  • Transparent traffic, noise and servicing mitigation
  • Employment quality and local procurement reporting

Approval risks currently underrepresented

  • Use permissions may not fit a single zoning category
  • Wetland, water, agricultural and natural-heritage constraints can reshape the plan
  • Parking, traffic and event peaks may drive site capacity
  • Private servicing can limit food, washroom and fire-protection intensity
  • Noise, lighting and operating hours affect resident acceptance
  • Accessibility applies to routes, grades, surfaces and operations—not only buildings

05 · Experience and physical design

Design the day as a sequence of emotional and operational thresholds.

The master plan should be evaluated as an arrival-to-departure journey with service movement, weather, accessibility, safety and resident impacts layered into every moment.

01

Before arrival

Clear status, hours when operating, accessibility, transit, weather, capacity and what is free.

02

Threshold

A calm, legible arrival that separates guest movement from deliveries and emergency access.

03

Orientation

One intuitive choice: active heart, quiet nature loop, family route or accessible short loop.

04

Discovery

Alternating compression and release: market energy, garden learning, shade, water and open lawn.

05

Belonging

Enough free seating, shelter, washrooms and informal space to stay without buying.

06

Return reason

Seasonal landscape, changing makers, stewardship progress and community rituals.

Design layerRequired standardFailure mode to prevent
Universal accessContinuous routes, rest intervals, sensory choice, accessible play and program design.A compliant building inside an inaccessible landscape.
Four-season comfortSun, wind, rain, snow, ice, drainage, lighting and warming strategy modelled together.A summer rendering marketed as year-round.
Back of houseDeliveries, waste, grease, utilities, storage, staff and emergency movement separated but efficient.Service conflicts that degrade the public realm.
Resident interfaceBuffers, hours, event caps, lighting cut-off, noise monitoring and complaint response.Community benefit undermined by neighbour fatigue.
Landscape stewardshipEstablishment plans, succession, irrigation, invasive control and lifecycle funding.Nature-first branding without funded horticulture.

06 · Operating model

Design the organization with the same discipline as the site.

CommonGround requires an accountable place-management model spanning guest service, vendor success, facilities, landscape, programming, food safety, security, community relationships and data governance.

Accountable operatorCommonGround Place Management

Owns standards, safety, stewardship, curation, reporting and the integrated guest experience.

Guest & community

Welcome, accessibility support, feedback, volunteer coordination and resident liaison.

Vendor success

Transparent selection, onboarding, shared services, performance support and fair exits.

Place & landscape

Preventive maintenance, horticulture, snow, cleaning, utilities and asset lifecycle.

Programming

Seasonal calendar, capacity, noise, permitting, partners, cancellations and learning outcomes.

Safety & compliance

Emergency plans, food/public health, inspections, incident review, insurance and training.

Finance & data

Budget control, cash, procurement, privacy, cybersecurity, reporting and evidence quality.

Vendor experience: replace “application” with a transparent lifecycle

  1. DiscoverFit criteria, costs when approved, accessibility and operating expectations
  2. Express interestLow-friction, non-binding profile
  3. ValidateDemand, product, readiness and shared-value review
  4. SelectPublished rubric, conflicts process and mix planning
  5. OnboardAgreements, insurance, food safety, systems and training
  6. OperateService support, data, maintenance and issue resolution
  7. Improve or exitFair review, coaching, renewal and transition

07 · Resilience, technology and public value

Make long-term stewardship measurable, fundable and secure.

Sustainability, AI and community impact should not be feature lists. Each needs a baseline, accountable owner, operating budget, privacy boundary and outcome review.

Regenerative place

Landscape and infrastructure

  • Protect and improve existing ecological assets before adding features
  • Water balance, low-impact stormwater and drought planning
  • Embodied-carbon and adaptive-reuse analysis
  • All-electric and low-energy scenarios tested against resilience
  • Waste prevention, organics, reusable serviceware and vendor standards
  • Lifecycle reserves for landscape and building systems

Community compact

Benefits with accountability

  • Affordable and free access commitments
  • Local procurement and entrepreneur participation reporting
  • Food recovery and food-security partner protocols
  • Indigenous engagement appropriate to site and duty context
  • Youth, older-adult and disability inclusion in co-design
  • Annual public impact and issue report

CommonGround One

Technology in controlled layers

  • Start with CRM, document control, forms and content governance
  • Add vendor onboarding and maintenance workflows only when operations require them
  • Use AI for document classification, inquiry triage, forecasting and knowledge retrieval with human review
  • Never use opaque scoring for vendor, volunteer or community access decisions
  • Minimize personal data, define retention and require role-based access
  • Maintain manual fallbacks for safety and public service
Minimum digital controls before scaleMFA and least privilegeEnvironment separationBackups and recovery testsVendor security reviewIncident responsePrivacy impact assessmentsAudit logs

08 · Enterprise risk

Manage the risks that can quietly destroy trust, capital or operating quality.

The register below focuses attention on structural risks. Ratings are directional review priorities, not claims that a specific site condition exists.

RiskExposureRequired controlGate owner
Site does not support the experience or intensityCriticalConstraints-first site rubric, option comparison, exit rightsDevelopment lead
Capital cost outruns operating capacityCriticalPhased design-to-cost, independent estimate, downside covenant modelBoard / finance
Year-round promise is operationally weakHighWinter operations prototype, comfort modelling, lifecycle budgetDesign / operations
Neighbour impacts erode municipal supportHighResident compact, event caps, noise/light monitoring, escalation protocolMunicipal lead
Vendor churn weakens quality and trustHighTransparent economics, selection rubric, shared services, renewal processCommercial lead
Landscape quality declines after openingHighEstablishment contract, stewardship staffing, lifecycle reservePlace director
Data, AI or payment systems create harmMediumPrivacy by design, limited automation, security controls, manual fallbackTechnology owner
Mission drifts toward event or retail dependenceHighPublic-realm KPIs, free-access covenant, board mission reviewBoard chair

09 · Digital estate redesign register

Every route receives a job, an audience and a measurable next decision.

The current estate contains useful work but duplicates journeys and mixes public storytelling with diligence, operations and administration. This register is the governing redesign backlog.

10 · Immediate mandate

Stop adding surface area. Start closing evidence gaps.

The next version of CommonGround should be earned through site intelligence, municipal pre-consultation, independent feasibility, operating prototypes, community evidence and disciplined governance. Digital work should make those decisions easier—not make the project appear further advanced than it is.

  1. Establish governance.Board mandate, decision rights, stage-gate owners, risk register and document control.
  2. Build the diligence spine.Site rubric, municipal pathway, capital model, operating model and data room.
  3. Run real-world prototypes.Validation market, winter operations, vendor workflows and community-benefit tests.
  4. Consolidate the digital estate.Audience-led navigation, one participation intake, status-linked content and protected admin.