8 Questions That Reveal Whether Your Financial Policies Actually Work 

Most nonprofits technically have financial policies. 

What’s less clear is whether those policies are actually doing any work — or whether people are quietly filling in the gaps with judgment calls, workarounds, or “just checking with one person.” 

When that happens, decisions slow down, risk concentrates, and leadership gets pulled into things they shouldn’t need to touch. 

These nine questions aren’t about compliance. They’re about whether your policies are supporting the organization — or relying on people to compensate for them. 

 1. Who Can Approve Spending — and When Does It Escalate?

Policy area: Delegation of Authority / Spending & Approval 

When approval limits aren’t clearly defined, decisions drift upward. Staff escalate purchases out of caution, not necessity. Leaders get pulled into routine approvals simply because no one is sure where the line is. 

Over time, this creates bottlenecks and frustration on both sides. Staff hesitate. Leaders feel buried. Risk also increases, because too much decision-making is concentrated in one role instead of being distributed intentionally. 

A working policy answers this cleanly: 

• Who can approve what 

• At what dollar thresholds 

• When escalation is required — and when it isn’t 

If those answers aren’t obvious, your organization is likely slower and more exposed than it needs to be. 

 

2. What Happens When the Usual Decision Maker Is Away? 

Policy area: Delegation of Authority / Continuity 

If payments stall, contracts wait, or expenses pile up because one person is unavailable, the issue isn’t staffing — it’s structure. 

Absences are normal. Vacations, illness, parental leave, and transitions should not bring routine operations to a halt. When they do, it’s often because temporary authority hasn’t been clearly defined. 

Strong policies anticipate this by spelling out: 

• Who steps in 

• What authority they have 

• What decisions still require escalation 

If your answer is “we just wait” or “we figure it out when it happens,” that’s a clear signal your policies aren’t carrying enough weight. 

 

3. How Do New Staff Know What’s Allowed Without Asking?

Policy area: Expenses / Purchasing / Credit Cards 

If new hires rely on constant confirmation before spending, approving, or submitting expenses, your policies aren’t functioning as practical guidance. 

This slows onboarding and creates inconsistency. One person might get approval for something another person avoids — not because the rule is different, but because the guidance isn’t clear. 

Good policies reduce questions. They give people confidence to act within boundaries instead of defaulting to “just check first.” 

If your policies aren’t helping new staff operate independently, they’re adding friction instead of removing it. 

 4. How Are Exceptions Documented — Not Just Approved?

Policy area: Financial Procedures / Exception Handling 

Exceptions are normal. Emergencies happen. One-off situations arise. The risk isn’t the exception — it’s what happens after. 

When exceptions are handled informally and never documented, patterns disappear. Decisions become harder to explain later. Accountability weakens, especially when staff or leadership changes. 

A solid policy doesn’t just say whether exceptions are allowed. It explains: 

• How they’re recorded 

• Who documents them 

• Where that record lives 

If your organization relies on memory or email trails to explain past decisions, that’s a gap worth addressing. 

 

5. Who Checks the Checker?

Policy area: Internal Controls 

High trust environments still need controls. 

If one person can initiate, approve, process, and reconcile a transaction, risk increases — even if everyone involved is competent and well-intentioned. The issue isn’t trust. It’s exposure. 

This question tests whether oversight is built into the process or simply assumed. Even small nonprofits can implement basic separation or review steps that reduce risk without adding complexity. 

If your answer is “we trust them” rather than “here’s how it’s reviewed,” your policies may be relying too heavily on individuals instead of structure. 

 

6. What Breaks If One Person Leaves Tomorrow?

Policy area: Financial Procedures / Documentation 

Turnover exposes gaps quickly. 

If key processes live in someone’s head — how invoices are approved, how reports are prepared, how deadlines are tracked — transitions become stressful and risky. 

Policies don’t need to capture every step in detail, but they should make it possible for someone new to understand how things work without starting from scratch. 

If your answer is “a lot,” your organization is more fragile than it appears. 

 

7. Can You Refer to a Policy for Clarity When a Decision Is Questioned?   

Policy area: Governance-Level Financial Policies 

When board members, auditors, or funders ask why something was handled a certain way, explanations should point to an agreed framework — not personal judgment. 

Without that, decisions feel inconsistent and harder to defend. This puts unnecessary pressure on staff and leadership and can create tension with governance bodies. 

Clear policies protect people by shifting conversations from “why did you decide this?” to “this is how we agreed decisions would be made.” 

 

8. Are Policies Used to Make Decisions — or Just Stored?

Policy area: Financial Policy Framework 

Policies that aren’t referenced in real decisions aren’t doing their job. 

If teams default to asking leadership instead of consulting policy, it’s usually because the policies aren’t accessible, clear, or practical. Over time, relevance erodes. 

A working policy framework shows up in day-to-day conversations. It helps resolve questions, guide decisions, and reduce back-and-forth. 

If your policies live in a folder no one opens, they aren’t supporting the organization. 

How to Use This Test 

You don’t need to score yourself. 

As you read through the questions, note: 

• Which ones were easy to answer 

• Which depended on a specific person 

• Which made you pause or say “it depends” 

Those moments of hesitation are useful. They show you exactly where structure may be missing. 

When financial policies are clear and usable, decisions move faster and leadership feels lighter. When they aren’t, the organization relies on people to compensate — and that doesn’t scale. 

If these questions surfaced gaps, the next step isn’t to write more policies. It’s to understand where structure is missing and what decisions your policies should be supporting today. 

That’s often easier to see with an outside lens. A short, focused review can quickly highlight which policies are pulling their weight — and which ones need attention.