The Inspection Is the Easy Part
Walking through a property takes twenty minutes. Serving the notice, getting access, producing a report that survives scrutiny and acting on what it found take the rest of the week, and the last of those has no home in any system.
Does the work of
- Routine Inspection Officer
- Property Officer
- Assistant Property Manager
- Property Manager
Eleven inspections were booked for Thursday. Two tenants have not replied, one has asked to move to next week, and the notice period means next week is really the week after. The photographs from the nine that go ahead will be filed the same day, and everything those reports found will be somewhere in an inbox by Monday.
In short
- The problem
- The walkthrough takes twenty minutes. The notice, the access, the report and the follow-up on what it found take the rest of the week.
- Why it slips
- Four of the five jobs inside an inspection are coordination and documentation, and the findings have no system of their own once the report is filed.
- What we would automate
- Notice generated from the current rule and served on schedule, tenant confirmations and reschedules, the run sheet, and turning findings into tracked items.
- What stays with a person
- The judgement inside the report, anything about how somebody is living, the breach conversation, a refusal of access, and the bond conversation at exit.
Want the whole thing by email?
This paper, plus the rest of the library. One click to stop them.
The Short Version
Inspection software solved the part that was already the easiest. Photographing a property against a template and producing a tidy PDF is genuinely better than it was ten years ago. Everything wrapped around that (the notice, the access, the rescheduling, and what happens to the findings) is roughly where it was, and that is where the week goes.
Two of those wrappers matter more than the others. Entry notice is a legal instrument, so getting it wrong makes the inspection itself contestable and the evidence with it. And the findings (the repairs, the breach conversations, the re-inspection, the report to the owner) have no system of their own, so they scatter into an inbox the moment the PDF is generated.
The reframe: an inspection is not an event, it is a small project with a legal front end and an open tail. The report is the midpoint, not the deliverable. Most agencies measure completion at the midpoint, which is exactly why the tail is invisible.
What we would automate: the notice on schedule, the tenant confirmations and reminders, the reschedule negotiation, the run sheet, and the conversion of findings into tracked items with dates. Not the judgment inside the report, and not anything about a person’s living conditions.
5
Jobs inside one inspection
Notice, access, the walkthrough, the report, and the follow-up on what it found
2
Reports that have to agree
Entry and exit. A bond claim is decided on the comparison, not on either one alone
0
Systems that track a finding
The report is filed and the repairs, breaches and re-inspections go into somebody's inbox
1. One Inspection Is Five Jobs
Written out as separate pieces of work, with an honest note about where the hours sit. The middle one is the only one anybody thinks of as the inspection.
Scheduling and notice
Deciding when it is due, choosing a date and time inside the permitted window, generating a valid notice, serving it by a permitted method, and recording that service. The recording is the part that gets skipped and the part that matters if it is ever questioned.
Access
Confirmations, reminders, pets, keys, whether anybody needs to be home, and the reschedule when the tenant replies the night before. This is the largest consumer of messages and the least visible in any system.
The walkthrough
Twenty to forty minutes on site, plus travel. Genuinely well served by software and genuinely not the problem.
The report
Written to be read by somebody who was not there and possibly by a tribunal member two years later. Consistency of coverage matters more than prose quality, and the deadline for providing it is prescribed in most jurisdictions.
The follow-up
Repairs raised, breach conversations had, owner informed, re-inspection scheduled, and each of those tracked to completion. Nothing owns this, which is section 5.
The bottom line
Four of the five jobs are coordination and documentation. When an agency says its inspections are behind, it almost never means nobody is walking through properties. It means the notices are late, the reports are late, or the findings from three months of inspections are still sitting in a mailbox.
2. Entry Notice Is a Legal Instrument
Everything about entering a rented property is constrained, and the constraints are the tenant’s protections rather than administrative preference. Across Australian jurisdictions the same four dimensions are regulated, with the detail differing in every one: the minimum notice before entry, how many routine inspections are permitted in a period, the days and hours entry may occur, and the permitted purposes for entering at all.
Four consequences worth designing around.
A defective notice makes the entry unlawful
Short notice, the wrong form, an impermissible time, or service by a method not allowed. The inspection may still happen and the tenant may not object, but if the tenancy later ends in dispute, everything gathered on that visit is arguable.
The frequency limit is a ceiling, not a target
Owners sometimes ask for more inspections than are permitted, and the answer is a rule rather than a negotiation. It is easier to explain that once, at the start of a management, than in the middle of a disagreement.
Service has to be evidenced, not just done
What was sent, to whom, when, and how. Where a jurisdiction allows electronic service by agreement, the agreement itself is part of the record. A notice you cannot prove you served is a notice you did not serve.
The rules are not the same across a border
An agency operating in two states runs two notice regimes under one brand, and the second one is usually the one nobody has re-checked since the office opened.
This is the strongest argument in the paper for automation, and it is not a time argument. A notice generated from the current rule for that property’s jurisdiction, on the right form, at a permitted time, served by a permitted method, with the service recorded, is strictly more reliable than a person doing it from memory at 4:45 on a Friday. The general version of that problem (a rule that has to live in the system rather than in a head) is the compliance calendar paper.
Notice periods, frequency limits, permitted hours, prescribed forms and service methods are set by state and territory legislation and change. Confirm the current requirement with your regulator or a property law adviser rather than with this paper.
3. Routing the Day, and the Reschedule That Undoes It
Inspections are batched because travel dominates. A well-built inspection day is a geographic run with realistic gaps, and building one is a genuine optimisation problem: the same shape as a trade’s dispatch board, which we wrote about in smart scheduling and dispatch.
The difference is what happens when one entry moves. A trade rescheduling a job annoys one customer. A rescheduled inspection may need a fresh notice with a fresh notice period, which can push it out by more than the delay itself, and it breaks the geography of the whole day. Three practical rules follow.
- 1
Notice early enough that a reschedule still fits
Serving at the legal minimum leaves no room. Serving with a margin means a tenant asking to move by a day does not require starting again, which is the difference between a five-minute change and a two-week slip.
- 2
Confirm twice, close to the day
A confirmation when the notice goes and a reminder the day before. Most no-access events are not refusals, they are people who forgot, and the reminder is the cheapest intervention available anywhere in this paper.
- 3
Keep a substitution list for the run
When one address falls out, the gap is worth filling with another property in the same suburb that is due soon. That requires knowing what is due, by suburb, at the moment the gap appears, which is a data problem, not a scheduling one.
Worth noting how much of this is conversation rather than calculation. The run sheet is arithmetic. Getting eleven households to confirm, and renegotiating with the two who cannot, is eleven conversations that have to happen in whichever channel each of those people actually answers.
4. The Report Is Written for a Tribunal You Hope Not to Attend
Entry and exit condition reports are the documents that decide bond disputes, and they decide them by comparison. An exit report that catalogues damage beautifully is worth very little if the entry report for the same property was thin, undated, or covered different rooms in different detail.
What makes a report hold up is boring and mostly procedural.
The same coverage every time
Same rooms, same items, same order, same angles. Comparability is the whole point, and it is created by a template being followed rather than by any individual inspector's diligence.
Photographs that carry their own date
Images with reliable capture metadata, stored against the inspection rather than in a phone's camera roll. A photograph whose date can be questioned is a photograph the other side will question.
Description without conclusion
Record the mark on the wall and its size and location. Whether it is fair wear and tear is a judgment made later, by a person, and a report that has already decided it is a report that is easier to attack.
Delivered inside the required window
Most jurisdictions prescribe how soon a condition report must be provided to the tenant, and some require an opportunity for the tenant to comment or dispute. A late report is a weak report regardless of its contents.
The tenant's own record matters too
Where the tenant is entitled to add to or dispute the entry report, their version becomes part of the file. Encouraging it feels like inviting argument and is actually the cheapest insurance available.
The honest version
If your entry reports are inconsistent, no amount of automation downstream will save a bond claim two years from now. Fixing the template and enforcing the coverage is unglamorous, costs nothing, and is worth more than every other item in this paper for the small number of tenancies that end badly.
5. The Findings Have Nowhere to Go
Here is the gap that costs the most and gets discussed the least. An inspection produces findings. The report records them and then the report is filed, at which point each finding becomes an item of work with no tracking, no due date and no owner.
A routine inspection typically generates four kinds of tail, and each needs a different thing.
| Finding | What it becomes | Why it goes missing |
|---|---|---|
| Something needs repair | A maintenance job, with an approval path and a threshold | Raised as a line in a report rather than as a job, so it never enters the maintenance loop at all |
| Tenant obligation not being met | A conversation, then possibly a breach notice with a remedy period | Needs a decision nobody schedules, so it waits for the next inspection and appears twice |
| Something the owner must decide | A recommendation, a quote, and an instruction to be recorded | Sent as commentary inside the report email, where an owner reads it and does not reply |
| Something to check next time | A re-inspection, or a note that must survive to the next visit | Lives only in the previous report, which nobody opens before walking in the door |
The structural fix is the same one that works for maintenance and for compliance: every finding becomes an item with a next action, a date and a named party, and the absence of movement is what raises its hand. We described that pattern from the maintenance side in six handoffs for one broken tap, and the two queues should be one queue: a repair found at an inspection is not a different kind of repair.
The bottom line
An inspection programme that produces reports on time and does nothing with the findings is an expensive photography service. The value was always in the tail, and the tail is the part no software in the stack currently owns.
6. What Stays With a Person
The inspection itself is the least automatable thing in property management, and quite a lot of the tail is not far behind.
The judgment inside the report
Fair wear and tear versus damage, whether cleanliness is a breach or a preference, whether something is deteriorating or was always like that. Nuanced, contestable, and the reason the inspector's name is on the document.
Anything about how somebody is living
Hoarding, evident hardship, signs of family violence, a welfare concern about a child or an older tenant. These come up at inspections more than at any other touchpoint and every one of them needs a person, an escalation path, and no template.
The breach conversation
Deciding to issue a notice about the state of somebody's home is a judgment about a tenancy. A system should surface that it is available and that nothing has happened. It should not send it.
Refusal of access
A tenant declining entry is sometimes a rights question, sometimes a fear question and occasionally the start of a dispute. It is always a phone call from a person.
The bond conversation at exit
Negotiating a bond claim is a discussion about money with someone who has just moved out. Automating it saves an hour and buys a tribunal application.
7. What Can Be Automated Today
Everything in section 6 is a small share of the elapsed time. What follows is the rest of it, and none of it requires a judgment about a property or a person.
| The work | What a machine does with it | What it hands back |
|---|---|---|
| Knowing what is due | Tracks inspection cycles per property against lease dates and the frequency limit | A due list by suburb, which is also the substitution list for a gap in the run |
| Notice generation and service | Builds the notice from the current rule for that jurisdiction and serves it by a permitted method | A valid notice with the service recorded, rather than a diary note that it was done |
| Confirmations and reminders | Confirms when the notice goes, reminds the day before, in the channel the tenant answers | Fewer no-access visits, which are the most expensive hour in the week |
| The reschedule | Handles the request, offers dates that still fit the notice period and the run | A new date without a manager mediating, and without an accidental short notice |
| The run sheet | Clusters the due list geographically with realistic travel and inspection times | A day that is actually achievable, built in seconds rather than over an afternoon |
| Findings to tracked items | Turns each finding into a repair, a decision request, a breach candidate or a next-visit note | A tail with dates and owners instead of a filed PDF |
| Owner reporting and chasing | Sends the report with the decisions separated out, then follows up the ones needing an instruction | Recorded instructions, or a documented record that one was sought |
| Previous-report recall | Surfaces the last visit’s open items before the next inspection | An inspector who walks in knowing what to look at, which no template provides |
Where we come at this
We build in some of this and not all of it, so it is worth being precise about which. The inspection app itself is a solved market: Inspection Manager, InspectRealEstate, SnapInspect, ConditionHQ and the modules inside the platforms all do the walkthrough and the report well, and we would not build a competitor to them. What we make is the conversation layer around it: Australian voice, the compliance that decides whether a call may be placed at all before it is placed, memory that persists across calls, and a single thread across voice, SMS and messaging instead of three channels that cannot see each other. The eleven confirmations, the two reschedules and the owner who has not replied are conversations, which is the part of an inspection programme nothing in the stack currently carries.
8. Getting Started
- 1
Count no-access visits over a quarter
Attended, nobody home, nothing done. Multiply by travel plus the hour and you have the cost of not reminding people, which is the easiest number in property management to fix.
- 2
Take three inspections from three months ago and trace the findings
For every item in each report, what happened? This is the single most revealing exercise in this paper, and in most offices at least half the findings have no recorded outcome.
- 3
Pull two entry reports and their exit reports
Do they cover the same rooms in the same detail? If not, your bond position at exit was decided at the start of the tenancy and nobody noticed.
- 4
Check your notice practice against the current rule
Notice period, permitted hours, frequency limit, service method, and where the evidence of service is kept, per state you operate in. Do this before automating anything, because automation will faithfully reproduce whatever you currently do.
- 5
Automate confirmations and the findings tail, in that order
The reminders pay for themselves immediately and annoy nobody. The findings tail is the larger prize and takes longer, because it needs a queue that does not exist yet.
Entry notice requirements, inspection frequency limits, condition report obligations and bond dispute processes are set by state and territory legislation, differ between jurisdictions and change regularly. Nothing here is legal advice: confirm the current obligation with your regulator or a property law adviser. Product names reflect the Australian market as at September 2026.
Before you build anything custom
If your agency also runs its own books, the chasing half of that is already a product rather than a project. Office Voice reads live Xero data, calls about open invoices and quotes, and sends a payment link while it is still talking. The inspection tail in this paper is the part that genuinely is custom, worth trialling the first before commissioning the second.
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.
What happened to last quarter’s findings?
Run the second exercise in section 8 and bring the answer. Eight minutes with our AI will price what the tail is costing across your portfolio, and tell you honestly which end of the inspection is worth fixing first.