How nonprofits plan for losing a major donor in cash forecasts

The short answer to how nonprofits plan for losing a major donor is that they move that gift out of the annual total and into the months when the cash was due. The main condition is that the forecast carries the gift as a dated event, with a version that assumes it never arrives.

Why a lost gift hits the timing of cash first

Most nonprofit budgets rest on an annual number: the gifts the organization expects to raise over the year. That number is useful in board discussions, but it hides when the money actually arrives. A major donor who gives in two large installments, one in the spring and one in the fall, does not sit in a single line that you can cross out. Losing that donor changes the calendar, and the calendar decides whether the bank balance covers payroll on the day it is due.

The first mistake many finance teams make is treating the loss as a cut to total revenue for the year. The plan goes down by the amount of the gift, the spreadsheet gets saved, and everyone assumes there is time to adjust. In practice, the gap shows up at specific points. A payment that was expected at the start of a quarter does not come, while rent, insurance and vendor invoices still arrive on their normal dates.

Here is the catch: a nonprofit can finish a year with a balanced budget and still need a short-term credit line or a delay in paying vendors. Budget and cash are different tools. The budget tells you whether the organization spent less than it raised. The cash forecast tells you whether the money on hand will be enough in each week or month. A major donor often matters more to the second question than to the first.

Timing gets harder when the gift is restricted. be used for a designated program, and they cannot always be moved to cover general operating costs. If the lost donor funded a restricted project, the question is not only how much cash is missing. The question is which costs the organization can pay from the unrestricted funds that remain, without misusing the restricted money. Ask the development team and the accountant to read the gift agreement before the forecast is finalized.

The size of the gap also depends on how much unrestricted cash comes from a small group of people. If one donor supplies a large share of that cash, the forecast needs a dated scenario for that donor, not a generic cut spread across every revenue line. A flat cut hides the months when the gap is widest. A dated view shows exactly where the account would have run short, and which bills would have been due that week.

Separating pledges, received gifts and expected renewals in the model

Before you remove anyone's gift, you need to know what kind of money the model is counting. Received gifts are cash already in the bank. Pledges are written promises with a payment schedule. Expected renewals are gifts the organization believes will happen because the donor has given before, but nobody has promised them yet. Each category carries a different level of confidence, and the forecast should show all three separately.

Pledges need care. A pledge is not the same as a check. Some are conditional on matching funds, a milestone or a board approval. Others are paid over several years, and the schedule may change if the donor's situation changes. The forecast should record each condition next to the payment, and the timing should follow the signed agreement, not the hope that the donor will pay early.

Expected renewals are where forecasts usually go wrong. A donor who gave every year may pause for reasons the organization does not know about, such as a shift in the donor's business, a new giving priority or a personal decision. The model should not assume a renewal without evidence. A simple rule helps: count an expected renewal only when a recent conversation supports it, and label the number as an estimate in the file itself.

Keep the categories visible in the model, not only in a footnote. When a board member sees one line labeled revenue, nobody can tell how much of it depends on a donor who has not committed. That is the part of the number that changes when a donor leaves, so it should be easy to find. The same goes for the accounting view. Nonprofit financial statements follow the not-for-profit guidance in the FASB codification, and the accountant decides how promises to give are recognized there. The cash forecast does not have to match the statements line for line, but the two should not contradict each other without an explanation.

Finally, date every pledge and every renewal estimate, and record when the information was last confirmed. A category without a date tends to drift into the base case over several months. Once a donor's renewal sits in the same row as a received gift, the model stops telling you which numbers are solid.

Building a loss scenario with real triggers and dates

A loss scenario is a version of the cash forecast in which one donor's expected payments do not arrive on the dates they were planned for. It is not a pessimistic guess about the whole year. It is a targeted removal of specific money from specific months, so the board can see the effect on the account in each period.

Start with the signed agreements and the gift log, not with a percentage. Suppose a hypothetical organization expects one donor to pay in March and again in September. The scenario removes both payments from those months and leaves everything else in the forecast unchanged. If the gap appears in April, the organization can see that the problem starts the month after the missing payment, which is when a decision is needed. The steps below keep the work consistent from one review to the next.

1. Pull the donor's scheduled payments from the signed agreements and the gift log.


2. Remove each payment from its scheduled month, not from the annual total.


3. Recalculate the cash balance month by month, using the existing payment calendar for payroll, rent and vendors.


4. Mark the lowest point in the forecast and note the month when it occurs.


5. Write down what would have to change to cover that low point, such as a delayed hire, a deferred purchase or a credit line.

Triggers matter because a loss rarely arrives on the day it is announced. Early signs tend to be quieter. A donor stops returning calls, a renewal conversation keeps getting pushed, the donor's company changes ownership, or a gift arrives later than usual without explanation. Decide in advance which signs move the scenario from a what-if exercise into an active plan. Write them down before anyone needs them, because during a stressful month people tend to argue about whether the warning sign counts.

Keep the scenario inside the same model as the base forecast, so the two can be compared line by line. A separate file tends to drift from the base case after a few updates, and then nobody is sure which version matches the bank statement. The board should see both versions side by side, with the same dates and the same vendor schedule. The only difference should be the removed payments.

The catch is that a scenario is only as good as the dates behind it. If the development team cannot say when a donor usually pays, the scenario will look precise and still be wrong. Ask for those dates before you build the model, and mark the ones that are estimates. A scenario with honest gaps in it is more useful than one that hides them behind neat monthly figures.

Setting cash thresholds that tell the board when to act

A forecast becomes a decision tool when it has a cash threshold: the minimum balance the organization wants to hold, set in advance and written into a board policy. Many organizations express that minimum in weeks of payroll and fixed costs rather than a single fixed amount, because the part-time CFO cost in Massachusetts base changes over the year. Whatever method you choose, the board should agree to it, and the minutes should record the reason.

A threshold without an owner is just a warning light nobody checks. Name who updates the forecast, who compares it to the threshold and how often that happens. In a stable period, a monthly check may be enough. When a major donor is at risk, the same check may need to happen every week until the renewal question is settled. The owner should also know who to call when the lowest point falls below the threshold, so the response does not wait for the next board meeting.

When the threshold is breached, the responses usually come in a rough order, starting with the ones that are easiest to undo:

• Pause discretionary spending, such as travel, events and non-urgent purchases.


• Delay hires that are not tied to a funded program.


• Ask existing donors for a bridge gift that covers the gap until the normal schedule resumes.


• Draw on a credit line only with a written repayment plan that the board has reviewed.


• Review any restricted fund that could legally cover eligible costs, with counsel or the accountant.

The bridge gift needs particular care. Asking a donor who just left to come back right away can damage the relationship and make the next conversation harder. It is usually better to approach other current donors and to explain the timing honestly, without framing the shortfall as a crisis caused by the donor who stopped giving. The development director should lead that conversation, because donors respond to people they know.

Credit lines and short-term borrowing carry their own conditions. Read the repayment terms, any covenants, and whether the lender can reduce or call the line during a weak quarter. A line can bridge a timing gap between an expected payment and a bill. It does not fix a shortfall that repeats every quarter, and the board should not treat it as a substitute for a sustainable revenue base. Record the decision, the amount the organization expects to repay and the date by which the plan will be reviewed.

Common mistakes that make the forecast look safer than it is

Most forecasting errors are not dishonest. They come from habits that make the numbers look steadier than the donor data supports. Spotting these habits early is often more valuable than building a more complicated model, because the same mistakes repeat across organizations of very different sizes.

The most common one is spreading a donor's loss evenly across the year. Finance teams do it because it is quick, and it feels fair. The problem is that the actual gap sits in one or two months, and an even spread makes the low point disappear into the average. A board that sees a small reduction every month may not realize that one payroll date is at risk.

• Spreading a major donor's loss evenly across all months, which hides the real low point.


• Counting a verbal commitment as a signed pledge.


• Keeping an old scenario after the donor has said no or stopped responding.


• Moving restricted money between programs without checking the gift terms.


• Updating the forecast only when the annual report or the audit is due.

Keeping an old scenario is a quieter error and a more costly one. A team builds a loss scenario in the spring, the donor's renewal stays uncertain, and the scenario is never refreshed. By the fall, the donor has formally declined, but the model still shows a small probability of renewal in the same month. Each update that is postponed makes the forecast a little more optimistic, and the board receives a document that no longer reflects the organization's situation.

Counting a verbal commitment as a pledge is another easy mistake. A donor may say they plan to give in the fall, and that is useful information, but it is not a signed schedule. The forecast should record it as an expected renewal, with a note about who heard the commitment and when. If the donor later confirms it in writing, the item can move into the pledge category with the new date.

A useful check is to ask whether the forecast would have caught a loss that already happened. Take a donor who stopped giving last year and run the model as if you had known about it at the time. If the model would not have shown the gap in the right month, the problem is in the method, not in bad luck. Fix the method before the next donor leaves.

What an outside finance lead can and cannot do in this process

Outside finance help can build the model, set up the scenario, define the thresholds and explain the results to the board in plain language. That is real work, and it is often the part that nobody inside the organization has time to do while running programs, payroll and reporting. A good finance lead also brings a second view of the numbers, which can catch errors that the team has stopped noticing.

There are things outside help cannot do. It cannot make a donor give again. No forecast changes the donor's decision, and no advisor can promise that a lapsed donor will return, that a bridge gift will arrive or that a credit line will be approved on the terms you want. Anyone who suggests otherwise is selling a hope, not a plan. Be especially wary of anyone who quotes past results without explaining how they were measured or whether they apply to your situation.

Outside help also does not replace the relationship work. The person who knows the donor's history, motives and concerns is usually the executive director or the development director. The finance lead depends on that information and should say plainly when the data is weak or when the answer depends on a conversation nobody has had yet. A forecast built on guesses from the finance office will look more certain than it should.

When you talk to a prospective advisor, ask what they will own and what they will not. Good questions include who updates the model after the first delivery, who presents it to the board, and what happens when a donor's status changes mid-quarter. Work product should include the model itself, a written list of assumptions, and a short board summary. If the answers stay vague, the engagement will likely stay vague too.

Outside finance work also has to fit alongside the accountant and, where there is one, the auditor. The accountant records gifts under the applicable rules and prepares the statements. The finance lead prepares the cash view that the accountant does not normally produce. The two should talk before the board meeting so that neither presents a number that the other cannot explain. Tools matter less than inputs. A spreadsheet can do this job, and accounting systems such as QuickBooks and NetSuite can track payments and pledges. Planning tools such as Adaptive Insights can hold multiple scenarios. Choose the tool your team will keep current, because an accurate tool that nobody updates does not help.

How to run the monthly routine with development, the board and the accountant

Donor data lives in more than one place. It usually sits in the donor database, the gift log, the accounting system and the development director's notes, and each of those sources is updated by a different person at a different pace. A monthly routine keeps the forecast tied to what is actually known, and it gives every contributor a clear job.

A simple version of the routine has four parts, and the order matters because later steps depend on earlier ones:

1. Confirm which gifts arrived and reconcile them to the bank deposits.


2. Update the pledge schedules with any changes to dates, conditions or amounts.


3. Review the signals from the development team, including new conversations, silence or changed plans.


4. Refresh the loss scenario and check the result against the cash threshold.

Confidentiality needs attention. A donor's giving history and the reasons for a change are sensitive, and a forecast file can travel further than anyone intended. Limit access to the detailed model to the people who need it to make decisions. Give the board a summary that describes the risk in plain terms and names individual donors only when the board must decide something about them. Many organizations find that the summary works better than the full file for most meetings anyway.

Board packets should show the scenario in language a non-finance member can follow. Include the month of the lowest point, the cash that would cover it, the actions available and the decision the board must make before a specific date. A chart can help, but the written sentence matters more. Something like "if this donor does not pay in March, the account falls below our minimum in April, and we need to decide on a credit line by the end of February" gives the board something to act on.

Some tension is normal. Development staff may feel that a loss scenario signals failure, and the finance team may feel that its warnings are ignored until the month they come true. Frame the model as a planning tool that protects the organization and the programs it serves, not as a judgment on the development team's work. When the development director helps write the triggers, the scenario becomes a shared tool instead of an accusation.

Agree in writing on who has the final word on a donor's status. Often that person is the development director, because they hold the relationship. The finance lead documents that status in the model with a date and a short note on the source. When the status changes, the change is visible to everyone, and nobody has to guess which version of the forecast is current.

A decision test for how much your cash plan depends on one donor

This test is the practical side of how nonprofits plan for losing a major donor, and it can be run in an afternoon. Take your current forecast, remove the scheduled payments of your largest individual donor from their months, and look at the lowest cash balance across the period. Compare that balance with your agreed cash threshold. The question is not whether you will lose the donor. The question is whether the organization can absorb the loss with the tools it already has.

If the lowest balance stays above the threshold, the dependence is real but manageable with normal monitoring. Keep the monthly routine, watch for early signals and revisit the test each quarter. If the balance falls below the threshold, the plan needs a named owner, a response list and a date for the first decision before the next payment is due. Waiting until the donor has actually left is the most expensive option.

Repeat the test for the second-largest donor and for any restricted fund that pays for core costs. Two donors that each leave a moderate gap can produce a serious gap together, and that combination is easy to miss when each donor is reviewed on their own. Run the removals together in one scenario, and check whether the low points fall in the same month. If they do, part-time CFO cost in Massachusetts the risk is concentrated in a way that a single-donor view would not show.

Here is the catch: the test is only as good as its inputs. If the gift log is incomplete, if pledges are missing from the model or if renewal estimates are hidden inside the base case, the result will look safer than reality. Check the inputs against the bank statement and the signed agreements before you trust the answer. A test that passes on bad data is worse than no test, because it gives the board false confidence.

A passing result does not mean you can stop watching. Donor status changes, and a forecast that was fine last quarter can fail the next one. Put the test on the calendar as a recurring review, and record the date, the result and the person who ran it. If the test fails, the decision is not whether to hire anyone. It is what the organization will do first if the gift does not arrive, and who will make that call. That answer belongs to the board, with the finance and development leads in the room.