Montea object map

Development Opportunity

Future space in the permitting pipeline, described at regional level with a time horizon — never a pinpointed plot.

Internally: the land bank, ~3.4M sqm. Deliberately has no address, no coordinates and no plot geometry, so W1's 'never pinpoint a plot' rule is structural rather than something Coleen has to remember on every record. Kept separate from Property because the two diverge on nearly every attribute; they are reunited at the presentation layer, where the finder and the compass query both and merge on the horizon axis.

Property

A commercialisable building at a known address — standing, under construction, or leased.

147 records today. documentDownloads is empty on every one of them; brochures are stitched into the content builder instead. The Document relationship has to be first-class and visible in the edit screen or it will silently go unused again.

Unit

A lettable part of a property: hall, office, mezzanine, storage, parking, or outdoor plot.

One object with a type attribute replaces the eight building-part entry types — the same 1,044 records, one picker instead of eight near-identical ones on the most-edited content type on the site.

Certification

A third-party grade held by a building or by the company.

Covers BREEAM and EPC on buildings and S&P / Moody's / MSCI / EPRA on the company — one shape, different subject. Splits into two objects later if the shared shape ever forces a compromise on either side.

ESG Metric

One published sustainability or performance figure, at company, market or asset level.

Records rather than PDF pages — so they chart, compare year on year, filter per asset, and get cited. This is the differentiation lane no competitor in the cohort fills, and the model-level expression of W1 D2: there is no Sustainability object, only these figures woven into the assets that produce them.

Market

A country, region or city Montea operates in.

Country › region › city nesting is carried in the Parent market attribute, since an object cannot nest itself on a board. Worth taking into the country/language workshop as an object rather than a sitemap: whether Market carries content or only structure is the same decision as whether the homepage carries market-specific blocks, and it is where Michael's block-sync caveat bites.

Solution

A commercial product: rent a warehouse, build-to-suit, sale & leaseback, brownfield redevelopment.

Each solution needs its own enquiry route — the shared Sale & Leaseback form has 0 lifetime submissions. 'What we need from you' makes the Random-thoughts idea structural: tell the prospect what a good first email contains and what happens next.

Sector

A tenant industry: 3PL and 4PL, ecommerce and omnichannel, retail and FMCG distribution, manufacturing and light industrial, cold chain and food, parcel and last-mile.

Not a nav item — a content facet, consistent with W1 D5. Also the highest-value GEO surface in the model: entity-rich, question-shaped, and the natural landing point for the non-brand commercial queries the site loses entirely today.

Contact

A named person a visitor can actually reach.

Warehouse detail pages carry contact information today with zero tel: or mailto: links — a tap-to-call dead end for a B2B leasing audience. Phone and email are core content on this object, not decoration.

Client Story

A named tenant's story in a Montea building.

The raw material for the paid LinkedIn three-P engine — authored once, syndicated. Consent status is a legal field, not a workflow nicety.

Client

A tenant company Montea houses.

Optional. Only earns its place if a tenant company will ever get its own page or become filterable — otherwise it collapses into Client Story attributes. Deleting it is one update-board away.

Shortlist

A visitor's saved set of space.

Email-token persistence rather than a login: no wall in front of the lowest-commitment action on the site, survives a device switch, and captures a contact at the moment of demonstrated intent — a better lead than the newsletter has ever produced.

Enquiry

A prospect's request, carrying its own context.

An object rather than a form — which is what lets one enquiry reference several properties, a shortlist, or a development opportunity that does not exist yet. Nothing in the competitor cohort does this. It is the most direct structural answer to 18 lifetime leads across 13 forms.

Job

A live vacancy.

Mileway is the benchmark: careers as a filterable feed first, culture content second.

Article

An insight, post, podcast episode or video.

Parked pending an editorial owner (NAV-02 open question), modelled anyway so it is not retrofitted later. Note the Transcript field: podcast transcripts are the cheapest GEO content Montea already owns and currently does not publish — 12 episodes sitting unindexed.

Share

The Montea share. One record, not a page of prose.

SEGRO carries a live ticker in the global header and CTP publishes the price as plain text. The utility strip already reserves room for it.

Dividend

One fiscal year's dividend, as a record rather than a page.

The top three search queries on the entire site concern the dividend. It is currently a page. It should be a series.

Report

An annual, half-year or ESG report, or a results presentation.

Supersession is carried in the Supersedes attribute, since an object cannot nest itself. The Canonical flag is what stops three nav links pointing at one annual report from coming back.

Press Release

A published announcement — 278 of them, at 26 to 38 a year.

One metadata field, Category, turns 278 flat entries into the filtered stream every peer already has, and settles the financial vs non-financial split W1 found confusing at ~95% overlap. 39 releases are live in EN and disabled in NL/FR today with nothing flagging the drift to authors.

Calendar Event

A results publication, AGM, capital markets day or silent period.

Analyst Coverage

An institution covering the Montea share.

Optional. WDP and CTP both publish coverage and consensus; drop it if Montea would rather not.

Document

Any downloadable file with a life of its own.

~2,800 files across three overlapping volumes with no taxonomy and no filtering UI. This object plus one consolidated type list is the document-management decision taken in the content model rather than in a vendor contract.