You're growing. Nobody is sure the systems behind the growth are keeping up.
Why this happens
Systems get sized for the organisation that bought them. Growth doesn't break them all at once. It makes each one work a little harder, and the strain shows up as human effort rather than as error: an extra approval, a longer spreadsheet, one more person who has to be asked before anything can move.
Growth is also busy. Attention goes where the growth is, to the new site, the new staff, the new contract, and the systems underneath get looked at only once something has gone wrong.
What usually gives way first isn't the software. It's the informal arrangements around it. A process that works because everyone knows each other stops working at the point where they don't.
We see this in
How to tell
Take one process you depend on (onboarding a new member of staff, opening a new site, raising an invoice) and ask what would happen if you had to run it four times in one month. If the honest answer means overload for a person rather than a system, you have found the ceiling.
Put your headcount two years ago next to today's, then list what you have changed about how work gets recorded. If the second list is shorter than the first, the gap is real.
Ask finance and operations for the same figure for last month, separately. If two different numbers come back, the reporting has already been outgrown.
Why it’s worth fixing
Growth is the point where an untidy system stops being an irritation and starts being a limit. Everything that works because somebody knows where things are gets slower as you add people, and the slowdown arrives after you have committed to the new site or the new contract.
The risk sits in the things that are only occasionally tested: safeguarding records across sites, staff vetting, funder reporting. They hold up at your current size because one person checks them personally. That check does not scale, and its absence stays invisible until it turns up as a finding.
Fixing it while you are growing is also cheaper than fixing it afterwards. You are already asking people to work differently, which is the one moment when a change is easy to introduce. Leave it, and the improvised version hardens into the way it has always been done.
We fixed this here

The Outdoors Group is growing fast. We are building the IT function that carries it. →
Does this apply to you?
The Operational Readiness Scorecard takes fifteen minutes and will tell you exactly how exposed your organisation is, and what to do first.
Start the Scorecard