What happens when your financial architecture depends on one person’s knowledge, energy, and presence?
Your finance person — the one who knows the passwords, the grant deadlines, the reporting quirks of every funder — gives notice. Or goes on leave. Or simply burns out and starts making mistakes. Within weeks, reports stop. Compliance deadlines surface that nobody else knew about. The board asks a question about cash flow, and nobody in the room can answer it.
This is not a hypothetical. Vantage Point’s 2025 Stretched Thin report found that nearly nine in ten BC nonprofits reported that demand for their services exceeded their ability to deliver — even as government funding remained flat and most other revenue sources contracted. When organizations are that stretched, work concentrates on whoever can carry it. The Charity Insights Canada Project shows that turnover in the charitable sector jumped from 27% to 39% between 2023 and 2024, with burnout growing as a primary driver. YMCA WorkWell reports that 71% of nonprofit leaders feel burned out. The pressure on the people who hold financial operations together has never been higher.
Most organizations respond to this risk the way you’d expect: try to retain the person, offer what flexibility you can, and hope they stay. And those are reasonable instincts. But they don’t address the underlying problem. Because the real risk isn’t that you might lose your best person. The real risk is that your financial architecture may not be reliable without them.
The reliability test
There is a pattern worth examining here. The organizations that feel most fragile financially aren’t necessarily the ones with the least money. They’re often the ones where financial knowledge, processes, and decision-making capacity live inside one or two people’s heads rather than inside shared, visible systems. And this is rarely an accident. Many organizations across the sector inherited financial structures designed for compliance and reporting to funders — not for building internal capacity. The architecture was never meant to serve the organization. It was meant to satisfy external requirements. What’s missing is not competence. It’s the infrastructure that serves the people doing the work.
A useful test: financial wellness isn’t about what exists — it’s about what is reliable under pressure.
Your organization may have a budget. But is it used for actual decision-making, or does it sit in a file from last January? You may have financial reports. But do they come out on a predictable cycle, or do they appear when one particular person has time? You may have a grant register. But could someone other than your finance lead tell you which compliance deadlines are coming in the next 60 days?
If the honest answer to any of those is “only when one particular person is here” — you don’t have a financial system. You have a financial hero. And heroes, however dedicated, are not architecture.
This is not a niche problem. The Nonprofit Finance Fund’s 2025 survey found that over half of nonprofits have three months or less of cash on hand. That is a funding problem, undeniably. But it is also a visibility problem — because when resources are that scarce, the ability to see them clearly and manage them deliberately is the difference between navigating uncertainty and being overwhelmed by it.
Visibility before systems
The instinct when you recognize this pattern is to jump to solutions: document the procedures, cross-train the team, invest in better software. And all of that matters — eventually. But our experience shows that those efforts routinely fail when they’re built on top of foundations that aren’t yet reliable. You can’t cross-train someone on a reporting process that doesn’t run consistently. You can’t document procedures that don’t exist yet. You can’t automate what you can’t see.
Which raises the question: why are so many foundations unreliable in the first place? Dan Pallotta argued over a decade ago that the sector’s obsession with minimizing overhead was starving organizations of the infrastructure they needed. He was right — and the consequences show up in exactly the pattern this article describes. When funders cap administrative costs, when donors judge organizations by their overhead ratio, the predictable result is underinvestment in financial architecture: too few finance staff, no budget for systems, no time to build what would make the organization resilient. The hero doesn’t emerge because the organization failed to plan. The hero emerges because the funding model made planning unaffordable.
This suggests that the first step may not be building better systems. It may be restoring basic financial visibility — making what is hidden, shared; making what is ad-hoc, consistent; making what lives in one person’s head, visible to everyone who needs it. When an organization has that visibility, the conditions exist for the next stage of work: building the policies, procedures, automation, and team structures that make those results durable. Not just making the information visible, but embedding it in systems that hold regardless of who is in the chair.
What the foundations are for
None of this work is an end in itself. Restoring cashflow visibility, building reliable reporting cycles, documenting policies — these are not the goal. They are the architecture that makes the goal possible.
In our framework, the developmental journey doesn’t end with sound bookkeeping or even with strategic financial leadership. It ends with financial systems that serve community-defined priorities — where accounting supports mission, impact, and long-term stewardship rather than just compliance. Where the question is no longer “are we meeting the funder’s requirements?” but “are our financial systems serving what this organization actually exists to do?”
That’s the horizon. And it becomes reachable when the foundations are in place — when more than one person can see the numbers, when reporting is consistent enough to trust, when a budget is a living tool rather than a historical document. Every foundation you restore is a building block toward financial architecture that serves your purpose, not someone else’s reporting requirements.
If your organization recognizes itself in this article — if the finances feel like they depend on one person’s knowledge, energy, and presence — that’s not a failure of your team. It’s a structural condition that can be identified, named, and addressed. And the starting point is simpler than you might think.
Join us
Pamela Oliva and Gordon Holley will be leading When Money Tightens, What Actually Holds? — Restoring Financial Visibility When Decisions Can’t Wait, an interactive three-hour virtual session that helps nonprofit leaders diagnose where financial visibility breaks down, apply practical tools to restore it, and leave with a concrete action plan and ready-to-use templates.
Part of the Building Reliable Financial Capacity in Times of Uncertainty seminar series, delivered in partnership with CharityVillage.
Not ready to register? Start with the free Financial Visibility Diagnostic — six questions to see where your organization stands. Download now!
Pamela Oliva is the CEO of Humanity Financial Management Inc., a B Corp, Benefit Corporation, and Bronze PAIR Certified firm dedicated to advancing financial wellness, governance capacity, and long-term sustainability for nonprofits, charities, and First Nations. She works at the intersection of finance, governance, and community development, and is recognized for translating complex financial information into practical, values-aligned tools that build internal capacity and confidence.
The views expressed in this article are the author’s alone and do not necessarily represent those of CharityVillage.com or any other individual or entity with whom the authors or website may be affiliated. CharityVillage.com is not liable for any content that may be considered offensive, inappropriate, defamatory, or inaccurate or in breach of third-party rights of privacy, copyright, or trademark.
