The short answer
A good automatic landlord update is a short, scheduled message pulled directly from your maintenance log, not written from memory. It names what's happened at the property since the last update, what's outstanding, and what's being done about it, and it goes out on a schedule rather than when someone finally gets around to it. The only real requirement is that the maintenance log itself has to be kept current, because the update is only as good as the record it's built from. Get that right and a landlord update stops being an evening task and becomes something your system does on its own.
Why landlords keep chasing
A landlord who owns one or two properties through an agency wants one thing above almost everything else: to know their property is being looked after without having to ask. When the honest answer to "what's happening with the leak at number 12" requires someone to scroll back through emails, texts and a phone's call history, that confidence erodes fast, even when the actual maintenance work is being handled perfectly well. The landlord doesn't experience the good work happening behind the scenes. They experience the silence, and the silence reads as neglect whether or not it is.
Chasing landlords chase because updates feel inconsistent: detailed one month, a single line the next, depending on how busy the week was. That inconsistency is often more damaging to the relationship than any individual repair taking a few days longer than hoped.
Why hand-written updates stop scaling
Writing a genuinely useful update by hand works fine for a handful of landlords. It stops working the moment one person is writing updates for sixty or a hundred properties on top of everything else they do. The update either gets shorter and vaguer to save time, or it gets skipped for the properties that aren't currently causing a problem, which is exactly backwards: a landlord with a quiet property still wants to hear that it's quiet, not just silence that could mean anything.
The honest fix isn't writing faster. It's not writing the update from scratch at all. If the maintenance log already holds what's been reported, what's been done, and what's still open, the update is really just a formatted extract of data that already exists, rather than a fresh piece of writing every single time.
What a good automatic update contains
A useful update is short and specific, not a dump of raw data. For each property, it typically covers: anything reported since the last update, with its current status (reported, in progress, completed); anything still outstanding and roughly when it's expected to be resolved; and a plain confirmation when nothing's happened, which matters as much as reporting a problem, because silence and "nothing to report" read very differently to a landlord. It's worth resisting the urge to include everything the system knows. A landlord wants to know their property's in hand, not read a full audit log of every internal note.
The data has to come from the log, not memory
This is the part that makes automatic updates trustworthy rather than just faster. If maintenance requests are still arriving by phone, email and text and landing in different places, an automatic update built on top of that mess just automates the gaps along with everything else, confidently reporting "nothing to report" on a property where something was actually reported by phone and never logged. Getting requests into one place first, whichever channel they arrive on, is what makes the automation trustworthy rather than merely fast. This is the same groundwork covered in fixing the maintenance admin eating your evenings generally: the update is the last step, not the first one to automate.
Schedules: weekly, monthly, on event
Different landlords want different rhythms, and it's worth offering more than one. A monthly summary suits most landlords with a quiet, well-maintained property, covering everything in one digestible message. Weekly updates suit a property with something currently in progress, where a landlord wants to see movement rather than wait a month to hear a repair's been sorted. An on-event update, sent the moment something's reported or resolved, suits anything urgent, a landlord generally wants to know about a leak or a boiler failure immediately, not in next month's summary. Most agencies end up running all three: a default monthly rhythm, upgraded to weekly automatically while something's open, with urgent events breaking through immediately regardless of schedule.
What landlords who want more detail see
Some landlords, particularly larger ones with several properties, want more than a short summary. Rather than writing a second, longer version by hand, this is usually better solved with a simple self-serve view: a link where a landlord can see the full history for their property whenever they want, without waiting for the next scheduled update or calling to ask. It's a bigger piece of work than the update message itself, and not every agency needs it from day one, but it's worth knowing it's the natural next step once updates are running smoothly and a handful of landlords start asking for more than the summary gives them.
When to get help, and what we'd do
We'd usually build this as document and form automation, a guide price from £500, pulling the update directly from your maintenance log and scheduling it by property rather than writing each one by hand. It depends on a single automated workflow already getting requests into one log consistently, a guide price from £350, since an automatic update is only as reliable as the record behind it. If landlords want ongoing self-serve access rather than scheduled messages, a customer portal is the step beyond that, worth discussing on a call once the basics are running well. These are guide prices for a typical project; the fixed quote comes after a free 30-minute call.
Related
- General guide: Admin eats our evenings and weekends
- Sector pillar: Property drowning in admin
- Example project: a letting agent with a maintenance portal for tenants and landlords
- Guide: 10 admin tasks small businesses can automate this month
Frequently asked questions
How do automatic landlord updates actually get the information?
They're pulled directly from your maintenance log, the same record that holds what's been reported, what's in progress and what's completed. The update is a formatted extract of that record, not something written separately.
Will an automatic update miss something important?
Only if the underlying log is missing it too. The update is as reliable as the record it's built from, which is why getting every maintenance request into one place, regardless of how it arrived, matters more than the update message itself.
Should landlord updates be weekly or monthly?
It depends on the property. A quiet, well-maintained property suits a monthly summary. One with something currently in progress benefits from a weekly update until it's resolved, with anything urgent sent immediately regardless of the usual schedule.
Can landlords get updates more often if they want them?
Yes, either by adjusting their schedule or, for landlords who want ongoing visibility rather than periodic messages, through a self-serve view of their property's full history. The second option is a bigger piece of work, usually added once scheduled updates are already running well.
Does this replace the landlord update features in Reapit, Alto or Arthur?
Not usually. Most core property platforms focus on the tenancy record rather than a plain-English, automatically written update, which is the gap this fills alongside software you already use rather than instead of it.