Why Councils Are Outgrowing the 3-Tool Juggle

by Sarah | Oct 23, 2025 | Process Improvement, Process Maps

Why Councils Are Outgrowing the 3-Tool Juggle

The modern council tech stack: a masterpiece of duct tape

If you work in a council or compliance team, this might sound uncomfortably familiar:

SOPs live in Word, Scribe, or somewhere deep in the shared drive.
Process maps sit in tools like Promapp, Visio or Lucidchart.
Automations (if they exist at all) run through Power Automate or Nintex Automation Cloud.

Three tools. Three owners. Three slightly different versions of “how things work.”

It’s not that these tools are bad – far from it. Promapp was revolutionary in helping councils map processes more clearly than ever before. Word is universal. Power Automate is incredibly capable for those who have the time and skills.

The challenge is that they’re all separate. Which means updates, changes and improvements often end up happening in three different places.

That’s the “three-tool juggle” – and it’s something more and more councils are looking to simplify.

1. Promapp helps you draw the map – Flowingly helps you take the next step

Promapp earned its place in local government. It gave process champions the visibility they’d been missing. For the first time, teams could see their processes mapped – who does what, when and why.

Promapp’s strength has always been in clarity and documentation, helping organisations define how their processes should work.

Flowingly simply picks up where mapping ends. Once your processes are documented, Flowingly makes it easy to bring them to life as live, running workflows – all in the same platform.

Flowingly delivers both the mapping councils rely on and the automation they’ve been missing.

2. When your SOPs, maps, and automations live in different tools, change becomes chaos

Here’s a scenario many councils know well:

The operations team updates a process map.
The compliance lead updates the SOP in Word.
And the automation built in Power Automate keeps running the old version because no one realised something had changed.

The result? A few crossed wires, some duplicated effort, and the occasional “local workaround” that no one remembers creating.

Whenever a regulation shifts, a form changes or a role gets updated, you end up making the same edit in three different places — and hoping everyone is working from the right version.

Flowingly simplifies that. One platform means one version of the truth.
Update a step once and it’s reflected everywhere: in the map, the SOP and the live workflow.

3. The mapping difference

Promapp gave process teams the structure and visibility they needed to bring process mapping into the mainstream.It supports BPMN for those who need detailed logic, while many users can see a simpler view designed for clarity and ease of use.

That balance between structure and simplicity made Promapp a trusted tool across local government.

But the bar for simplicity has risen sharply since those early days. Today’s users expect Miro-level ease – visual, intuitive, and instantly understandable.

Some customers tell us legacy tools feel geared towards process specialists. Our design goal is a visual, intuitive UX for everyday teams.

It still works brilliantly for those who’ve trained in it, but for general business users, it can feel more complex than it needs to be.

Flowingly builds on Promapp’s foundation by taking that simplicity to the next level. Each step becomes a clear, interactive card showing who’s responsible, what happens, and what’s next – no symbols, no training, no jargon.

It’s mapping designed for everyone – from governance leads to frontline staff, so the people running the process can actually understand it, follow it, and improve it.

4. Automation shouldn’t need an IT degree

Once councils finish mapping in Promapp, the next question is always the same:
“Okay… who’s going to automate it?”

Usually, that means handing it over to IT to rebuild in Power Automate.
Weeks later, a workflow appears – if the priority list allows.

Then the cycle starts again: change one step in Promapp, and IT has to re-build the automation manually.

It’s not sustainable.

Flowingly was built to remove that dependency.
If you can drag and drop, you can automate. Approvals, notifications, escalations – all managed visually, with zero code.

So the same team mapping the process can also make it work.

No hand-offs. No waiting. No tickets.

5. Visibility disappears when tools don’t connect

Promapp documents what should happen.
Power Automate executes what you’ve told it to do.

Both do their jobs, but neither shows you what’s actually happening right now.

When Promapp holds the map and Power Automate runs the workflow, visibility gets lost in between.
You can’t see which request is waiting for sign-off, who’s holding it up, or how long each step takes.
Operations teams are left chasing updates through inboxes or spreadsheets.

Flowingly closes that gap.

When your process map and automation live in the same place, you get real-time visibility across every workflow:

Which steps are completed
Who’s next in line
Where bottlenecks are forming

6. SOPs that live where the work happens

In most councils, Standard Operating Procedures sit miles away from where the work is done – often buried in folders or Word docs.

Promapp helps centralise them, but they still live next to the process, not inside it.

Flowingly embeds SOPs directly into each workflow step.
When someone completes a task, the “how-to” appears right there, no extra search, no broken links.

Your team doesn’t just write procedures; they use them.
And when a change’s needed, update it once – instantly everywhere.

Why councils are making the switch

Promapp is an incredble tool to this day. It helps councils capture knowledge that used to live in people’s heads.

But today, councils need more than static diagrams – they need connected, live workflows.

Flowingly replaces the three-tool juggle with a single platform where SOPs, process maps and automations work together.

Less complexity.
More visibility.
And processes that finally work the way they’re drawn.

What Does “Process Improvement” Actually Look Like in a Council?

by Sarah | Oct 21, 2025 | Process Improvement

What Does “Process Improvement” Actually Look Like in a Council?

We all say it. Few can explain it.

You’ve heard it before: “We need to improve our processes.”

Cue: nods around the table, someone opens Excel, and suddenly there’s a brand-new tracker… for the old tracker.

The truth? Most councils don’t need another spreadsheet. They need a better way to see how work actually happens.

Because real process improvement isn’t about adding more admin. It’s about removing it.

At Flowingly, we like to define process improvement as:

Turning invisible inefficiencies into visible wins.
(Fewer steps. Faster decisions. Happier staff.)

If that sounds familiar, it’s because in our recent blog The 60,000-Minute Problem we uncovered just how much time councils lose writing, rewriting, and chasing SOPs.

This blog is about what happens next and how to spot real improvement once you start fixing those inefficiencies.

1. Make the invisible visible

Most councils don’t have a process problem, they have a visibility problem.

When something gets stuck, people assume “the process is broken.”
In reality, it was probably never built properly in the first place.

Start by mapping a single process everyone complains about – maybe building consents, customer requests, or leave approvals.

And if you’re not sure what “mapping” actually means, we broke it down in Process Maps, SOPs & Automated Workflows: What’s the Difference?.

Once you can see your process end-to-end, the waste jumps off the page – double-handling, mystery approvals, endless email loops.

💡 Metric to watch: Average completion time.
At Glenelg Shire Council, one single process (Kerbside Waste & Recycling Request) was taking their team 430 hours a year. This process now takes 61 hours, which adds up to over 9 weeks of a full-time job saved on a single process.

2. Measure what matters, not what’s easy

It’s tempting to measure the things that are easy to count:
“How many SOPs did we write?”
“How many staff did we train?”

Useful, sure. But they don’t tell you if work is actually flowing better.

Here’s what to measure instead:

Metric	What it shows	Why it matters
🕒 Cycle time	How long tasks take from start to finish	Reveals bottlenecks
✅ First-time right rate	% completed without rework	Measures clarity & training
📨 Approval latency	Time between submission and sign-off	Shows decision delays
😊 Staff satisfaction	“How easy is this process now?”	Reflects morale & adoption

These are your true process improvement measures.
They turn “I think it’s better” into “I can prove it.”

3. Fix one small thing (fast)

The biggest mistake councils make?
Trying to improve everything at once.

Start tiny. Pick one pain point, like automating the approval chain for purchase orders or simplifying a customer request form.

Then track the before-and-after:

5 days down to 2
4 emails down to none

Small wins build momentum faster than any strategy document.

4. Stop measuring improvement by hand

Most teams start strong, until the “improvement spreadsheet” quietly dies three months in.
Someone forgets to update it. Another person moves departments. Suddenly, no one’s quite sure if things are actually better or just different.

That’s the trap. Manual measurement becomes its own workload.

Instead, make progress measurable by default.
When your workflows are digital, the data captures itself – how long each step takes, where requests pile up, and when things actually get done.

No extra forms. No new tracker. Just real visibility baked into the process.

When you can see performance in real time, improvement stops being a guessing game.
It becomes part of everyday work – transparent, automatic, and easy to act on.

5. Make improvement a habit, not a project

The best process work rarely makes headlines.
It’s the quiet habit of reviewing, tweaking, and celebrating small wins.

Skip the annual “process improvement project.”
Instead, build a culture where teams continuously fix friction.

Celebrate when:

A process runs 20 minutes faster.
A form loses three pointless fields.
Someone says, “That was actually easy.”

That’s what real improvement looks like – less noise, more progress.

The bottom line

Process improvement in councils isn’t about jargon or software. It’s about making everyday work simpler – and being able to prove it.

When your team can see progress, they’ll keep improving.
When you can measure it, leadership will notice.
And when you can automate it, it finally lasts.

6 Reasons You Shouldn’t Use the Flowingly AI SOP Recorder

by Sarah | Oct 15, 2025 | SOPs

6 Reasons You Shouldn’t Use the Flowingly AI SOP Recorder

AI might be the buzzword of the year, but let’s cut through the noise.

The Flowingly AI SOP Recorder isn’t built to dazzle you in a demo (though someone did fall off their chair when we showed them!). It’s built to fix the soul-destroying task of documenting procedures – the same procedures that auditors, regulators, and managers never stop asking for.

But here’s the catch: it’s not for everyone.

If you’re the wrong type of organisation, you’ll hate it. And we’d rather you work that out now than book a demo you don’t need.

Here are five reasons you shouldn’t use the Flowingly AI SOP Recorder.

1. You’re a small team with barely any procedures

Let’s be real: if you’re an SMB with a dozen procedures that rarely change and a team that can train each other over coffee, you probably don’t need the Recorder.

Yes, your documentation will be a bit messy. Yes, your staff will still occasionally bug each other with “How do I do this again?” emails. But it’s not going to sink you.

For smaller teams, Word, PDFs, or even a laminated checklist can get you by. The AI SOP Recorder really shines in councils and mid-sized organisations, where there are hundreds of procedures that need to be captured, updated, and shared across multiple teams.

If you’re not managing that level of complexity, it’s probably overkill.

Competitor tools like Scribe are awesome for individuals or small teams documenting quick steps, while Flowingly is built for bigger organisations managing hundreds of users and dozens of departments.

On average, Flowingly customers have around 300–400 active users, compared to Scribe’s typical team size of under 10. Not a dig – just a reminder these tools were built with different use cases in mind.

2. You’re not worried about audits or compliance

If the words “audit trail,” “privacy request,” or “LGOIMA” don’t strike fear into your heart, you’re in a rare position.

Most councils and public sector organisations deal with constant audit pressure. Whether it’s finance audits, privacy requests, or health and safety compliance, there’s always someone asking for evidence that procedures are documented and consistently followed.

The SOP Recorder is built for those teams – the ones who lose sleep over whether their 2019 Word doc will satisfy the next audit. It ensures procedures are standardised, governed, and version-controlled.

If compliance isn’t a headache for you, the AI SOP Recorder may not be your painkiller.

3. You love writing procedures manually

There are people who genuinely enjoy building SOPs by hand. They’ll happily spend an afternoon taking screenshots, resizing them in Word, formatting tables, and trying to make everything look neat.

If that’s your idea of a productive day, the Recorder will only ruin your fun.

It’s designed to cut procedure creation from 60 minutes to 5. It captures screenshots and steps automatically as you work, then generates a polished SOP without the formatting battle.

For organisations that need to create hundreds of procedures, this is a lifesaver. But if you only document once in a blue moon and like the manual grind, it’s probably not gonna be worth it.

4. User training isn’t high on your priority list

We’ve all seen the “sink or swim” approach to onboarding and system rollouts.

If that’s your training philosophy, the SOP Recorder probably isn’t for you.

Flowingly’s Recorder shines in teams rolling out big changes – ERP systems, CRM upgrades, whole-of-council transformations, where user training is seen as essential, not optional. Because a new system implementation is only as good as the change management and user adoption.

5. You’re not planning to modernise anytime soon

Some councils and organisations are ready to modernise. They’re moving away from legacy systems, they’re investing in better digital experiences, and they’re serious about service delivery.

Others… aren’t.

If your organisation is comfortable with SharePoint folders, outdated PDFs, and staff quietly hoarding knowledge in their inboxes, then AI will feel like too much too soon.

The Recorder isn’t a gimmick – it’s built for teams actively trying to reduce audit stress, cut admin time, and modernise how they capture and share procedures. If that’s not on your agenda, it’s not the right fit.

6. You’re married to your current tools

Here’s the big one. If you just want a lightweight SOP recorder like Scribe to sit quietly next to your existing tool stack, Flowingly isn’t for you.

Flowingly works best when you’re all-in on process improvement: SOPs embedded into process maps, connected to automated workflows, governed from a single platform.

Sure, it’s powerful as a standalone tool. But the SOP Recorder really shines when it’s part of your bigger process story. Not just capturing steps, but turning them into living, automated workflows.

If you’re not ready to unify your SOPs, maps, and workflows, you might still have the same frustrations and disconnect. And that’s okay – stick with the point solutions until you are.

So, who should use it?

If you’ve read this far and thought, “Actually, that sounds like us,” then the Flowingly AI SOP Recorder might be worth a look.

It’s built for:

Councils drowning in compliance, audit, and LGOIMA requests.
Mid-sized organisations with hundreds of procedures across HR, finance, and customer service.
Teams who don’t have the luxury of reinventing the wheel every year when staff turnover hits.

For those organisations, the Recorder can cut documentation time by 90%, bring order to compliance chaos, and make procedures actually useful again.

If that’s not you? No hard feelings – stick with Word.

Process Maps, SOPs, Automated Workflows: What’s the Difference

by Sarah | Oct 7, 2025 | Process Maps, SOPs, Workflows

Process Maps, SOPs, Automated Workflows: What’s the Difference

Let’s be honest – “procedures,” “SOPs,” and “workflows” get thrown around interchangeably. I’ve even made the mistake myself when talking about SOPs.

One council manager says “procedure,” their IT lead says “workflow,” and their compliance officer insists on “SOP.” Meanwhile, staff are stuck wondering whether they’re all talking about the same thing.

Spoiler: they’re not. And the confusion isn’t just semantic, it creates real-world headaches when it comes to training, compliance, and automation.

So, let’s clear this up once and for all.

Process maps = what we do

A process map is the high-level overview of a process.

Think of it as the recipe card for how something is done. It outlines the steps, decision points, and hand-offs between people or teams.

For example, a council’s Rates Rebate Process Map might show the resident submitting an application, the rates team reviewing the documents, the decision being recorded in the system, and a notification being sent back to the resident.

It’s the “what,” not the “how.”

Process maps are useful because they give everyone a shared understanding of the big picture. They’re often the first thing you’ll show to new staff so they can see how a service fits together. They’re also important for regulators, because they demonstrate that there is a structured approach behind the service you’re delivering.

SOPs = how we do it

A Standard Operating Procedure (SOP) goes deeper. It describes exactly how each step is carried out.

This is where you’ll see the screenshots, system logins, and “click here, then here” instructions. An SOP should be detailed enough that a new staff member could pick it up and complete the task correctly.

Take the same Rates Rebate Review example. An SOP might explain how to log into the software, where to find the rebate module, how to check that a proof-of-income document is attached, and what to do if information is missing.

It’s the “how,” not just the “what.” And without SOPs, process maps stay too vague – leaving room for errors, shortcuts, or staff “doing it their way.”

Automated workflows = doing it

Finally, an automated workflow is the orchestration of the process in action.

Instead of relying on staff to follow documents, the workflow guides them as they go. Forms are prefilled, tasks are automatically assigned, and reminders are sent without anyone chasing them.

In our Rates Rebate example, an automated workflow might trigger the moment a resident submits an online application. The system assigns the task to the right staff member, sends a reminder if the application sits idle for three days, and even generates the approval or decline letter automatically once a decision is recorded.

It’s the “doing,” not the “describing.”

Why organisations get this wrong

So why are these terms so often muddled?

Different departments use different language. HR might say “process,” IT says “workflow,” and Finance prefers “procedure.” Add to that the legacy tools councils and organisations are stuck with, Word docs, PDFs, SharePoint folders – and it’s no wonder the lines blur.

Then there’s the pressure to automate. Teams jump straight into digitising without first mapping the process or capturing the SOP. The result? Messy rollouts, misaligned expectations, and services that look neat on paper but fall apart in practice.

What happens when you skip a layer

Here’s where the risk really shows.

A process map without SOPs leaves too much open to interpretation, so staff end up with inconsistent outcomes. SOPs without automated workflows still rely on manual effort. The rules are followed, but hours are wasted chasing emails and approvals. And if you build an automated workflow without a process map or SOPs to back it up, you’ve created a black box: the workflow runs, but no one really understands the “why” behind it.

Skipping a layer is like building a house without foundations. It might hold for a while, but it won’t last.

Why the distinction matters

When councils and organisations link these three levels together, everything gets easier.

Process maps provide clarity. SOPs provide consistency. Automated workflows provide efficiency.

That’s when you stop firefighting and start building services that actually scale.

Bringing it all together

This isn’t just about tidy definitions. It’s about doing the work right.

New hires need the right level of guidance. Auditors want to see intent, consistency, and evidence. And IT teams can’t build reliable automations if the underlying maps and SOPs aren’t clear.

In short: process maps, SOPs, and automated workflows are connected, but not interchangeable.

Final word

Process maps, SOPs, and automated workflows aren’t three ways of saying the same thing. They’re three layers of the same system.

Process maps = What we do
SOPs = How we do it
Automated workflows = Doing it

Keep them separate but connected, and you’ll give staff clarity, auditors confidence, and IT teams a foundation to automate without headaches. Mix them up, and you’re back in SharePoint chaos with out-of-date documents and inconsistent service delivery.

It’s time to get the terminology – and the practice right.

The 60,000 Minute Problem: Why SOP Creation is Broken

by Sarah | Sep 29, 2025 | Process Improvement, SOPs

The 60,000 Minute Problem: Why SOP Creation is Broken

Let’s do the maths.

Some councils and mid-sized organisations have hundreds, even thousands of procedures that should be documented as Standard Operating Procedures (SOPs).

At an average of 60 minutes per SOP, that’s 60,000 minutes.
Or in plain English: 1,000 hours of admin.

That’s 25 weeks. More than half a year.
And that’s just to create them.

We haven’t even touched the hours wasted maintaining them, searching for them, or fixing the mistakes caused by missing or outdated SOPs.

This is the 60,000 Minute Problem. And it’s why SOPs, as most councils and organisations know them today, are broken.

Why SOPs matter (and why they drive everyone mad)

SOPs aren’t optional.

They keep you compliant when the auditors come knocking.
They stop key knowledge walking out the door when staff leave.
They prove to regulators (and your community) that you’ve got procedures under control.

The problem? They’re hated by everyone.

Managers hate chasing staff to “just write the procedure down.”
Staff hate creating them because it feels like paperwork for paperwork’s sake.
New hires hate using them because half the time they’re buried in a 79-page PDF last updated in 2019.

If you’ve ever heard “just ask Sharon, she knows how to do it”, you know exactly how broken the system is.

The real cost of SOPs

The 60,000 Minute Problem isn’t just about the time it takes to create SOPs. It’s about everything that happens afterwards.

Maintenance madness: SOPs need updating every time a system or procedure changes. Most never are.
Scavenger hunts: Staff waste hours trying to find the right doc in SharePoint, OneNote, or someone’s desktop.
Inconsistency: Different teams format SOPs differently (or don’t at all). Some are detailed novels, others are two bullet points and a smiley face.
Compliance chaos: Outdated SOPs = audit nightmares.

Multiply that across hundreds of procedures, and you’ve got a hidden cost running into the hundreds of thousands of dollars in wasted staff time, compliance risk, and delayed projects.

How we got here (and why it’s not your fault)

Most SOPs today live in a Frankenstein mix of Word docs, PDFs, SharePoint folders, and screenshots.

Different departments use different tools:

Finance uses Word.
HR uses OneNote.
Field services send SOPs around by email.
IT dumps them in SharePoint.

The result? A patchwork of SOPs that no one can find, no one can govern, and no one trusts.

This isn’t because your teams are lazy. It’s because SOP tools haven’t kept up with how we actually work.

When procedures change weekly (sometimes daily), asking staff to manually document and format everything is unrealistic.

The broken SOP lifecycle

Here’s what usually happens in councils and mid-sized organisations:



Someone requests a SOP

Usually after a mistake, an audit finding, or a new hire is onboarded.



Staff cobble it together

Screenshots pasted into Word, inconsistent formatting.



The SOP gets buried

Lost in a folder with poorly followed naming conventions.



The SOP gets outdated

New system, new procedure, but the doc stays the same.



The SOP gets ignored

Staff go back to asking Sharon how to do it.

Sound familiar? This is why SOP creation feels like busywork. Because in its current form, it is.

Why the old way doesn’t scale

The truth is, SOP creation the old way (manual, document-heavy, one procedure at a time) doesn’t scale.

It doesn’t work for councils with high staff turnover and constant compliance requests.
It doesn’t work for organisations juggling dozens of software systems.
It doesn’t work when teams are already drowning in emails, forms, and audits.

The old way assumes staff have hours free to write “mini manuals.”
They don’t.

And the kicker? The people who know the procedure best (frontline staff) are usually the least likely to have time to write it down.

A better way forward

So what’s the alternative?

Instead of staff spending 60 minutes manually writing a SOP…

AI can capture it in 5 minutes.
Screenshots are taken automatically.
Steps are recorded as you work.
Docs are standardised in a single format.
Everything is stored in one governed location.

That’s the difference between 60,000 minutes and 5,000 minutes.
Between SOPs being a hated chore and SOPs being a helpful tool.

What this means for councils & mid-sized orgs

Imagine:

Faster onboarding: New hires follow clear, up-to-date SOPs embedded directly into workflows.
Less staff drain: Existing staff aren’t constantly pulled away to re-explain tasks.
Audit readiness: Every SOP is traceable, standardised, and version-controlled.
Continuous improvement: Teams update SOPs as they work, not six months later (or never).

For councils, this could mean faster LGOIMA responses, smoother ERP rollouts, and less risk during audits.

For mid-market businesses, it could mean scaling operations without scaling headcount.

Why fixing SOPs unlocks everything else

Broken SOPs don’t just waste time – they hold back your entire transformation journey.

You can’t automate a procedure you haven’t standardised.
You can’t train staff on systems without reliable SOPs.
You can’t prove compliance without auditable procedures.

Fixing SOPs is the foundation for everything else: mapping, automation, and better service delivery.

💬 Final word

The 60,000 Minute Problem isn’t just a number. It’s a symbol of how much time, energy, and opportunity organisations waste trying to do SOPs the old way.

The good news? You don’t have to accept it.

With AI-driven SOPs, what once took 60 minutes now takes 5.
What once drained staff now empowers them.
What once got buried in SharePoint hell now lives in a single, trusted platform.

It’s time to stop burning thousands of hours a year on documentation nobody uses – and start building SOPs your teams will actually thank you for.

« Older Entries

Next Entries »