Real estate operations
Make property requests easy to route and evidence.
We map the workflows around enquiries, leases, maintenance and reporting, around the property systems you use. A request never disappears between a tenant, a contractor and an inbox.
Property decisions, lease interpretation, tenancy rights, legal or tax treatment, regulatory compliance, contractor appointment, expenditure authority and completion acceptance stay with your authorised people and specialists.
What you keep asking
The questions a tenant, a contractor or a landlord asks before you can.
A tenant reports a leak by phone on Friday. The note goes to one person, the contractor is booked by another, the invoice arrives at a third, and on Tuesday the tenant calls again because nobody can say whether anyone went. The lease renewal due the same week sits in a calendar reminder.
Did anyone actually go?
The leak was reported on Friday by phone. One person took the note, another booked the contractor, and on Tuesday the tenant calls back because nobody can say.
What changes
One request record carries priority, owner, booking and evidence, so the answer is on screen rather than in someone's recollection.
Which renewals are due this quarter, and who is on them?
Lease dates sit in calendars and a spreadsheet. The date is known; who reviews, advises and acts on it is not.
What changes
Each milestone has a named owner and a next action, with a route to the adviser where one is needed.
Why did an invoice arrive for work nobody approved?
The contractor was booked, the job changed on site and the approval never caught up. The first record of the change is the invoice.
What changes
Expenditure authority stays with your people. The request shows who approved what, and when, before the invoice does.
What happened to Saturday's enquiry?
Enquiries arrive by portal, email and phone. The ones that arrive outside hours are answered when someone remembers them.
What changes
Every enquiry gets an owner and a next action on arrival, whichever channel it came through.
What is underneath
Where a request loses its owner.
Each question comes back to an absence, not a missing tool. There are six: no named source record, no held status, no written authority, no outstanding-items list, no agreed definitions, no exception route. These are the places they open up here.
- Enquiry ownership
- Property or tenant enquiries arrive through several channels without one current owner or next action.
- Viewing and application handoffs
- Status is copied between systems while exceptions and approvals sit in inboxes.
- Lease milestones
- Dates and document references exist, but who reviews, advises and acts on them is not explicit.
- Maintenance intake
- Requests arrive without an agreed priority, owner, contractor handoff, evidence requirement or escalation path.
- Reporting and documents
- Operating views are rebuilt by hand, and required records are chased without a status anyone trusts.
Worked example
A maintenance-request flow, step by step.
Worked example. The business, people and systems shown are fictional. The property, tenant, roles, contractor and systems are invented.
- 01Request recorded with the agreed intake fields
- 02Operating owner and any urgent route assigned
- 03Priority and contractor decision by the authorised person
- 04Appointment, dated status and evidence recorded
- 05Closed only when the authorised party accepts the evidence
The operating layer
Keep the property systems that earn their place.
Commercial path. Free audit first, then a paid Blueprint, then only the deployment you agree. See how each layer is priced
What we configure
Your property-management, lease, accounting and contractor systems stay the specialist sources. We give every request one record that carries its priority, its owner, its contractor booking and its evidence, once the Blueprint confirms:
- the agreed source for each field;
- permissions and who is responsible for access;
- migration and connection limits;
- approval and exception routes;
- what is recorded and what counts as done.
What stays with your firm
The decisions ScalePass never makes
Property decisions, lease interpretation, tenancy rights, legal or tax treatment, regulatory compliance, contractor appointment, expenditure authority and completion acceptance remain with your authorised people and specialists.
A connected record does not itself establish legal compliance, contractor performance or financial accuracy. Managed Operations covers named recurring queues only where separately scoped and agreed.
Start
Bring us the request that disappears between systems.
Describe where it enters, who decides what happens next and how completion is evidenced, and you get a written read of where it stalls. Do not provide credentials or unnecessary tenant, financial, legal or identity information.