You didn’t take this job to spend your afternoons filling out forms.
You took it because the work matters. Because the people you serve deserve someone in their corner. If you are honest about how your days actually look, a significant portion of your time goes to things that have nothing to do with why you showed up. Timesheets. Case notes. Progress reports. Data entry. Email after email. All of it is part of the job, and all of it pulls you away from the people.
This is the third in a four-part series on what a People-First approach to AI means across nonprofit organizations. Parts 1 and 2 addressed board governance and executive leadership. This one is for you.
What You’re Carrying
Burnout in the nonprofit sector is not a personal failing. It is a structural reality. The people drawn to this work tend to be deeply committed, which means they often give more than is sustainable. Add the emotional weight of working alongside people in crisis, the administrative demands that multiply every year, and a funding environment that rarely allows organizations to hire at the level the work actually requires, and you have a recipe for exhaustion that resilience alone will not fix.
If you are feeling stretched thin, you are not alone. You are working in a system that asks a great deal of the people closest to the mission.
What You’re Hearing About AI
The headlines are not reassuring. Job losses. Automation replacing workers. Entire industries being disrupted. Those concerns are real, and dismissing them would not be honest.
Nonprofit organizations exist to serve people. The relationships your programs depend on, the trust you have built with the individuals and communities you work alongside, the judgment and compassion you bring to situations that are rarely simple, none of that can be automated. AI cannot do it. It was never designed to.
What AI can do is handle the parts of your job that don’t require you. The first draft of a report. A summary of a long document. Routine data entry. The email you have written twelve times with slightly different details. That is where the real opportunity sits.
How Staff Are Using AI Right Now
Whether or not your organization has a policy, some of your colleagues are already using AI tools on their own. A case manager drafting monthly reports in half the time. A program coordinator summarizing meeting notes. A development associate getting a head start on grant narratives. These uses are largely helpful, but they are happening without guidance or guardrails.
Other uses are more concerning. When staff paste client information into a public AI tool to write a case note, that data does not stay private. When someone uploads financial or personnel records to get help analyzing them, they may be sharing confidential information with a third-party system that retains it. These are not hypothetical risks. They are happening right now in organizations that have not yet had a clear conversation about how AI should and should not be used.
Some staff have avoided AI entirely, out of principle, uncertainty, or because no one has shown them how it might actually help. That is understandable, but it also means missing tools that could make a genuinely difficult job more manageable.
What You Should Expect from Your Organization
If your organization is implementing AI, you have every right to ask: What tools are we using, and why were they chosen? How is client data being protected? Will I receive real training with time to practice and ask questions? Is there a clear policy for what I should and should not use AI for in my work?
Those are the right questions. If your organization is approaching AI in a People-First way, leadership should be able to answer them clearly.
Part 4 focuses on the people at the very center of this conversation: the individuals and communities your organization exists to serve.