Home / AI for Nonprofits / Nonprofit technology and AI readiness assessment
Nonprofit technology and AI readiness assessment
Direct answer. A nonprofit technology assessment is a working review of the systems, data, workflows, people, and privacy gates you already have. I use it to rank what to pilot, what to leave alone, and what has to be true before any tool sees client information. It is not an IT audit and it is not a rip-and-replace plan.
Written by Justin Ingram, healthcare AI consultant. Reviewed November 9, 2026.
Administrative and operational AI only. Not a clinical tool. A person reviews the work.
What the assessment covers
I look at five layers: the tools you pay for, the data those tools actually hold, the steps staff repeat, the people who approve exceptions, and the agreements that cover client information. A screenshot of a vendor demo is not one of those layers.
The session is for program, data, and operations leads. I want the person who rebuilds the quarterly report and the person who gets the after-hours intake calls. If only the executive attends, the map will be wrong.
The five areas I score
Intake and referral flow: where a person enters, which form they touch, and who owns the next step. Case and record quality: missing fields, duplicate people, and notes that cannot be found. Reporting load: which numbers are rebuilt by hand. Staff skills: who already uses an AI tool on personal accounts. Vendor posture: which agreements exist and which tools see client information with none.
Each area gets a plain note: ready for a small pilot, needs a cleanup first, or leave it alone. I do not publish a numeric score on this page.
Why multi-site groups drift
A second site often copies the form and then changes three fields. A third site keeps a spreadsheet because the case system was slow on a Friday. Six months later leadership asks for one number and gets three definitions. The assessment names those forks before anyone buys another login.
From assessment to a roadmap
The roadmap is a sequence, not a wish list. Quick cleanup that staff can do without a vendor. One pilot with a named reviewer. Work that should wait because the data is not trustworthy yet. I link the booking path on the assessment form. I do not use the bare phrase as the title of this page, because that generic search belongs on the existing assessment URL.
Digital change here means using what you already pay for before you replace it. A new case system is a later decision, and it has its own selection page.
Change management for field staff
Program directors will ignore a tool that adds a step without removing one. I write the pilot so the reviewer can say what got easier and what got worse. If the field team cannot name the benefit in a week of real use, we stop.
What you receive, and what you do not
You get a written map of the current workflow, a ranked list, the privacy checks that block a pilot, and the name of the owner. You do not get a software license, a grant, a clinical protocol, or a promise that a funder will accept a new process.
Cost and time are scoped on the call. I will not print a fee on this page. If the first workflow is not real, I would rather decline than invent a package.
How the assessment runs
- You send the systems list and one painful report before the call. I read them. I do not need client records.
- On the call we walk one intake and one report. You correct me when the steps are wrong.
- I write the ranked list and the stop conditions. You mark what is in scope.
- We pick one pilot or we stop. A person on your team is named as the reviewer before any tool is connected.
Checklist you can use this week
- List every system that stores a client or a service.
- Circle the report someone rebuilds by hand.
- Ask who pastes notes into a personal AI account.
- Find which vendors have a signed agreement and which do not.
- Name one workflow you will not automate yet.
Hypothetical: three sites, one intake form
An operations lead thinks every site uses the same intake. On the call, site two still faxes a paper form into a shared inbox, and site three keeps eligibility in a spreadsheet. The assessment records those three paths and ranks a single queue as the first pilot. The spreadsheet is not declared a success story. It is a risk to clean up. This is an illustration, not a client.
What this is not
This page is not the generic assessment product, not an IT security audit, and not a recommendation to replace your case system first.
Questions people ask
What is a nonprofit technology assessment?
It is a scoped review of the systems, data, workflows, people, and privacy gates you already have, written so you can sequence work. I rank a pilot, a cleanup, and a leave-alone list. It is not a software catalog and it is not a score you can post to a funder as proof of readiness.
How is an AI readiness check different from an IT audit?
An IT audit usually asks whether accounts, backups, and devices are controlled. This review asks whether a workflow is ready for an assistant to draft or route work, and whether a person can review it. Both can matter. I do not replace your security assessor.
Do we need to replace our case management system first?
Usually no. I want to see whether the current system can hold a clean queue. Replacement is a selection project, and it has its own page. Starting with a new database because a demo looked modern is how teams pause the work they already owe.
Who from our team needs to be involved?
The person who owns the painful queue, someone who touches the data, and a leader who can say stop. A vendor should not be the only voice in the room. If clinical judgment is in the workflow, your clinical lead listens. I still do not make clinical decisions.
What does the assessment deliver at the end?
A written map, a ranked list, the privacy gates, and a named reviewer for any pilot. It does not deliver a tool, a grant narrative, or a compliance certificate. You decide whether the first pilot is worth booking.

