Practical AI for marae, iwi and kaupapa-led teams

Kia ora e te whānau,

AI won't replace the relational mahi your people do. But used carefully, it can take some of the admin off their plate.

Think of it like a good photocopier. It doesn't run your office. It doesn't make decisions. But when it works well, your team isn't standing at a machine wasting twenty minutes before a hui.

That's the kind of useful AI can be, if you start in the right place.

‍

Where it actually helps

AI is good at first drafts and repetitive text tasks.

A kaimahi finishing a long hui can paste their rough notes in and get a draft set of action points in under a minute. A coordinator writing the same welcome email for the tenth wānanga (workshop) this year can get a solid first draft without starting from scratch.

It can also summarise long reports, reshape policies into plain language, and pull themes from feedback, as long as the information going in is safe to use.

‍

Where to be careful

Don't put private whānau information into AI tools.

That means health details, case notes, sensitive referrals, whakapapa, legal issues, or anything shared in confidence. Most free AI tools store what you type. Treat them the same way you'd treat a public noticeboard: if you wouldn't put it there, don't put it in.

‍

Keep a person in charge

AI can draft. A person should decide.

Before anything goes out, a real person needs to check the facts, the tone, and whether it actually sounds like your organisation. This matters especially for grant applications, funder reports, and anything that speaks on behalf of your kaupapa.

‍

Good places to start

Low risk, practical tasks are the best first step.

• Summarise a long set of public funder guidelines
• Turn rough hui notes into a draft action list (no sensitive details)
• Create a first draft of a pānui (newsletter update) or thank you email
• Reshape a long document into plain language headings

These save real time without handing over anything that matters.

‍

Set a few simple rules first

Your team doesn't need a 40-page policy. You do need a short, clear agreement.

What can go in, what can't, which tool is approved, and who checks the output before it's used. Write it in one page. Revisit it once a year.

‍

The Hono way

We're interested in practical AI, not hype. If it helps a small team get off the blank page faster, good. If it helps a kaimahi finish a report without working late, good.

But the kaupapa stays with people. AI handles the admin around the mahi. It doesn't carry the relationship.

‍

Common pātai

How do we use AI safely?

Start with low-risk tasks. Keep private whānau information out of it. Always have a person check the output before it goes anywhere.

‍

What should never go into an AI tool?

Health details, case notes, whakapapa, sensitive referrals, legal issues, or anything shared in confidence, unless you know exactly where it's stored and who can access it.

‍

Do we need an AI policy first?

Not a long one. A one-page agreement covering what can go in, what can't, which tool is approved, and who checks the output is enough to start.

‍

Keen to see how AI could help your team? Let's kōrero and we'll talk through where it makes sense for your mahi.