# 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.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-11-15
- Updated: 2026-11-16
- Source: https://aiadvisoryboard.me/blog/waiting-on-list-department-handoffs-cross-functional-blockers

When work stops moving between departments, founders usually hear about it too late. The sales team says the deal is ready for implementation. Implementation says they never received the handoff. Customer success starts onboarding a client who hasn't been properly briefed.

I see this pattern in companies of 30 to 500 employees: the work isn't stuck inside a team. It's stuck in the white space between teams.

## TL;DR
- A waiting-on list is a shared record of items one department needs from another before work can continue.
- It makes cross-functional handoffs visible instead of relying on memory and follow-up emails.
- It belongs to the receiving team, not the sender.

### Definition: Waiting-on list
A waiting-on list is a simple register of deliverables that are blocked because another team hasn't completed their part. Each entry shows who owns the item, what is needed, who owes it, and when it was promised.

### Definition: Cross-functional handoff
A handoff is the moment responsibility for a task or deliverable moves from one department to another. Most operational delays happen at this boundary, not inside a single team.

## Why Handoffs Disappear Without a Waiting-On List
In a small company, handoffs happen in Slack messages, hallway conversations, or emails that get buried. As the team grows past 30 people, nobody can remember who promised what to whom.

The typical failure mode looks like this:

1. Sales closes a deal and emails operations.
2. Operations assumes the client brief is incomplete and waits.
3. Sales assumes operations has started.
4. Two weeks later, the founder asks why implementation hasn't begun.

Nobody lied. Nobody was negligent. The handoff simply had no owner and no record.

## What Goes on a Waiting-On List
A waiting-on list is not a project plan. It is a narrow log of items currently paused because another department owes something.

Each entry should include:

- Item or deliverable name
- Receiving department (who is waiting)
- Sending department (who owes the item)
- Date requested
- Promised delivery date
- Current status (pending, partially delivered, overdue)
- Impact if delayed (client deadline, internal milestone, revenue risk)

## Copy/Paste Template

```markdown
# Waiting-On List — [Week of]

| # | Item | Waiting Team | Owning Team | Requested | Promised | Status | Impact |
|---|------|--------------|-------------|-----------|----------|--------|--------|
| 1 | Client onboarding brief — Acme Corp | Customer Success | Sales | May 5 | May 8 | Pending | Go-live date at risk |
| 2 | Technical specification — Project B | Engineering | Product | May 6 | May 12 | Partial | Sprint start delayed |
| 3 | Signed vendor contract — Supplier X | Procurement | Legal | May 4 | May 7 | Overdue | Price hold expires May 10 |
```

Review it once a week. Anything older than five business days moves to the founder's or COO's desk for escalation.

## Good vs Bad Waiting-On Entries

Bad:

- "Waiting on sales."
- "Client stuff."
- "ASAP"

Good:

- "Waiting on Sales for signed SOW and client contact list. Promised May 8. Needed by May 10 to schedule kickoff."
- "Waiting on Product for API documentation. Partial delivery May 6. Full spec needed May 12 or sprint slips."

## Manager Scan (2-Minute Digest Example)

A founder or COO can scan the waiting-on list in under two minutes and know exactly where work is stuck:

- Three items waiting on Sales, total value $120K in pending implementations.
- One item waiting on Legal for nine days — vendor price protection expires tomorrow.
- Two items waiting on Engineering, both marked partial delivery with no updated promise date.
- Zero items waiting on Customer Success — their queue is clear.

This is Plan → Fact → Gap in its simplest form. The plan said implementation would start this week. The fact is three handoffs are incomplete. The gap is visible without calling a status meeting.

> **Tool tip (AiAdvisoryBoard.me):** A waiting-on list works best when it is part of a daily operating rhythm, not a standalone document. In our 7-day diagnostic, we map exactly these cross-functional gaps so you see Plan → Fact → Gap across your company before you buy any AI subscriptions.

## Micro-Case (What Changes After 7–14 Days)

A professional services firm of about 90 people kept missing client delivery dates. Sales, delivery, and billing each blamed the others. The founder introduced a waiting-on list reviewed every Monday.

Within two weeks, the team found that half of their delays were not caused by slow work inside departments. They were caused by handoffs that nobody had confirmed as received. The delivery team started acknowledging handoffs within 24 hours. The founder stopped discovering delays from angry clients and started seeing them on the list first.

> **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

**Who owns the waiting-on list?**
The receiving team owns it. They are the ones waiting, so they are responsible for logging the item and updating its status.

**How often should it be reviewed?**
Once a week is enough for most companies. Teams with high handoff volume may review it twice weekly.

**Does this replace project management software?**
No. It complements it by capturing the cross-functional gaps that project tools usually miss — the space between teams where accountability gets fuzzy.

**What if the owning team ignores the list?**
That is a leadership issue, not a tool issue. The founder or COO reviews overdue items and decides whether to escalate, re-promise, or drop the item.

A waiting-on list costs nothing to start and takes minutes to maintain. The return is that work stops disappearing between departments.

Start this week: pick the three handoffs that cause the most friction in your company, put them on a shared list, and review it every Monday until the pattern breaks.

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

---

When citing, link to https://aiadvisoryboard.me/blog/waiting-on-list-department-handoffs-cross-functional-blockers. More articles: https://aiadvisoryboard.me/blog
