Planned UnifyOS module · Leasing intelligence
Leasing decides what the delivery team is later held to: fit-out obligations, landlord works, rent-commencement triggers, brand and design conditions. Today that intent lives in lease documents and negotiation email, and reaches delivery as an incomplete summary.
The planned leasing module reads the agreed terms and turns them into structured obligations that UnifyReview and UnifyRetail OS can enforce, so what was signed is what gets reviewed and handed over.
In design — shaped with landlord and developer input
These modules are roadmap positions within UnifyOS. They are in design or scoping, are not available today, and no delivery dates are committed. They are published so clients can see the direction of the platform and shape it — not to imply released functionality.
The problem
The intent
Data it would work from
Capabilities
Worked through with delivery teams running live completions, so the design starts from how handover actually behaves.
Agreements for lease, executed leases and heads of terms are read into a structured obligation set — fit-out scope, landlord works, design conditions, brand requirements, access and rent triggers — with the clause reference kept against every extracted item.
Landlord and tenant responsibilities are mapped item by item against the unit record, so the split is settled once from the signed terms rather than re-argued during fit-out.
Access, possession, fit-out period, opening and rent-commencement dates are tied to programme milestones, so a slip in delivery shows immediately as a leasing consequence.
Tenant-specific design and brand conditions are passed into the UnifyReview rule pack for that unit, so a fit-out submission is reviewed against the terms actually signed.
Each obligation carries a state — outstanding, satisfied, waived or varied — with the evidence and approval behind the change, giving an auditable position at any date.
Across a portfolio, the module reports what has been committed to tenants: landlord works exposure, incentive obligations, recurring conditions and where the same clause creates repeated delivery risk.
What it produces
Structured obligation register
Every obligation per unit, with clause reference, owner, due trigger and current status.
Works-split schedule
Landlord and tenant scope mapped item by item, ready for the delivery team.
Leasing milestone calendar
Access, fit-out, opening and rent-commencement dates aligned to the programme.
Tenant condition pack
The design and brand conditions handed into compliance review for that unit.
Portfolio commitment report
What has been promised across the portfolio, and where those promises repeat.
Who it is for
Leasing and commercial teams
Hand over agreed terms as structured obligations instead of a summary email.
Delivery and project managers
Start fit-out knowing exactly what the lease commits the landlord and tenant to.
Landlords and asset owners
See portfolio-wide exposure created by leasing commitments before it lands in delivery.
Tenant coordination teams
Review submissions against the conditions in the signed document, not a restated version.
Where the line sits
The boundaries matter as much as the capability.
Roadmap position · Next
Sequencing is driven by dependencies, not by marketing convenience. Nothing here is available today and no delivery date is committed.
Depends on
Already in place
Still needed — In design
See where this sits against every other module on the UnifyOS roadmap.
Inside UnifyOS
Every module shares the same governance, evidence and audit standards, so intelligence carries forward instead of being rebuilt.
Tenant-specific lease conditions become part of the rule pack a fit-out submission is reviewed against.
Access, possession and opening obligations line up with the unit delivery and handover sequence.
Lease and tenant records flow in from the client's leasing or property-management platform.
Client systems connect through IntelliBridge™, so this module would read from and write back to the platforms you already run.
Requirements from live portfolios shape what gets built first — and what gets built at all.
