Five things multi-programme youth charities struggle with before they even think about switching systems

Referral routes that blur together. Funder years that never match your own. Hard outcomes and soft outcomes living in separate systems. Here's what growth actually breaks first.

Most conversations about switching case management systems start the same way: with a spreadsheet, a strained team, and a nagging sense that reporting shouldn't be this hard.

We talk to a lot of charities delivering employment support, skills training and youth services across multiple programmes and funders. Long before anyone mentions a specific platform, the same handful of problems tend to surface. Not because any one system is badly designed, but because growth creates complexity that most systems were never built to absorb.

Here are five of the most common ones.

1. Referral routes blur into each other

When a charity runs one programme, referrals are simple: one form, one inbox, one team looking at it.

Add a second programme, then a third, and referral routes start to overlap. A young person referred by a school might also come through a general enquiry form. A colleague spots someone at a partner event and logs them separately from a formal referral that arrives the same week. Before long, the same person exists in the system twice, under two different programmes, and nobody's entirely sure which record is the "real" one.

The result isn't just messy data; it's double-counted beneficiaries, duplicated outreach to the same family and staff time spent untangling which record to update. Teams often know exactly where the confusion comes from; new programmes were built on top of an existing structure rather than given their own clean routes in, but fixing it once it's in place is a much bigger job than designing for it from the outset.

2. Funder years never match your operating year

Every charity has an internal operating rhythm which is often tied to its financial year and distinct from the timeframe in which a funder expects a report. One grant might run August to July. Another September to August. A third wants a report at the ten-month mark; a fourth only wants final numbers once the year has fully closed.

None of this lines up with how the work actually happens, which is continuously, without natural start and end points. Teams end up manually reconstructing figures for whichever window a particular funder cares about, often weeks after the fact, hunting through spreadsheets and case notes to reassemble numbers that were never captured with that window in mind.

The teams which cope best with this are the ones the ones whose systems let them define reporting periods per funder without needing to restructure how the underlying work is recorded.

3. Hard outcomes and soft outcomes live in different places

Employment numbers, volunteering placements and qualifications gained are usually tracked properly because funders ask for them directly and they're easy to count.

Softer, longer-term change is a different story. Confidence, wellbeing and sense of direction are the types of thing that validated tools like outcome stars are designed to capture but they often live in a completely separate system, sometimes with a separate login, sometimes still on paper. Bringing the two together for a single beneficiary, let alone a whole cohort, usually means manually cross-referencing two data sets that were never designed to talk to each other.

Teams increasingly want one place that holds both: the numbers that prove reach,and the story of distance travelled that proves depth.

4. Case studies are a scavenger hunt

Every fundraiser knows the request: "Can we get a case study for this report?" And every fundraiser will also be familiar with what that actually involves in practice; messaging frontline staff, waiting for replies, digging through shared drives for the right photo, checking whether consent was actually given and hoping someone remembers which young person had the story worth telling.

None of this is because staff don't care about capturing good stories. It's because when a great quote or a meaningful update happens - often in a one-to-one session, in passing - there's rarely a fast, low-friction way to record it there and then, attached to the right person's record, with consent already logged alongside it. So it gets remembered informally, or not at all and reconstructed under deadline pressure instead.

5. People get lost between programmes

Charities that serve people with additional needs such as disabilities, neurodivergence, complex personal circumstances, often see the same individual move through more than one service over time. A young person joins an employment programme, then later a separate skills course, then reappears through a different partner referral entirely.

Systems built around a single programme view make this hard to see. Staff on one project have no visibility of someone's history on another, even when that history is directly relevant to how best to support them now. It's not a privacy problem to solve by throwing open access to everyone, it's a design problem.that's solved by having one coherent profile with appropriate visibility, rather than forcing a choice between fragmented records or unrestricted access.

None of these show up on a feature list

What's notable about all five is that they rarely get resolved by a single feature. They get resolved by how a system is structured: whether it lets you define your own referral routes without straining one generic form, whether reporting periods are flexible per funder, whether qualitative and quantitative data sit on the same profile, whether capturing a story takes seconds rather than a follow-up email chain and whether a person can be seen holistically without compromising the boundaries between services.

If any of these sound familiar, you're not alone... and you're not behind! These are simply the growing pains of doing good work at scale. The good news is that all five are solvable with the right structure in place and most charities don't need to overhaul everything at once to start fixing them.

See what this looks like in practice

Makerble is built around exactly these problems: flexible referral routes per programme, funder-specific reporting periods, combined qualitative and quantitative data on every profile, one-click case study capture, and a person-centred view that respects boundaries between services.

Book a free demo to see how it could work for your organisation or start a free trial to explore it yourself.

‍

Our CRM receives referrals and event signups from forms on your website.