How to Fix Cross-Functional Handoffs So Nothing Falls Through

Two months ago, a product launch at a company I advise went sideways. Engineering finished the feature on time. Marketing had the landing page ready. But nobody told the sales team about the new pricing structure, so the sales deck still showed the old numbers. The launch went live on Tuesday. By Wednesday afternoon, two reps had quoted the wrong price to prospects.

When the CEO asked what happened, the answer from every team was the same: "I thought they had it."

Why handoffs fail

Cross-functional handoffs fail for a specific reason. The person handing off the work considers their part done. The person receiving it does not know it has arrived. In the gap between "I sent it" and "I received it," the commitment dies.

Amy Edmondson, in "Teaming: How Organizations Learn, Innovate, and Compete in the Knowledge Economy" (Jossey-Bass, 2012), describes this as a "boundary problem." Teams optimize for within-team execution and neglect between-team execution entirely.

A 2023 report from the Project Management Institute ("Pulse of the Profession 2023") found that 28% of projects fail primarily due to poor communication between teams. Cross-functional handoffs are the most common point where that communication breaks down.

The old way vs. the system way

The old way: someone finishes their part and sends a Slack message to the next team. "Hey, the API is ready for integration. Let me know if you have questions." The recipient sees the message, reacts with a thumbs-up, and adds it to their mental list. Two weeks later, someone asks why the integration is not done.

The system way: every handoff follows a standard format with five elements. The sender creates a handoff record that both parties acknowledge. The commitment transfers from one person's tracked list to another. At no point does the work exist in a gap between systems.

The five-element handoff

Every cross-functional handoff needs these five things:

1. What: specific deliverable being handed off 2. From: person completing the upstream work 3. To: single person receiving the work (not a team, a person) 4. By when: deadline for the receiving person to act 5. Context: link to the deliverable, docs, or instructions

Real example:

Handoff: What: Final API documentation for v3 auth flow From: Priya (Engineering) To: Marcus (Developer Relations) By when: March 7 (publish to docs site) Context: Google Doc link, Figma link for diagrams

The handoff is not "engineering is done with the API." It names the exact deliverable, the exact person, the exact deadline, and the exact materials Marcus needs.

The handoff acknowledgment

The handoff is not complete until the receiving person acknowledges it. This step prevents the "I thought they had it" problem.

The acknowledgment:

Acknowledged. I have what I need to start. Target completion: [date] Questions or blockers: [none / list them]

Or:

Acknowledged, but I need the following before I can start: - [Missing item 1] - [Missing item 2] Expected start date once I have these: [date]

If there is no acknowledgment within 24 hours, the sender follows up. After 48 hours, it gets escalated to both managers. This sounds rigid, but it prevents handoffs from sitting in limbo for weeks.

The handoff Slack message template

Handoff to @[person]

What: [specific deliverable] From: me ([team name]) To: @[person] ([their team name]) Deadline: [date] Context: [links]

Please acknowledge by replying with: - Confirmed, I have what I need - OR: I need [missing items] before I can start

cc: @[both managers if needed]

Post this in a shared channel (not a DM) so both teams have visibility. Handoffs that happen in DMs are invisible and cannot be tracked.

Common handoff failure modes

Handing off to a team instead of a person. "I sent it to the design team" means nobody specific owns the next step. Always name one person.

Handing off without context. Sending a deliverable without explaining what the recipient needs to do with it creates a research project for them. Two minutes of context from you saves an hour of discovery for them.

Handing off without a deadline. If the upstream team finished on time but the downstream team has no deadline, the work sits in a queue indefinitely.

The invisible re-handoff. Person A hands off to Person B, who hands off to Person C, without telling Person A. Any re-handoff must loop in the original sender.

Quick answers

Q: How do I track cross-functional handoffs without another tool? A: A shared Slack channel works for small teams. Post every handoff using the five-element format. Pin unacknowledged handoffs. Review weekly.

Q: What if the receiving person pushes back on the deadline? A: Negotiate before finalizing the handoff. The acknowledgment step is where the receiving person can counter-propose a date.

Q: How many handoffs per week should a team expect? A: Most teams of 6-10 people handle 5-15 cross-functional handoffs per week.

Q: What is the difference between a handoff and a dependency? A: A handoff is an active transfer of work. A dependency is a passive blocker. Both need tracking, but handoffs require an explicit transfer and acknowledgment.

Q: How do I handle handoffs across time zones? A: Add 24 hours to the acknowledgment window. Post during the overlap window when both parties are online.

Try this

Identify one cross-functional handoff in progress right now. It might be a design review waiting on engineering feedback, a contract waiting on legal, or a spec waiting on product sign-off. Write it out using the five-element format: what, from, to, by when, and context. Send it to the receiving person and ask for an acknowledgment. This takes about 10 minutes.

If you want a system that tracks commitments across teams with built-in ownership and reminders, take a look at Tether.