AI for Strata Managers Replies in Seconds. The Job Stays Open

At ten past seven on a Thursday evening, Marcus is still at his desk with a spreadsheet of open jobs across forty-one schemes.

His AI assistant has had an excellent day. Sixty-one owner emails answered, every one inside two minutes, all politely worded and filed against the right lot.

None of it touched the balcony leak in Lot 12, reported in March, whose quote has been sitting unapproved since May. None of it helped when the committee at his Chatswood scheme put the management agreement out to tender on Tuesday.

Nobody decided to let those slide. The portfolio simply produced more open loops than one person could close. That is the gap in how AI for strata managers is being sold: inbox assistants that reply in seconds, triage bots that categorise a maintenance request, portals that acknowledge an owner faster. All of it aimed at the first reply. I build these systems for Australian businesses, so let me say the uncomfortable half out loud. Committees almost never leave because your first reply was slow. They leave because the last one never came.

What AI for strata managers actually gets right

Give the inbox tools their due, because the case for them is real.

A strata manager fields questions that are genuinely repetitive. Can I keep a dog. Where are the by-laws. When is my levy due. An assistant that answers those from your own documents at 9pm, without pulling a manager off an agenda, is doing work that was never going to be done well under that load. Triage is the same story one layer down, and I have written about the rent roll version of that problem before.

But notice what all of it touches: the moment a message arrives. The industry builds there because inbound volume is trivial to count, and a chart of falling response times makes a very good screenshot.

Committees do not sack you over response time

Now look at the same firm from the committee's side of the table.

The treasurer who has asked twice about the water ingress quote. The owner whose insurance claim was lodged in April and has had no update since. The secretary still waiting on last meeting's minutes.

Every one of those began with a fast, courteous acknowledgement. Every one is still open.

A queue with a two minute first reply and a six month tail is not a service. It is a waiting room with good manners.

That is what loses an agreement, and losing one is not a soft cost. Say a scheme pays your firm eight thousand dollars a year. Three walking is twenty-four thousand dollars of recurring revenue gone, and replacing them costs more than that in tender work. Run your own fee figures through that before you buy faster replies.

Your portfolio is a list of open loops

Here is what makes strata unusual, and why generic office automation misses it.

A manager does not hold one workflow. They hold a portfolio, and every scheme in it runs the same handful of loops at once: a work order awaiting a quote, a quote awaiting approval, an approval awaiting a contractor, a claim awaiting an assessor, minutes awaiting distribution.

Forty schemes with six live loops each is about two hundred and forty things that are somebody's problem and nobody's task. None of them are hard. They are invisible, because your software records that a job exists and never tells you it has not moved since May.

Nothing in strata is difficult. Everything in strata is outstanding.

Start with the ageing job, not the inbox

Pick one workflow, not the whole firm.

A system reads what your strata platform already holds: open work orders, their status, the date each one last changed, and the scheme it belongs to. It surfaces the ones that have gone quiet, then drafts the specific chase to the specific party. The contractor who never sent the quote. The committee sitting on an approval. The insurer gone silent on a claim.

Your manager approves each one. Nobody writes follow-ups at 8pm.

That gives you numbers to put in front of a committee at renewal: jobs opened, jobs closed, and the median age of what is still open. That last figure is the one that keeps agreements, and almost no firm can quote it today.

The levy nobody wanted to ring about

Then point the same loop at the money.

Arrears rarely build because owners refuse to pay. They build because the reminder is uncomfortable to send, so it sinks down the list, and a small balance quietly becomes a recovery matter. A system that reads the ledger, drafts the graduated reminder at the right stage, and escalates only when a balance passes the threshold your committee actually set is not aggressive. It is consistent, which no human under portfolio load ever is.

The same machinery closes the certificate loop, where the information certificate a conveyancer orders before settlement is one of the few pieces of strata work carrying someone else's deadline.

Consistency is not a personality trait you can hire for. It is a system property.

Automate the chasing, never the advice

Here is the line that keeps this safe, and it is not negotiable.

No system interprets a by-law, decides whether an item is common property, rules on a levy dispute, or drafts advice to a committee. Those are judgement calls with legal weight, and your professional indemnity cover assumes a person made them. A model that reads confidently and is wrong about a lot boundary will cost you more than the salary it saved. Trust accounting is the same: software may prepare and present, a licensed human authorises.

Point the technology at the work nobody trained in strata wants to do. Chasing quotes, tracking claims, drafting reminders, assembling agenda papers, flagging what has stopped moving.

Aim the software at the follow-up, never at the finding.

What AI for strata managers costs

Work down this list in order and stop the moment something works.

• The tools already inside your strata management platform. Ageing job reports, arrears reminders, meeting document templates, owner portals. Usually half configured. Turn them on before you spend anything.
• An assistant or inbox subscription, priced per user each month. Cheap enough to trial on one manager's portfolio and judge inside a quarter.
• A custom build that reads your job register and ledger, drafts the chases, and writes status back where your team already looks. A few thousand up to the mid teens of thousands, depending on how many systems it must talk to.

Hold that against one retained agreement. What catches firms out is the running cost rather than the build, and I broke those layers apart in what AI actually costs a small business.

The Australian layer: state acts, trust money and owner data

Two things separate a system built for an Australian strata firm from an overseas template.

The first is that there is no single Australian strata law. A firm operating across borders runs different meeting requirements, prescribed notice periods and terminology in every state, and the words on your notices are not decorative. A tool that respects the correct requirement per scheme protects you. One that applies a single template everywhere quietly manufactures challengeable meetings, and that risk sits with your licence.

The second is data. A strata roll holds names, addresses, contact details and payment history for every lot owner you manage. Ask where it is stored, whether it trains someone else's model, and whether you can get it out when a scheme leaves.

Common questions about AI for strata managers

What should a firm automate first?

The ageing work order report. It runs on data you already hold, and one quarter measures it with two numbers: jobs closed, and the median age of what is still open.

Will AI replace strata managers?

No. The relationship with a committee and the judgement on what is common property are the product. The chasing is not.

Is an inbox assistant worth it?

Often, if enquiries genuinely sit unanswered overnight. Check that first. If your problem is jobs that stall after the first reply, answering faster only gets you to the same place sooner.

Go back to Marcus. He did not lose Chatswood because he was rude or slow. He lost it because a leak reported in March was still a leak in September, and every polite acknowledgement in between made that worse rather than better.

If you want a straight read on what is actually stalled across your portfolio, that is what a first call is for. Book a strategy call and bring your open job register with the last-updated date on every line. We will count the loops before we talk about building anything.