How Do You Stop Work From Getting Lost Between Teams?

Stop work from getting lost between teams by defining what is ready to transfer, who receives it, and how both sides know responsibility has changed. Sending a message is not the same as completing a handoff. A reliable process also explains what happens when information is missing or the receiving team cannot act.

For a nonprofit program manager coordinating with operations staff, the goal is not more tracking. It is one shared understanding of where work stands and who needs to move it next.

Follow one item across the boundary

Choose a recent request that stalled. Ask the sending and receiving staff to describe what happened, using the working record rather than memory alone. Look for the moment when each person believed someone else owned the next step.

Approach this as a process review, not a search for someone to blame. Teams may use the same word, such as "complete," to mean different things. One may mean the form was submitted; another may mean it was reviewed and accepted.

Map the steps from the original request to the next meaningful action. Include any informal messages or personal reminders that keep the process moving today.

Agree on a small handoff standard

Define the minimum information the receiver needs, where it belongs, and who checks it. Keep the standard proportionate to the work. A routine room booking should not need the same review as a complex service referral.

Handoff question	Agreement to make
Is it ready?	Required information and any approval are present
Where does it go?	One designated queue or working record
Who receives it?	A named role, with backup coverage
Has it been accepted?	A visible status or acknowledgment
What if it cannot proceed?	A reason, an owner, and a route to resolve it

Agree on a realistic response expectation rather than leaving "soon" undefined. Include urgent exceptions and absence coverage, without requiring every routine item to become urgent.

Test a normal case and an incomplete case

In a hypothetical example, frontline staff send participation records to an operations coordinator for a monthly summary. Records frequently come back because staff use different definitions for a completed session.

The team agrees on the definition, adds a brief completion check, and uses a shared status to show whether a record is ready for review. They also decide who answers questions about exceptions. The improvement is not a new software feature; it is a shared rule attached to an existing workflow.

Test both a complete record and one with missing information. Can staff tell who owns the next action in each situation? Avoid putting unnecessary personal or confidential details into shared messages just to demonstrate that the handoff happened.

Make workload visible without duplicating records

Use the system the team already relies on when it can support the agreed process. The sender and receiver need enough visibility to avoid duplicate work, but they do not necessarily need access to every detail.

Review a small sample of handoffs together. Look for items waiting without an owner, repeated returns for the same missing information, and work that advances only after a personal reminder. Those are specific signals to investigate, not automatic evidence that someone is underperforming.

Start with one boundary

Pick the handoff that creates the most repeated clarification this week. Write its readiness rule, receiver, acknowledgment, and exception route on one page. Test the agreement before applying it to other teams.

When the difficulty is deciding who owns the work in the first place, use the small-team ownership mapping exercise. When ownership is clear but work still waits, investigate the workflow bottleneck around that boundary.

---

P.S. Your operations and your finances are connected. Here's a check to help you explore that connection. Take the Operations & Funds Check