Not every building in a portfolio behaves the same. A lifestyle center might give tenants a tighter radius restriction than a power center across town. A trophy asset might escalate differently than a value-add. Per-building defaults make those differences automatic: when your team starts a new draft for a given building, the right starting values are already there.
01How it works
This isn't a screen you configure yourself. The defaults that vary by building, or by group of buildings, are encoded by your implementation team during onboarding and updated as your standards evolve. When a drafter picks a building from the dashboard, the platform applies that building's specific defaults to the new document — base rent rules, restriction radii, escalation conventions, fallback language, whatever your portfolio needs to differ.
You won't see knobs. You'll see correct documents.
02When something needs to change
If a default is wrong, or your standards for a property have shifted, tell your implementation team. The building (or the group) and the new value is enough. The next draft against that building reflects the change. It's a normal request, not a support ticket.
NoteWhy it's not self-service. Per-building defaults sit underneath conditional logic that's tuned to each property. Getting one wrong silently breaks downstream documents — a wrong escalation compounds for a decade, a wrong radius gets locked into a dozen leases — so we encode them once, with you, and keep them consistent.
The buildings themselves live in building management. The values these defaults pre-fill are the same fields you see on the deal terms screen when you draft a new document.