Glossary
Precise definitions of the terms that anchor Cornerstone’s work.
Experience intent
The defined, explicit statement of what a development is designed to feel like for the people in it; the quality of daily life that a developer has committed to delivering through the positioning, marketing, and design of a project.
Experience intent is the brief against which operational decisions are evaluated: does this sourcing strategy, technology investment, or governance model serve the experience that was promised? In its absence, operational decisions default to cost minimisation, which rarely produces the experience the development was sold on.
Place experience
The sum of what it feels like to be in a development: not the physical environment itself, but the lived quality of that environment as experienced by the people in it. In master developments, place experience is determined by the operational layer: the FM and CM services, the community infrastructure, the quality and responsiveness of the people and systems that run the place day to day.
Place experience is distinct from place design. Architecture creates the form; place experience is what the form delivers, or fails to deliver, in practice.
Operating model
For a development entity, an operating model is the governance architecture, processes, and tools that translate strategic intent into operational reality. It defines how decisions are made (delegation of authority), how work gets done (playbooks and process design), what information is trusted (single source of truth), and how the organisation learns and improves over time. An operating model is not an organisational chart, though an organisational chart is part of it. Its primary test is not whether it looks right on paper but whether the organisation actually runs that way.
Most developer operating models describe how the organisation should work. The ones that function describe how it does work, and design from that reality forward.
Operator model
The governance architecture, processes, and capabilities that enable a developer’s own operations function to run a place post-handover: managing service providers, governing the community, holding FM and CM performance to account, and sustaining the experience the development was sold on. The operator model is distinct from the development model (how the organisation plans, designs, and builds) and is typically commissioned as a separate engagement at or approaching handover.
The transition from development model to operator model is the moment at which most developments lose ground. The organisation that built the place is not the same organisation that needs to run it, and few developers design that transition deliberately.
PROA (Public Realm Operational Assets)
The physical infrastructure required to operate the public realm of a master development. PROA is sized and specified against the experience the development has promised to deliver, not against available space or convention.
Getting PROA right in scale, location, and design intent is one of the most consequential operational decisions made at masterplan stage. Getting it wrong adds cost, constrains experience, and cannot easily be corrected after construction.
Activation strategy
The designed approach to how a development’s shared and community spaces are programmed and used to deliver the experience intent. An activation strategy answers a specific set of questions before a place opens: what should happen in the shared spaces, for whom, at what frequency, and how is that programming sustained operationally over time. It is distinct from events management or marketing programming: it is an operational design discipline that determines how spaces generate value for residents and, where relevant, revenue for the developer.
Activation designed reactively, after handover in response to resident requests, produces a place that feels unmanaged. Activation designed before the masterplan is fixed produces a place that feels intentional from day one.
Strata framework
The governance structure, community rules, and operational principles that define how a residential or mixed-use development is owned, managed, and experienced in common. A strata framework covers the constitution and mandate of the owners association, the allocation of shared costs and responsibilities between owners and the developer or manager, the community guidelines that govern how residents use shared spaces, and the dispute resolution mechanisms that give the governance structure practical authority.
A strata framework drafted for legal compliance produces a governance structure that satisfies registration requirements. A strata framework designed to support the experience promise produces a governance structure that sustains the community the development was sold on.
Service charge
In master development, a service charge is the mechanism through which residents and owners contribute to the cost of operating the shared environment of the development: public realm maintenance, community management, security, landscaping, and the infrastructure that supports them. It is often framed as a cost recovery tool. Its more accurate frame is an experience delivery mechanism: the level and structure of the service charge determines what can be delivered, and the quality of delivery determines whether residents regard it as fair value or as an ongoing grievance.
A service charge set against a cost model produces the minimum viable operation. A service charge set against an experience brief produces a defensible value proposition for residents.
Shared space
In master development, shared space refers to the publicly accessible or communally managed environment of a development: public realm, community facilities, amenity areas, and the infrastructure that runs them. Shared space is distinct from private units or exclusively owned assets.
Its quality, management, and operational cost structure determine how a development is experienced by residents, workers, and visitors on a daily basis and, over time, whether it holds its value and attracts long-term residents rather than short-term occupiers.
The tier model
A structured approach to technology investment decisions in master development portfolios in which the level of technology specification is explicitly matched to the product positioning and resident profile of each project or building type. Rather than applying a uniform technology stack across a portfolio, the tier model establishes distinct investment levels, each defined by the experience promise and resident profile at that positioning level, and each carrying a coherent and defensible technology specification.
The number of tiers and their definitions are determined by the developer’s specific portfolio, not by a fixed standard.
Place intelligence
The discipline of making technology investment decisions for a development that are derived from competitive intelligence, experience intent, and product positioning rather than from available technology. Place intelligence starts with the question: what does this place need to do for the people in it? And then asks: what technology, at what level of investment, serves that? The result is technology that enhances the place experience without being noticed.
Place intelligence is not a product category or a technology standard. It is a design discipline applied to technology investment decisions.
