What Fragile Handoffs Look Like in a Small Nonprofit

You finish your part, send it on, and assume it will keep moving.

Then it sits.

An email stays unread. A spreadsheet is waiting for one more number. A message gives some context, but not quite enough for the next person to act. Nobody is ignoring the work, but nobody is clearly picking it up either.

That is a familiar pattern in small nonprofits. The task itself may be fairly straightforward. The slowdown happens when the work moves from one person to another.

That usually does not mean the team is careless or disorganised. More often, the handoff is weak. The process depends on memory, inboxes, informal follow-up, and staff filling the gaps as they go.

When work slows down between people, not within the task

You can often spot this when the work seems fine until it needs to move.

One person finishes their part. After that, progress becomes less clear.

Maybe the next step is assumed rather than stated. Maybe the information exists, but it is scattered across email, chat, a spreadsheet, and a verbal update from yesterday. Maybe nobody is exactly stuck, but nobody is actively moving it on.

This often shows up in small ways:

• updates sitting in inboxes waiting to be noticed
• next steps being implied rather than assigned
• people waiting without realising they are waiting
• follow-up only happening after someone checks or reminds
• a task being “nearly done” for days because one final transfer never quite happens

Take a grant application. Programme staff provide the content, finance signs off the numbers, and someone sends the final version. If nobody is fully sure who confirms it is complete, who sends it, or where the final version lives, the application can stay half-finished even when everyone involved is trying to help.

The issue is often not effort. It is how the work passes from one pair of hands to another.

What fragile handoffs usually look like day to day

Fragile handoffs often look ordinary.

There may not be a dramatic failure. More often, there is a steady pattern of small delays, clarifications, and rescue work.

A new client enquiry comes in. The first person forwards the email to whoever needs to act and adds a quick note. The next person is in meetings, the email drops down their inbox, and they are not quite sure whether they should reply straight away, log it somewhere, or wait for more information. Follow-up becomes uneven.

Or month-end reporting depends on several people sending updates and figures. There is a spreadsheet, but not everyone uses the same format. Some updates arrive by email. Some come up in meetings. One person ends up pulling everything together, checking what is missing, asking for clarifications, and rebuilding the picture manually.

This is often where the hidden work sits.

In many small nonprofits, the handoff is the part nobody has really designed, but everyone is working around. The process might say “finance reviews” or “manager approves” or “operations follows up.” What it does not show is the checking, clarifying, chasing, and gap-filling in between.

Day to day, that often means:

• nobody is fully sure who owns the next step
• the trigger for the next step changes from case to case
• the next person has to piece together what is going on
• status is hard to see without asking around
• progress depends on someone remembering to nudge it along

When that becomes normal, work stalls between people even if each individual task seems manageable.

What may actually be going wrong at the handoff point

A weak handoff is usually a process problem, not a personality problem.

The handoff becomes fragile when there is no clear trigger for the next step, no shared understanding of what “ready” means, and no reliable place to see status.

For example, a programme manager may think finance will review a budget once the latest draft is emailed over. Finance may think review starts only after certain figures are confirmed and the template is complete. Both people are being reasonable. The problem is that the start point is unclear.

The same goes for ownership. If a task moves forward only when someone notices it, that is not a dependable flow. If the next person only becomes aware through a forwarded message, a verbal mention, or a line in a meeting, the process is relying more on attention and staff memory than on a clear handoff.

It helps to separate this from occasional mistakes.

People miss things sometimes. That is normal. But if the same delay keeps happening in the same place, it is less likely to be a one-off error and more likely that the process is asking people to compensate for unclear ownership, inconsistent triggers, scattered information, or poor visibility.

If that sounds familiar, this related piece may help: Why teams keep chasing updates.

How to tell whether this is a handoff problem, a capacity problem, or both

This can be hard to untangle in a small team because both can be true.

A capacity problem usually looks like this: the next step is clear, the owner is clear, and the information is available, but the work still takes longer because there is simply too much to do.

A handoff problem looks different. The delay tends to show up as waiting, ambiguity, repeated checking, or rework between steps.

A few simple tests can help.

If work moves mainly because one person manually checks what is happening, reminds others, interprets what the next step should be, or pieces together missing context, the handoff is probably part of the issue.

If the delay happens before the next person has clearly taken ownership, that points to a weak handoff.

If the work keeps bouncing back for missing information, unclear status, or format differences, that also suggests the transfer between steps is weak.

By contrast, if everyone knows exactly what to do next and the work still sits because there is not enough time to do it, that is more of a straight capacity issue.

In practice, small nonprofits often have both. But weak handoffs can create extra admin that makes capacity look worse than it is. If staff are spending time chasing, checking, reconciling, re-entering, and manually updating, that hidden effort is taking time away from the actual work.

This is where When ‘we just need to be more organised’ is the wrong diagnosis can be useful too.

A simple way to review one handoff

You do not need to map your whole organisation to make this useful.

Start with one recurring process where work often stalls. That might be approvals, reporting inputs, onboarding, grant submissions, or service follow-up.

Then look at just one handoff point.

Focus on the moment where one person finishes and someone else is meant to begin. Ask:

• Who completes the current step?
• What exactly signals that the next step should start?
• What information does the next person need?
• Where does that information actually live?
• How does the next person know they now own it?
• How can someone see the current status without asking around?

Keep it simple. The point is not to create a polished process map. It is to make the handoff visible.

As you review it, look for a few common weak spots:

• no clear trigger to start the next step
• no agreed definition of what “ready” looks like
• duplicate tracking across email, spreadsheets, or notes
• key information arriving in fragments
• hidden checking or chasing work that someone quietly does every time

Even this basic review can tell you a lot. It can show whether the problem is really inside the task, or whether it sits in the gap between people.