The Relational Guide to Tenancy Management

Why the lettings handover is broken, and how structured data fixes the entire tenancy lifecycle

A Tenancy is a Lifecycle, Not a Date

In property management, a signed contract is universally celebrated. The lettings team rings the bell, the landlord is happy, and the unit is officially let.

But for the property management team, a signed Assured Shorthold Tenancy (AST) isn’t the finish line. It is the starting gun.

Managing a tenancy involves referencing, Right to Rent checks, deposit registrations, inventory logs, compliance document handovers, rent tracking, maintenance requests, inspections, and eventually, the move-out process.

A tenancy is a complex, multi-stage lifecycle. Yet, surprisingly, most agencies and portfolio operators try to manage this living, breathing process using static, disconnected tools.

As we explored in our previous guide on why spreadsheets break property operations, trying to force relational real estate data into flat rows is a recipe for chaos. Nowhere is this more obvious—or more risky—than in tenancy management.

The Danger Zone: The Lettings-to-Management Handover

In most property businesses, lettings and property management operate in silos.

Lettings teams use a CRM to track leads, viewings, and offers. Once the AST is signed, the data has to be passed over to the property managers.

In a fragmented system, this handover usually looks like this:

An email chain with five PDF attachments.
A copied-and-pasted row in a master “Tenancy Tracker” spreadsheet.
A manual calendar invite to remind someone to register the deposit within 30 days.

This gap between systems is where critical details fall through the cracks. It’s exactly how deposits miss their protection deadlines, how “How to Rent” guides aren’t served (invalidating future Section 21 notices), and how maintenance teams end up calling the wrong tenant.

The problem isn’t your team’s attention to detail. The problem is that the data doesn’t flow.

Why Flat Systems Fail Tenancies

If you track tenancies in a spreadsheet or a rigid legacy system, you are forced to view a tenancy as a single row of data.

But look at the true anatomy of a tenancy. It consists of multiple moving parts:

The Unit: The physical space being rented.
The Tenants: The individuals living there (who may change mid-tenancy).
The Guarantors: The financial backers linked to specific tenants.
The Contract: The legal agreement (AST, corporate let, etc.) with start and end dates.
The Deposit: The funds held, linked to a specific protection scheme (e.g., DPS, TDS).

When you try to track all of this in a spreadsheet, you run into immediate structural failures:

The Tenancy Reality	The Spreadsheet Workaround	The Resulting Risk
Joint Tenancy (3 people in 1 flat)	Squeezing three names and emails into one cell	Automated communications fail; referencing gets confusing.
Tenant Swap (One moves out, one moves in)	Overwriting the old tenant’s name with the new one	Historical records are destroyed; deposit disputes become nightmares.
Contract Renewal	Adding “AST End Date V2” columns	Missed rent reviews and forgotten renewals.
Guarantor Tracking	Leaving a note in a hidden “Comments” column	If rent arrears happen, the guarantor is impossible to find quickly.

When your system cannot handle the relational complexity of a tenancy, your team spends their days doing administrative damage control instead of managing properties.

The 5 Stages of the Structured Tenancy Lifecycle

To manage tenancies at scale without dropping the ball, you need a system that models the full lifecycle.

When you build a relational tenancy system, data moves seamlessly through five distinct stages, triggering the right actions at the right time.

Stage 1: Pre-Tenancy & Onboarding

Before the keys are handed over, a structured system connects the incoming tenant to the unit and tracks the required prerequisites.

Fields tracked: Referencing status, Right to Rent expiry, initial funds received.
The Structural Advantage: You cannot physically change a tenancy status to “Active” until the mandatory compliance checkboxes (like the EPC and Gas Safety Certificate) are linked and valid.

Stage 2: Move-In & Compliance

The riskiest part of the tenancy. Statutory obligations must be met instantly.

Fields tracked: Deposit protection certificate, inventory signed, meter readings.
The Structural Advantage: Because the deposit is its own record linked to the tenancy, the system can automatically flag if 20 days have passed since move-in without a registered DPS/TDS number.

Stage 3: Mid-Tenancy (The Operational Phase)

This is where the tenancy lives for 12 to 36 months.

Fields tracked: Routine inspections, reported maintenance, rent arrears.
The Structural Advantage: When a tenant logs a broken boiler, the system automatically links the Work Order to the Tenancy, the Unit, and the Property Manager. Everyone has full context instantly.

Stage 4: Renewals & Rent Reviews

Two months before the AST expires, the system should do the heavy lifting.

Fields tracked: Target rent increase, notice periods, renewal status.
The Structural Advantage: Instead of manually filtering a spreadsheet for “Dates in the next 60 days,” a structured system generates an automated view of “Upcoming Renewals,” assigning tasks directly to negotiators.

Stage 5: Move-Out & Voids

When notice is served, the teardown process begins.

Fields tracked: Check-out report, deposit deductions, void works.
The Structural Advantage: The tenancy record isn’t deleted or overwritten. Its status simply changes to “Historic.” The history remains perfectly intact for auditing, whilst the physical Unit automatically flips its status back to “Available/Void.”

How to Build a Relational Tenancy Tracker

If you want to escape the trap of flat spreadsheets and clunky legacy PropTech, you need to transition to a relational data model.

In a platform built for custom operational structures, you don’t track tenancies on a single sheet. You build distinct, connected tables:

Units Table: Holds the physical addresses, target rent, and block details.
Tenants Table: Holds the human details (names, contact info, referencing).
Tenancies Table: The vital bridge. This table links Units and Tenants together with a Start Date, End Date, and Rent Amount.
Deposits Table: Linked directly to the Tenancy, tracking the protection scheme, amount, and registration dates.

Because these tables are connected, a Property Manager can click on a Unit and instantly see who is currently living there, who used to live there, and what their current AST terms are.

No copy-and-pasting required. No overwritten data. Total historical accuracy.

The Mindset Shift: From Data Entry to Exception Management

When you structure your tenancy data relationally, the role of a property manager changes fundamentally.

In a spreadsheet environment, managers practice Data Entry Management. They spend hours updating columns, searching for expiry dates, and cross-referencing PDFs to figure out what needs to be done today.

In a structured, relational environment, managers practice Exception Management. The system knows the rules. It knows when an AST expires. It knows when a deposit needs protecting. It only alerts the human when an action is required or an exception occurs.

You don’t manage the data. The data manages the timeline. You manage the tenant.

The Takeaway

Tenancies are the lifeblood of your property business. They dictate your rent roll, your management fees, and your legal liabilities.

Tracking them in a flat, disconnected spreadsheet is a liability you can no longer afford as your portfolio scales.

You need a system that understands the difference between a building, a contract, and a person—and knows exactly how to connect them.

Ready to structure your tenancy lifecycles?

You don’t need a bloated legacy system to achieve enterprise-grade tenancy management.

With the right relational platform, you can map out your exact tenancy workflows, automate your compliance triggers, and give your lettings and management teams a single, unbroken source of truth.

Stop losing data in the handover. Discover how Gridfox gives you the power to build custom, relational tenancy management systems that work exactly the way your team does.