The Dates Live in Five Different Systems
Alarm dates in a provider’s portal. Lease dates in the platform. Rent review dates in somebody’s head. Insurance with the owner. Nothing looks across all of them and says what falls due next week, which is why the answer to “are we compliant?” is usually “probably”.
Does the work of
- Compliance Officer
- Rentals Administrator
- Property Manager
- Head of Property Management
Somewhere in your portfolio is a property whose smoke alarm service fell due months ago, and the reason nobody has noticed is not carelessness. The date lives in a provider’s portal that nobody has logged into since the contract was signed. Nothing in the office is wrong, exactly. It is that no single thing is looking.
In short
- The problem
- Thirteen recurring obligations across a rent roll, and one of them lives in a system that raises its hand. The rest are in provider portals, certificates and somebody's memory.
- Why it slips
- Four failure modes, and only one is forgetfulness. The others are structural: a date nobody owns, a system nobody opens, and a rule that changed under you.
- What we would automate
- Consolidating every due date into one queue, chasing owners and providers until an answer exists, and capturing evidence with its own expiry.
- What stays with a person
- Deciding what the current rule is, anything following a safety finding, acting against an owner instruction, and the first conversation about new obligations.
Want the whole thing by email?
This paper, plus the rest of the library. One click to stop them.
The Short Version
A rent roll is a calendar wearing a portfolio costume. Almost nothing in it is triggered by a person deciding to do something: it is triggered by a date arriving. Leases expire, rent reviews become available, alarms fall due for service, certificates lapse, inspections come round, notice periods open and close.
The problem is not that any one of those is hard. It is that they are recorded in five or six different places, by four different parties, and no single view exists. Ask an agency what falls due in the next fortnight across every obligation and the honest answer requires somebody to open the platform, a provider portal, a spreadsheet, an email folder and a filing cabinet.
Why this one is differentfrom the other papers in this set: most of the work in a rent roll costs time when it slips. This costs a penalty, a tribunal finding, a lost year of rent increase, an uninsured claim, or in the case of safety obligations, considerably worse. The cost does not scale with the delay: it arrives all at once, on the day something goes wrong.
What we would automate is the consolidation and the chasing: one queue holding every due date regardless of which system it came from, requests to owners that follow themselves up, evidence captured with its own expiry, and a weekly account of what is due and what has stopped moving. Not the decision about what to do when an owner declines, which is section 5.
5+
Systems holding a due date
The platform, provider portals, a spreadsheet, the owner's own records, and somebody's memory
8
Jurisdictions, eight rulebooks
Obligations, intervals and notice periods are set per state and territory, and they move
0
Systems that look across them
Which is why nobody can answer what falls due next week without opening five things
1. Every Date in a Rent Roll, and Where It Actually Lives
Not every line applies in every state or to every property. That is part of the point: the set of obligations attaching to a given property depends on its jurisdiction, its features and its tenancy, and no platform asks you those questions on the way in. The right hand column is the one to read.
| Obligation | Cycle | Where the date lives |
|---|---|---|
| Lease expiry and renewal window | Per tenancy | The platform, the one date that is reliably in a system |
| Rent review eligibility | Limited by statute and by the lease | Somebody’s head, or a note in a file. Frequency limits and notice periods are prescribed |
| Routine inspections | Periodic, capped by statute | The platform or the inspection tool, two places, sometimes disagreeing |
| Smoke alarm testing and replacement | Annual and at tenancy change, plus alarm end-of-life | The compliance provider’s portal, which nobody in the office logs into |
| Pool and spa barrier certification | Periodic where applicable | A certificate PDF, a council or state register, and hopefully the property file |
| Gas and electrical safety checks | Periodic where required | The provider’s records. Whether it is required at all depends on the jurisdiction |
| Blind and window safety devices | At tenancy start and on change | Usually nowhere. Recorded, if at all, as a line inside a condition report |
| Minimum standards at a new tenancy | Every new tenancy, where the regime applies | Nowhere. It is a checklist somebody either runs or does not |
| Water efficiency, to charge usage | Once, then on fixture change | A certificate in the file. Charging water without it is a refund waiting to happen |
| Bond lodgement, and top-up on increase | At tenancy start and on rent increase | The state bond authority, reconciled against the platform by hand |
| Landlord insurance currency | Annual | With the owner and their insurer. You find out it lapsed when you make a claim |
| Trade licence and insurance currency | Annual, per trade | Certificates emailed once and never revisited |
| Agency licence, trust audit, training | Annual | The principal’s own diary, which is a single point of failure with a family |
The bottom line
One of those thirteen lines is reliably in a system that raises its hand. The rest depend on a person remembering to look somewhere specific. That is not a discipline problem: it is an architecture problem, and no amount of diligence fixes an architecture.
2. Four Ways a Date Gets Missed
Every missed obligation we have seen described falls into one of four patterns, and each has a different fix. Diagnosing which one you have is more useful than resolving to be more careful.
The date nobody owns
It sits in the gap between the agency and the owner (insurance is the classic), so both parties assume the other is watching. The fix is not a reminder, it is writing down which party owns each obligation and telling the owner in writing which ones are theirs.
The date in a person's head
Rent reviews are the usual example, and they are worth money: a review window missed is a year of increase gone, and the owner never sees the loss because it never appears on a statement. The fix is a system holding the date, which means somebody has to enter it once.
The date in a system nobody opens
The alarm provider's portal knows exactly which properties are overdue. Nobody logs in between renewals, so the information is available and unread. The fix is a feed or a report into the one queue, not another login.
The date that was right for last year's rule
The nastiest one, because the process runs perfectly and produces a compliant-looking outcome under a superseded requirement. Nothing raises its hand. The fix is section 3.
Worth noticing that only the second one is a memory problem. The other three are structural, and the third (information that exists and is not read) is the cheapest to fix of anything in this paper.
3. The Rule Changes Under You
Australian residential tenancy law is not stable, and it does not change in one place at one time. Reform lands per jurisdiction, on its own timetable, often with a transition period attached, and frequently in areas where the previous process looked fine.
Two examples of the shape, both of which we have written about before. Smoke alarm obligations have converged over recent years on photoelectric, interconnected alarms meeting AS 3786:2014, with placement, age and testing requirements attached, but the detail and the timing differ by jurisdiction, so a portfolio spanning a border is running two standards. And prescribed rental application forms are arriving: South Australia already mandates its Form A1, and Victoria introduces a prescribed form from 31 March 2026, which constrains not only what is recorded but what may be asked.
A rule needs an effective date, not just a value
“Alarms serviced annually” is not a rule a system can hold safely. “This obligation, in this state, as at this date, superseding that one” is. Anything without an effective date will silently keep applying after it stops being true.
Somebody has to own watching
One named person, a standing calendar item, and the regulator's own update channel for every state you operate in. Industry bodies and software vendors are useful, but they are not the source and they are not accountable to you.
Transitions are where portfolios get caught
A requirement phasing in at tenancy change, or by a fixed date, splits your portfolio into compliant and not-yet for a period. That is a per-property state, which spreadsheets model badly and memory not at all.
Changes cost money the owner has not budgeted
New obligations usually mean spend on properties whose owners agreed to nothing. Section 5 is the harder half of every rule change, and starting that conversation early is the whole skill.
The two examples above are illustrations of how reform arrives rather than statements of your current obligation. Requirements, standards and commencement dates vary by state and territory and change regularly: confirm the current rule with your regulator or a property law adviser.
4. What a Real Compliance Calendar Requires
Most agencies have something they call a compliance calendar. Six tests separate one that works from a spreadsheet that gets updated when somebody remembers. If yours fails the first or the last, the others do not matter much.
- 1
One queue, every source
Platform dates, provider portals, certificates, owner-held obligations and agency-level items in a single ordered list. If answering “what falls due in the next fortnight” takes more than one place to look, you do not have a calendar, you have several.
- 2
The rule lives in the system, with an effective date
Per jurisdiction, per obligation, versioned. This is what stops last year's requirement quietly running for another eighteen months, and it is the test almost every homemade calendar fails.
- 3
Per-property applicability
Whether an obligation applies at all depends on the state, the property's features and the tenancy. A calendar that raises pool certification on properties without pools trains people to ignore it, which is worse than silence.
- 4
Evidence attached, with its own expiry
The certificate, the service record, the photograph, stored against the property and carrying the date it stops being current. Compliance is not the work having been done, it is the work being provable.
- 5
Escalation when nothing happens
An item that is due and unmoved for a fortnight has to surface to somebody who is not the person it was assigned to. Without that step a calendar is a list of things everyone has become comfortable seeing in red.
- 6
Somebody accountable for the whole view
Not per property manager. One person who reads the portfolio-wide picture weekly, because the failures cluster in the properties whose manager is most overloaded.
The honest version
None of those six is an AI problem. They are a data-modelling problem: one queue, versioned rules, per-property applicability, evidence with expiry. Automation makes it cheap to run afterwards, and it makes a badly modelled calendar wrong faster. Do this part first, even if you never automate anything.
5. The Hard Part Is the Owner Saying No
Everything above assumes the difficulty is knowing what is due. Often it is not. The property manager knows exactly what is required, has the quote, and cannot get the owner to authorise the spend, or has been told plainly not to.
This is the part of compliance that no calendar solves, and it is worth having a settled position on before it happens rather than during.
Ask in a way that creates a record
The obligation, the quote, the consequence of not acting, and a date by which an answer is needed. In writing. An owner who has been properly informed usually says yes, and the ones who do not have now put their instruction on the record.
Silence is not an instruction
An unanswered approval email is the most dangerous state in the process, because it feels like waiting and functions like a decision. Chase it, then escalate it, then treat continued silence as a refusal and act accordingly.
Know which obligations you cannot let slide
Safety obligations are not commercially negotiable, and an owner declining to fund one is a different category from an owner declining to repaint. Draw that line as agency policy, not case by case under pressure.
Be willing to resign a management
Uncommon, uncomfortable, and occasionally the only correct answer. A property the agency cannot bring into compliance is an exposure the agency is carrying for a management fee, and that arithmetic never works out.
Record the conversation the day it happens
Not summarised later from memory. If the property is the one that eventually goes wrong, the contemporaneous record of what you advised and what you were told is the entire difference between two very different outcomes for the agency.
The automatable part of that list is narrow but real: asking in the right form, chasing until an answer exists, and recording what came back with a date. The judgment about what to do with a refusal is not, and it is the reason this section exists.
6. What Stays With a Person
We automate this kind of work for a living and this is where we would draw the line.
Deciding what the current rule is
A machine can hold a rule, apply it consistently and flag when a date passes. It should not be the thing that determines what your obligation is in a given state this quarter. That is a person reading the regulator, or an adviser.
Anything following a safety finding
A failed alarm test, a non-compliant pool barrier, an electrical fault. The finding can be captured automatically. What happens next involves risk to somebody's life and belongs with a person the same day.
Acting against an owner instruction
Overriding a client's express decision, or resigning a management over it, is a principal-level judgment with legal and commercial consequences in both directions.
The wording of a notice or a formal communication
Generated from a template and the current rule, yes. Sent unread on a matter that may end up in front of a tribunal, no, particularly where the notice affects somebody's tenancy.
The first conversation about new obligations
Telling a portfolio of owners that a reform will cost them money is a relationship conversation. Automate the scheduling of it, not the having of it.
7. What Can Be Automated Today
What is left is most of the running cost, because compliance work is overwhelmingly consolidation, chasing and record-keeping rather than decision-making.
| The work | What a machine does with it | What it hands back |
|---|---|---|
| Consolidation | Pulls due dates from the platform, provider portals, certificates and agency records into one queue | A single answer to what falls due in the next fortnight, portfolio-wide |
| Applicability | Matches each property’s jurisdiction, features and tenancy against the obligation set | Items that actually apply, so the list stays credible enough to be read |
| Owner requests | Sends the obligation, the quote and the consequence, with a required-by date | A request in a form that creates a record rather than a conversational email |
| Chasing an answer | Follows up unanswered requests on a schedule, by email and then by voice | A recorded instruction, or documented evidence that one was sought repeatedly |
| Provider chasing | Tracks whether the booked service actually happened and the certificate arrived | The gap between booked and done, which is where most compliance failures hide |
| Evidence capture | Files certificates against the property and reads the expiry off them | The next due date created automatically by the last one being satisfied |
| Trade currency | Monitors licence and insurance expiry across the panel and requests renewals | No unlicensed or uninsured trade attending a managed property |
| The weekly account | Reports what fell due, what was satisfied, and what has not moved in a fortnight | The escalation in section 4, delivered without anyone assembling it |
The equivalent problem in trades (licences, insurances, vehicle registrations and subcontractor currency all falling due on different calendars) is the subject of licence, insurance and compliance tracking, and the mechanics carry over almost unchanged. What is different here is that the obligation is usually somebody else’s property and somebody else’s money, which is why section 5 exists and has no equivalent there.
Where we come at this
We build in this gap, so read the table above as interested rather than neutral, with one qualification we would rather state than have you discover. Most of the value here is the data model in section 4, not the conversation layer we make, and an agency that builds the queue and never automates a single call will have captured the majority of the benefit. Where we do add something is the chasing: owners who do not reply to email, providers who booked and did not attend, and trades whose certificates expired eleven months ago. That is voice and messaging with memory across attempts, Australian compliance about when a call may be placed, and one thread rather than three channels: the same layer that sits under our own products. It is a scoped build rather than a subscription, and the honest sequence is queue first, automation second.
8. Getting Started
- 1
List every source of a due date
Walk section 1 against your own operation and write down which system each line lives in. If the list has more than three entries (it usually has six), that is the finding, and it takes an hour.
- 2
Answer “what falls due in the next fortnight” from a standing start
Time yourself. However long it took is what it costs every time anybody needs to know, which is why nobody asks.
- 3
Audit ten random properties against the current rule
Ten files, every applicable obligation, evidence present and in date. Ten is enough to tell you whether you have a discipline problem or an architecture problem, and the answer is nearly always the second.
- 4
Find the rent reviews you did not do
Tenancies where a review window opened in the last two years and no increase was issued. This is the exercise that pays for the project, and it is the one owners would most want you to run.
- 5
Build the queue before buying automation
One list, every source, with an owner and an effective-dated rule per obligation. Then automate the chasing on top of it. Doing those in the other order produces a fast, confident, wrong calendar.
Compliance obligations, intervals, standards, prescribed forms and commencement dates are set by state and territory legislation, differ between jurisdictions and change regularly. The obligations in section 1 are a map of the kinds of date a rent roll carries, not a statement of what applies to your properties, and nothing here is legal advice: confirm the current requirement with your regulator or a property law adviser.
Not ready to talk yet?
Leave your email and we’ll send this paper to your inbox, with a link to the rest of the library. We publish a new one every few weeks and you’ll get those too, one click to stop them.
Your email is used to send you the papers and nothing else. We don’t share it.
How long did the fortnight question take?
Run the second exercise in section 8 and bring the number, plus how many systems you had to open. Eight minutes with our AI will tell you what the consolidation is worth at your portfolio size, and where the queue has to exist before any of it is automatable.