Taking a farming charity's case-work out of the spreadsheets
The FCN Support Portal is one secure place where the Farming Community Network's staff and volunteers open and work cases, find the right colleague to help, and get the documents they need.
The Mission
The Farming Community Network (FCN) supports farmers and farming families through difficult times. Its helpline and volunteers across the UK handle sensitive, sometimes urgent cases. FCN wanted to run that work safely and without strain on its team. That meant protecting the personal details of people at a vulnerable moment, making sure every case reaches the right person and never stalls, and freeing its small team from the spreadsheet admin that was taking up their week.
The Outcome
The FCN Support Portal is one secure place where staff and volunteers open and work cases, find the right colleague to help, and get the documents they need.
The Impact
- Helpline volunteers now open a case themselves as they take the call. They no longer wait for the admin team to create and share a spreadsheet.
- The portal is designed to remove most of the roughly 20 hours a week of spreadsheet admin that fell on one person. [TODO: confirm the real saving after go-live]
- The twice-yearly breakdowns that needed a developer to fix them are gone.
- Access to sensitive case information follows each person's role and county automatically, not sheet by sheet.
- FCN's leaders can see what changed each day and spot cases that have stalled.
- It's built for 20 staff and more than 100 volunteers, rolling out in stages, with case-work going live in spring 2027.
When the spreadsheet became the system
When a farmer rings FCN's helpline, they might be facing debt, animal disease or a bereavement, or simply feel alone. A volunteer takes the call. From there, the case needs to reach someone local who can help, and quickly.
For years that journey ran on Google Sheets: lots of them, linked together. For every new case, someone in the admin team created a sheet by hand and shared it with the helpline volunteer. The set-up kept running into Google's limits on how many parts of a sheet can be locked and how widely a sheet can be shared. Access had to be managed one sheet at a time. That came to about 20 hours a week, almost all of it falling on one person: the helpline coordinator. And about every six months the whole thing broke badly enough that a developer had to rescue it.
FCN's team knew this was a data-protection risk. It had been on their radar for a while. The tipping point came when the developer who had built the set-up disappeared. I was brought in to keep it running, and once I understood it from the inside, I told FCN honestly that it was no longer fit for purpose. They needed a system built around how they actually work.
Working it out together
FCN's team know their work better than anyone. They knew what they needed and had good ideas about how it might work. What they couldn't know was what the technology made possible. So we worked side by side. They started with a wish list, we split it into phases together, and we agreed what the first version absolutely had to do.
Case-work like FCN's is intricate. One phone call can go many different ways. Rather than pretend we could map every path in advance, we agreed a fixed price with a deliberately flexible scope. Sometimes you have to see version one before you can see what's possible. The scope changed as we learned, and the price didn't. FCN had cost certainty and still ended up with the system they needed, not just the one they first described.
Three problems shaped the work.
Getting each case to the right people, and only them. FCN is organised by county, with coordinators at county, regional and national level. A call from Doncaster needs to reach the local volunteer in South Yorkshire and stay visible to the people above them, but nobody else. The portal routes every new case automatically by county, across all the UK's counties. Some areas are covered by partner organisations rather than FCN. That wasn't in the original brief, but I suggested we could handle it within the budget. Those cases are now referred on automatically, and the partner confirms with one click that they've received it.
Protecting people at a vulnerable moment. Many calls involve health, money and family details. Where there's no permission to share a case, it's held back for FCN's admins. Email alerts never include personal details, only a case number and a link that needs a login. Even the links in emails are built so that automated email scanners can't "confirm" a referral nobody has actually read.
Coping with real life. A farmer with an ongoing case might ring the helpline again. The helpline volunteer no longer has access to that case, because it's being handled locally. Before, this meant a duplicate case or details passed around by email. Now the volunteer can be given 24 hours' access to the existing case, adds what they've learned, and the access ends automatically.
As FCN saw what could be automated, more ideas followed. Reminders now go out when a case has sat unclaimed for three days, a daily morning summary goes to the right people, and each case shows when it was last touched, so stalled cases stand out. A directory lets support officers find who across the organisation knows about finances, managing people or specific farming issues, so the right expertise can be brought into a case.
Every change was tested on a separate practice site with made-up data before it went anywhere near the real thing. The team got plain-English checklists so they could try each feature themselves.
A decision made carefully
FCN had spoken to another company, which quoted more than £50,000. My proposal came in well below that, and FCN rightly asked whether something critical would be missed. [TODO: confirm you're happy to publish the competing quote figure]
So we tested it together. We had several conversations working through every requirement, and FCN looked at off-the-shelf tools before agreeing that nothing on the market fitted the way their network operates. Because I'd spent time inside their existing system, I could size the job accurately. What they were really deciding was whether to trust that knowledge.
They did their homework, and then they made the call. For a small charity, committing to bespoke software is a real decision. FCN made it with their eyes open.
Rolling out carefully
Because the information is so sensitive, the rollout is staged on purpose. Staff are joining the portal now, volunteers follow between December and March, and case-work goes live in April/May 2027. A built-in pilot switch lets FCN start case-work with a hand-picked group before opening it to everyone. In the meantime, sign-up, the directory and the document library are already in use. [TODO: confirm]
For FCN, the change is about more than time saved. Volunteers can act the moment the phone rings. The helpline coordinator's time goes back to the people the charity serves. There's no fragile set-up waiting to break. And FCN's leaders can see, day by day, how every case is moving. [TODO: after go-live, replace expectations with real results: hours saved, cases handled, time to claim]
The portal is live at support.fcn.org.uk (sign-in only), and it's designed to grow, with training records next on the list.
“[TODO: testimonial from FCN's helpline and operations coordinator]”
Running something important on spreadsheets?
If your team's work has outgrown the tools it started on, let's talk about what it could look like.
Get in touch