Let’s be real for a moment: every council team has that process.

You know the one. It starts as an email, gets tracked in a spreadsheet, involves a few hallway conversations, and somehow still manages to get missed. Deadlines fly by, fingers point, and the process limps forward until someone quietly mutters, “There has to be a better way.”

Good news: there is. But before you can fix a broken process, you need to spot one. And the best part? You don’t need to run a workshop, gather metrics, or even open a spreadsheet (phew).

All it takes is five minutes, a few honest questions, and maybe? a strong cup of coffee.

1. Does anyone actually own the process?

If the answer is “kind of,” “depends who’s in the office,” or “I think it’s Karen’s? – that’s your first red flag.

Processes without clear ownership are like council bins without labels: everyone assumes someone else is handling it. That’s how things slip through the cracks.

Clear ownership means accountability. If you don’t know who owns it, chances are… no one really does.

Broken process signal 🚨

No one knows who’s meant to start, finish, or approve the work.

2. Are you still relying on spreadsheets and email chains to run it?

If a process is being tracked across a spreadsheet, your inbox, and a post-it note on your monitor – it’s not a process. It’s a scavenger hunt.

Email-based workflows and manual trackers might feel manageable, but they’re prone to errors, delays, and missed steps. And don’t get us started on version control. Was it “FINAL_final_updated_v3.xlsx” or “Copy of final_v2”?

Broken process signal 🚨

If one person’s away, no one else knows where the process is at.

3. Can a new staff member follow it without asking five people?

Tribal knowledge might work for Friday lunch spots, but not for workflows. If the only way to understand a process is to shadow Sandra for three weeks, it’s time to rethink it.

Well-mapped, clearly documented processes should be self-explanatory. Think step-by-step, with clear actions, ownership, and guidance – even for someone who just walked in the door.

Broken process signal 🚨

New staff are constantly asking “How do we usually do this?”

4. Does everything grind to a halt when someone’s on leave?

If a single person going on leave means everything stalls, your process is built on shaky ground.

You shouldn’t need a backup spreadsheet, six Teams messages, and three calendar reminders to reassign a task. Leave-resilient processes are flexible and can be picked up by others with minimal fuss.

Broken process signal 🚨

Staff spend more time covering gaps than doing their own work.

5. Could you audit this process tomorrow?

We’re not trying to give you heart palpitations. But if an audit came through next week, would you be ready?

A healthy process should leave a clean, trackable trail. You should know who did what, when, and why – without having to dig through old emails or cobble together a timeline.

Broken process signal 🚨

Audit prep turns into a week-long panic attack.

So… what’s actually causing all these breakdowns?

Nine times out of ten, it’s not your people. It’s the lack of structure. Manual handoffs, inconsistent workflows, no system of record – these are the usual suspects.

Other common culprits:

• One-size-fits-none software
• Complicated tech stacks no one wants to touch
• Processes built on “how we’ve always done it”

The fix? Bring structure, visibility, and simplicity back into the way your team works.

Fixing it doesn’t have to be hard

This isn’t about launching a massive digital transformation project. It’s about taking one clunky, frustrating process – and making it better. Then doing it again.

With Flowingly, councils are:

• Mapping broken processes in minutes (without needing to book a BA)
• Automating tasks and approvals to reduce email ping-pong
• Creating audit trails and clear ownership paths
• Empowering non-technical teams to fix their own workflows

We’ve seen teams cut process times by 75%, go paperless, and reduce audit stress – all by fixing processes one at a time.

And the best part? No developers, no code, no “we’ll get to that next year.”

Real talk – your process might be broken (and that’s OK)

Spotting a broken process isn’t an admission of failure. It’s step one toward building something better. Something your team actually wants to use. Something that works.

So go ahead – take five minutes today and run the test.

Ask your team:

• Who owns this process?
• Where does it live?
• Could someone new run it tomorrow?
• What happens if you’re away?
• Could we audit it next week?

If you’re getting nervous laughter or vague shrugs, congrats—you’ve found your first fix.

Ready to turn chaos into clarity? Let’s chat.

Convincing your council or local government team to try something new? It can feel like wrangling a committee to agree on Friday’s lunch order – everyone has an opinion and there’s always a budget to watch.

But when it comes to adopting process management tools like Flowingly, a little extra effort upfront can lead to less admin pain, fewer headaches, and happier communities on the other side. 

Let’s dive into some simple ways you can inspire your council leaders, department heads, and colleagues to get excited about better ways of working.

Why should councils care about process management tools? 

Local government teams have a lot to juggle: community grants, building approvals, service requests, compliance… You name it. Where things get sticky is keeping track of all those moving parts, especially when you’re slogging through spreadsheets or chasing emails across departments. 

Enter process management tools. They take the chaos out of your daily grind, letting you automate the dull jobs (think: approval workflows, status tracking) and focus more on work that really helps your community. Not only does that mean faster response times and better compliance, it’s also less stress for everyone involved. 

But how do you get everyone on board? Start here.

1. Zero in on your team’s real pain points 

Instead of bombarding folks with features and sales pitches, begin with what actually causes friction in your workflows. Does reporting feel endless? Are community requests slipping through the cracks? Are you stuck in a never-ending email loop for approvals? 

For example: 

• A rural New Zealand council might see grant applications sitting in limbo for weeks on end.
• An Australian metro council could lose hours consolidating compliance data for state audits. 

Pointing out these everyday pain points helps people see that process management tools aren’t just ‘nice to have’ – they’re a practical fix for the stuff that keeps you up at night.

2. Show the money (and the time, and the peace of mind) 

Let’s face it: council budgets are tight and everyone wants to know, “What do we actually get out of this investment?” 

Be specific: 

• Show how moving from paper or spreadsheet-driven workflows to digital can save staff hours (and the grey hairs that go with them). 
• Share real numbers. “Automating building consent approvals could save 200 hours a month. That’s whole weeks’ worth of staff time, ready to put toward new projects.” 

The more you can point to actual hours, dollars, or improved service measures, the more convincing your case will be.

3. Share stories from similar councils

People trust stories from peers way more than flashy marketing stats. Do some digging: Has another council in NZ or Australia already taken the plunge with workflow automation? What changed for them? 

Huon Valley Council in Australia halved the time it took to onboard new staff by digitising their core processes. Otorohanga District Council in New Zealand found regulators breathing easier knowing LGOIMA requests were now processed in just five days instead of 20.

Even small wins at similar councils can help tip the scales.

4. Tackle concerns with a human touch 

No one likes it when something new crashes into their daily routine – especially if it means learning yet another system. Address this early by being upfront and empathetic. 

Acknowledge the learning curve. Share how Flowingly (or your chosen tool) is designed to be easy for everyone, not just tech whizzes. Offer hands-on training, and let folks know there’s support around the corner if they get stuck. 

Frame it as a helping hand: fewer manual tasks and a clearer view of what needs doing. Not a “replace the team” scenario, just a better way to get the jobs done. 

5. Highlight the wins for you and the community

At the end of the day, local government exists to serve the community. Always circle back to how these tools help customers: faster permit turnaround, fewer mistakes, clearer communication. 

But don’t forget to remind your team what’s in it for them – less busywork, an easier time meeting compliance, and more bandwidth for projects that spark pride. 

For example: “Imagine if residents could lodge a service request online and check the status anytime, no calls needed, no chasing for updates. Or if your finance team could sail through audit prep instead of drowning under paperwork.”

6. Make buy-in a team sport 

Don’t do all the heavy lifting yourself. Get enthusiastic peers involved and encourage champions across departments. Run short workshops to brainstorm process pain points, and be sure to celebrate (even the small) wins together. 

When people see colleagues getting excited about improvements, rather than just ‘management’ pushing change – it’s much easier to get them on board. 

When you speak your team’s language, focus on real problems, and bring a bit of humanity to the conversation, moving to better, smarter workflows isn’t just possible – it’s inevitable.

And as councils across New Zealand and Australia are starting to discover, these changes really do help teams deliver more for the people they serve.