A Time And A Place – rethinking project-based land tenure for community benefit

Land tenure security is treated, almost universally, as a binary good: the more permanent and unassailable a claim to land, the better the outcome for the people who depend on it. This assumption underlies most housing policy, development finance, and land reform effort worldwide, and it is correct often enough to have earned its status as conventional wisdom. But it quietly breaks down in a specific and increasingly common case - project-based development of community assets that incorporate public funding mechanisms. A project, by definition - is finite - it has a beginning, a fixed scope, and an end. Permanent private ownership, by definition, has none of those things. Forcing the second concept onto the first produces a structural mismatch that shows up, again and again, as underperforming developments, or more commonly projects with high potential that never move into the implementation stage.

An asset, by definition, is something that provides future benefit, and therefore it follows, that development of a community asset is intended to provide future benefit to a community. Implementing sustainable community strategies typically comprises two phases - the asset development phase and the asset utilization phase. There is a general consensus that the development phase is most effectively implemented using a project-management based methodology, but appropriate methodologies for the utilization phase are as diverse as the communities they serve. The connection between the two phases is a stage of the overall process that is often overlooked - the project benefits transfer step.

This isn't an argument against secure tenure or project-based development. It's an argument that security and sustainable community assets are not the same thing, that treating them as synonymous can and often does create a mismatch, and that adequate consideration of the project benefits transfer stage at the earliest planning stages of the overall process can go a long way to solving the mismatch.

A leasehold, a community land trust, or a renewable long-term license can all provide genuine, defensible security - protection against arbitrary eviction, a stable basis for investment, inheritable value - without requiring that the underlying legal structure pretend to outlast the timeframe and associated structure that it was created for. Security is about the reliability and enforceability of a claim during the period it's meant to cover. Permanence is a separate design choice about time horizon, and conflating the two forces every project into a tenure model built for a different kind of asset entirely.

The practical fix then has two key elements. First, project-based tenure instruments should be structured with the same rigor applied to the project's financing and construction elements, rather than defaulting to whatever ownership template is locally conventional. Second - the project strategy should adequately address and resource the project benefits transfer stage, ie, that stage of transition between the finite project-based development phase and the realization of benefits for the community over the long term.  A project intended to operate for three to five years should consider a tenure structure scoped to those years, with an explicit, pre-negotiated transition mechanism for what happens at the end - renewal, conversion to a different tenure form, transfer to a successor institution, or an orderly wind-down. That transition planning is usually the missing piece. Most tenure failures in finite projects don't happen because the initial arrangement was insecure; they happen because nobody designed what comes after, and a legal structure meant to be temporary calcifies into a permanent one by default, simply because reversing it later proves harder than extending it.

Matching tenure design to project lifespan is not a technicality for lawyers to sort out after the substantive planning is done. It belongs at the same table as the financing structure and the construction plan, because it determines whether the benefits of the project are actually sustained once the project itself is gone, or whether they quietly erode into disputed land and orphaned obligations the moment the funding does.