Preferences cascade
You set wayleave preferences once for your organisation, and they apply to every building in the portfolio: processing fee, insurance minimums, notice periods, access hours, and who is named as Grantor. Individual buildings override where they need to. A building with a difficult riser can carry tighter access hours without you restating every other term, and a building whose freeholder insists on being named can do that while the rest of the portfolio names your organisation. The order of precedence runs portfolio, then building. The building wins where it has an opinion.Buildings that are not one building
Two situations that a one-building-at-a-time model handles badly. An estate or a block covering several addresses can be claimed and managed as one building. This produces a single building record covering its constituent addresses, rather than one record per address that you then have to keep in step.This is not bulk onboarding. A grouped claim produces one building, not many. Buildings are added one at a time or as one grouped building, and there is no import path.
The portfolio view
On the Portfolio tier and above, a view across every building you hold: requests in flight, agreements in force, and what is expiring. The point of it is the thing a building-by-building model cannot give you, which is knowing what is happening without going and looking. Below the Portfolio tier the same information exists, one building at a time. The tenancy schedule exports as a spreadsheet, on the same tier. This is the artefact that goes to a client, an asset manager or a valuer, so it leaves the platform as a file rather than a screen.The tenants register
A register of tenants across the buildings you hold, available on every tier rather than gated to Portfolio. It answers the question that arrives by phone: which of our buildings has this operator in it, and on what terms.Documents you can hand to someone else
Two generated documents exist because the decision often is not yours to make. Information guides, produced per building, in an operator variant and a tenant variant. The operator guide tells an incoming operator what the building requires before they ask. The tenant guide tells a prospective tenant or a letting agent what connectivity the building has and how access works. Both carry your own branding rather than Wayline’s. The recommendation report is a two-page PDF capturing the facts of a request alongside your own sign-off recommendation. Where the authority to approve sits with a client or an asset manager rather than with you, this is the artefact that goes to them: printable, signable, and readable by someone who has never logged in.Superior landlord consent
Where a head lease requires the superior landlord’s consent before an operator can install, that requirement is recorded against the request along with its status. The agreement cannot proceed to signature until the consent position is resolved. This is enforced rather than flagged, which is the difference between a checklist and a control. Once a request reaches signing the consent fields lock, so the record of what was relied on cannot be edited after the fact.What tiers actually change
Size bands are about building size, not capability. A Small building and a Large building get the same wayleave process; the price differs because the buildings differ. The tier differences that are real are the portfolio view and the tenancy schedule export, and on Enterprise, claiming a building by confirmation rather than document upload. Current prices are on wayline.uk/pricing.Quick start for managing agents
Setting up your first building and your portfolio preferences.