Branditify

Property Management System

The tenant changes. The lease changes. Unit 2048 does not.

One unit, from ready to occupied to a renewal decision and back to ready — with the occupant, the lease and every request that has touched it attached to the same file.

Where property management ends

Park View ResidencesPR-118 · Residential

  1. U-20724thRenewal review
  2. U-20613rdOccupied
  3. U-20482ndOccupied
  4. U-20311stReady
  5. U-2019GroundRequest open
U-2048OccupiedSecond floor2 BHK · 1,040 sq ft
Occupant
Maya K.
Lease
LS-2048active
Term
Month 4 of 11
Rent state
Current
Open request
None
Renewal window
Opens at 3 months left

NextNothing due

Illustrative interface · sample dataStep through the unit. The file keeps what the lease does not.

Occupied. U-2048 is occupied. Next: Nothing due.

An empty unit is still a record. It has a specification, a history of who has lived in it and every request ever raised against it — none of which arrives with the next tenant.

A signed lease is not an occupied unit. Somebody has agreed to live here and nobody has moved in, and a system that cannot hold those apart will report the wrong occupancy for a fortnight.

The quiet state, and the one most software is bad at. Nothing is happening, and everything about who is here and on what terms still has to be answerable in one place.

A request is not a ticket in a separate tool. It belongs to this unit, it stays in this file after it closes, and the next occupant’s surveyor will want to read it.

Two months of the term are left, which puts this lease inside the renewal window the business configured. Nothing has expired; a decision has become due.

A new term on the same unit, with the same file underneath it. The lease reference changes; the request history, the specification and the occupancy record do not.

The record underneath

One of these lists never changes.

A property system is worth having because of the left column. Every tool can hold the right one for as long as it happens to be true.

The unitTrue for as long as the building stands

Property
Park View Residences
PR-118
Unit
U-2048
Second floor
Specification
2 BHK · 1,040 sq ft
Recorded once
History
Every occupant, lease and request
Kept

What hangs off itTrue until it is not

Occupant
Maya K.
Third on this unit
Lease
LS-2048
Second term
Rent state
Current
A state, not a ledger
Open requests
None today
Four closed, all kept

Sheets hold the right-hand column. They lose the left one the moment somebody starts a new tab for next year.

What is property management software?

Property management software runs the ongoing operation of property you already have under management: the properties and units themselves, who occupies each one, the lease or rental agreement they occupy it under, the state of that occupancy, the requests raised against the unit and the renewal decisions that come round. It is the record that survives every tenant.

What does a property management system manage?

Properties and their units, occupant records, leases and rental agreements with their terms and renewal state, occupancy, unit-level requests and their history, documents and references attached to any of those, who in the business is allowed to see or change what, and the same picture across more than one property.

What is tenant management software?

It is the occupant half of the same system — who lives in or uses a unit, under what agreement, with what requests open and what is due next. It is worth saying that a tenant is a state of a unit rather than the record itself, because a well-built system has to answer questions about a unit that is empty.

The lease clock

A lease is a state, not a PDF in a folder.

Eleven months, a window the business sets, and one decision that becomes due inside it.

LS-204811-month termRenewal window: last 3 months

StartEnd of term

Where LS-2048 is nowMonth 9 of 11. 2 months left, and the window opens at 3 — so the decision is due now.

  1. StartTerm begins, occupancy starts
  2. ActiveNothing due — the state most software forgets to model
  3. Renewal windowThe decision becomes due, on a threshold the business configured
  4. DecisionRenew on new terms, or begin the handover

What the system does with the agreement itself

It records the reference, the term, the renewal state and whichever fields the business needs to search on, and it holds the approved document against the unit. It does not draft the agreement, stamp it, register it or tell you whether it is enforceable. Those follow the operation’s own legal process and its own source documents.

The window is a number somebody in the business chooses — ninety days, sixty, whatever the operation actually works to. It is not a statutory notice period, and nothing on this page is legal advice about one.

Every lease that quietly expired was recorded correctly somewhere. It was just recorded somewhere nothing was watching.

What is lease management software?

Lease management is the part of a property system that treats an agreement as a running state rather than a stored file: the term, where the lease currently is inside it, when the renewal window opens, what the decision was and what the next term became. The document still matters and is held against the unit — but the thing you can act on is the state.

Can property management software track renewals?

That is most of the point. The system knows each lease’s term and the threshold the business set for reviewing it, so a renewal surfaces as work that is due rather than as something somebody remembers. What it will not do is invent a notice period — that threshold is configured, not assumed.

Can rental and lease management be part of one system?

They are one system. A rental agreement and a lease are the same relationship between a unit and an occupant, described differently by different operations, and splitting them across two products would mean the same unit had two records. Rental terminology, lease terminology and tenancy terminology all describe states of the unit file.

Renew or vacate

Two answers. One record either way.

The lease ends in both branches. The unit ends in neither.

RenewA new term on the same unit

Unit
U-2048
Occupant
Maya K.
Lease
New reference, new term
Unit file
Carries on

Unit endsOccupied

LS-2048The decisionDue inside the window11-month term, inside the renewal window

VacateA handover, then the unit again

Unit
U-2048
Occupant
Ends with the term
Lease
Closes on the handover
Unit file
Carries on

Unit endsReady

Two of these 4 rows hold whichever way the decision goes — the unit and the unit file. That is exactly why the file belongs to the unit and not to the tenancy.

What a handover actually is here

A state the unit passes through: keys and access accounted for, documents received, a condition note recorded, open requests closed or carried. It is an operational checklist the business defines — not a certified inspection, not a legal handover and not a deposit settlement.

Software that models the tenancy has to be told the unit exists. Software that models the unit already knows.

The ongoing relationship

The request belongs to the unit.

Not to the tenant who raised it, and not to a ticketing tool nobody opens after it closes.

RQ-2048U-2048Leak in the kitchen ceilingRaised by the occupant

  1. RaisedAgainst the unit, with the occupant recorded as the source
  2. AssignedTo whoever in the business owns this kind of work
  3. In progressA state somebody updates, visible to whoever needs it
  4. ClosedWith a note, and it stays on the unit afterwards

And it is still there in four years

When the same ceiling is raised again by a different occupant under a different lease, the file already says what happened last time and who did it. A request that lives in a mailbox or a chat thread cannot do that.

Where this stops

This page owns which unit has a problem, who owns the work and what state it is in. Which technician goes, when they are scheduled, what the visit found and how the job is closed out is a service-execution system — a different record with a different shape, and one that would be connected rather than merged.

Nothing here dispatches anybody, promises a response time or scores a request by urgency on its own. Priority is whatever the operation decides it is, and the system records the decision rather than making it.

The unit remembers. That is the entire difference between a property system and a shared inbox.

What happens to the record when a tenant leaves?

Nothing is deleted. The lease closes, the occupancy ends and the unit returns to a ready state with everything still attached to it — who lived there, what was raised, what was repaired and what the condition note said at handover. That history is the reason the next tenancy starts from something rather than from nothing.

Can tenant requests be managed digitally?

Yes, and the useful part is where they live. A request is raised against a unit, assigned to whoever owns that kind of work, moved through states somebody updates and closed with a note — and it stays on the unit file afterwards. What makes it worth having is not the ticket; it is that the next person asking about that unit can read it.

Property management or field service software?

They meet at one moment. A property system owns the unit, the occupant and the fact that something is wrong; a field service system owns the technician, the visit and the completed job. An operation that runs its own maintenance team eventually wants both, connected at the point where a request becomes a scheduled visit.

One unit, five questions

Everyone asks about U-2048. Nobody asks the same thing.

Five systems, one unit, and only one of them is this page.

Who is in it, on what terms, and what is due?

Property ManagementThis page

The unit, the occupant, the lease and its renewal state, the requests raised against it and the history of all of them. This page.

U-2048

  1. Who might take it, and where did that conversation get to?

    CRM

    Prospects, enquiries and the pipeline before anybody signs. A CRM closes when the deal closes; this record starts there.

    CRM
  2. When is somebody coming to see it?

    Booking

    Viewings, appointments and resource slots. A viewing is an event in a calendar; a tenancy is a state that runs for a year.

    Booking Platform
  3. What can the occupant see and raise themselves?

    Client portal

    A controlled surface onto some of this record — selected requests, documents and updates — for people outside the business.

    Client Portal
  4. What did the money actually do?

    Accounting

    Books, ledgers, statements and tax treatment. This record can hold a rent state; it is not the place any amount is reconciled or accounted for.

Property Management is not a real-estate CRM with a lease tab, and it is not an accounting product that happens to know about buildings. It is the operating record of a unit.

And the two sector pages next door

Marketing a development and selling units in it is a developer’s journey; listings, buyer matching and referrals are a broker’s. Both are live pages about a sector rather than a system, and both stop where the keys are handed over.

Real Estate Developers Property Brokers

Every one of these is a real system with a real owner. A property page that answers all five is a page nobody will trust with any of them.

What it meets · what changes size

The parts every property build gets, and the parts that are a decision.

Some of this is the system. The rest is scoped from how the operation actually runs.

  1. Properties, units and specificationsIn every buildThe record everything else hangs off, at whatever depth the operation needs — a building of units, a row of shops, a set of scattered houses.
  2. Occupants and leasesIn every buildWho is in a unit, under which agreement, for what term, and every occupant and agreement that came before.
  3. Occupancy and renewal stateIn every buildDerived from the lease rather than ticked by hand, with the renewal threshold configured per operation.
  4. Requests against a unitIn every buildRaised, assigned, moved through states, closed with a note, and kept on the unit afterwards.
  5. Documents and referencesIn every buildThe approved agreement, a condition note, whatever the operation needs to find again, held against the unit rather than in a folder tree.
  6. Roles and accessIn every buildWho can see a unit, who can change a lease, who can close a request, and who can only look.
  7. Multiple propertiesScoped per projectMore than one property, with the same units-and-leases model underneath. Worth naming early because it changes how access and reporting are shaped.
  8. An occupant or owner portalScoped per projectA controlled outside surface for raising requests, reading updates and finding documents. Real work, and a real decision about what those users may see.
  9. Rent state and payment connectionsScoped per projectA state on the record is one thing; connecting to a payment provider or an accounting system is another, and it is shaped around whichever ones the business already uses.
  10. Verification workflowsScoped per projectWhere an operation checks an occupant before a tenancy, the system can carry the workflow and the outcome. The checking itself belongs to whichever approved provider the business uses, and is never assumed.
  11. Move-in and move-outScoped per projectAccess accounted for, documents received, a condition note, open requests resolved or carried. An operational checklist, defined by the business.
  12. NotificationsScoped per projectEmail, SMS or a messaging channel for renewals and request updates. Each channel is its own provider decision rather than a checkbox.
  1. Number of units, and how many propertiesThirty units in one building and three hundred across nine are different systems to model and to give access to.
  2. How many people touch a unitOne owner-operator is configuration. An operations team, an owner and an occupant are three role models.
  3. Whether outsiders get a loginA portal is the single biggest scope decision here, because it changes what every screen is allowed to show.
  4. How much of the request flow you runRecording a request is small. Running the work behind it is a second system.
  5. Which systems it has to meetAccounting, payments, a CRM, a messaging channel — each connection is real work and worth doing on purpose.
  6. Commercial or residential rulesEscalations, common-area terms and unit-specific clauses change the lease model, so they are settled before it is built.

What we check before anything is quoted

How many properties and units, how the leases actually differ from each other, who needs to log in and what each of them may see, what happens today when a request comes in, which systems must keep working, and where the current records live. That conversation shapes the build far more than a feature list does.

Property management vs real estate CRM — what is the difference?

A CRM manages people who might do business with you: leads, enquiries, viewings booked, offers made, the pipeline. A property management system manages what happens once they have — the unit, the occupant, the lease, the renewal and the requests. The category itself draws this line at the signature: a CRM’s job finishes where a property record’s begins.

Property management vs booking software?

Booking owns an event — a viewing, an appointment, an amenity slot — that occupies a moment in a calendar. Property management owns a relationship that runs for a term and then has to be decided again. An operation can genuinely need both, and they connect where a viewing turns into a tenancy.

Property management vs accounting software?

A property system can hold a rent state — current, due, under review — because the operation needs to know it while looking at a unit. Accounting owns the money itself: what was received, how it is treated in the books, what the statements say and what the tax position is. Keeping the state here and the ledger there is what stops two systems disagreeing about the same rupee.

Does property management software collect rent?

Not by default, and the honest version matters here. This system records rent as a state so an operator can see it beside the unit and the lease. Actually taking money — a gateway, a mandate, reconciliation, receipts, tax treatment — is a payments and accounting problem with its own providers and its own compliance, and it is scoped as a connection rather than assumed as a feature.

Can payment or accounting systems connect?

Yes, and it is scoped against what the other system can actually expose rather than assumed. The useful shape is usually the same: the property system stays the record of the unit, the lease and the rent state, and the money is recognised where money belongs. What is deliberately not claimed is a collection engine, reconciliation or any tax treatment.

Can tenant verification providers connect?

Where an operation already verifies occupants, the system can carry the workflow — what was requested, what came back, who approved it — and connect to the approved provider doing the checking. Branditify does not perform identity, credit or background checks, and no such capability is included by default.

Can leases and documents be stored?

Yes, held against the unit and the lease they belong to rather than in a shared drive, with the fields the operation needs to search on recorded alongside. Storing the approved document is different from producing it: the drafting, stamping and registration follow the business’s own legal process.

Can it work across multiple properties?

Yes, where the operation runs more than one. Each property carries its own units and each unit its own occupancy, and the interesting decisions are about access and reporting — who sees which property, and what a figure means when it spans several of them.

Who owns the system and the data after a custom build?

You do. The code, the database and the hosting account are yours, and every property, unit, lease and request record in it is yours. There is no per-unit licence and nothing that stops working if a relationship ends.

What determines the scope of a property management project?

Mostly four things: how many units and properties, how much the leases differ, whether people outside the business get a login, and how much of the request flow you intend to run yourself. Feature lists predict badly; those four predict well.

Going live

Getting a portfolio onto it.

The risky part is not the software. It is the week the spreadsheet stops being the truth.

  1. What exists nowA units sheet, a tenants sheet, a rent tracker, a folder of agreements, an old system nobody logs into. We look at what can genuinely be exported before promising anything.
  2. One property firstReal data, one building. It surfaces what a schema never does — units named three ways, leases with no end date, a tenant who is two rows.
  3. Map the four recordsProperty, unit, occupant, lease. Everything else attaches to those, so getting them right is the whole migration.
  4. CleanDuplicate units, closed tenancies still marked live, agreements with no unit against them. Decided with you, not silently.
  5. Import and checkLoaded, then walked through against what the operation believes is true today. Occupancy is the number that has to agree first.
  6. ReadyRoles set, the renewal window configured, and the two screens the team will actually use every day worked through with them.

Before it is the system of record

  1. Occupancy agrees with realityEvery unit the system calls occupied has somebody in it, and every one it calls ready is actually empty.
  2. Every live lease has a termA lease with no end date cannot be renewed, reviewed or reported on.
  3. The team can raise and close a request unaidedIf it needs the project team present, it is not live yet.

U-2048The system of record

Only then does the old sheet stop being consulted. Running both for a few weeks is normal and worth planning for.

Nobody can promise every historical document and payment record comes across intact. What matters at go-live is that the current picture is right — who is in what, on what terms, with what open — and that the history worth keeping is identified rather than assumed.

A property system goes live on the day somebody stops opening the spreadsheet to check, and not before.

Can existing Excel or property records be migrated?

Usually, and the first job is finding out what the current tools can export rather than assuming. Unit lists, occupant lists and current lease positions normally move cleanly. Historical payment records and years of scanned documents depend entirely on what shape they are in.

What should a property operator digitise first?

Units, then leases. A named, complete list of every unit is what everything else attaches to, and a lease with a real term is what makes renewals and occupancy computable rather than remembered. Digitising requests or payments before those two exist just moves the confusion onto a screen.

Custom property management software, or off-the-shelf?

Off-the-shelf is the right answer more often than agencies admit: a standard residential rental operation with standard leases is well served by a product built for exactly that, particularly where the payment and accounting ecosystem is the main requirement. A custom build earns its place when the unit or lease model is genuinely unusual, when several existing systems have to stay in step, or when the standard product forces a workaround the team has to remember every day.

Does every landlord need property management software?

No. One or two units with simple agreements are managed perfectly well with a sheet and a folder, and a system would be overhead. It starts paying when the unit count grows past what one person can hold in their head, when more than one person manages the properties, when renewals begin slipping, or when the same question about a unit has three different answers depending on who you ask.

Straight answers

What property operators ask before they commit.

We run everything on spreadsheets. Is that actually a problem?
It is a problem the day two people edit it, or the day somebody is away. A sheet holds this year’s tenancies well and loses the unit’s history every time a new tab is started. If the portfolio is small and one person owns it, sheets are fine. If it is growing, that is the thing that fails first.
Can occupants raise requests themselves?
Where a portal is in scope, yes — a controlled surface where an occupant can raise a request, see its state and find documents that concern them. It is a real decision rather than a default, because it changes what every screen is allowed to show.
Does it handle commercial property as well as residential?
The unit-and-lease model is the same; the lease terms are what differ. Commercial agreements bring escalations, common-area terms and unit-specific clauses, so those are settled before the lease model is built rather than bolted on after.
What about deposits?
The system can record that one was taken and what state it is in, because an operator needs to see that beside the unit. Settling it, adjusting it against a condition note and accounting for it are money questions that belong with the money, and any legal requirement around holding it belongs to the operation’s own process.
Can it generate the rent agreement?
It records the agreement, its term and its renewal state, and holds the approved document against the unit. It does not draft the agreement, stamp it, register it or advise whether it is enforceable. Where an operation has a standard template and a defined legal process, the system can follow that process — the legal work stays where it already is.
Do you do tenant verification or background checks?
No. Where an operation verifies occupants, the system can carry the workflow and record the outcome, and connect to whichever approved provider does the checking. Branditify does not perform identity, credit or police verification, and nothing here implies a provider we have not looked at.
Can it send renewal or request reminders?
Yes, where a channel is in scope. The system already knows which leases are inside their window and which requests are open; sending that somewhere — email, SMS, a messaging channel — is a provider decision each operation makes for itself.
What if a unit is used for something other than a tenancy?
That is common — a unit held back, one under renovation, one used by the business itself. Those are states of the unit rather than exceptions to it, and naming them early is worth doing because they decide what occupancy actually means in your reporting.
Who can see what?
Whoever you decide. Viewing a unit, changing a lease, closing a request and seeing anything about money are separate permissions, because in most operations they belong to different people — and anyone outside the business sees only what a portal is configured to show.
How long before it is actually running the operation?
It depends on the unit count, how much the leases differ and the state of the current records — which is why no timeline appears on this page. What we can say is the sequence: units first, then leases, then requests, and the occupancy check before any of it becomes the system of record.
What happens after it goes live?
The system is yours — code, database and hosting account. Most operations want changes in the first few months as the team discovers what it actually wants, and that is either an agreed period of work or an ongoing arrangement. Neither is a licence.

Start a project

Tell us about the portfolio.

The useful first conversation is about units and who touches them, not about features.

  • How many properties, and how many units in each
  • Residential, commercial, or both
  • How much the leases actually differ from one another
  • Who needs to log in — and whether occupants do
  • What happens today when a request comes in
  • Where the records live now
ERP & Operations