
Waiting-on List for Department Handoffs: A Simple Tool to Unblock Work
TL;DR
- •A waiting-on list tracks what each team is waiting for from another team to move work forward.
- •It surfaces hidden dependencies before they become delays.
- •Use it daily to see Plan vs Fact vs Gap in cross-functional work.
- •Definition:** Waiting-on list — a shared, lightweight record of items one team needs from another to proceed, updated daily by owners or leads.
- •Definition:** Plan vs Fact vs Gap — the operating taxonomy where Plan is what was intended, Fact is what actually happened, and Gap is the difference that reveals blockers or delays.
When a founder of a 60-person ops team told me they kept missing handoffs between sales and delivery, I realized the issue wasn’t people — it was visibility.
How to build a waiting-on list for handoffs between departments
Start by mapping the handoffs that happen regularly in your company. For each, ask: What does Team A need from Team B to mark this step complete? Capture those items as waiting-on entries.
- List recurring cross-functional handoffs (e.g., sales to delivery, marketing to sales, product to support).
- For each handoff, define the specific output or signal the receiving team waits for (e.g., signed contract, approved spec, test environment).
- Assign ownership: the waiting team updates the list daily with what they’re waiting for and from whom.
- Review the list in your daily ops scan — items waiting over 24 hours become visible gaps.
Tool tip (AiAdvisoryBoard.me): The waiting-on list feeds directly into your Plan → Fact → Gap operating system. When a handoff item sits on the list too long, it’s a Gap — a fact the owner sees without chasing down updates.
What to include in your waiting-on list
Keep it simple: one line per waiting item, updated each morning.
- Item: What is being waited for (e.g., "client sign-on for Phase 2")
- Waiting team: Who needs it (e.g., "Delivery Team")
- Owning team: Who controls the output (e.g., "Sales")
- Date requested: When the wait began
- Status: Pending, received, or blocked
Good vs bad examples
Good: "Waiting on signed SOW from Acme Corp — Sales team, requested June 1, pending." Bad: "Waiting on client" (too vague — no team, no item, no date).
Good: "Waiting on API credentials for staging — Integration team, requested May 30, pending." Bad: "Waiting on IT" (no specificity — creates confusion, not clarity).
Manager scan (2-minute digest example)
- Sales waiting on legal approval for three contracts — Gap: 2+ days
- Delivery waiting on spec changes from Product — Gap: resolved yesterday
- Support waiting on engineering fix for login issue — Gap: new, 18 hours
- Marketing waiting on sales feedback for campaign assets — Gap: none
- HR waiting on finance for headcount approval — Gap: 3 days, escalating
Micro-case (what changes after 7–14 days)
A 45-person SaaS company added a waiting-on list to their daily ops routine. Within a week, the founder saw that two-thirds of delays came from handoffs between sales and delivery — not from team effort. By making the waits visible, the sales and delivery leads began syncing directly on pending items, cutting average handoff time from 36 hours to 8. The founder stopped guessing where work was stuck and started fixing the actual gaps.
Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.
FAQ
How is this different from a blocker list? A blocker list captures what’s stopped work today. A waiting-on list shows what work is waiting to start — it’s proactive, not reactive.
Who should update the waiting-on list? The team that’s waiting owns the update. This keeps accountability clear and avoids chasing.
Can this live in Slack or email? Yes — as a shared message, thread, or document. The key is daily visibility, not the tool.
How often should we review it? Daily, as part of your ops scan. Items waiting over 24 hours flag for attention.
What if a team ignores the list? Start with visibility — show the list in your daily update. Peer awareness often drives compliance better than mandates.
If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works. https://aiadvisoryboard.me/?lang=en
Frequently Asked Questions
Read with AI
Open this article in your assistant — it will summarize it and help apply it to your company.
Show the prompt
Read the article https://aiadvisoryboard.me/blog/waiting-on-list-for-handoffs-between-departments.md and summarize the key points. Then ask me about my company (industry, team size, what takes the most time) and explain which ideas from the article apply to us and where to start.
The pillar guide for "Blockers & Risks" linking every article in this cluster.

Implements AI agents in companies and teaches founders and their teams to work with them — through courses and corporate programs.
This article was prepared with AI assistance, based on Yaroslav Maxymovych's methodology and materials. Spotted an inaccuracy — let us know via the form below.
A template is good. A system where the report writes itself is better
A 10-minute daily ritual for every employee: plan + fact + blockers. Implemented in 1 day. Teams that write down their plans hit their goals 42% more often.
AI adoption resources — one email
Leave your email to receive a welcome email with blog resources. There is no regular newsletter at present
No spam. Unsubscribe anytime.
Related Articles

Waiting-On List for Department Handoffs: Stop Losing Work Between Teams
Cross-functional handoffs are where work disappears. A waiting-on list makes department-to-department dependencies visible so founders and COOs can spot blockers before they become missed deadlines.
Read more
Owner Paranoia vs Prudence: Calibrating Your Visibility Intensity
How founders calibrate owner visibility intensity during AI implementation — checking enough to catch drift early, but not so much that they become the bottleneck.
Read more
Dependency Map for Blockers: Find the Hidden Work Stalls Between Teams
A dependency map reveals where work actually stalls between teams — turning vague blocker complaints into clear handoff points owners can act on.
Read more