Your donor relationships are an asset. They are not on any balance sheet.
Best fit: board governance, nonprofit finance, leadership and strategy audiences
A nonprofit's balance sheet records cash, investments, property and pledges receivable. It does not record the thing that produces most of the future income, which is the set of relationships the organisation holds with the people who fund it.
That is defensible accounting. It is a poor way to run an organisation, because things that are not measured are not protected, and relationship capital depreciates quietly.
What the asset consists of
It is not the donor list. A list of names and giving history is easy to replace and largely reconstructible from records.
The asset is the context around each name. Why this person gives. What they care about specifically, which is usually narrower than your mission statement. Who introduced them. What has gone wrong before. What they were promised. Who on your staff they actually trust.
That context is what converts a name into a relationship, and it is what makes the difference between an appeal that lands and one that reads as a mailing.
Almost none of it is recorded in a form that survives the departure of the person holding it.
How it depreciates
Three mechanisms, running constantly.
Staff turnover. The obvious one. Development roles turn over at a normal professional rate, and each departure takes a portfolio's worth of context. The organisation notices the vacancy and does not notice the loss, because the loss has no line item.
Attrition of detail. Even without turnover, context decays. The reason behind a decision made four years ago is fuzzy at two years and gone at five, unless somebody wrote down not just what happened but why.
System changes. Every CRM migration, every platform consolidation, is an opportunity for the unstructured half of the record to be dropped. Notes fields transfer inconsistently. Attachments frequently do not. The structured data survives because it fits a column, and the context does not because it never did.
We looked at the compounding effect of these three in a piece on institutional memory loss in nonprofits.
Why the notes field is not the answer
Most organisations believe they have solved this, because their CRM has a notes field and people use it.
Notes fields have two properties that limit them severely. They are unstructured, so a decade of them becomes an undifferentiated block of text nobody reads before a meeting. And they are per-record, so anything spanning two donors, a donor and a board member, a donor and a programme, has no natural home.
The information that matters most is precisely the relational kind. This person is the reason that person gives. This grant was declined because of a decision made in a different programme. That is a network, and a notes field is a list.
That structural mismatch is why the problem persists in organisations that are genuinely diligent about record-keeping. The discipline is fine. The container is wrong. It is the reason knowledge graphs for institutional memory have become a serious topic in this sector rather than an academic one.
What a board can do about it
You cannot put relationship capital on a balance sheet. You can govern it.
Ask the continuity question annually. If our development director left next month, what would we lose that is not written down? Ask it in the meeting, out loud, and record the answer.
Treat departures as data events. A resignation should trigger a structured capture process, not just a handover meeting. It will be imperfect under time pressure, and imperfect is far better than nothing.
Fund the capture, not just the campaign. Recording context takes staff time that produces no measurable result this year. That is exactly the kind of spending that loses budget arguments, and exactly the kind that determines what the organisation is worth in five years.
Ask what happens to notes in any system change. Before a migration is approved, ask specifically about unstructured data. The answer is often that nobody had considered it.
The framing that works with boards
Boards understand deferred maintenance. A building that is not maintained looks fine for years and then costs a great deal all at once.
Relationship capital behaves the same way. The organisation performs normally right up until several key people leave in the same eighteen months, at which point the cost arrives in full and nobody can point to the year it was incurred.
It was incurred every year. It just was not on the statement.
More on the subjects above
Gratefully is an AI intelligence layer for nonprofit fundraising teams. It works alongside your existing CRM rather than replacing it.
Comments