What we took away from the National Village Leadership Forum
Last week we presented at the National Village Leadership Forum, delivered by Infotrust for the Property Council of Australia, on AI in the village office. The brief was simple: not a futuristic AI talk, but the things a village manager can actually do now, often without a big IT project. The promise we opened with was thirty minutes, and three things you can do on Monday.
What we heard, before and on the day
Before we built a single slide, we listened. Two pre-session conversations, one with Aveo and one with Anglicare, kept surfacing the same four themes. That is what shaped the session.
- The manager’s time belongs with people: The role is with residents, families, staff and the community, not an evening buried in paperwork. As one manager put it, the time you get back is time you spend with residents and staff. This mattered most at move-in and a resident’s first 30 days, an earlier forum thread we picked up, where the tone of the whole relationship is set and things slip when a manager is stretched.
- Communication and the inbox: Managers wanted long email threads summarised into a clear timeline without copying every message into a resident file, incoming email triaged and routed before it clogs the inbox, and the writing itself made easier. Resident forums and one-on-one conversations were another load, with managers wanting minutes, actions and follow-up emails captured automatically.
- Property, maintenance and existing systems: Gardening, upkeep, electrical and air-conditioning servicing are a heavy, recurring load. Managers use tools like FM Clarity for work orders and preventative maintenance, and wanted AI to complement those systems rather than replace them, ideally nudging them before something fails, such as an ageing hot-water system due for a check.
- Paperwork, compliance and reporting: A standout pain point was the handwritten resident information form, hard to read as residents age and a yearly burden, which managers wanted scanned, digitised and reissued to simply amend. Alongside that sat plain-English access to the NSW Retirement Villages Act and committee obligations, monthly budget commentary, and time-consuming incident reporting, all made harder by a fragmented toolset (one manager counted roughly 17 systems).
The session: the flow we took the room through
We built the session as a deliberate arc, lowering the barrier before raising the ambition. The through-line was confidence, not expertise, and we said it plainly early: if you can write an email, you can do all of it, and you are not behind, you are exactly where everyone else is.
- How we got here: We walked the room from rules in the 1950s, to pattern learning in the 2000s, to plain language in 2022, to agents today. The point we wanted to land was that the breakthrough was access, not intelligence. Machines did not suddenly get smarter, they started speaking our language, which removed the gatekeeper, and between 2023 and 2025 that capability quietly moved inside Word, Outlook and Teams, so many managers already have it and do not know.
- What AI actually is: We framed generative AI as a pattern engine, not a thinking machine. It generates from patterns rather than looking things up, and by default has no memory between sessions. The analogy that carried the room was a capable graduate on their first day: fast, tireless, patient with rough instructions and brilliant at the first eighty percent, while you bring the last twenty. It drafts, you edit and approve, and it can be wrong fluently, which is exactly why you read it.
- The words that matter: We gave the room a small, practical vocabulary to hold their own in any AI conversation, three terms to use (prompt, agent, your Copilot) and three to watch (hallucination, public tools, autopilot). We named the risk of a confident wrong answer once, plainly, and moved on, because naming it early earns permission for everything after.
- Three things for tomorrow: We turned concept into action with three habits, not three tools, each usable on day one with no budget, project or IT ticket. Turn a mess into a message, rough notes into a resident-ready update. Ask before you write, using AI to draft the difficult family conversation. And make it your own, telling it your role and tone once rather than every time.
- The art of the possible: We then lifted it from personal productivity to the whole office, pointing the same technology at the work managers already do: a resident front door that answers enquiries consistently and after hours in plain words, with a person on anything sensitive, and the evening paperwork, disclosure statements, compliance packs and board reporting, drafted in minutes instead of evenings. We were careful not to promise outcomes or savings we cannot evidence.
The demo: three ways to make it real
We did not talk about the art of the possible, we showed it, three times, each one narrated live so the room heard the structure rather than seeing a magic trick.
- Demo 1, paperwork in one prompt: We took a scanned, handwritten resident information form and, with a single Copilot prompt, had it read and fill out a clean blank form as a typed digital record. This was the exact pain point managers had raised, the yearly re-do of forms that get harder to read as residents age, solved in seconds rather than an afternoon.
- Demo 2, an agent that knows the Act: We showed a purpose-built agent grounded in the NSW Retirement Villages Act and the village rules, so a manager can ask plain-English questions of the legislation and check their accountabilities, rather than trawling through lengthy documents. This landed the point that the Act, the community manager’s bible, can become something you simply ask.
- Demo 3, Copilot across my week: The one that hit home. We ran a real, de-identified Copilot query across emails, Teams and calendar: what do I have on, what did I miss this week, and what do I need to focus on. When the output appeared, pulled together from across the tools and generated as a clean PDF, the room saw their own week reflected back, organised and prioritised. That was the moment the idea stopped being abstract.
Across all three, the message was the same: this is not a future capability, it is out of the box and available now, and the human still edits and approves before anything is acted on. A genuine thank you to Melinda Akehurst from Aveo for helping make the paperwork example real.
The rules that let you say yes
Everything we showed sat on four simple rules, delivered as permission with boundaries, not a list of things you cannot do. Always use the approved tool, and always read it before it leaves your desk. Never put resident details in a public tool, and never let AI make the decision about a person. Australian privacy obligations do not change because AI is involved, it is the same duty with a new tool, so check with your privacy officer before using resident data anywhere new. Those rules are exactly what let a manager say yes to everything else on day one.
Where to start
Our closing message was the same one we opened with: do not be afraid to start. You do not need a budget, a project or an IT ticket. Pick one weekly task, try it once, and tell one colleague what worked. Start small, start tomorrow.
To continue this conversation with the specialists at Infotrust, feel free to contact us.
