Case notes for nonprofits that work with the same people for years
Most software sold to nonprofits is built around reporting upward: how many people served, how many sessions delivered, outputs by quarter. That is a real obligation and you almost certainly have something that does it.
What those systems rarely hold is the account of one person over time. The intake form is a form. What happens afterwards — what was tried, what didn't work, what changed at home in the middle of it — is a record, and the two are hardly ever the same system. So the record ends up in somebody's notebook, a shared drive, an email thread, or the head of the caseworker who has just handed in her notice.
BeornNotes is that missing piece: one record per person, that everyone adds to.
Where this fits
Programs where the same person is worked with over months or years, usually by more than one member of staff:
- Reentry and diversion
- Refugee resettlement and immigrant services
- Workforce, employment readiness and vocational training
- Mentoring and youth transition programs
- Legal aid and immigration advocacy
- Transitional and supportive housing
- Family support and self-sufficiency programs
The common thread is not the sector. It is that someone's progress only makes sense in order, and that the person who needs to understand it next is often not the person who was there.
Where it doesn't
Worth saying plainly, because it saves everyone an afternoon.
If the work is distributing goods, running classes, putting on events, or serving members — a food program, a thrift operation, a club, an association — then a system built around one long record per person is more than you need, and something simpler will serve you better.
One record, added to by whoever was there
Notes, important dates and documents sit on the person, not in a folder somebody has to find. Every entry is stamped with who wrote it and when.
A note can be corrected, but it cannot be deleted, and an edit is marked as an edit. That means the account of someone's progress is cumulative rather than overwritten — a revised plan sits on top of the old one instead of erasing it. For work that is reviewed, funded or occasionally challenged, that is not a bookkeeping nicety; it is the point.
Underneath it, every change to every field is kept: the previous value, the new one, who made it, when — with a separate trail for each document. See the audit trail.
Your words, not ours
The fields, the tabs they sit on, and the labels on them are set in your own settings, by you, without asking us and without waiting for a release. Dropdowns are yours to define. If you decide next year that a particular fact is worth capturing on everyone, you add it that afternoon.
This matters more in this sector than most, because no two programs mean the same thing by "status", and education readiness and employment readiness are not the same shape. See customization for what that covers — it is considerably more than the three renameable text boxes most systems offer.
Finding it again
Notes are searchable across every record by their full text. "What did we agree about the housing application?" doesn't require remembering whose file it was in or which month it happened.
Who sees what
Access is set per person: full, read-only, or restricted to only the records they own — which is how volunteers and part-time staff can use the same system without seeing everyone. Individual fields can be hidden or made read-only, and two-factor authentication can be required across the organization.
What it isn't
It doesn't do your funder reporting. Whatever you use for grant reporting and outcomes, keep it. This is the layer underneath — the thing those numbers are eventually counted from.
It isn't a billing or time-recording system, and it doesn't file anything with anyone.
It is not HIPAA compliant and we sign no business associate agreements. For non-clinical work that generally doesn't matter, but you should hear it here rather than discover it in month three. If your program handles protected health information, we are not the right answer and we would rather say so now.
Getting started isn't a project
Existing records come in from a spreadsheet — the import checks your file against the rules you've set and commits all of it or none of it, so a malformed row can't leave you half-migrated. See importing data.
Setup is an afternoon: name your record type, set your fields, decide who sees what, bring in what you have. If you're coming from a shared drive and a master spreadsheet, that transition is its own page.
There's a 14-day trial and no card required to start. Nothing charges when it ends — the account simply pauses.
Questions before you start? Support is handled by our own people in the US — not AI agents, and not an outsourced help desk. Whoever answers knows the product. We record the help videos ourselves too.