A commercial lease management portal is where a landlord or property manager keeps every tenant and lease in one list, sees upcoming lease ends on a calendar, and gets a reminder before each one expires. Lease documents sit with the lease they belong to, not in someone's downloads folder.
Pattern: TrackingDescribe it to Pory
“We manage a retail and office precinct with about 40 commercial tenants. We need one place for tenants and leases, a calendar of lease ends, reminders before a lease expires, and lease documents stored against each lease.”
Leases
| Tenant | Suite | Lease end | Status | Tenant contact | |
|---|---|---|---|---|---|
| Chai Point Café | G04 | 31 Oct 2026 | Renewal offered | Rahul Bhatia | |
| Chai Point Kiosk | K2 | 14 Oct 2026 | Active | Rahul Bhatia | |
| Harbourside Physio | L1-03 | 30 Sep 2026 | Renewed | Nadia Haddad | |
| Kowalski Legal | L2-01 | 20 Oct 2026 | Active | Piotr Kowalski | |
| Bloom Florist | G11 | 28 Sep 2026 | Vacating | Sarah Eldridge | |
| Northside Dental | L1-07 | 9 Oct 2026 | Renewal offered | Farah Siddiqui |
Showing 1–6 of 6
In plain English
A commercial lease management portal is where a landlord or property manager keeps every tenant and lease in one list, sees upcoming lease ends on a calendar, and gets a reminder before each one expires. Lease documents sit with the lease they belong to, not in someone's downloads folder. It follows the Tracking pattern: a person's or asset's history, built up over time. Pory generates it from a plain-English description, with a login for each role (leasing manager and tenant) that shows only what that role should see, and flat pricing with unlimited tenants.
What it does
Lease details lived in a spreadsheet one person understood, with tenant contacts in someone else's phone. The leasing manager keeps each lease as a row (tenant, suite, lease end, status, contact and rent) and filters by status or searches by name. Nobody digs through a spreadsheet with four tabs called Leases to find out when the florist's lease ends.
Renewal dates were buried in PDFs, so the first sign of an expiring lease was often the tenant's own email. Every lease sits on a month view by its lease end, coloured by status: renewal offered, renewed, vacating. Click a date to open the lease behind it and start the conversation weeks ahead instead of days.
Missing a notice window meant a tenant rolled onto holding-over terms nobody chose. When a lease end date is coming up, a reminder lands in the leasing manager's inbox here and by email, naming the tenant and the date. The diary check that relied on one person's memory stops being anyone's job.
Lease PDFs were scattered across email attachments, a shared drive and a filing cabinet in the back office. Each document is uploaded with its type and the lease it belongs to, so the café's renewal offer sits next to its original lease. Finding the current insurance certificate takes a filter, not an afternoon in the cabinet.
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the rows a viewer is allowed to read.
Control
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
On purpose
A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Pory keeps the service record, not the map.
Describe it in a sentence and send the invite. Unlimited tenants, flat price.
