Site icon Kevin Waites Consulting Services

Digital shovelling: the admin work burning out nonprofit managers

Most of the burnt-out nonprofit managers I meet in Calgary still believe in the mission. What wears them down is the manual admin work that fills their week, the shovel they pick up every morning.

In my work across the sector here, I keep seeing the same pattern drain the energy out of strong teams. I call it digital shovelling. It’s the work of moving data by hand from an email into a spreadsheet, from that spreadsheet into a CRM, and then from the CRM into a board report. It’s repetitive and low value, and every piece of it has to be carried by a person, one step at a time.

What digital shovelling looks like

In a linear workflow, a person is the glue between your systems, which makes that person the bottleneck. If a donor changes their corporate affiliation, someone has to remember to update three different records in your CRM. If a grant deadline moves, someone has to update the project tracker by hand. Miss one, and your systems quietly stop agreeing with each other.

All of that adds up to a lot of administrative drag. We have brilliant people in this city, program leads and gift officers, who spend as much as 30% of their mental energy acting as manual bridges between systems. It’s a way of working from before our tools could talk to each other, and plenty of teams still run on it in 2026. That’s energy that should be going into donor relationships and program work.

What a parallel workflow looks like

The move to AI agents is a move from linear work to parallel work. Your role shifts from moving data yourself to directing the agents that move it for you.

Picture a workflow where:

  1. An AI agent watches your incoming email.
  2. It notices that a donor’s relationship with you has changed and updates the CRM on its own.
  3. It checks that change against your moves management plan.
  4. It gives you a drafted follow-up task and a short brief on why the change matters.

The shovelling happens in the background, at machine speed. You spend your time on strategy and on the human relationships that actually move your mission forward. Your job becomes directing the work and checking it.

Anything that goes out to a donor should still get a person’s approval, and the relationship itself stays with your staff.

How to find the shovelling in your organization

Before you buy anything, find the places where your team is acting as a manual bridge. Here’s how I’d go about it:

  1. Follow one piece of data. Pick something common, like a new donation or a change of address. Trace every place it gets typed, from the first email to the last report.
  2. Count the hand-offs. Every time a person copies something from one system to another, mark it. Note who does it and roughly how long it takes each week.
  3. Ask staff about their Mondays. If people spend the start of the week cleaning up data, ask what they’re cleaning and where it came from. They’ll know exactly which steps they dread.
  4. Pick the step that happens most. Skip the hardest workflow for now. Start with the hand-off that happens most often and follows the same pattern every time.
  5. Replace that one step. That might be a direct integration between two systems, or an agent that makes the update and tells you what it changed. Keep a person reviewing anything that goes out to a donor.
  6. Check the result after a month. Make sure the step actually went away and didn’t move to someone else’s desk. Then move on to the next one.

For leaders: redesign the workflow before you buy a tool

If your staff spend their Mondays cleaning up data, that time is going into the software instead of the mission. To get to the frontier, redesign the workflow so the manual steps go away.

A new tool can come later. Start by finding where your team is acting as the bridge between systems, and replace that step with something that runs on its own.

A few questions for your next leadership meeting:

Then pick one place where the shovelling happens and map it this week, using the steps above.

Exit mobile version