The Report Nobody Has to Remember to Send
A managing agent's product is one document per owner per month, and the thing that erodes a mandate is not a bad month — it is the month the statement went out on the eleventh because somebody was on leave. What can be scheduled, and the day of the month you cannot pick.
Ask a property owner why they moved agents and the answer is rarely dramatic. The rent came in. The repairs got done. What changed was that the statement started arriving on the eleventh instead of the third, then the fifteenth, then only after they asked — and somewhere in there the owner stopped feeling informed and started feeling managed.
Nothing went wrong operationally. What happened is that producing the statement was a task somebody did rather than a thing that happened, and tasks somebody does are subject to leave, illness, month-end pressure and whatever else was more urgent on the third.
The difference between a report that is sent and a report that is scheduled is not effort saved. It is that one of them has a variance and the other does not.
Why consistency beats quality here
This is counter-intuitive enough to be worth stating directly. For recurring client reporting, arriving on the same day every month matters more than the document being better.
- A predictable document gets read. An owner who knows the statement arrives on the third opens it on the third. One that arrives at random gets filed for later, and later does not come.
- Irregularity reads as trouble. An owner does not know why a statement is late. What they know is that the month the agency had a problem was the month it was late, and they will remember the correlation whether or not it existed.
- Chasing is the expensive part. An owner who has to ask has already spent some goodwill, and the reply costs you a person's afternoon on a document that was going to be produced anyway.
- Consistency is what makes comparison possible. Twelve statements on the same day, in the same format, are a series an owner can reason about. Twelve at irregular intervals are twelve documents.
An owner does not know why the statement was late. They know the month you had a problem was the month it did not arrive, and they will remember that whether or not it was true.
What can be scheduled
A report can be given a schedule and a recipient list, and from then on it goes out without anybody in the loop.
| Setting | Options |
|---|---|
| Cadence | Daily, weekly or monthly |
| Time of day | Any time, in a timezone set per schedule |
| Day | Day of week for weekly; day of month for monthly |
| Formats | PDF, CSV, XLSX — any combination, attached together |
| Recipients | A list per schedule |
| Record | Each delivery stores its status, its recipients and any error |
The per-schedule timezone is worth noticing if you manage property across borders — a schedule is anchored to its own timezone rather than to the server's, so a report intended for eight in the morning arrives at eight in the morning where it is being read.
The delivery record is the part that turns this from automation into something you can rely on. A schedule that silently fails is worse than no schedule, because you stop checking. Each delivery stores whether it went, to whom, and what the error was if it did not.
The day of the month you cannot pick
One constraint will matter to a managing agent immediately, and it is better known in advance than discovered in February.
The day of the month is limited to the range one to twenty-eight. There is no twenty-ninth, thirtieth or thirty-first, and no "last day of the month".
The reason is sound — the thirty-first does not exist in seven months of the year and the twenty-ninth is conditional in one, so a schedule set to any of them either skips months or needs a rule about what to do instead, and both behaviours surprise people. Clamping to twenty-eight means a monthly schedule fires twelve times a year, every year, with no exceptions to reason about.
Schedule month-end reporting for the 1st, not the 28th
If you want a report covering a completed month, run it early in the following month rather than late in the current one. A statement scheduled for the twenty-eighth covers a month that has three days left in it, which is a statement you will be correcting. The first, second or third of the following month gives you a complete period and lands while it is still fresh — and it sidesteps the clamp entirely.
What AWRA OpsHub does today
- Daily, weekly and monthly schedules with a time of day and a timezone set per schedule.
- PDF, CSV and XLSX, in any combination, attached to the same delivery.
- A recipient list per schedule, so different reports go to different people without anybody forwarding.
- A delivery record for every run — status, recipients and the error if one occurred — so a silent failure is visible rather than assumed.
What it does not do
- No day of month past the twenty-eighth, and no "last day of month". Schedule month-end reporting for the first of the following month instead.
- Delivery is on an hourly pass, so a report due at nine fifteen goes out on the next hourly run rather than at nine fifteen exactly. Fine for a monthly statement; worth knowing if you were expecting a precise minute.
- No per-recipient personalisation. A schedule sends the same report to its whole list, so one owner statement per owner means one schedule per owner rather than one schedule that splits by owner.
- No conditional sending. A report with nothing in it still goes, so a schedule over an empty period sends an empty document rather than staying quiet.
Not ours, by choice
- We will not silently swallow a failed delivery. Every run records what happened, because automation you cannot audit is automation you will stop trusting at exactly the wrong moment.
- We will not guess what "month end" means for a schedule set to the thirty-first. A rule that quietly moves to the twenty-eighth in February, or skips the month, is a behaviour somebody discovers in a client meeting.
A last-day-of-month option, per-recipient splitting so one schedule can serve a portfolio of owners, and suppression of empty reports, are all scope rather than ceilings. The scheduling model, the timezone handling, the multi-format rendering and the delivery log all exist and work.
The per-recipient limitation is the one that shapes how an agency uses this. Owner statements are inherently one document per owner, so today that means one schedule per owner — workable for a portfolio of twenty landlords and unwieldy at two hundred. Weigh it against your actual owner count rather than in the abstract.
What to put on a schedule
The instinct is to schedule everything, which produces a stream of attachments nobody opens and trains recipients to ignore the sender. A short list is worth considerably more.
-
The report a client is waiting for
Owner statements above all. This is the document your mandate rests on, and it is the one where lateness costs you something specific.
-
The report that surfaces a problem while it is small
Aged receivables, weekly, to whoever works the arrears ladder. A weekly rhythm catches a tenant at fifteen days when a call still changes the outcome.
-
The report somebody genuinely reads on a Monday
Whatever your portfolio manager actually opens to plan the week — open repairs, upcoming lease expiries, vacancies. If nobody would notice it missing, do not schedule it.
-
Nothing else
A recipient who receives four scheduled reports reads one. The discipline is in what you leave off, and every report you add reduces the attention paid to the ones that matter.
One further habit worth adopting: put yourself on the recipient list for anything going to a client. Not to check the numbers — to notice when it stops arriving. A schedule that fails quietly is discovered by an owner asking where their statement is, and that is the most expensive way to find out.
The reporting rhythm an agency actually needs
Scheduling is a mechanism, and a mechanism without a rhythm behind it produces a lot of email. The rhythm worth building is short.
A working monthly cycle
- First of the month: owner statements for the completed month, scheduled, to each owner.
- Every Monday: aged receivables to whoever works the arrears, so the fifteen-to-thirty band is caught weekly.
- Every Monday: open repairs by age to the portfolio manager, so nothing sits for a fortnight unnoticed.
- First of the month: lease expiries in the next ninety days, because a renewal conversation started at ninety days is a different conversation from one started at thirty.
- Check the delivery log once a month. It takes two minutes and it is the only thing standing between a failed schedule and an owner noticing first.
The fourth line is the one agencies most often leave manual, and it is the one with the largest revenue attached. A vacancy costs a month of rent and a mandate; a renewal conversation at ninety days usually prevents both, and it only happens if something puts the expiry in front of somebody.
The statement's contents are worked through in owner statements and payouts, the renewal calendar in leases, renewals and vacancy, and the arrears ladder the weekly report feeds in the reminder that treats everyone the same.
Our take
Schedule three things and leave the rest manual: owner statements on the first of the month for the completed month, aged receivables every Monday, and lease expiries at ninety days. Schedule month-end work for the first rather than the twenty-eighth — the day of month stops at twenty-eight, and a statement covering a month with three days left in it is one you will be correcting anyway. Put yourself on every client-facing list so you notice a failure before an owner does, and check the delivery log monthly, because the whole value of this is that it removes the variance, and a schedule failing silently puts the variance straight back.
See reports that send themselves
Daily, weekly and monthly schedules with a timezone of their own, PDF, CSV and XLSX together, a recipient list per schedule, and a delivery record for every run.
Explore scheduled reportingFrequently asked questions
Can we schedule owner statements for month end?
For the twenty-eighth at the latest, since the day of month is limited to the range one to twenty-eight — there is no twenty-ninth, thirtieth, thirty-first or "last day of month". In practice you want the first of the following month anyway: a statement scheduled for the twenty-eighth covers a month with three days still to run, which is a document you will end up correcting. Running it on the first gives you a complete period and lands while it is still fresh.
Why is the day of month capped at twenty-eight?
Because the thirty-first does not exist in seven months of the year and the twenty-ninth is conditional in one, so a schedule set to any of them has to either skip those months or follow a substitution rule — and both behaviours surprise people, usually in front of a client. Clamping to twenty-eight means a monthly schedule fires twelve times a year with no exceptions to reason about. The cost is that genuine last-day reporting needs the first-of-next-month workaround.
Will a report arrive at exactly the time we set?
On the next hourly pass rather than to the minute — the runner checks hourly, so a report due at nine fifteen goes out shortly after ten. For a monthly owner statement or a weekly arrears report that is immaterial. It is worth knowing if you were planning a schedule around a precise minute, for instance timing a report to land just before a standing meeting.
Can one schedule send each owner their own statement?
No. A schedule sends the same report to its whole recipient list, so one statement per owner means one schedule per owner. That is entirely workable for a portfolio of twenty landlords and becomes unwieldy at two hundred, so weigh it against your actual owner count. Per-recipient splitting is a well-defined addition rather than a rewrite if it is the difference between using this and not.
How do we know a scheduled report actually went out?
Every delivery records its status, its recipients and the error if one occurred, so a failure is visible rather than assumed. Check that log once a month — it takes two minutes. The failure mode worth guarding against is a schedule that stops quietly: you stop thinking about a report precisely because it always arrives, and the first sign that it did not is an owner asking where their statement is, which is the most expensive way to find out.
What should we actually schedule?
Three things, and resist the rest. Owner statements on the first for the completed month, aged receivables every Monday to whoever works the arrears, and lease expiries at ninety days. The last is the one most agencies leave manual and it has the largest revenue attached — a vacancy costs a month of rent and often the mandate, and a renewal conversation started at ninety days usually prevents both. A recipient who receives four scheduled reports reads one, so the discipline is in what you leave off.
