Nonprofit AI readiness
AI readiness assessment vs. AI strategy: what should a nonprofit do first?
Learn whether your nonprofit should assess AI readiness, set immediate guardrails, or develop an AI strategy first, with a practical sequence for overwhelmed leaders.
Should a nonprofit assess AI readiness or create an AI strategy first?
Most nonprofits should assess readiness before writing a full AI strategy. The assessment shows where AI could create value, whether the organization has the information, ownership, safeguards, and staff capacity to support it, and what must be fixed first. The strategy then turns those findings into priorities, boundaries, investments, and a sequence of work.
There is one important exception. If staff are already using AI with donor, client, financial, personnel, or other sensitive information, put interim guardrails and practical staff guidance in place now. Readiness work can continue at the same time. A nonprofit should not wait for a polished strategy document before addressing an active risk.
The three activities solve different problems
An assessment, an interim policy, and a strategy are related, but they are not interchangeable. The right sequence depends on what is already happening inside the organization.
| Activity | Question it answers | Use it when |
|---|---|---|
| AI readiness assessment | Are we prepared, and what should we do first? | Leaders see possible uses but need evidence about value, risk, data, workflow, ownership, and staff capacity. |
| Interim AI policy and guidance | What may staff do safely right now? | People are already experimenting and need clear rules for approved tools, sensitive information, review, and escalation. |
| AI strategy | Where are we going, and how will we invest? | Leadership has enough readiness evidence to choose priorities, governance, measures, budget, and an implementation sequence. |
What should a nonprofit AI readiness assessment include?
A useful assessment is not a personality quiz or a score based on how many tools the organization owns. It examines whether a specific use can work responsibly inside the organization as it exists today.
- Mission value: the result the organization needs and who benefits
- Workflow clarity: the trigger, steps, decisions, handoffs, and human reviewer
- Information readiness: where source material lives, who can access it, and whether it is reliable
- Risk and governance: privacy, accuracy, bias, approval, documentation, and escalation requirements
- People and ownership: who will test, review, maintain, and improve the work
- Technology fit: whether approved systems can support the use without creating another disconnected tool
- Measurement: time returned, quality, errors, staff experience, and mission value
A practical order for an overwhelmed executive director
Start with one recurring problem, not the entire organization. Choose work that is time-consuming, reasonably repeatable, low enough in risk to review safely, and important enough that improvement would matter.
Next, document the current workflow and identify the information it uses. Put minimum guardrails in place. Test the smallest useful change with a named owner and human reviewer. Measure what happened. Only then decide whether that use belongs in a broader AI strategy.
- Name one operational problem in plain language
- Confirm what staff are already doing with AI
- Set immediate boundaries for sensitive information and human review
- Assess the workflow, data, risk, ownership, and adoption conditions
- Pilot one bounded use and measure the result
- Build the strategy from evidence rather than pressure or hype
What the readiness assessment should produce
The output should be a decision leaders can explain. That may be build, prepare, or pause. A build recommendation names a bounded use, owner, safeguards, success measures, and next step. A prepare recommendation names the process, information, role, or policy gap that comes first. A pause recommendation explains why the risk or effort currently outweighs the value.
LUR Growth’s Capacity Diagnostic takes 2 to 3 weeks and includes an executive conversation, a current-state review, a capacity and cost baseline, and board-ready findings. It is designed to identify practical opportunities, risks, governance needs, and a prioritized next move. It does not assume that every organization should buy software or begin a larger implementation.
The short answer
Assess first, set urgent guardrails in parallel when staff are already using AI, and write the strategy after leadership has real evidence. That sequence gives an overwhelmed team a responsible first move without turning AI planning into another abstract project.
Questions nonprofit leaders ask
Can a nonprofit create an AI policy before an AI strategy?
Yes. A short interim policy can establish approved tools, prohibited information, human review, and escalation while the organization assesses readiness and develops a broader strategy.
How long should an AI readiness assessment take?
A focused assessment can often be completed in a few weeks when leadership can name the workflows, people, systems, and risks involved. A larger enterprise review may take longer because more teams and use cases must be examined.
Do we need to choose an AI tool before the assessment?
No. Start with the operational problem and the information, risk, ownership, and review requirements. Tool selection should follow those requirements.
What if our staff are already using ChatGPT or another AI tool?
Do not wait for a full strategy. Establish interim guidance, identify current uses, stop unsafe data practices, and assess which uses should be approved, changed, or discontinued.
Sources and further reading
Put the insight to work